I don't have a problem with compiling the stuff into an swf/swc, even if I will use the commandline fort hat as I will have to do this for every non-swc theme in every official Flex SDK. Doing this manually will take me days, I think ;-)
I have decided that I will deploy all of the themes as SWCs, because I think this is the most generic approach. If there are any objections to this, I would be glad to hear them ;-) Chris -----Ursprüngliche Nachricht----- Von: Omar Gonzalez [mailto:omarg.develo...@gmail.com] Gesendet: Sonntag, 23. September 2012 11:42 An: flex-dev@incubator.apache.org Betreff: Re: Difference between CSS, SWC and SWF themes? Just right click on the CSS file in Flash Builder and check the Compile CSS to SWF option. It'll compile the CSS to SWF. You can use Embed meta data to embed any assets you need. -omar On Sunday, September 23, 2012, christofer.d...@c-ware.de wrote: > Hi Alex, > > so it should be possible to use the FDK binaries of a FDK to create an > SWC out of a theme and deploy that instead of the originals? > I am trying to deploy all themes and it would make life for maven a > lot easier if it were only one file. The other alternative would be to > zip up each theme (even the swc) and to deploy those Zips. I have to > admit that I think swcs would be the nicer way. > > Chris > > > > -----Ursprüngliche Nachricht----- > Von: Alex Harui [mailto:aha...@adobe.com <javascript:;>] > Gesendet: Sonntag, 23. September 2012 06:19 > An: flex-dev@incubator.apache.org <javascript:;> > Betreff: Re: Difference between CSS, SWC and SWF themes? > > A theme is described by its CSS file, which usually refers to some assets. > Those assets might be Flash SWF assets, or FXG or ActionScript classes. > Depending on the type of assets, it is sometimes more convenient to > package it up as a SWC (the CSS file is in the SWC). This is usually > the case when the assets are classes. If they are just SWF symbols > then we don't bother. > > It should be possible to package the SWF and CSS as a SWC, but there > might be some detail I'm forgetting. > > > On 9/22/12 9:46 AM, "christofer.d...@c-ware.de <javascript:;>" < > christofer.d...@c-ware.de <javascript:;>> > wrote: > > > Hi, > > > > I finally got some time to continue work on my FDK generator. Thanks > > to Frédéric I don't have to deal with the automatic Zipping oft he > > Source artifacts any longer :) He also made me realize that I also > > have to deploy the stuff in the themes directory. He manually > > deployed the halo.swc, but I would like to auto-deploy them all in some way. > > > > Up till now my way of deploying the themes was to zip up the entire > > themes directory and create a special zip artifact for that. This > > was the way Velo used to do it, but I thought this allways was sort > > of hacky. Having a more detailed look at the themes, I can't seem to > > work out why some themes are SWC files, some are SWFs (AeonGraphical > > ) and some others are simple CSS files (sometimes accompanied with > > one or two image resources). So my question now > > is: What are these differences and what ist the reason for them? My > > current assumption is that the CSS themes are deployed as simple CSS > > Files because creating a SWC containing only a CSS and mabe one > > image > was too much overhead. > > > > Would it be possible to make SWCs out of these non-swc-themes and to > > use them the same way the more hevy weight halo theme is used? This > > would make deploying them and using them in Flexmojos a lot easier. > > > > Chris > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
