We’re having an Indian Summer in Oregon this year. The trees are alive with vibrant reds and bright yellows against a backdrop of Douglas Fir green and a bright blue sky. Balmy, clear weather in Oregon, in October – Fantastic! As the sun climbs up over the Cascades and lights up the maples in the parking lot, I’m thinking back on the fact that I spent the entire summer working on the tools for GLASS and it looks like I’ll be spending my Indian Summer doing the same thing.
While I was playing with GemStone/S and Seaside, Isaiah Perumalla spent some time porting Magritte to GemStone/S. Isaiah (with some help from Lukas Renggli) got to the point where all but a few of the tests were passing. Some GemStone-specific work was needed and I’ve stepped in to finish off the port, but the bulk of the work was done by Isaiah and Lukas.
In the midst of working through the remaining Magritte tests, I decided that I would get breakpoints working in the OmniBrowser tools. I’ve got them working now, but I now have to add a Breakpoint Browser to the list of tools that need to be implemented.
Also, Otto Behrens and Liliana Ivan from Finworks found time to extend Shout to do syntax highlighting for GemStone/S Smalltalk, which is very nice.
If you have 64 bit hardware and the time to explore GLASS right now, visit our website and drop us an email to let us know that you’re ready to rumba.
Meanwhile, I’m going heads down on the tools.
4 comments
Comments feed for this article
November 6, 2007 at 5:51 pm
Bill
Dale, Have you’ll chosen a solution approach to dealing with transactions which are different than page boundaries? Will the upcoming general release include it?
November 6, 2007 at 6:05 pm
Dale Henrichs
Bill, we’re pretty much staying with commits on page request boundaries, but I would be interested in hearing a little bit more about what you are thinking…there are usually several ways to skin a cat and in this case there are also a number of different cats that can be skinned:)
For operations that will be spanning multiple page requests, it is possible to arrange to store your data along with the session state (i.e., segregated from the data you are updated). This usually involves a copy of some sort – so in the simple case you will create a copy of the object that will participate in the ‘long running’ transaction and link the copy into your seaside session state. This copy will be persisted along with session state. When you’ve finally gathered all the relevant info and are ready to commit the ‘long running’ transaction, you’d copy the new state into the primary object…
Is the type of operation you were thinking about?
December 2, 2007 at 8:48 pm
GLASS Beta Update: Remember November? « (gem)Stone Soup
[...] 2, 2007 in Gemstone, Seaside, Smalltalk Back in October, I said that I was going heads down on the tools and I really wasn’t kidding. During November I didn’t blog very much, but I did make [...]
December 2, 2011 at 10:24 am
GLASS 101: Remote Breakpoints for Seaside 3.0 « (gem)Stone Soup
[...] been available in GLASS, for a long time now. In 2008 I added remote breakpoints for Seaside2.8 and finally with the release of Seaside [...]