Uncategorized

The Gnash Project

Gnash is the GNU Flash movie player, which can be run standalone on the desktop or an embedded device, as well as a plug-in for several browsers.

The official project website…

http://www.gnashdev.org/

…and this is the official Wiki of the project where you can find loads of documentation which not only relates to the Gnash project, but also can be a rich source of information to give insight into the inner workings of the SWF execution model…

http://wiki.gnashdev.org/

Adobe Flex, Tools

IDEFactory… currently in Beta… soon in production…

When using Adobe Flex to build enterprise scale systems, the limitations of Flex Builder becomes not only very apparent, but also a limitation for productivity and flexibility (note the irony :-) )

However, a group of talented developers have started on the quest to deliver architectural features to us inside Flex Builder… fortunately they have decided NOT to change the base, but build it as a plug-in to Eclipse / Flex Builder.

IDEFactory… looking really good sofar…

http://www.idefactory.com/

Adobe Flex

RSL and the lack of a build-in map over class-definitions

In response to the lack of Reflection in ActionScript and the emergence of techniques such as RSL and Modules and the combination of these two, several initiatives have been launched to facilitate a map of class definitions within a SWF.

One is the SWFExplorer by ByteArray which is still in a very early stage of development, but it appears to become a simple and easy way to get the definitionNames from a SWF at Runtime.

Another is the getDefinitionNames by Dennis Kolyako which is a bit more complex in its implementation than SWFExplorer, but yields the same gross results.

SWFExplorer overall seems to fit the OO design model of Flex more than the latter implementation by Dennis which seems to match a more traditional Flash Authoring design model.

Uncategorized

Guice (pronounced 'Juice')

Guice (pronounced ‘juice’) is a lightweight dependency injection framework for Java 5 and above, brought to you by Google, however the principles are sound and could be used for other frameworks too.

Writing factories and dependency injection logic by hand for every service and client can become tedious. Some other dependency injection frameworks even require you to explicitly map services to the places where you want them injected.

Check it out… exciting stuff
http://code.google.com/p/google-guice/