Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.de>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Sun, 23 Sep 2012 11:16:27 +0200
Subject: AW: Difference between CSS, SWC and SWF themes?
Thread-Topic: Difference between CSS, SWC and SWF themes?
Thread-Index: Ac2Y3IuQGRSt6Y6sRL+zBKkueeF0yQAZgZxCAApHdRA=
Message-ID: 
 <66E38C42347D6446BF7FCB22C3D3878072DDC9596D@ECCR06PUBLIC.exchange.local>
References: 
 <66E38C42347D6446BF7FCB22C3D3878072DDC9595C@ECCR06PUBLIC.exchange.local>
 <CC83DBCA.46549%aharui@adobe.com>
In-Reply-To: <CC83DBCA.46549%aharui@adobe.com>
Accept-Language: de-DE
Content-Language: de-DE
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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?=20
I am trying to deploy all themes and it would make life for maven a lot eas=
ier 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 thin=
k swcs would be the nicer way.

Chris


-----Urspr=FCngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]=20
Gesendet: Sonntag, 23. September 2012 06:19
An: flex-dev@incubator.apache.org
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 whe=
n the assets are classes.  If they are just SWF symbols then we don't bothe=
r.

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.dutz@c-ware.de" <christofer.dutz@c-ware.de>
wrote:

> Hi,
>=20
> I finally got some time to continue work on my FDK generator. Thanks=20
> to Fr=E9d=E9ric I don't have to deal with the automatic Zipping oft he=20
> Source artifacts any longer :) He also made me realize that I also=20
> have to deploy the stuff in the themes directory. He manually deployed=20
> the halo.swc, but I would like to auto-deploy them all in some way.
>=20
> Up till now my way of deploying the themes was to zip up the entire=20
> themes directory and create a special zip artifact for that. This was=20
> the way Velo used to do it, but I thought this allways was sort of=20
> hacky. Having a more detailed look at the themes, I can't seem to work=20
> out why some themes are SWC files, some are SWFs (AeonGraphical ) and=20
> some others are simple CSS files (sometimes accompanied with one or=20
> two image resources). So my question now
> is: What are these differences and what ist the reason for them? My=20
> current assumption is that the CSS themes are deployed as simple CSS=20
> Files because creating a SWC containing only a CSS and mabe one image was=
 too much overhead.
>=20
> Would it be possible to make SWCs out of these non-swc-themes and to=20
> use them the same way the more hevy weight halo theme is used? This=20
> would make deploying them and using them in Flexmojos a lot easier.
>=20
> Chris

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui