[Seaside] Design of WAComponent(s)

[stephane ducasse]

Hi sebastian

I still see the point of andreas.
I would love to have a usable report widget in which I can plug other  
components.
I already sent that a while back but once I show Seaside to a guy at  
microsoft.
He was impressed then after 3 min he asked me how many widgets are  
ready to use.
And he was right.

There are no incompatibilities between seaside as it is now and a cool  
widgets set.
Having a cool widgets set with basic but fully working widgets would  
be a big plus: we could
prototype even faster our applications. I do not have the skills and  
time of lukas
to create widgets from scratch. But I imagine that I should be able to  
reuse them.

Stef


On Mar 6, 2008, at 5:10 PM, Sebastian Sastre wrote:

>> -----Mensaje original-----
>> De: seaside-bounces at lists.squeakfoundation.org
>> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
>> de Philippe Marschall
>> Enviado el: Miércoles, 05 de Marzo de 2008 17:25
>> Para: Seaside - general discussion
>> Asunto: 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
>>
>
> Quoting you:
> "...They are not made with reusabilty, configurabitlity or  
> customyzability in mind..."
>
> Quoting Seaside site:
> "About
> Seaside provides a layered set of abstractions over HTTP and HTML  
> that let you build highly interactive web applications quickly,  
> reusably and maintainably.
> ..."
>
> Note that *reusably* is the second *bold* word after quickly.
>
> And also (from same source):
> "...Embedded components. Stop thinking a whole page at a time;  
> Seaside lets you build your UI as a tree of individual, stateful  
> component objects, each encapsulating a small part of a page. Often,  
> these can be used over and over again, within and between  
> applications - nearly every application, for example, needs a way to  
> present a batched list of search results, or a table with sortable  
> columns, and Seaside includes components for these out the box..."
>
> So?
>
> Sebastian
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>