Another New Build
March 9th, 2010
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]
Just installed Eclipse 3.5.2 with Flash Builder Plugin 4 Beta 2 and Potomac Plugin.
The Getting Started where you create a first application with one bundle does not work.
Errors:
1144: Die Schnittstellenmethode callInContext in Namespace mx.core:IFlexModuleFactory wird mit einer inkompatiblen Signatur in Klasse _my_app_mx_managers_SystemManager implementiert. my_app line 21 Flex-Problem
Translation: The interface method callInContext in Namespace mx.core.IFlexModuleFactory is implemented with an incompatible signature in class _my_app_mx_managers_SystemManager.
Hope you can help.
Sebastian
Hi Sebastian,
This comment would be better posted on the forums (forum.potomacframework.org). But I’ll go ahead and answer this here.
First, the latest Potomac builds for Flex4/FlashBuilder4 do not support Beta2. Beta2 is quite old and Potomac has been built against much more recent versions of Flex4/FlashBuilder4. Those versions are only available to a private beta community until FlashBuilder4 is officially released (real soon now we hope). All of these errors are likely related to what version of Flex4 and FlashBuilder4 you’re using.
Until FB4 is released (again we hope real soon), we can only offer the Flex3 version of Potomac.
regards,
-Chris
Same problem with the sample app.
Further, you should remove absolute paths to icons, like
C:/Users/cgross/runtime-potomac_0112/potomac_mailexample_mail/extensionAssets/mail.png
in the ExtensionAssets class or to the logo in the appManifest.xml.
Regards, Sebastian
@admin
Okay, thanks for that hint!
The paths you see are derived during the project compilation/build. If the builder was working correctly, these paths would automatically update to your local path. The builder likely isn’t working because of the version mismatch I mentioned above.
I do believe that once all the version problems are cleared up, you should be up and running without any issues. Please post back here or on the forums.
Thanks,
-Chris