IMPORTANT NOTE

Anyone upgrading from an earlier version of the Potomac plugin should perform the following steps in any of their application projects:

• Delete the potomac.derived.StyleReferences.as
• Add “-keep-all-type-selectors=true” to the compiler arguments in the project properties

New application projects will be configured correctly. This is only necessary for projects created and configured with earlier versions of the Potomac plugin.

Bug Fixes

The Potomac plugin now property installs and activates in fresh instances of FlexBuilder standalone.

Updates

The rpc.swc which includes the data services classes is now automatically linked as an RSL. This is necessary for most any data service calls.

Potomac has now been tested on the latests Flex 3.4 SDK. There is one known issue which is possible due to a bug or change in the latest 3.4 SDK.

New Features

Extensions can now be enabled and disabled through an optional “enablesFor” attribute. This mechanism is global to all extension points.

The extension attribute ‘enablesFor’ is a comma separated list of enablement flags. Flags are specified in the appManifest.xml in the application project. When specifying an enablesFor attribute, that extension will then only be active when the appManifest contains the flags specified. For example:

[MyExtensionTag(enablesFor="qatest,unittest")]

This tag would only be active when the application includes the ‘qatest’ or ‘unittest’ flags in the appManifest.xml. Additionally, you can use the dash or minus operator to specify that an extension should be active except when certain tags are used. For example:

[MyExtensionTag(enablesFor="-production,-release")]

This tag would be active as long as neither the ‘production’ nor ‘release’ tags were specified in the appManifest.xml

---

The bundle.xml and appManifest.xml editors now contain an “Update Build Path Locations…” option. This feature is rarely necessary but can be used when moving projects to different folders.