@AlexU - Not sure if this is the same thing, but I had a similar experience when migrating to Flex 4 final and using Spark and MX components together. I ended up examining my compiler errors more closely to discover that when using the Spark theme, certain styles didn't exist as they once did in Flex 3 on MX components. You could use the Halo theme, but then no styles for the spark components would be defined. Not sure if this is the same thing you ran into, but thought I'd share.
-Brian On Apr 22, 3:18 pm, AlexU <[email protected]> wrote: > How can I compile themes for Halo and Spark component into one module? > I’ve defined the below inside the pom.xml of the Flex module project: > > <dependency> > <groupId>com.adobe.flex.framework</groupId> > <artifactId>sparkskins</artifactId> > <version>${flex4.sdk.version}</version> > <type>swc</type> > <scope>theme</scope> > </dependency> > <dependency> > <groupId>com.adobe.flex.framework</groupId> > <artifactId>spark</artifactId> > <version>${flex4.sdk.version}</version> > <type>swc</type> > <scope>theme</scope> > </dependency> > > It compiles but once the module gets loaded, it throws runtimes on > various Flex components for missing skins. How can I enforce that the > correct skins are compiled into the module? I have the same dependency > definition for my shell application and it works. > > I’ve tried to force compilation into the Flex module with a CSS class > selector: > i.e.: > > s|ComboBox > { > skinClass: ClassReference("spark.skins.spark.ComboBoxSkin"); > } > > When I have enough of those, I don’t get runtimes anymore. But of > course, my question is how I can prevent those forced compilations via > i.e. CSS? > > Also, my ultimate goal is to apply CSS definitions of a custom library > project (via defaults.css). In my shell project and the module I have > the following definition to the custom library project (that contains > the CSS definitions to apply) > > <dependency> > <groupId>${myproject.application.groupId}</groupId> > <artifactId>my_default_skins_project</artifactId> > <version>${myproject.application.version}</version> > <type>swc</type> > </dependency> > > It already works fine with compiling it into the shell Flex project, > just not into the module. > > -- > 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 athttp://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ -- 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/
