mbany at cincom.com
Fri Oct 20 08:35:24 UTC 2006
> Does this mean that going forward I'd have to look at jumping
> my production code over to the 2.7a branch if I want to stay
> up to date with Scriptaculous?
I already tried the port of 2.7a to VW, but did not publish it
because I would like to check how it fits with the other components
(SeasideAsync, SeasideTesting, etc.).
I may also explore another possibility: retrofiting what is
needed by Scriptaculous into 2.6b1.
Just a matter of time...
More information about the Seaside