I imported my IDEA Flex project an cannot get it to compile. I basically want to use the Flex SDK flex-config.xml and override some values with my project flex-config.xml (no special Astella dialog options) but I cannot find a configuration setting for that. Tried "Load configuration file" in the compiler settings but it does not work.
What do I overlook? If this legacy behaviour were not possible, switching to Astella would be a complete blocker for me.
Thanks and Regards,
We don't want to literally use flex-config.xml from SDK for several reasons. But config file that Astella generates by default is equivalent to standard config from SDK. Support for custom config file with additional parameters will be added later.
May I ask what the reasons are?
I always felt comfortable using SDK flex-config.xml:
- selecting SDK version automatically uses the correct flex-config.xml
- flex-config.xml contains the reference documentation
- custom flex-config.xml is in the GIT project repo (easy to clone GIT project and get going)
- no fiddling with the overloaded dialog
- imported IDEA Flex projects do not work/compile
I tried to apply my custom flex-config.xml to the Astella compiler configuration dialog but I could not match all xml tags against the dialog labels.
So I would still vote for an optional expert mode - SDK flex-config.xml + custom flex-config.xml.
Custom configs will be supported, so just wait for some time.
Do you also patch standard flex-config.xml from SDK? One of the reasons why we won't use config from SDK is library path. Astella allows to configure whether your build configuration is pure AS or not, whether you use Spark, MX or both, whether famework is merged, external or RSL. Configuration from standard flex-config.xml doesn't work for all these cases.
why am I getting this error in side my perfectly valid services-config.xml file included with my coldfusion installation?
[ComplaintsSystem (ComplaintsSystem)] unexpected element 'services-config', expected 'flex-config'
Looks like you have configured services-config.xml as an additional compiler config file. In fact it is not a compiler config file, it doesn't contain compiler options. It is a Data Services config file. So its place is in the table at Compiler Options tab, there look for Server Technology node and Data Services config file subnode.
See legend at the right to understand colors.
Why? This should work in the same way as Data Services config file set in the table.
additional compiler options:
-locale en_US -services 'X:\ColdFusion9\wwwroot\WEB-INF\flex\services-config.xml'
[ComplaintsSystem (ComplaintsSystem)] command line: unable to open ''X:\ColdFusion9\wwwroot\WEB-INF\flex\services-config.xml''
Cool, now I get:
[ComplaintsSystem (ComplaintsSystem)] flex.messaging.config.ConfigurationException: The services configuration includes a channel-definition 'java-polling-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
Try double quotes.
Also you can set both context root and DS config file as I mentioned above, under Server Technology node. To set empty value there you'll need to set some non-empty value first and make it empty afterwards, the option will remain bold in this case (this usability issue will be fixed, empty context root will be used automatically as soon as DS coinfig file is specified).
I feel like giving up with this and going back to FB 4.6
things like the design view dont work,complains about remote object not having default property, and things like outerDocument flag up red as unresolved type, reminds me of the troubles I had with IDEA ages ago that I thought might have been fixed by now.
<s:Image source="assets/18edit.png" useHandCursor="true" buttonMode="true" toolTip="Edit complaint" >
UI designer doesn't work currently with flex SDK 4.6. Will be fixed before release.
FB doesn't have live errors highlighting, so it is impossible to compare.
But outerDocument is highlighted correctly for me. If <s:Image/> tag is inside <fx:Component/> then outerDocument is green. If not - it is red because such code doesn't compile. Can you please give full code sample that is highlighted incorrectly for you?
By the way early access program (EAP) is done exactly for the purpose of collecting feedback on bugs and usability issues from our users. Without your feedback chances to overlook some bugs grow bigger. So please don't hesitate to paste incorrectly highlighted code to the forum or (better) issue tracker.
opps sorry, it was my bad the OD code was non inside an inline component but a sererate mxml file
In fb all non as3 and mxml files in src dir are automatically transfered to the output dir on saving, this was handy for .cfc and .cfm files as it saved me manually copying them or writing ant files,
there appears not to be a similar option in Astelli, not essential but would be cool for lazy coders like me
Go to File | Settings | Compiler, and add ?*.cfc and ?*.cfm patterns to the Resource patterns field.
Note: this is IDEA-style resource management, and it will work only if you use standard output folder, i.e. [project folder]/out/production/[module name]. We plan to make more convenient resource management before release.