[Seaside] Join forces
stephane ducasse
stephane.ducasse at free.fr
Tue Aug 29 19:28:36 UTC 2006
On 28 août 06, at 14:40, Pavel Krivanek wrote:
> Hi all,
>
> I'm creating ShoreComponents layout for Magritte and I see some
> compatibility problems that originate from differences between common
> Seaside components and ShoreComponents. I have solved it but it also
> ment to create the modified stand-alone copy of all classes in
> Magritte-Seaside. This is not good way to go.
>
> 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.
> Conceive it as optional modules of one big framework that
> together with persistency model can bring more easy way how to create
> Seaside applications.
>
> Traits may be the good answer on some issues but we don't want to
> break VW compatibility.
>
> Any suggestions and comments?
>
> -- Pavel
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
More information about the Seaside
mailing list