My thoughts are -- it depends on the application. The existing themes are great if you are doing a lot of forms based 'screens'. I don't have a designer on my team, and I most likely never will get one. My apps are used by professions that like good usability and a good clean layout -- that is one thing some of the existing themes give.
Separating them out and making them easily accessible is not a bad idea, but removing them -- I'd vote against hat. -Nick On Sat, Feb 25, 2012 at 1:11 PM, David Francis Buhler <davidbuh...@gmail.com > wrote: > My own personal preference would be to remove the current themes (both MX > and Spark) from the SDK. This includes the Cobalt theme, Zen theme, etc. I > would stick with the "Wireframe" theme for Spark controls. In doing so, we > remove the obvious visual impression of a "Flex Application", and > encourage the use of Flex/AIR apps that look like part of their native > environment (FaceBook, Android, iOS, Windows 8, etc.). Most developers take > short-cuts and use one of the existing themes when building a product for > their client, and unintentionally give the impression of a hodgepodge of > technologies that prevent the impression of product cohesion. Removing the > Cobalt theme, Zen theme, and other themes would discourage this practice of > use-what-i-found. > > If companies have designers, they're better off with a tool like Martin > suggests then they are with existing Themes. Moreover, the existing themes > confuse designers (with the MX and Spark namespaces, the inability to > understand each and every style property, or the overwhelming number of > properties available). If companies don't have designers, they're better > off sticking with Wireframe theme until they do. > > Incidentally, I'd love to see a tool that generates themes from a > user-defined base color, with the palette generation of complimentary, > monochromatic or triad colors, similar to Kuler. > > [1] http://kuler.adobe.com/ > > On Sat, Feb 25, 2012 at 12:20 PM, Martin Heidegger <m...@leichtgewicht.at > >wrote: > > > On 23/02/2012 17:59, Haykel BEN JEMIA wrote: > > > >> I think the first step should be to create new skins for the current > Spark > >> components. Designers could make designs for them (ideally using a tool > >> that enables export to FXG like Illustrator) and then developers can > >> create > >> skins out of them. > >> > >> Haykel > >> > > > > Doesn't necessarily be a design for flex: Here i found some nice > > inspiration[1]. A *fictional* > > Windows 8 user interface - very nice :) > > > > yours > > Martin. > > > > [1] http://www.theverge.com/2012/**2/24/2822891/windows-desktop-** > > ui-concept< > http://www.theverge.com/2012/2/24/2822891/windows-desktop-ui-concept> > > >
