flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cortlandt Winters <c...@cortwinters.net>
Subject Re: Why Spark? (was Re: s:Spacer (was Re: Missing Spark components))
Date Sat, 03 Mar 2012 20:14:16 GMT
I hope I didn't come on too strong with my tone. I agree that we're not
really differing much.

And I do agree that spark is a better architecture from a programmers point
of view and for the long term. The point that I was trying to make is that
many flex users both in the past and in the future will never develop a
single user interface component. The architecture is not so important to
them as the end user facing features. How easy it is to develop a carosel
is unimportant to them, because it's outside of what they are focused on,
regardless of architecture.

They are really php or coldfusion developers that wear a half a dozen
different hats and manage every part of their project from gathering the
content to the database, the server configuration and hosting, to the user
interface. For these folk the mx components gave them the ability to create
pretty nice user interface without having to learn about flex's internals.

It's not having to add a horizontal layout, it's that when a client says
"can you change the thumb of the scrollbar so that it's dark and the track
so that it is light" that you can do so without overriding 8 classes.

Anyway I hope I didn't waste too much of your time here. I'll shift my
energy into doing something useful rather than talking about it now.

I'm pretty happy with where flex is now really and I definitely feel
empowered to fix what I'm not happy with because of this move to Apache.

On Fri, Mar 2, 2012 at 9:40 PM, Michael A. Labriola <
labriola@digitalprimates.net> wrote:

> >...When the little guy was pushed out.
> > Most projects can't create components for the project. Most projects use
> components to build the project. That's why they are called components.
> I need to respond to this one separately because I think this point is
> absolutely false and incorrect.
> In the old framework you had a List and a HorizontalList.
> <mx:List/> <mx:HorizontalList/>
> Now you have to type this:
> <s:List/>
> <s:List>
>        <s:layout>
>                <s:HorizontalLayout/>
>        </s:layout>
> </s:List>
> So, to clarify, the difference in this syntax pushes the little guy out?
> These extra lines of code are the difference between success and failure?
> To me, that can't be true. If anything, while more verbose Spark is
> infinitely friendlier to the little guy. In mx, as soon as you wanted to do
> anything different, your only choice was to hire a component developer to
> extend/copy/rewrite these classes. Take for example a circular or carousel
> list. You can create a layout object for a circular list in a hundred lines
> of code in Spark. Since I did this in mx, I will let you know it's a
> thousand plus. If you wanted to change the headers of a datagrid in mx,
> several hundred lines of cut and paste plus maintaining a component
> extension version to version of framework changes. In Spark, you change a
> skin. Sorry, to me spark is verbose not harder, and it doesn't push anyone
> out. Its friendlier to businesses who do not have the budget or dedicated
> staff for component development.
> BTW, if the extra lines bother someone, then create a library calls spark
> basic, which does nothing but extend list and set the horizontal layout...
> then the syntax is nearly identical.
> IMO, the complaining about spark doesn't address the actual issue. There
> is nothing harder about it. It is different. The things I mentioned earlier
> in this thread have absolutely nothing to do with how mx or spark would be
> used by the average developer.  It is all internal architecture and doing
> so would in no way affect someone who didn't want to use it.
> Mike

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