[Seaside-dev] Seaside 3.1 ready

[Dale Henrichs]

Philippe,

Hmmmm, I don't have a lot of extra time right now, to port Seaside3.1 to GemStone and build configurations:( Some advance warning would have been nice... If I'd known you were aiming for a release in this time frame...ah, well...

Regarding the 256 literal limit, would you be amenable to breaking Seaside3.1 up into smaller chunks? I think that it is high time that the configuration for Seaside be revisited and revamped

I have spent zero time looking at Seaside3.1 so I have no idea that's been going on there, but things like the javascript support and REST and JSON and Examples and etc. could actually be managed in separate configurations. Splitting those things out into separate configurations would not only reduce the number of literals needed in the monolithic version spec, but would make it easier for people to understand what is optional and what is required ...

What do you say?

Dale

----- Original Message -----
| From: "Philippe Marschall" <philippe.marschall at gmail.com>
| To: "Seaside - developer list" <seaside-dev at lists.squeakfoundation.org>
| Sent: Tuesday, May 8, 2012 11:51:52 AM
| Subject: [Seaside-dev] Seaside 3.1 ready
| 
| Hi
| 
| I feel Seaside 3.1 ready for release [1]
|  - apart from the usual refactorings and cleanups we managed to fix 2
| of the 3 major regressions in 3.0 [2]
|  - session continuations are now WARequestHandlers
|  - we have a new WAPluggableActionContinuation
|  - the session tracking code has been refactored, it's simpler and
| supports new features
|  - document handlers are no longer stored as sessions
|  - JSON support has been updated
|  - HTML5 support has been updated
| 
| What's missing right now are Metacello configurations. I started
| working on them but would welcome help.
| 
| I updated ConfigurationOfGrease to version 1.1, that was easy but the
| GemStone versions of course still point to 1.0.7. I did not rename it
| to ConfigurationOfGrease11. Dale, should I rename this?
| 
| I started a Seaside configuration named ConfigurationOfSeaside31.
| Dale, is this OK our should I name it ConfigurationOfSeaside30? This
| is a bit more problematic, because I run into the 256 literal limit
| in
| #version310:. I did not add the new packages Seaside-JSON-Core,
| JQuery-JSON and Seaside-REST to any group. Dale, tell we how you want
| this done and I'll do it.
| 
|  [1] http://code.google.com/p/seaside/wiki/Seaside310Changelog
|  [2] http://code.google.com/p/seaside/wiki/BigIssues
| 
| Cheers
| Philippe
| _______________________________________________
| seaside-dev mailing list
| seaside-dev at lists.squeakfoundation.org
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|