[Seaside] Design of WAComponent(s)
stephane.ducasse at free.fr
Thu Mar 6 19:04:07 UTC 2008
I'm far from a newbie (at least I believe it) and this is boring to
develop from scratch the same. I imagine that lot of people reuse
their own component.
When I write a desktop app, I'm not a newbie still I like to reuse
window, buttons and label.
At least I'm not interested in knowing how scrollbar and other details
Where is the newbie here?
Why people like to take extreme statements.
On Mar 6, 2008, at 7:25 PM, Ramon Leon wrote:
>> You mean the point is Seaside must apply as a Vi kind of
> No, Vi was just an example. My point is it's a false assumption
> that every
> program *must* be friendly to newbs to be successful or worth using.
> Not that Seaside is that difficult, but the goal shouldn't be trying
> to hand
> hold people who don't know anything about web development,
> Ajax and try and make web developers out of them. The goal is a
> better web
> framework for *web developers*. If you don't know much about web
> development, you've got things you need to learn before you pick up
>>> core framework. It'd be great to have a wide variety of component
>>> options, no one disputes that, they just don't belong in the core
>> This very important. None is questioning what the core of
>> Seaside has to be made of. I'm happy with the taken path for
>> 2.9. In any case Seaside must care for the interest of the
>> better preserve and mature the good platform it is.
>> The things we create *on* it are just talking about the
>> richness it provides.
>> Something good can grow from it beacouse is a solid fundation.
> And that's the main point, Seaside is the foundation, it's not
> supposed to
> be the ultimate component library nor should it try to be, that's
> not what
> frameworks are for. Frameworks serve as the foundation of such
> Ramon Leon
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside