[Seaside] ShoreComponents test cases -- worth doing?

Avi Bryant avi.bryant at gmail.com
Sat Jul 23 01:20:02 CEST 2005

On 7/19/05, Pavel Krivanek <squeak3 at continentalbrno.cz> wrote:

> You may look at structure of demo application. The base part of
> resultant page is built from page content and side menu. The side menu
> has subcomponent with anchors. Its actions look like "self target call:
> something". #target is standard method which returns parent target or
> self if no parent is available.

> So we may build very general reusable components. Real root also may
> contain next useful information like session cache.

> Thanks parents we may also use components with nested forms (only the
> most outer form is rendered - formRoot) and assign some attributes to
> this forms (see ShoreRichEdit). Finally we still can use classical
> Seaside components.

These sound like interesting patterns; I'll have to consider whether
to adopt them more widely for Seaside 2.6.  What do others think?

Can you explain #formRoot in more detail?


More information about the Seaside mailing list