Hi folks,

As I’m currently starting to dig myself into migrating my stuff from Flex to 
Royale, I noticed that BlazeDS could use an update.

So I was thinking: This is actually the last part of the Flex project that 
might still have a future. So how about we move the BlazeDS component to Royale?
Perhaps even rename it to something like RoyaleDS? I would also like to ask the 
Spring folks if we could possibly take over the retired Spring Flex module
and build a Spring Royale module from that, but as part of the Royale project.

While at it I think in order to build the Framework and the Compiler with SWF 
support, we still need some Adobe artifacts.
That’s why we’re still using the Flex Mavenizer.

So how about taking part of that code and have a Royale version (Just for the 
Flash and Air libs)?

Chris

Reply via email to