ANN: Seaside 2.9a1 release
Locked
12
12
ANN: Seaside 2.9a1 release
 
|
After months of development, the Seaside Development Team is very
pleased to announce the release of Seaside 2.9 Alpha 1. We are announcing this first release in stages: first to the developer mailing list, then the main seaside list, and finally to the website. We hope this will let us catch any major problems with this first release as soon as possible. Here's what we need to cover: 1. What's new 2. Things to be aware of 3. How to get it 4. When things go wrong (as they certainly will) 5. How-To's =================== What's new =================== The focus of this release has been on flexibility, portability, and understandability. Some highlights include: * Sub-packages. The code has been split up. This facilitates porting because platform-specific code has been put into platform-specific packages. It also means that you can load only the parts of Seaside that you need. For example, when building your production image, you can leave out tests, examples, and development tools. * Architectural cleanup. A lot of work has been done under the hood to rewrite some of the messier parts of Seaside. We introduced a RequestContext which stores information related to a single HTTP request, which greatly simplified request handling in general and the Session object in particular. The RenderLoop has been refactored to be much more understandable; Server Adaptors have been made more flexible; the Configuration system was rewritten; and a new pluggable Cache was introduced to hold sessions and continuations. These are just a few examples. * Reification. Many things that were Strings in Seaside 2.8 are now first-class objects. For example, we added WAMimeType and WALocale, and WAUrl and WAExternalID are now used much more consistently throughout the system. * Lots of bug fixes, security improvements, and tests. A more complete list of change and new features can be found at http://seaside.st/community/development/seaside29 In addition, I have been tasked with documenting some of these new features. I plan to start a series of blog posts in the next few weeks talking about new features in Seaside 2.9. Keep an eye on http://blog.fitzell.ca/ or keep following the aggregated news on the Seaside home page: http://seaside.st/community/weblogs ========================= Things to be aware of ========================= First of all, it is important to remember that this is an Alpha release and SHOULD NOT be used in production. While we believe that the most disruptive changes are largely complete, we may still need to make non-backwards-compatible code changes, rename packages and so on. We are also still trying to work out some issues with the packaging and distribution tools (now that we have so many sub-packages) so you would be wise to wait for a Beta release to begin active development. You have been warned. For the average developer using WAComponent, WACanvas, and WASession, we hope that most things will be pretty backwards-compatible. In fact, we want you to let us know about anything you find that is not (see below for details about reporting problems). You'll find a current list of migration issues at http://seaside.st/documentation/migration/28to29 We have moved or renamed quite a few methods (particularly on WASession). Whenever possible, the old methods should have been marked as deprecated; you will be alerted about any call to a deprecated method when using your application with the Toolbar turned on. These deprecated methods will be removed in the next major version of Seaside and you should make every effort to update any code that is using them. If you find that a method you were using has disappeared without being deprecated, please let us know (again, see below) so that we can correct this. ================== How to get it ================== If you've made it this far, you must want to try the thing. We're still experimenting with the best way to distribute all these packages. In the meantime, we didn't want to hold up the release so we are providing load scripts to get you going. Two scripts are included with this email. The first will install most of the available Seaside 2.9 packages and give you a working system. The second will install the test packages. After loading, all tests should pass. We have tested the load scripts in the following images: * Squeak 3.9: http://ftp.squeak.org/3.9/Squeak3.9.1-final-7075-withSources.zip * Pharo: http://gforge.inria.fr/frs/download.php/10409/Pharo0.1-10107-oneclick.zip They will probably also work in Squeak 3.10 but this has not been tested. DO NOT attempt to load Seaside 2.9 into an existing 2.8 image: it won't work. If you want to try porting an existing application, start with a clean image, load Seaside, then load your own application packages. ================================================= When things go wrong (as they certainly will) ================================================= If (when) you run into problems, please visit our issue tracker at http://code.google.com/p/seaside/issues/list to see if the problem has already been reported. You can also check the migration page at http://seaside.st/documentation/migration/28to29 to see if the problem has been mentioned. If you are convinced your problem is unreported, either file a new issue in the tracker or post it to the developers mailing list ( http://seaside.st/community/mailinglist ). We would also be happy to hear any feedback and to discuss any of the changes in Seaside 2.9 on that list. ============ How-To's ============ In the absence of updated documentation, here are the answers to a few questions you might have right off the bat: Q: How do I turn on authentication for an application? A: Authentication is now handled by the new RequestFilter mechanism. Unfortunately, there is currently still no UI support for configuring RequestFilters. The simplest way to add an authenticated application is therefore to execute something like this in a workspace: WAAdmin register: MYComponentClass asApplicationAt: 'myapp' user: 'juser' password: 'pass' Q: How do I enable or disable the Toolbar? A: This release has the Toolbar enabled by default for all applications. To disable it, open the configuration application (by default at http://localhost:8080/seaside/config ). Under 'Shared Configurations', click on 'Application Defaults'. Under 'Ancestry', find WADevelopmentConfiguration and click the 'X' next to it to remove it. To enable the Toolbar again, simply add WADevelopmentConfiguration again. To enable the Toolbar in a single application, add WADevelopmentConfiguration to that application's configuration screen instead of to 'Application Defaults'. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
seaside-2-9-0a1.cs (5K)
Re: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
Re: Seaside 2.9a1 release
|
|
Re: Re: Seaside 2.9a1 release
|
|
Re: Re: Seaside 2.9a1 release
|
|
Re: Re: Seaside 2.9a1 release
|
|
Re: Seaside 2.9a1 release
|
|
Re: Re: Seaside 2.9a1 release
|
|
Re: Re: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
2008/11/15, Philippe Marschall <[hidden email]>:
> 2008/11/11, Lautaro Fernández <[hidden email]>: >> Hi, >> >> 2008/11/9 Julian Fitzell <[hidden email]> >> >>> [...] >>> A more complete list of change and new features can be found at >>> http://seaside.st/community/development/seaside29 >>> >> >> That page (under Modularization) says the following: >> >> [...] >> >> It allows for smaller Seaside installations. For example you can have >>> Seaside without the tests or without Kom and use Swazoo 2 instead. >> >> [...] >>> >> >> This mean that just a few changes need to be made in order to get a >> working >> Swazoo-Seaside server? > > It means no changes need to be made. Swazoo 2.1 is supported out of > the box (well in theory at least, in practice it has only been tested > on Squeak). > >> Could you tell me a place to see a how-to use this modularity in order to >> make the port of Swazoo to work with Seaside? > > To get everything working in Squeak you need to: > - open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo loaded > - drag and drop the attached file over the Squeak window > - select "fileIn entire file" > - if a debugger opens telling you that instance variables start with a > lower case letter hit proceed > - when everything is done evaluate > WASwazooAdaptor startOn: 8080 > - go to http://127.0.0.1:8080/seaside/tests/alltests > > If you open the Monticello Browser from the world menu you'll see a > lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-* > packages that make up Seaside. Everything that has no -Squeak- in the > package name should load directly into VW. Everything that has a > -Squeak- in the package name has to be reimplemented (only if you want > it of course). However most parts can probably be salvaged either from > the existing 2.8 port or the Squeak implementation. > > Cincom supports Seaside so it's probably best to talk to them. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: ANN: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
2008/11/17, Lautaro Fernández <[hidden email]>:
> 2008/11/15 Philippe Marschall <[hidden email]> > >> 2008/11/11, Lautaro Fernández <[hidden email]>: >> > Hi, >> > >> > 2008/11/9 Julian Fitzell <[hidden email]> >> > >> >> [...] >> >> A more complete list of change and new features can be found at >> >> http://seaside.st/community/development/seaside29 >> >> >> > >> > That page (under Modularization) says the following: >> > >> > [...] >> > >> > It allows for smaller Seaside installations. For example you can have >> >> Seaside without the tests or without Kom and use Swazoo 2 instead. >> > >> > [...] >> >> >> > >> > This mean that just a few changes need to be made in order to get a >> working >> > Swazoo-Seaside server? >> >> It means no changes need to be made. Swazoo 2.1 is supported out of >> the box (well in theory at least, in practice it has only been tested >> on Squeak). >> >> > Could you tell me a place to see a how-to use this modularity in order >> > to >> > make the port of Swazoo to work with Seaside? >> >> To get everything working in Squeak you need to: >> - open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo >> loaded >> - drag and drop the attached file over the Squeak window >> - select "fileIn entire file" >> - if a debugger opens telling you that instance variables start with a >> lower case letter hit proceed >> - when everything is done evaluate >> WASwazooAdaptor startOn: 8080 >> - go to http://127.0.0.1:8080/seaside/tests/alltests >> > > All ran OK, except to save the image. The WASqueakPlatfrorm (class) does not > understand the method "withName:withPriority:fork:", which is called from > the CTPusher(classs)>>startUp. I commented that part and the where no more > troubles anymore. > About the first seaside-2-9-0a1.cs that Julian had attached, I keep getting > an error if I tried to load it on a fresh Squeak 3.9 image. > Internal Server Error > MessageNotUnderstood: WAKom>>dispatchRequest: > > I'm loading it wrong? (this didn't happened to me on last Thursday) Nope the script is wrong. It should load Seaside-Core-jf.320. It's probably time to publish an alpha2 script. >> If you open the Monticello Browser from the world menu you'll see a >> lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-* >> packages that make up Seaside. Everything that has no -Squeak- in the >> package name should load directly into VW. Everything that has a >> -Squeak- in the package name has to be reimplemented (only if you want >> it of course). However most parts can probably be salvaged either from >> the existing 2.8 port or the Squeak implementation. > > > Good to know, thank =] > > >> Cincom supports Seaside so it's probably best to talk to them. > > > The main problem is that they will port (or made it avaible) Seaside 2.9 for > the next realise (which will be in US summer), but now we need to work with > Swazoo instead of Opentalk-Http (which does not support streaming responses > quite well). > But I'll try again to see if they can give me a workaround. very latest code from yesterday evening. It has seen only very little testing. It loads almost everything including both Comanche and Swazoo because we only implemented Comet on Comanche. However the Seaside Control Panel now seems to work. You'll find it in the world menu under tools. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: ANN: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
Re: ANN: Seaside 2.9a1 release
|
|
Re: Seaside 2.9a1 release
|
|
| Free forum by Nabble | Edit this page |