I don't believe so, but I think it could be if someone was trying to
include both the Halo and Spark themes and wanted to control the
precedence (see the spark-theme-vs-halo-theme link below). But again,
I'm not sure.

I think people are getting the Halo and Spark themes confused with the
Halo and Spark component sets. I'm not 100% clear on the distinction,
but I think it's the difference between the themes/Spark/spark.css and
the spark.swc (??). Perhaps someone with more of a flex background can
better define the distinction.

Here is some of the documentation and forums that I've been looking
through for answers...

http://livedocs.adobe.com/flex/gumbo/flex_4_featuresandmigration.pdf
http://livedocs.adobe.com/flex/3/html/help.html?content=styles_12.html
http://www.adobe.com/livedocs/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Book_Parts&file=styles_069_30.html
http://askmeflash.com/qdetail/593/spark-theme-vs-halo-theme
http://butterfliesandbugs.wordpress.com/2009/03/01/flex-4-sdk-downloads-now-include-spark-skins-for-all-the-components/
http://www.flashdevelop.org/community/viewtopic.php?f=13&t=6919&start=0


On Jul 27, 2:50 pm, Marvin Froeder <[email protected]> wrote:
> Flexmojos does automatically include themes/Spark/spark.css , is that a
> problem?
>
> On Tue, Jul 27, 2010 at 6:37 PM, Karla Jacobsen <[email protected]> wrote:
> > Providing an update to an old discussion on this thread...
>
> > The author was having a problem migrating an Ant build to Maven. The
> > solution turned out to be fairly simple. The custom theme (slp-app-theme)
> > was not being built correctly, so the SWC did not include any of the
> > necessary CSS or images. Once the theme SWC was correctly built, the custom
> > theme simply needed to be included as a dependency with the scope 'theme',
> > and everything worked as expected.
>
> > One a broader note...I've seen a number of discussions about themes and it
> > seems like there is a recurring misunderstanding concerning the Spark theme.
> > Velo and a few people have touched on the misunderstanding, but most of the
> > threads were dropped before anyone clarified. Users of Flex/Flash Builder or
> > those switching from an Ant build seem to have the most difficulty.
>
> > In John's posting, he indicated that he was using themes/Spark/spark.css in
> > his flex-config.xml when using an Ant build. In turn, he interpreted that to
> > mean that he needed to explicitly include the spark theme as a dependency:
> >         <dependency>
> >             <groupId>com.adobe.flex.framework</groupId>
> >             <artifactId>spark</artifactId>
> >             <version>${flex-version}</version>
> >             <type>swc</type>
> >             <scope>theme</scope>
> >         </dependency>
> > It seems like a logical assumption; however, the spark swc should not be
> > included as a theme-dependency in this case. The themes/Spark/spark.css and
> > the com.adobe.flex.framework:spark:swc:theme are not the same thing. You can
> > see this for yourself if you compare the themes/Spark/spark.css with the
> > default.css in the spark.swc. (Note: The themes/Spark/spark.css can be found
> > in your flex sdk under frameworks. You can look inside any SWC using an
> > unzip utility -- such as WinZip -- to view the default.css.)
>
> > I think the Flex/Flash Builder UI also contributes to this misunderstanding
> > because it shows projects using the default Spark theme. But again, this
> > does not mean that you need to include the spark.swc as a theme.
>
> > In summary, don't try to include the Spark theme in your maven build just
> > because your IDE shows the default Spark theme or you reference spark.css in
> > some other build tool.
>
> > I hope I have offered a little clarification and not further muddied the
> > waters for anyone experiencing theme related problems. I'm not a Flex
> > developer and have just worked with it enough to transition a large set of
> > projects to Maven builds and troubleshoot problems, so please feel free to
> > correct any mistakes or offer more explanation.
>
> > On May 11, 4:43 am, Marvin Froeder <[email protected]> wrote:
> > > This sample you provided me you did use spark.css, but on your tries with
> > > flexmojos you are using a spark.swc.... why is that?
>
> > > Sent from DROID
>
> > > Em 10/05/2010 23:50, "John Siegrist" <[email protected]>escreveu:
>
> > > Hello Velo,
>
> > > Yes, this is possible. We have a working ant-based built where this is
> > > in use. Basically, the spark theme is applied first, then only those
> > > elements of the theme that are redefined by slp-app-theme have the slp-
> > > app-theme styles and elements applied. The flex-config.xml as relates
> > > to the theme looks like this:
>
> > > <theme>
> > >    <file>themes/Spark/spark.css</file>
> > >    <file><absolute_path_to_project>/slp-app-theme.swc</file>
> > > </theme>
>
> > > The Adobe Flex compiler docs also state that this is supported. It's
> > > interesting because it's one of the few things where the order really
> > > matters (as the last style definition overrides any previous ones):
>
> > > "You can specify more than one theme file to be applied to the
> > > application. If there are no overlapping styles, both themes are
> > > applied completely. The ordering of the theme files is important,
> > > though. If you specify the same style property in more than one theme
> > > file, Flex uses the property from the last theme in the list. In the
> > > following example, style properties in the Wooden.css file take
> > > precedence, but unique properties in the first two theme files are
> > > also applied"
>
> > >http://livedocs.adobe.com/flex/3/html/help.html?content=styles_12.html
>
> > > Thanks for your assistance.
>
> > > Regards,
> > > John
>
> > > On May 10, 4:49 pm, Marvin Froeder <[email protected]> wrote:
>
> > > > How do you do that using mxmlc or c...
> > > > On Mon, May 10, 2010 at 8:38 PM, John Siegrist <[email protected]>
> > wrote:
> > > > > Hello All,
>
> > > > > I am...
> > > > > [email protected]<flex-mojos%[email protected]>
> > <flex-mojos%[email protected]<flex-mojos%[email protected]>
>
> > > <flex-mojos%[email protected]<flex-mojos%[email protected]>
> > <flex-mojos%[email protected]<flex-mojos%[email protected]>
>
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/flex-mojos
>
> > > > >http://f...
> > > > 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 pos...
>
> > > --
> > > 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 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]<flex-mojos%[email protected]>
> > For more options, visit this group at
> >http://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/

Reply via email to