The Potomac Framework for Flex is:
There’s a new drop of Potomac. Specifically, this build resolves some memory issues encountered when building large projects (many bundles). There are few other changes. Read the release notes.
We’re ramping up development on Potomac after a bit of a lull. Probably like most of you, we’re excited by the new stuff coming in Flex 4 and Flash Builder 4. We’ve talked to alot of you guys using Potomac and it seems most everyone is using Flex 4 currently or plans to shortly after its released. So we’re considering droping support for Potomac on Flex 3. This would mean that you’d need to use Flex 4 and Flash Builder 4 to develop with Potomac.
If you’re using Flex 3 and don’t plan on upgrading to Flex 4 anytime soon, and don’t want us to drop support – speak now. Leave a comment on this post and let us know. If we don’t hear from anyone, then we’ll proceed with a Flex 4 only Potomac.
You can hear Chris Gross (the architect of Potomac) discuss how Potomac came to be and other cool stuff at TheFlexShow podcast.
This isn’t directly related to Potomac, but the team behind Potomac is proud to announce the beta for our upcoming professional add-on for Flash Builder 4: SourceMate.
Refactoring, code generation, code snippets, metadata integration, and much much more. Give it a run during our free beta testing program.
Mike of Teoti Graphix has been an active contributor on the forums and now he’s started a new blog focused entirely on Potomac and his upcoming extensions for Potomac.
Mike is definitely on the forefront of Potomac customizations with his custom template work and the other fun stuff he’s working on.
Kudos Mike!
A small new update has been posted. Included in this build are a few bugs fixes and one minor new feature. The most important bug fix resolves a problem when using the Potomac FlexBuilder plugin on Mac OSX. Prior to this release, the plugin would report errors during every application project build due to file locking/writing issues. Those problems are now resolved.
The one feature addition is the new [InjectWithin] tag. [InjectWithin] provides a declarative way to provide injection within a created class instance. It’s functionally equivalent to Injector#injectInto(). This tag is most useful when declaring components in MXML and those component classes contain [Inject] references.
As always, read the release notes for more details.
We’ve just released a new drop of Potomac that includes support for AIR and an initial download for Flex4 Beta2.
The AIR support is significant including support for downloading bundles remotely and bundle caching. Check out the latest release notes for more details.
The documentation for templates has just been fleshed out. If you’re interested in creating custom templates for Potomac go check it out.
Its still not as comprehensive as we hope but it should help you get started. Creating a custom template can be as easy as 100 to 200 lines of code.
If you’re at Adobe MAX and you wanna chat about Potomac head down to the Potomac Birds-of-a-Feather session tomorrow at lunch time. The BOF sessions are held in the community pavilion (on the far right side) from 12:30-2:00 12:00 – 1:30. Potomac hasn’t been officially added to the BOF schedule board yet – expect to see it added early tomorrow morning.
Update: Confirmed for today (Tuesday) at 12:00.
A new build has been posted that resolves an issue when installing the plugin into Flex Builder standalone instances. If you’ve installed the plugin but have been unable to see the Potomac menu options or preference page – this new drop should fix your issue.
There have been a few other changes (support for the 3.4 SDK) and features added. Please read the Release Notes.
If you’re on an older version of the plugin please read the important note at the top of the release notes. There’s been a small change that requires you to update your application projects.