On 9/17/13 9:21 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> Seems like the options are (at least): >> 1) The release notes say that Falcon only works with 4.11 and greater so >> 'too bad' if you try against an older SDK >> 2) Hard-code Spark as the default theme >> 3) Have Falcon report an warning if no theme is found in any config >>file. >> 4) Have Falcon inject a theme into air-config.xml if it is missing >> 5) Have a Falcon installer inject a theme into air-config.xml. >> >> #1 is the least work, but my second choice would be #3. > >1 is going to disappoint a lot of people (IMO), they will want to use the >falcon compiler as a drop in replacement and wont understand why it's >married to a version of the SDK and As Erik pointed out, it could get really tricky to make it support old SDKs. The codegen for MXML changed in between some versions of Adobe Flex. >2 is going to stop it working out of the box with any existing AIR >project, it's a small change sure but better to not have to make everyone >make that change for all projects if possible. > >Why not go with spark as a default (if required) if it not configured via >a command line option or in the config file? Because then you have hard-coded a dependency on the current Flex framework. It may not be what you want for FlexJS, for example. There is a #6 which is to use flex-config.xml as a base. More work, and we'd have to see if there are any negatives, but might be what we have to do. > >I assume there are going to be people who want to compile pure AS with >Falcon how with that effect them? We could not report the warning unless you are compiling a Flex project. > >> But Falcon reports a warning. Why isn't that sufficient or even better? >A warning is good. Why do you need to change the SDK's ResourceManager? Because ResourceManagerImpl throws an error if it doesn't find all bundles in all locales. It should be more forgiving, IMO. It seems like an unnecessary requirement and you'll probably catch missing resources during development. > >> At least with Falcon you'll find out that you don't have a bundle for a >>locale. MXMLC just copies a default. >It fails to compile if the locale is missing.. I'm not seeing that if you have a folder but not all properties files. Are you seeing differently? -Alex
