- A modularity framework inspired by OSGi
- A UI composition framework that pulls user interface ‘parts’ together to form applications
- A general purpose business application framework (providing reusable features for business applications)
- A dependency injection framework
- An extensible metadata processor with reflection support
There’s a new build up. This new build fixes a serious bug that resulted in applications hitting an exception (“Type coercion error …”). This new build only updates the Potomac plug-in so users do not need to update their target platform.
Please see the release notes.
This is a smaller build that fixes a few bugs and includes some internal refactoring. Check out the release notes.
We’ve released another new build of Potomac (release notes).
In this build a new messaging system has been added. This new system allows an easier way to dispatch and handle events throughout a Potomac application. It also includes a cool agile eventing system that alleviates the need to create Event subclasses to pass message data. Please see the new documentation page for more details.
An additional new feature – Potomac [Injectable]s can now be initialized asynchronously before they’re injected.
There have been quite a few smaller bug fixes as well.
After a long wait, we’ve released the custom Ant tasks to allow you to build Potomac applications from the command line or during a continuous integration build. This is part of the new build we just posted (release notes).
Running the Ant task is complicated by the need to use a custom, patched version of the Flex SDK. The method we’re using to build Potomac project is the Flex Compiler Extensions. Unfortunately that feature is missing an important API for us and we’ve had to patch it to add this feature. You can help by voting on this bug in the Adobe bug database:
Instructions on running the new Ant tasks can be found here:
As always, use the forums to report problems and ask for help (we know this is complicated so we expect some questions).
A new build of Potomac is available from the downloads page. Importantly this new build fixes an issue where the paths in the example projects where causing headaches. This new build also includes a refactoring of Potomac’s bootstrapping code. This change helps (among other things) those who want to run a bootstrapped Potomac instance for unit testing but don’t want to run a full blown Potomac UI.
Please see the release notes.
Check out the latest RIA article from InfoQ.com:
Potomac is featured as are other well known Flex frameworks like Swiz, SpringAS, Mate, FlourineFx, and RestFulX.
As we’ve mentioned many times, Potomac is heavily inspired by Eclipse. Eclipse’s focus on modularity (particularly OSGi) and enterprise applications has made modular development in Java much simpler. Potomac is our attempt to do the same for Flex applications.
Considering this close heritage, it only makes sense that we’ve just proposed bring Potomac to Eclipse.org. Many developers may not realize, but Eclipse is much more than just an IDE for Java development. Of course, its the underpinning of Flash Builder, but Eclipse.org also hosts a variety of like-minded projects. This is comparable to Apache (which contains the Apache web server, Tomcat, Ant, Maven, and many more).
You can read the Eclipse Potomac proposal here:
Eclipse proposals have to go through a process of vetting and finally voting by Eclipse council members. We feel confident that Eclipse will accept Potomac and we’ll be brought into the Eclipse fold. What does this mean for the future of Potomac? Only good things. We’ll gain better visibility through the high traffic Eclipse websites and mailing lists. We’ll make use of the Eclipse infrastructure for things like source repositories, forums, bug tracking, and more. Importantly, it will also lend a bit of confidence about the IP questions that invariable arise when large companies adopt open source projects. Eclipse has a very comprehensive IP review and approval policy. Overall, we’re very excited about being part of Eclipse and what effect that will have on helping push Potomac forward.
One of the most significant new releases of Potomac is now available for download. New features include dynamic bundle loading, enhanced preloader support, SourceMate integration, and more. The dynamic bundle loading has been a long planned feature that brings alot of exciting new potential for Potomac applications. The build contains a new example application that demonstrates this feature (along with the new preloading support).
We’ve just put the finishing touches on a release to ease the pain of using Potomac together with source control systems. Previously, the files automatically generated by Potomac would cause source control systems to request merges unnecessarily. With this new build those issues should be resolved.
We’ve uploaded another new build of Potomac. This build includes a fix for a long standing (and frustrating) issue where the Potomac builder froze intermittently. Also included is a new preference page that allows users to configure which metadata tags Potomac should ignore. The default list of ignored tags has been updated as well. [Release Notes]