Hi
This is just a reminder, there are heavy refactorings going on and some things don't work yet fully. Also remember that loading Seaside 2.8 into an image that has Seaside 2.7 will break this image irrecoverably. Cheers Philippe _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> This is just a reminder, there are heavy refactorings going on and
> some things don't work yet fully. Exactly, I just wanted to write the same ;-) > Also remember that loading Seaside 2.8 into an image that has Seaside > 2.7 will break this image irrecoverably. This is because there was a compiler hack in Seaside 2.7 and earlier were that is luckily not needed anymore in 2.8. Unfortunately loading 2.8 into a 2.7 removes some important methods from the compiler causing the image to irrecoverably freeze. Before loading you need to remove all the old Seaside extension methods from the Seaside package. Unfortunately I don't see a simpler solution ... To give an update on the status: - Cleanup of WARoot, WADocument and friends. - Tests and much more comments for WACanvas, WABrush and friends. - Better and more efficient encoding of URLs and XHTML. - Got rid of WAHtmlRenderer and all its former users. - Removed unused code. Still ongoing are the following tasks: - We are working on major speed optimizations, depending on the application Seaside 2.8 is already up to twice as fast as earlier versions. - I am currently investigation ways to reduce the per session memory consumption. No figures available yet. - The responsabilities of WARenderer, WARenderLoop, WASession, WARenderingContrext are not clear. Especially the session contains a lot of request related things, that should not be there. - New implementation of state backtracking. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> To give an update on the status:
> > - Cleanup of WARoot, WADocument and friends. > - Tests and much more comments for WACanvas, WABrush and friends. > - Better and more efficient encoding of URLs and XHTML. > - Got rid of WAHtmlRenderer and all its former users. > - Removed unused code. > > Still ongoing are the following tasks: > > - We are working on major speed optimizations, depending on > the application Seaside 2.8 is already up to twice as fast as > earlier versions. > - I am currently investigation ways to reduce the per session > memory consumption. No figures available yet. > - The responsibilities of WARenderer, WARenderLoop, > WASession, WARenderingContrext are not clear. Especially the > session contains a lot of request related things, that should > not be there. > - New implementation of state backtracking. > > Cheers, > Lukas All this stuff sounds great. Given that you're a core developer, much of this stuff would make good post material for your blog. I'd sure love to read about your experiences, good and bad, and get more insight into the thinking behind the changes. Maybe even invite some of the other core developers on as guest bloggers to write about their trials and tribulations. For any of you core developers who don't already have a blog, you're more than welcome to be a guest blogger on my blog, onsmalltalk.com. I can't think of any topic I'd rather be reading about on blogs, than Seaside. Ramon Leon http://onsmalltalk.com _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I second Ramon's suggestion! I think this will also alleviate the
other big headache Smalltalk/Seaside learners like myself have in documentation. Sausheong http://blog.saush.com - brain dump On 10 Apr 2007, at 11:43 PM, Ramon Leon wrote: >> To give an update on the status: >> >> - Cleanup of WARoot, WADocument and friends. >> - Tests and much more comments for WACanvas, WABrush and friends. >> - Better and more efficient encoding of URLs and XHTML. >> - Got rid of WAHtmlRenderer and all its former users. >> - Removed unused code. >> >> Still ongoing are the following tasks: >> >> - We are working on major speed optimizations, depending on >> the application Seaside 2.8 is already up to twice as fast as >> earlier versions. >> - I am currently investigation ways to reduce the per session >> memory consumption. No figures available yet. >> - The responsibilities of WARenderer, WARenderLoop, >> WASession, WARenderingContrext are not clear. Especially the >> session contains a lot of request related things, that should >> not be there. >> - New implementation of state backtracking. >> >> Cheers, >> Lukas > > All this stuff sounds great. Given that you're a core developer, > much of > this stuff would make good post material for your blog. I'd sure > love to > read about your experiences, good and bad, and get more insight > into the > thinking behind the changes. Maybe even invite some of the other core > developers on as guest bloggers to write about their trials and > tribulations. > > For any of you core developers who don't already have a blog, > you're more > than welcome to be a guest blogger on my blog, onsmalltalk.com. > > I can't think of any topic I'd rather be reading about on blogs, than > Seaside. > > Ramon Leon > http://onsmalltalk.com > > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |