You are currently browsing the monthly archive for April 2008.
The beta includes the following features:
- Primitive support for UTF8 encoding (100x faster than Smalltalk-based algorithm).
- Primitive support for HTML encoding.
- Thread local support for GsProcess and continuations. Thread locals are being used in Seaside2.9.
- Improved ProfMonitor output code moved from GLASS-only to base image.
The beta is shipped with GLASS.230-dkh.130 and GemStone-dkh.270 (both can be found in the GLASS project on GemSource). GLASS.230-dkh.130 is equivalent to GLASS-dkh.114, except for references to the UTF8 and HTML encoding primitives.
A version of the appliance based upon 2.3 beta 1 will be available shortly.
I’ll be giving a technical presentation at Smalltalk Solutions entitled “GLASS: Share Everything”:
Seaside has been characterized as a “heretical” framework because it breaks many of the widely-accepted “best practices” for web applications, including “share as little state as possible.” With GLASS (GemStone/S, Linux, Apache, Seaside, Smalltalk) GemStone takes this heresy to the next level where “everything is shared” – transparently and persistently….
According to the preliminary schedule, I will be talking on June 20th from 9:15am to 10:00am.
James Foster will be giving a tutorial entitled “Building a Seaside Application (with GLASS)”:
James’ tutorial is scheduled for June 19th from 1:30pm to 5:00pm.
The conference will be held June 18-21, 2008 in Reno, Nevada, so if you haven’t already signed up, get busy and register!
While the 2.3 beta for GemStone/S and the next version of the appliance are going through production, I’ve started working on my next project for GLASS which is to get to the point where one can load the OB-Enhancements package into GemStone/S.
When I first ported OmniBrowser to GemStone, I cloned the OB-Standard package and renamed all of the classes to use an ‘OG’ prefix (rather than ‘OB’). At the time I was concerned that I might need an implementation for the ‘OG’ classes in the Squeak (client) side and I wanted to avoid class name collisions.
In the end, custom client-side behavior wasn’t required, but I was stuck with the ‘OG’ prefix. The unique class names have gone from being an annoyance (manual merging of OB-Standard updates into OG-Standard) to a hindrance (OB-Enhancements and OB-Refactory rely on OB-Standard for their functionality).
I am currently in the process of rectifying that problem. I am porting OB-Standard to GemStone (again) and backporting the changes from OG-Standard into OB-Standard. I’ve been able to load OB-Standard into GemStone alongside OG-Standard and there are about 200 methods that I will have to reconcile to complete the port. Shouldn’t be too bad.
Once I’ve got OB-Standard running under GemStone/S I will take a run at OB-SUnitIntegration, OB-Enhancements, OB-regex, and OB-Refactory so that the GLASS tools will be equivalent to the tools that are running in the current Squeak development image.
Wish me luck:)
- AutoCommit and AutoMigrate features added to GLASS tools. If you ever do something that is truly experimental, you can turn off AutoCommit, but in the majority of cases you should be using AutoCommit. With AutoCommit turned on, the system will perform a commit after every UI action that can change state. In the Code and Monticello browsers that means there are commits after virtually every operation. In a workspace, a commit is performed after the expression is evaluated (doIt, printIt, inspectIt, etc.).
- Seaside2.8.1 merged in (Seaside2.8a1-lr.541).
- Refactored the Exception hierarchy for GemStone-specific exceptions.
You can get more information by reading the comments in the package history.
The 22.214.171.124 release of GemStone/S delayed the work towards releasing a new version of the appliance based on 2.3 beta, but we should have a 2.3 beta build done later today and the new version of appliance should be available early next week.
We just announced the release of GemStone/S 64 version 126.96.36.199.
As I mentioned for 2.2.5, most Seaside users should wait for the 2.3 beta appliance. 188.8.131.52 was created primarily for those Seaside users that need a production release for development as well as deployment.
From a GLASS perspective we fixed only a hand full of bugs. The 2.2.5 release primarily contains features and bugfixes for a commercial customer.
For GLASS users, I recommend that you wait for the 2.3 beta that is scheduled to be available at the end of this week.