[Seaside] Using Mewa with Seaside 2.6 or higher..
garduino at gmail.com
Tue Aug 8 10:27:24 UTC 2006
I'm using Mewa with Seaside 2.6b without problems.
As Philippe says, components with different renderers (managed by the
#rendererClass) works ok together.
The thing to take in account is that the olders no-canvas components
need some adjustment to work with canvas api. I've done this to a
complete project in a couple of hours (to one part of the project).
The part that includes Mewa work with the old api without problems and
2006/8/8, Philippe Marschall <philippe.marschall at gmail.com>:
> 2006/8/8, Rick Flower <rickf at ca-flower.com>:
> > While I realize that this was asked about a month ago regarding Mewa use
> > with Seaside 2.x, I'm curious if anyone has tried using Mewa with
> > Seaside 2.6x specifically.. I've got existing code I'm working on that
> > uses the new Canvas API and am curious as to whether or not Mewa would
> > mix in that environment (mixed Canvas vs. old API) or does Seaside get
> > sea sick with that (sorry couldn't resist!)?
> > Also, In my case I'm using VisualWorks, so I gather that some changes
> > may not have been done on this variant perhaps.. So, is anyone using or
> > tried using the current Mewa on a newer Seaside?
> Components, with different renderers should work beside each other.
> Halos are a prime example for this. That's why there is #rendererClass
> on the component not on the application. The VW port of seaside is
> actually quite up to date these days.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
Germán S. Arduino
More information about the Seaside