Hi!<br><br>You could also use my SeasideLoader <br><br>MCHttpRepository<br> location: '<a href="http://www.squeaksource.com/SeasideLoader">http://www.squeaksource.com/SeasideLoader</a>'<br> user: ''<br>
password: ''<br><br>to always load (or check for) the latest Seaside 29 packages.<br><br>It works fine with Pharo and Squeak 3.9!<br>Squeak 3.10 works fine too, only some issues with running the SUnit Tests.<br>
<br>- After loading the package just use "SeasideLoader loadSeaside29WithComanche" to load everything!<br>- To check for new packages use "SeasideLoader checkSeaside29"<br>- To open a workspace use "SeasideLoader openWorkspace"<br>
<br>cheers<br>Gerhard<br><br><br><br><div class="gmail_quote">On Sun, Nov 2, 2008 at 9:58 PM, Julian Fitzell <span dir="ltr"><<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
After months of development, the Seaside Development Team is very<br>
pleased to announce the release of Seaside 2.9 Alpha 1. We are<br>
announcing this first release in stages: first to the developer<br>
mailing list, then the main seaside list, and finally to the website.<br>
We hope this will let us catch any major problems with this first<br>
release as soon as possible.<br>
<br>
Here's what we need to cover:<br>
<br>
1. What's new<br>
2. Things to be aware of<br>
3. How to get it<br>
4. When things go wrong (as they certainly will)<br>
5. How-To's<br>
<br>
<br>
===================<br>
What's new<br>
===================<br>
<br>
The focus of this release has been on flexibility, portability, and<br>
understandability.<br>
<br>
Some highlights include:<br>
<br>
* Sub-packages. The code has been split up. This facilitates porting<br>
because platform-specific code has been put into platform-specific<br>
packages. It also means that you can load only the parts of Seaside<br>
that you need. For example, when building your production image, you<br>
can leave out tests, examples, and development tools.<br>
<br>
* Architectural cleanup. A lot of work has been done under the hood<br>
to rewrite some of the messier parts of Seaside. We introduced a<br>
RequestContext which stores information related to a single HTTP<br>
request, which greatly simplified request handling in general and the<br>
Session object in particular. The RenderLoop has been refactored to be<br>
much more understandable; Server Adaptors have been made more<br>
flexible; the Configuration system was rewritten; and a new pluggable<br>
Cache was introduced to hold sessions and continuations. These are<br>
just a few examples.<br>
<br>
* Reification. Many things that were Strings in Seaside 2.8 are now<br>
first-class objects. For example, we added WAMimeType and WALocale,<br>
and WAUrl and WAExternalID are now used much more consistently<br>
throughout the system.<br>
<br>
* Lots of bug fixes, security improvements, and tests.<br>
<br>
A more complete list of change and new features can be found at<br>
<a href="http://seaside.st/community/development/seaside29" target="_blank">http://seaside.st/community/development/seaside29</a><br>
<br>
In addition, I have been tasked with documenting some of these new<br>
features. I plan to start a series of blog posts in the next few weeks<br>
talking about new features in Seaside 2.9. Keep an eye on<br>
<a href="http://blog.fitzell.ca/" target="_blank">http://blog.fitzell.ca/</a> or keep following the aggregated news on the<br>
Seaside home page: <a href="http://seaside.st/community/weblogs" target="_blank">http://seaside.st/community/weblogs</a><br>
<br>
<br>
=========================<br>
Things to be aware of<br>
=========================<br>
<br>
First of all, it is important to remember that this is an Alpha<br>
release and SHOULD NOT be used in production.<br>
<br>
While we believe that the most disruptive changes are largely<br>
complete, we may still need to make non-backwards-compatible code<br>
changes, rename packages and so on. We are also still trying to work<br>
out some issues with the packaging and distribution tools (now that we<br>
have so many sub-packages) so you would be wise to wait for a Beta<br>
release to begin active development. You have been warned.<br>
<br>
For the average developer using WAComponent, WACanvas, and WASession,<br>
we hope that most things will be pretty backwards-compatible. In fact,<br>
we want you to let us know about anything you find that is not (see<br>
below for details about reporting problems). You'll find a current<br>
list of migration issues at<br>
<a href="http://seaside.st/documentation/migration/28to29" target="_blank">http://seaside.st/documentation/migration/28to29</a><br>
<br>
We have moved or renamed quite a few methods (particularly on<br>
WASession). Whenever possible, the old methods should have been marked<br>
as deprecated; you will be alerted about any call to a deprecated<br>
method when using your application with the Toolbar turned on. These<br>
deprecated methods will be removed in the next major version of<br>
Seaside and you should make every effort to update any code that is<br>
using them. If you find that a method you were using has disappeared<br>
without being deprecated, please let us know (again, see below) so<br>
that we can correct this.<br>
<br>
<br>
==================<br>
How to get it<br>
==================<br>
<br>
If you've made it this far, you must want to try the thing. We're<br>
still experimenting with the best way to distribute all these<br>
packages. In the meantime, we didn't want to hold up the release so we<br>
are providing load scripts to get you going.<br>
<br>
Two scripts are included with this email. The first will install most<br>
of the available Seaside 2.9 packages and give you a working system.<br>
The second will install the test packages. After loading, all tests<br>
should pass.<br>
<br>
We have tested the load scripts in the following images:<br>
<br>
* Squeak 3.9: <a href="http://ftp.squeak.org/3.9/Squeak3.9.1-final-7075-withSources.zip" target="_blank">http://ftp.squeak.org/3.9/Squeak3.9.1-final-7075-withSources.zip</a><br>
* Pharo: <a href="http://gforge.inria.fr/frs/download.php/10409/Pharo0.1-10107-oneclick.zip" target="_blank">http://gforge.inria.fr/frs/download.php/10409/Pharo0.1-10107-oneclick.zip</a><br>
<br>
They will probably also work in Squeak 3.10 but this has not been tested.<br>
<br>
DO NOT attempt to load Seaside 2.9 into an existing 2.8 image: it<br>
won't work. If you want to try porting an existing application, start<br>
with a clean image, load Seaside, then load your own application<br>
packages.<br>
<br>
<br>
=================================================<br>
When things go wrong (as they certainly will)<br>
=================================================<br>
<br>
If (when) you run into problems, please visit our issue tracker at<br>
<a href="http://code.google.com/p/seaside/issues/list" target="_blank">http://code.google.com/p/seaside/issues/list</a> to see if the problem has<br>
already been reported. You can also check the migration page at<br>
<a href="http://seaside.st/documentation/migration/28to29" target="_blank">http://seaside.st/documentation/migration/28to29</a> to see if the problem<br>
has been mentioned.<br>
<br>
If you are convinced your problem is unreported, either file a new<br>
issue in the tracker or post it to the developers mailing list (<br>
<a href="http://seaside.st/community/mailinglist" target="_blank">http://seaside.st/community/mailinglist</a> ). We would also be happy to<br>
hear any feedback and to discuss any of the changes in Seaside 2.9 on<br>
that list.<br>
<br>
<br>
============<br>
How-To's<br>
============<br>
<br>
In the absence of updated documentation, here are the answers to a few<br>
questions you might have right off the bat:<br>
<br>
<br>
Q: How do I turn on authentication for an application?<br>
<br>
A: Authentication is now handled by the new RequestFilter mechanism.<br>
Unfortunately, there is currently still no UI support for configuring<br>
RequestFilters. The simplest way to add an authenticated application<br>
is therefore to execute something like this in a workspace:<br>
<br>
WAAdmin<br>
register: MYComponentClass<br>
asApplicationAt: 'myapp'<br>
user: 'juser'<br>
password: 'pass'<br>
<br>
<br>
Q: How do I enable or disable the Toolbar?<br>
<br>
A: This release has the Toolbar enabled by default for all<br>
applications. To disable it, open the configuration application (by<br>
default at <a href="http://localhost:8080/seaside/config" target="_blank">http://localhost:8080/seaside/config</a> ). Under 'Shared<br>
Configurations', click on 'Application Defaults'. Under 'Ancestry',<br>
find WADevelopmentConfiguration and click the 'X' next to it to remove<br>
it. To enable the Toolbar again, simply add WADevelopmentConfiguration<br>
again. To enable the Toolbar in a single application, add<br>
WADevelopmentConfiguration to that application's configuration screen<br>
instead of to 'Application Defaults'.<br>
<br>_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
<br></blockquote></div><br>