Hi Roland
Glad to help.
I just posted an example built with Spring Actionscript on my website
and would love feedback -
http://www.richardlord.net/blog/flexcaster-spring
I'm including Spring Actionscript in my session at <a href="http://
www.gotoandski.com/">GotoAndSki</a> this Saturday. Still weighing up
my opinion, and as usual with my framework sessions I'll try to
present the facts and let others choose.
But, having worked with SpringAS, here's a few thoughts...
1. The documentation is very comprehensive but also rather heavy for
beginners (this is a feature of the Spring Java documentation too).
It's great to have all this information, but a simpler document
showing just what a beginner needs to know to create a simple app
using one recommended architecture would, I suspect, help with the
uptake from less experienced developers. I should add, however, that
given my knowledge of both Spring Java and Flex I found Spring
Actionscript very easy to understand.
2. The need to include the autowiringStageProcessor and
eventhandlerProcessor in the config makes a lot of sense but I suspect
will appear like config for the sake of it to most flash/flex
developers. Adding a config option to "use the defaults" (something
like Spring Java's <mvc:annotation-driven/>) would help here. When I
had the problem mentioned above, I spent some time suspecting I'd
failed to include another config setting and searching in the docs and
example projects for it before discovering the real cause of the
issue.
3. I chose to embed the xml file because I don't see much value in
loading an xml config at runtime. Without a decent class-loader to
dynamically load classes I think dynamic runtime configuration has
little to offer me, and the majority of flex developers. I may well be
wrong here so go with your conviction, but if you haven't considered
it then maybe embedding the xml file should be your default
recommendation.
That's all. I like Spring Actionscript a lot, and having recently done
a lot of work with Spring Java it slotted straight in with what I
already know. This is likely its greatest strength - Java developers
will understand it immediately.
Cheers
Richard.