[Seaside] Design of WAComponent(s)

Boris Popov boris at deepcovelabs.com
Wed Mar 5 20:32:59 UTC 2008

+1, for example there's no way I could see a standard "login" component work for us, let alone anything else that I can think of. Components is something you build as you make up your own application, its not something you take off the shelf and plug in.


DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Philippe Marschall
> Sent: Wednesday, March 05, 2008 12:25 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Design of WAComponent(s)
> 2008/3/5, Andreas Tönne <atoenne at cincom.com>:
> > ....
> I think the main point to understand here is that the components that
> come with Seaside are not a component library or even a component
> framework. They are simple stand alone components. They are not made
> with reusabilty, configurabitlity or customyzability in mind. They are
> focused on KISS and "getting the job done" and mostly for use Seaside
> itself. They will get you started fast but at one point sooner rather
> than later you will hit their limits. That's ok, they're not supposed
> to be the "be all, end all".
> The points you made IMHO apply only if you want to build a component
> library or even component framework. That should be an addon protect
> and has no place in Seaside-Core. Honestly I have my doubts if such a
> such thing could ever work given the very special needs of users
> concerning not only functionality but also mark up.
> Cheers
> Philippe

More information about the seaside mailing list