Cincom Smalltalk: Heading to the Seaside
Widgetry reached the "1.0" milestone earlier this week - Sam announced that on his blog. A few people noticed that we didn't make much of that announcement, and that's true - we've talked (probably over-talked) about Widgetry for a long time, so we thought it best not to make a big thing about the release.
It's out there, we support it, and it will be included in a service pack we'll ship in August. We'll be formally releasing ObjectStudio 8 at that time, which is a very big deal for our ObjectStudio customers - it's a major upgrade. Details on the service pack will be forthcoming, but here's what it'll probably look like - a downloadable archive of component updates (new parcels, possibly updated VMs, that sort of thing). We'll make that available as we ship ObjectStudio 8.
![]() |
So what's next for Cincom Smalltalk? Well, many people noticed Gemstone's announcement of Seaside support at Smalltalk Solutions - we saw the enthusiasm for that, and got a number of questions about what we plan to do with the Cincom Smalltalk port of Seaside. We plan to support Seaside, and that support will include a relational persistence solution. We are still in the early stages of what that persistence solution will look like, so I don't have any details yet. However, we won't be waiting on that for basic Seaside support. Michel Bany has done a great job of porting Seaside to Cincom Smalltalk, and we will be supporting that. |
Right now, you can consider the Seaside port in the "preview" directory to be a public beta. Within the next couple of weeks I'll have timelines available for full support, and a first roadmap for our Seaside plans. Also - we would love to hear from you about this - where can we add value to Seaside while at the same time remaining part of the Seaside community? Send your feedback to me on that.


Comments
Great News
[Boris Popov] June 19, 2007 12:19:27.159
Thanks, James, I do think what Cincom and GemStone are doing will help Seaside move forward and gain recognition it rightfully deserves. One place I'd start would be the cleanup of the WebToolkit to separate the built-in web brokers (IPWebListener and TinyHTTP) and remove extra layer of site/session management that gets in the way of developing Seaside applications as it manages its own sessions and resources. That would mean I could ditch Swazoo and stop running both Tiny for our toolkit based servlets with Swazoo for Seaside in the same image :)
Seaside for Hyper
[Ken Treis] June 19, 2007 13:02:17.850
Hi James -- along the lines of what Boris posted, I just replicated my lightweight "SeasideForHyper" package to the public repository. I don't use WebToolkit, but I also don't use anything from Swazoo (no need for resource resolution). You're welcome to use whatever part of it you may find useful.
Finally... Thank you...
[anon] June 19, 2007 14:16:00.050
This is great... can't wait...