You are currently browsing the category archive for the ‘Seaside’ category.
WorldPulse is application for the iPhone and iPad, that shows live accurate cloud cover data, the day/night terminus, night lights, and in 2.0 weather data from all the weather stations in the world.
In John’s presentation:
GemStone/S 64 22.214.171.124 was released August 28, 2012. This release fixes a number of bugs and we recommend all 3.x customers use this release. Be sure to review the release notes and install guides for this release.
GemStone 126.96.36.199 ships with GLASS 1.0-beta.8.7.2 pre-installed in
$GEMSTONE/bin/extent0.seaside.dbf, but there are a few minor issues that show up as test failures. GLASS 1.0-beta.8.7.3 has been released to address those issues.
You should update to GLASS 1.0-.8.7.3 when you start using GemStone 188.8.131.52.
A One-Click GemTools 1.0-beta.8.7 for GemStone 184.108.40.206 can be obtained from the seaside.gemstone.com downloads page or you can download GemTools 1.0-beta.8.7 for Gemstone/S 220.127.116.11 all platforms directly.
You can build a custom GemTools image by following these steps on the glass db wiki.
Seaside 18.104.22.168 should be used with GemStone/S 3.1.x. There are a few critical bug fixes included in that version.
You can download the binaries from ftp://ftp.gemstone.com/pub/GemStone64/22.214.171.124, use the installGemStone.sh script to download and install GemStone/S on your machine (highly recommended), or visit seaside.gemstone.com downloads page.
To use the installGemStone.sh script, your supply the GemStone version number as an argument to the script. The following downloads and installs the GemStone/S 126.96.36.199 release:
If you are upgrading from GemStone/S 2.x, then be sure to read my post on GemStone/S 3.1.0 first.
Let’s say that you’ve got Seaside 188.8.131.52 installed in your GemStone/S 3.1.0 repository. According to the upgrade instructions you will need to define the BootstrapApplicationLoadSpecs for your application. For Seaside 184.108.40.206, that means you’ll run the following topaz script BEFORE running the upgradeSeasideImage.sh script:
The important bits are that you are specifying GLASS 1.0-beta.8.7.3 and specifying the <path to seaside cache repository>. The seaside cache repository is a directory on your machine where you’ve stashed all of the mcz files needed to reload Seaside 220.127.116.11 into your upgraded repository. You can use the following script to create the seaside cache repository:
Finally, as noted in Issue 354, you need to reload the ConfigurationOfGLASS and ConfgurationOfSeaside30:
- CofigurationOfSeaside30 18.104.22.168
- Issue 636: expected exception behavior WAWalkbackErrorHandler not portable (and not ANSI compliant)
- Issue 694: Swazoo adapter does not respect Request URIs ending in slash
With this release I have finally implemented remote breakpoints for Seaside 3.0 which will be covered in a separate blog post.
Kaliningrad oblast (sometimes called Yantarny krai which means “The amber region”) is located on the coast of the Baltic sea and is the site of the world’s largest amber deposits.
Kaliningrad automatically maps Amber package names to Monticello package names, so Kaliningrad is pretty easy to use.
To load Kaliningrad execute the following expression:
Gofer new url: 'http://ss3.gemstone.com/ss/Kaliningrad'; package: 'ConfigurationOfKaliningrad'; load. ((Smalltalk at: #ConfigurationOfKaliningrad) project version: '0.1') load.
Once you’ve got the Seaside server running, hit (user/password : admin/tool):
If you want save your Amber code into a Monticello package follow these steps:
- Create an Amber package (‘tODE-AmberClient’) in the Amber Browser.
- Create a Monticello package with the same name (‘tODE-AmberClient’) using the Monticello Browser in your image.
- Register the Monticello package with the KOAmberBrowser class:
KOAmberBrowser addMonticelloPackage: 'tODE-AmberClient'
Thereafter, when you hit the Commit package button for ‘tODE-AmberClient’ in the Amber Browser, the .js and .st source will be saved in the ‘tODE-AmberClient’ Monticello package.
The class KOAmberBrowser is also a good example for how to integrate Amber code into a Seaside component.
Importing classes into Amber
If you want to import a class from your Smalltalk image into Amber, you can evaluate an expression like the following in an Amber workspace:
KOImporter importClass: 'TOSession' intoModule: 'tODE-Amber'
Be aware that there are differences between Amber Smalltalk and other Smalltalk implementations (see the section entitled Differences with other Smalltalk implementations on the Amber documentation page). KOImporter does not check for correctness.
Kaliningrad 0.1 is based on Amber 0.9.
If you run into problems, let me know.
 Photo by http://www.flickr.com/photos/paul_garland/5133520694 / CC BY-SA 2.0
Bob Nemec, a long-time Smalltalker and GemStoner just posted a description of how he is using Seaside to extend the life of a couple of legacy Smalltalk applications:
Consequently we are resuming work on SS3 and are committed to taking SS3.gemstone.com into production.
The warning that packages stored in SS3 will not be preserved beyond the Alpha period has been withdrawn and we have instituted daily backups for the site. We are still in the alpha period, but the basic operation of the site is sound. Tobias Pape has bugfixes queued up for most, if not all of the outstanding bugs and we will be working towards pushing the fixes into production over the coming weeks.
It should be noted that some mcz files cannot be stored in SS3. We plan to characterize and fix the known problems with loading mcz files.
Please report issues you run into with the SqueakSource3 issue tracker.
When we’ve addressed the initial crop of critical bug reports we will move into a short Beta period and then transition to full production. In the interim, if you are willing to put up with the current set of bugs in exchange for stability, then you should consider hosting your project on SS3.
With that said, keep in mind that work on SmalltalkHub is continuing and I understand that there is an active project to improve the reliability of www.squeaksource.com, so carefully consider the impact on your users before moving to SS3. SS3 is intended to be a stable alternative until SmalltalkHub is brought online and www.squeaksource.com is stabilized.
 Photo by http://www.flickr.com/photos/marcus_hansson/87885327 / CC BY 2.0
[Updated: 1/4/2010] If you are interested, you should also check out the discussion on the Seaside list.