[Seaside] Join forces
philippe.marschall at gmail.com
Tue Aug 29 20:29:28 UTC 2006
2006/8/29, Pavel Krivanek <squeak3 at continentalbrno.cz>:
> On 8/29/06, stephane ducasse <stephane.ducasse at free.fr> wrote:
> > > I think that we should look at current Seaside, Magritte,
> > > ShoreComponents and other projects and find a way how to increase code
> > > reusability.
> > PLEASE DO!!!
> > Each time I ask people about shoreComponents they told me that they
> > were not
> > usable as any other seaside components and I found that sad. because
> > we need
> > a library of standard reusable components. So what you are doing is
> > important.
> Yes, this was the most painful decision during desing of
> ShoreComponents. But the changes had IMHO very good reasons and they
> were done for better reusability of this components. The main change
> is adding of obligatory parent reference that enables to control the
> components hierarchy, use embedded forms etc.
> The big problem is that every bigger set of components use own basic
> component class - and the main motivation is to do not break the old
> code. ShoreComponents adds parent reference and attributes and
> Magritte overrides constructors etc.
Magritte-Model-lr.224 and Magritte-Seaside-lr.192, add _zero_
overrides, class extensions or constructors to Seaside. MAComponent
is basically a small collection of convenience methods. The added
concept of abstractness affects only the creation of subclasses and is
not needed to integrate into Magritte. Magritte plays well together
with standard seaside components that are not subcomponents of
MAComponent. Same goes the other way around, you can use Magritte
components anywhere standard seaside components work.
The only "conflicts" are #description and #asComponent. If you want to
use these (describe your components with Magritte), you need Magritte
specific code anyway.
More information about the Seaside