I would really prefer the package to become a normal theme ... could you create issues for what's missing? Eventually this would be some great "low hanging fruit" for potential new committers and for people wanting to contribute in general?
Especially when thinking about using it as a theme-like thing in Maven, it would be very helpful if it were to be handled in the default way. I'd be glad to help ... even if I currently think I shouldn't open another "thread" and I should focus on Flex PMD now that the Mavenizer is almost finished ;-) Chris ________________________________________ Von: Mahmoud Ali <mudd...@gmail.com> Gesendet: Dienstag, 21. April 2015 00:18 An: dev@flex.apache.org Betreff: Re: Flatspark location > > >> 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? > FlatSpark is not ready to be used as a theme, that's why there is this distinction. The project is meant to be a port of the FlatUI theme, so customization was not in our minds when we started this project. >> 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. If I remember correctly we had a discussion about whether or not the two components should be added. Maybe we could move it to the experimental package? Although that would be a breaking change now.
