Thanx again for the clarification. Looks like my "skinning-quest" is finally over ;-)
Allthough, I just had the idea of compiling the project (AS class + css + skins.swf) and use the keep-generated-actionscript compiler option to see how flex tackles this behind the scenes. I'm just gonna go dig in that a bit ;-) regards, Muzak ----- Original Message ----- From: "Michael Schmalle" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, March 07, 2007 12:36 AM Subject: Re: [flexcomponents] graphical skinning - css - swc (part 2) >> which route do you think is currently the best (or least cumbersome) to > take? > > My advice is include your defaults css file and assets with your library > SWC. > > Then tell your users they can either; > > 1. Copy your default css sheet into there folder and edit as will. > 2. Throw the -theme compiler arg into there build or compiler settings. > 3. Create the default config for them and just have them include it. > - remember with configs, you don't have to touch the compiler if you name > it 'MyApp-config.xml' > > Any one else out there listening, trust me, these are your only options. :) > > Oh, yeah, for NON link dependent styles there is also initialization default > setting. I don't like this because it hides defaults. Although in some > components I am about to release I had to do this in areas because of design > view. > >> the config file, is that as a replacement for the compiler argument, > > Yes, it is a replacement. > >> can the config file somehow be "connected" to the component swc. > > I wish, :) As I said, the closest you can connect this config to your users > app is include it in you distribution zip file and tell them where to put it > and how to name it. Really, it's not that hard. But, yeah we are talking > about users or application devs here... ;-) > > Peace, Mike >
