Looking at the docs and after that at the code it actually seems if this is actually just a skin and 2 tiny components. I would think that we should think about moving the two components over (or removing them) to one of the component bundles and moving the skin stuf to a real skin package.
Having this hybrind thing hanging between the chairs sort of feels a little messy. Chris ________________________________________ Von: Erik de Bruin <e...@ixsoftware.nl> Gesendet: Montag, 20. April 2015 16:25 An: dev@flex.apache.org Betreff: Re: Flatspark location https://cwiki.apache.org/confluence/display/FLEX/Using+FlatSpark+skins Now you know as much as I do ;-) EdB On Mon, Apr 20, 2015 at 3:36 PM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > Hmmm ... ok ... so I can't use normal spark components and have the > "flatspark" theme applied and I don't pass it to the compiler as theme? > > Chris > > ________________________________________ > Von: Erik de Bruin <e...@ixsoftware.nl> > Gesendet: Montag, 20. April 2015 15:07 > An: dev@flex.apache.org > Betreff: Re: Flatspark location > > The word 'theme' is used when referring to FlatSpark, but not > correctly. Technically it's a collection of skins and some components. > > EdB > > > > On Mon, Apr 20, 2015 at 2:48 PM, Christofer Dutz > <christofer.d...@c-ware.de> wrote: >> Hi, >> >> >> I just noticed that my mavanizer generates a new artifact "flatspark" ... >> isn't that a theme? Shouldn't this be located in the themes directory? >> >> >> Chris > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
