I'd love to. Take a look at some of the components that are being submitted via our own SVN (in the whiteboard area). For example, the MobileAlert component I've been writing uses Spark skinning, and in all honesty, it is pretty nice.
http://svn.apache.org/viewvc/incubator/flex/whiteboard/quetwo/MobileAlert/src/org/apache/spark/components/ (Take a look at MobileAlert.as and the AppleOSAlert.mxml skin paired with it). Once you get your head around what is going on, it is not too bad. What makes it really powerful is the ability to use the same layer effects, vectors, etc. as you do in Photoshop or Illustrator as you do through code. This is unlike the Halo model where you tie together all sorts of raster images, or worse yet, rely on the low-level drawing apis to make your skins. Mind you, making raster images in Halo works, but the quality of the skins you can come up with if you draw them in FXG can be much higher. -Nick On Sat, Mar 24, 2012 at 12:21 AM, Williams Farias <will.far...@gmail.com>wrote: > Ok, so please show me a great example with Spark skinning, with really > custom components... and of course, with source code... like that: > http://fleksray.org/skins/scribble/Scribble.html > > If you see the source code, you´ll se the simplicity, its ridiculous, just > CSS and images. > > Its not about what the technology can do... its about who will use it and > whith what ammount of work? Man, developers usually dont do design... they > only code the things... acess databases and so on. Spark components dont > have so much impressive skinning examples, in my point of view, because of > that: designers where excluded from skinning components! So, if only > hardcode developders can do it... what meters if it´s the best whay? if > nobody will use it... I what just to see an exemple, with source code with > a great custom skin... > > If you have, please show me. > >
