You are currently browsing the daily archive for April 25, 2008.

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:)

I’ve just published GLASS-dkh.114 which should be used with GemStone-dkh.270 (both can be found in the GLASS project on GemSource). Here are some of the highlights:

  1. 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.).
  2. Seaside2.8.1 merged in (Seaside2.8a1-lr.541).
  3. Refactored the Exception hierarchy for GemStone-specific exceptions.

You can get more information by reading the comments in the package history.

GLASS-dkh.114 can be loaded into version 2.2.5 of GemStone/S 64 (including the just annouced version 2.2.5.1). It can also be loaded into version 1.0beta6 of the appliance.

The 2.2.5.1 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 2.2.5.1.

2.2.5.1 includes a Seaside extent based on GLASS-dkh.114. For our Seaside users we fixed a bug related to remote breakpoints, so that with 2.2.5.1, you can set/debug/resume remote breakpoints.

As I mentioned for 2.2.5, most Seaside users should wait for the 2.3 beta appliance. 2.2.5.1 was created primarily for those Seaside users that need a production release for development as well as deployment.

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 446 other followers

Categories

RSS GLASS updates

  • An error has occurred; the feed is probably down. Try again later.

RSS Metacello Updates

  • An error has occurred; the feed is probably down. Try again later.

RSS Twitterings

  • An error has occurred; the feed is probably down. Try again later.
April 2008
M T W T F S S
« Mar   May »
 123456
78910111213
14151617181920
21222324252627
282930