Thanks, Bouiaw. There are a couple of items I can probably already
contribute. For example, I think in another version of the code, I had
fixed the issues with broken tiles and the DragPan problems (which I
mention in the demos). I will look to try to find the fixes and then
commit these (if I am able to find them).
As far as your questions below:
I will take a look at the OpenStreetMap.js file and see if I think
there is anything to prevent the conversion to AS3.
It is my belief that you should be able to easily use pure AS3 classes
instead of the Flex components (substituting a Sprite for Canvas and
Bitmap for Image, etc.). I don't think there was anything Flex based
that was necessary.
Sorry about all of warnings for missing type definitions. I was under
a bit of a time crunch when I did this and didn't add these when I
converted from OpenLayers code.
About creating explicit object types... I had worked a little with gwt-
openlayers - which is a wrapper of OpenLayers in Google Web Toolkit
(written in Java). What they did was create their own objects. For
example, the Options object which I pass into the Map as a parameter
could be a MapOptions object which you create. The MapOptions class
could have get/set functions for setting the various options the Map
has available. I'm not positive how much work this would add
throughout all of the code base, but it is one option.
Hopefully this answers your questions, but let me know if you have
further questions.
Thanks,
Scott
On Mar 10, 10:27 pm, Bouiaw <
bou...@gmail.com> wrote:
> Hi,
>
> I have finished the first step of the import of flexlayers code into
> openscales SVN.
> To browse, usehttp://
openscales.org/p/openscales/source/tree/HEAD/branches/flexlayers
> To checkout, usehttp://
openscales.org/svn/openscales/branches/flexlayers
> To test last snapshot usehttp://
openscales.org/openscales-flexlayers.swf