<div class="gmail_quote">On Tue, Dec 30, 2008 at 10:35 AM, Miguel Enrique Cobá Martínez <span dir="ltr"><<a href="mailto:m.coba.m@gmail.com">m.coba.m@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="Wj3C7c">Lukas Renggli wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Over a month has passed since the last release of Seaside 2.9. We are<br>
very pleased to announced Seaside 2.9 Alpha 2 as a next step towards<br>
the release of Seaside 2.9.<br>
<br>
We've mainly worked on two things: (1) closing critical issues that<br>
have been collected in the bug tracker, and (2) making different<br>
configurations of Seaside a snap to load.<br>
<br>
<br>
1. Closed Issues<br>
================<br>
<br>
- Issue 3: A RESTful configuration editor would be very useful<br>
- Issue 87: ColorValue>>hex fixes<br>
- Issue 126: review request handler documentation<br>
- Issue 165: consider WAPainter refactoring<br>
- Issue 193: do we really need #vmStatisticsReportString?<br>
- Issue 200: Seaside 2.9 project page on SqueakSource outdated<br>
- Issue 206: check weird #value call on block in WADebugErrorHandler<br>
- Issue 211: deprecate the scriptcaulous convenience methods on Canvas<br>
- Issue 216: RSS Changes demo produces invalid XML<br>
- Issue 218: WADispatcherEditor doing a #call: in #initialRequest:<br>
- Issue 219: Why does WADecorationTask override #updateStates: ?<br>
- Issue 227: #halt should always halt<br>
- Issue 228: Move the Swazoo server adapter over to WAServerAdaptor<br>
- Issue 234: Source code view is broken after painter refactoring<br>
- Issue 240: JSJsonTests are not portable<br>
- Issue 241: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index<br>
- Issue 242: Using a niladic actionBlock with on:do: in not portable<br>
- Issue 245: WAHalo Source View is broken<br>
- Issue 246: Anchor callbacks should not accept blocks with one argument<br>
- Issue 249: WATree broken in example browser<br>
- Issue 250: JQuery Droppable does not seem to work right<br>
- Issue 251: Accepting code in the browser opens a deprecation warning in Pharo<br>
- Issue 254: Sourceview via halo does not seem to work<br>
- Issue 256: Setting the default entry point does not seem to work<br>
- Issue 258: Bad XHTML for versionuploader<br>
- Issue 259: Request modification to WAPlatformTest>>#testIsResumable<br>
<br>
... and uncounted enhancements to the core code and various other<br>
optional packages such as JQuery, JQuery-UI, Swazoo Server Adapters,<br>
etc. We've further improved portability to other Smalltalk dialects,<br>
in this round we mostly focused on VA Smalltalk.<br>
<br>
<br>
2. The Seaside Builder<br>
======================<br>
<br>
We are proud to announce the Seaside Builder, the tool that makes it a<br>
snap to load a specific set of Seaside 2.9 packages into any recent<br>
Pharo or Squeak image:<br>
<br>
<a href="http://builder.seaside.st" target="_blank">http://builder.seaside.st</a><br>
<br>
The Seaside Builder lets you either select a predefined configuration<br>
of Seaside packages or manually choose the packages you need. The<br>
builder automatically ensures that all prerequisites are selected and<br>
loaded in the right order. For the first time it is possible to<br>
conveniently choose between the MIT licensed Comanche or the LGPL<br>
licensed Swazoo web server.<br>
<br>
At the bottom of the page there are two download options available:<br>
"Load Script" creates a change-set that can be dragged onto any image<br>
causing it to load the selected Seaside packages. There is also the<br>
possibility to download a "Monticello Configuration" of the selected<br>
packages. In the future more download options might become available.<br>
<br>
<br>
3. Things to be aware of<br>
========================<br>
<br>
First of all, it is important to remember that this is an Alpha<br>
release and therefore might not be suited to be used in production. We<br>
are however rapidly approaching the beta phase and disruptive changes<br>
are unlikely. Some of the core team members are already using Seaside<br>
2.9 in production.<br>
<br>
You'll find a list of current migration issues at<br>
<a href="http://seaside.st/documentation/migration/28to29" target="_blank">http://seaside.st/documentation/migration/28to29</a>.<br>
<br>
<br>
4. When things go wrong<br>
=======================<br>
<br>
If you run into problems or encounter problems, please let us know<br>
using the 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> or through the mailing<br>
list. We are especially interested into feedback concerning "The<br>
Seaside Builder".<br>
<br>
</blockquote></div></div>
Congratulations, thanks for the hard work. We really appreciate it.<br><font color="#888888">
<br>
Miguel Cobá</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br><div>Hi Lukas, thanks for getting this out in the wild and you and the</div><div>development team has done a great job. Next, are there any development</div><div>images that contain Seaside 2.9 Alpha? Well, thanks again for the</div>
<div>great work.</div><div><br></div><div>-Conrad</div><div><br></div>