@Velo - Thanks for the quick response and making it through my details. I've filed an improvement request to add support to CSS files as theme dependencies @ https://issues.sonatype.org/browse/FLEXMOJOS-286. There are 4 themes that come with the SDK that would need to be included in the framework-configs.zip file: Halo, Spark, AeonGraphical, and Wireframe. You wouldn't have to include the compiler flags to use them, but providing a way to say you'd like to use them w/o uploading a copy to your own artifact repo would be helpful (e.g - deploying stock themes to the FM artifact repo).
You mentioned "... I only deploy the flex-config.xml because flex compiler does need this files, they can be empty (because they aren't really necessary)". Right now it's my understanding that the default flex-config.xml and air-config.xml files that comes with the SDK are used to convey the Adobe set of standard defaults. When a new SDK ships, these files are updated so that the recommended defaults are pushed to anyone using the defaults with their tools. Flash Builder, the Flex compilers, and the Flex SDK Ant tasks all use the flex- config.xml as a central configuration point and then diverge based on user configuration. If FM, is dynamically building the equivalent of user configuration portion, similar to the other tools, shouldn't it base its default config off of the SDK default files (e.g. - flex- config.xml)? I understand there would still be growing pains, as there are now, to match up configuration options offered in the SDK with FM features, but at the very least couldn't people specify a new set of defaults if feature parity wasn't available in FlexMojos? Case in point, support for multiple SDK themes using a new default flex- config.xml before the CSS theme artifact feature is ready? Right now, from what I understand, FlexMojos offers building with a custom flex- config.xml, but not the ability to override the settings in that custom flex-config.xml file once you've said to use it as a config option (configFile option in compile-swf/swc). What do you think? -Brian On Mar 24, 3:21 am, Marvin Froeder <[email protected]> wrote: > On Wed, Mar 24, 2010 at 2:02 AM, Brian <[email protected]> wrote: > > Ok, so I've been racking my brain over getting a Flex 4 app we've > > written using beta 2 working with 4.0.0.13875. It uses a combination > > of halo and spark components and I've been able to resolve all > > compilation errors except for having the Halo and Spark themes being > > used together at compilation. Please note, I've updated the halo > > namespace to the mx namespace as well as migrated all spark components > > that have changed from beta2. > > > I've tried the following permutations with FlexMojos 3.6 to no avail: > > > --------------------------------------------------------------------------------------------------------- > > > Tried: Deploying a new framework-configs-4.0.0.13875.zip to my local > > nexus repo with both the Halo and Spark themes in their appropriate > > folders and updating the flex-config.xml file to also use the halo.swc > > as a theme. I also tried commenting out all themes, as done in > > previous SDK releases of the flex-config.xml file, with the same > > results as given below. > > > Result: The changes to the flex-config.xml are ignored by the compile- > > swf/swc goals and only the spark.css file is listed as the theme to > > use to the compiler. I receive compilation errors for unknown > > components in the mx namespace due to the lack of the halo.swc file > > being present as a theme. > > DO NOT CORRUPT THE ORIGINAL FILES, THAT IS THE BEST WAY TO SCREW FLEXMOJOS > BEHAVIOR. NUKE THIS! This is kinda change Java compiler files and expect it > will work nice. > > In the end flex-config.xml files are mainly ignored by the compiler. > > > > > --------------------------------------------------------------------------------------------------------- > > > Tried: Deploying halo.swc and spark.css as artifacts in local nexus > > repo and including them as dependencies with the theme scope. > > > Result: Only the halo.swc artifact is used as a theme by the compile- > > swf/swc goals although the spark.css artifact is downloaded by > > dependency management, just never referenced during compilation. I > > receive a successful build with warnings that particular styles don't > > exist for numerous spark components. These styles are in the > > spark.css theme which is not being included, and the spark styles are > > not applied. > > IIRC, Flexmojos will add scope:theme type:swc dependencies only. No css > files. I can easily fix that for Flexmojos 4.x... on 3.x the code is quite > complicated to be changed. > > > > > --------------------------------------------------------------------------------------------------------- > > > Tried: Using the updated framework-configs-4.0.0.13875.zip from the > > above example, I listed the halo and spark themes as themes under the > > config section for the plugin. > > > Result: The compile-swf/swc goals look in my src/main/resources folder > > for files named "themes/Spark/spark.css" and "themes/Halo/halo.swc" > > instead of in the appropriate folder under target from the exploded > > framework-configs.zip file. > > DO NOT CORRUPT THE ORIGINAL FILES, THAT IS THE BEST WAY TO SCREW FLEXMOJOS > BEHAVIOR. NUKE THIS! This is kinda change Java compiler files and expect it > will work nice. > > > > > --------------------------------------------------------------------------------------------------------- > > > After trying the above I ram out of ideas. I noticed in the source > > for AbstractFlexCompilerMojo there is a case to include only the Spark > > theme if no other themes are declared in the POM, which explains some > > of the behavior I saw in my first trials. > > > So here are my questions: > > - What is the recommended way of working with multiple themes in Flex4 > > using FM? > > - If we're to use dependencies in the theme scope, can we have a way > > to use css artifacts since these are valid theme artifacts in Flex > > 4? > > As dependency? > No.http://sites.sonatype.org/flexmojos/flexmojos-maven-plugin/compile-sw... > > You must add it to the resources folder. > > > - If the framework-configs.zip is going to be distributed with the > > spark theme bundled, can you distribute all the default themes that > > comes with the SDK and allow us to select which to use? > > Yes, but I won't change the files I already released. Could you list the > exact file you wanna, so I can include on Flex 4.0.0.14159 when I do that? > > > - Any suggestions on how to solve the immediate need of devs using > > halo and spark with FM 3.6? > > Patch it to include css also =D, but that can be tricky since a wrong change > can break the entire dependency list =( > > BTW, file a ticket for that. > > > > > Any help is appreciated as I expect the same problem will crop us with > > the 4.0 final release as it uses an identical flex-config.xml which > > I'm guessing may help dictate how the SDK is deployed. > > Not really.... in fact I only deploy the flex-config.xml because flex > compiler does need this files, they can be empty (because they aren't really > necessary) > > > Thanks at the > > very least for reading this far :) > > > -Brian > > > -- > > You received this message because you are subscribed to the Google > > Groups "Flex Mojos" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected]<flex-mojos%[email protected]> > > For more options, visit this group at > >http://groups.google.com/group/flex-mojos > > >http://flexmojos.sonatype.org/ > > > To unsubscribe from this group, send email to flex-mojos+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject. > > -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/ To unsubscribe from this group, send email to flex-mojos+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
