incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Williams Farias <>
Subject Re: Halo x Spark
Date Sat, 24 Mar 2012 04:04:36 GMT
Hi Richard,

Thanks for the reply, but i dont think you got the point i try to explain.
Ok, there are some ways on Spark to skin the scrollbar, or to put a
background image, but thats not the point here.
The thing is not if you can or if you cant skin an component. I´ve already
seem the link you pass, and I´ve problably seem all the exemples on the web
about Flex4 Spark components. Thats why i choose Flex3. I havent seem
nothing so far with Spark Skinning that impressed me, with less work and
more intelligent way to do then Halo components. Thats for me a step back
in the technology: they complicated a lot the way to do a simple job.

Take a look at this:

and more specifically this:

*Man, that thing i can make that in 20 minutes using Flex3 and Flash with a
tablet, even with Photoshop or any other image tool. But show me a way to
skin like this on Spark. With that easiest, its impossible for a "non super
advanced developer". With Halo components, designers skin each component
the way they want (in photoshop or flash) in minutes, and developres just
use them in a 4 lines CSS Flex code! Now on Spark, it seems designers was
eliminated of the process! Adobe dont whant more creative interfaces, only
form based ones with a little make up, and only developers now can skin the
componets with code!

The scrollbar example was just to illustrate how dificult is to do a simple
skin with Spark. Ok, your link skins the component.... but that example
just change the colors. Try do a more specific scrollbar... a more creative
design one... you will spend days and days trying to achieve something that
on Halo you got in minutes; and thats why Flex is (was? had been?) so
impressive! Its about business!

Halo is much, much more simple to skin components - less time (money) and
more clients happy with their really exclusive components (not only changed
colors one). Designers do them on Flash... clients aprove, or do changes on
the fly, and its done. Spark: open flex, work hours and hours to create a
custom skin with just a code view (need to compile hundreds of time to get
it), pray to the client aprove - if disaprove ... more hours of coding
work.. Its too much work, time and money lost to do a such simple thing.
Got this point of view? Does anyone have any news about that: future about
skinning components? Will Spark continues on Apache plans?

I vote: Halo architecture for skinning future!


On that point of view: Flex3 Halo = 10!! Flex4 Spark: 2 ...

2012/3/23 Richard Oren <>

> 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.
> Hang in there! You can Do it! :)
> On Fri, Mar 23, 2012 at 3:44 PM, Cortlandt Winters <
> >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 <
> > >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
> > >
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message