And my final question is: why just not mix them? I belive in 'superable' comment. I know that Spark has great advantages. But Halo is so much simple! So, why just mix them? take the best of their too... and make a HaloSpark all in one architeture. Man, imagine if your client dont need a insanely custom skin... just need a simple custom scrollbar! In Halo, 5 minutes: open Flash, draw it literally with your hands... and thats it. Spark... code... code and more code on blind view.
I havent seen any insanely Spark skinning exemple so far... 2012/3/24 Williams Farias <will.far...@gmail.com> > 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. > > > > 2012/3/23 superabe superabe <super...@gmail.com> > >> I disagree. I think Spark skinning was the best thing to happen to Flex. >> It makes it possible to do some insanely custom skins that I would have >> shuddered to think about attempting to do with Halo >> >> Yes it makes it harder to simply style based skinning initially, but if >> you >> use that a lot, its possible to build that style support in in your core >> component class, once and then reuse. >> It's a tradeoff that I am completely happy to make. >> >> One important piece to skinning in Spark is to understand the Catalyst >> workflow. >> I realize the product itself is discontinued, but even at the state its >> in, >> it great for taking assets from designers and generating FXG graphics or >> even mxml skin code, that you can then use in your Flex app. >> >> superabe >> >> On Fri, Mar 23, 2012 at 8:25 PM, Richard Oren <roren...@gmail.com> wrote: >> >> > I am not sure what you were trying to do... but with a little bit of >> > research you should have been able to still use Flex 4 for your project. >> > There is a learning curve to get behind the concept so I have felt your >> > pain before but if you stick with it it does get somewhat easier. I have >> > had to resort back to OLD school ways and Draw a lot of graphical stuff >> for >> > Mobile Development with the Drawing API, but for desktop stuff you >> should >> > be able to go with MXML. >> > >> > >> > >> http://blog.flexexamples.com/2009/11/04/setting-a-custom-horizontal-scroll-bar-skin-on-a-spark-list-control-in-flex-4/ >> > >> > Hang in there! You can Do it! :) >> > >> > On Fri, Mar 23, 2012 at 3:44 PM, Cortlandt Winters < >> c...@cortwinters.net >> > >wrote: >> > >> > > Hi Will, >> > > >> > > I do have a prediction. And it's not a dire one. >> > > >> > > It's true what you say, but though this is an area that the flex >> > > components most need some TLC in, I'm confident that it's the one area >> > that >> > > it's most likely to get it. >> > > >> > > As for predictions, I predict that Adobe will do what it said it will >> do >> > > and it will leave Flex "5?" in a pretty stable state. It will take >> some >> > > time for folk to get familiar with the apache process and the >> framework >> > and >> > > to determine how to deal with scrolling on mobile apps that have a >> whole >> > > new level of performance requirement, but that there are going to be >> > plenty >> > > of opportunities to make both web based apps easy to skin and mobile >> ones >> > > performant. >> > > >> > > The toughest part about taking flex and making it open source is that >> > most >> > > flex users are not component developers, they are end user app >> > developers, >> > > but as far as folk that are comfortable with styling and skinning >> there >> > > should be a lot of easily available expertise to create a good system. >> > > >> > > >> > > On Fri, Mar 23, 2012 at 6:16 PM, Williams Farias < >> will.far...@gmail.com >> > > >wrote: >> > > >> > > > Greatings everyone, >> > > > >> > > > I´d like to know why does Spark skining is so dificult to get a >> simple >> > > > result. >> > > > >> > > > I´m building now a web application and I need just to skin the >> > ScrollBar. >> > > > Ok, in Flex3 i just open my Flash CS5, create a new Symbol and >> "Export >> > > for >> > > > actionscript". Then i just add 4 new lines in my CSS style code, and >> > its >> > > > done. I have now a simple and 2 minuts made scrollbar. >> > > > >> > > > But in Spark component... ohhh, what a brutal work i´d had to >> take... >> > > > create a new Style... and put everything on the code... ohhh man, >> > thats a >> > > > really waste of time with hundreds of codes lines and without a >> design >> > > > interface to see how it looks like... in my opinion its too much >> work >> > for >> > > > such a little result! >> > > > >> > > > Just because of that scrollbar man, i had to decide to use Flex 3 >> > insted >> > > of >> > > > 4!!! A simple and mediocre scrollbar skin! >> > > > >> > > > I was wondering: how can the most simple thing to do in Flex could >> be >> > > > transformed in a bunch of lines and hard work as that scrolllBar >> skin? >> > > > >> > > > If i could propose something to chance in the next releases of Flex, >> > is a >> > > > mix of Halo and Spark Skins. I think that Flex3 skinning is much >> more >> > > > simple and intelligent to do. >> > > > >> > > > Antoher thing that frightened me was to read that Adobe will not >> update >> > > > more the Design View of Flash Builder! Does Apacge group have any >> > > > prediction about this? >> > > > >> > > > Thanks! >> > > > >> > > > Williams Farias >> > > > >> > > >> > >> > >
