You are currently browsing the category archive for the ‘Amber’ category.
The original motivation for Kaliningrad was:
The FileTree project implements a Monticello repository type that is compatible with Cypress, it is easy to save Squeak/Pharo/GemStone Monticello packages on disk and use Git for version control.
Everything isn’t quite hunky dory:
- Metacello does not have Git/GitHub support, but there is a project underway to address that.
- Amber Skeleton is currently only implemented on Pharo, but Squeak and GemStone versions shouldn’t be too difficult to implement
- Currently there is no image-based tool support for Git/GitHub, but there is a project underway to address that.
Despite the limitations, I still think that you might find Amber Skeleton interesting.
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