Shortly after I announced the GemTools Client for Pharo, Gerhard Obermann jumped in and refactored a number of the GemTools menus using sub menus. Unfortunately, I got involved in a number of other tasks (including refining the Metacello API) before I could push his changes out. Now that Metacello is stabilized, it is time to revisit the installation and update procedures for the GemTools Client.
[Update 10/16/2009: fixed egregious errors in the installation instructions … 2 steps and the first step was plain wrong:) … thanks Gerhard]
[Update 11/04/2009] Please see the GemTools Client 1.0-beta.1 post for up-to-date instructions.
Installation
[Update 11/04/2009] Please see the GemTools Client 1.0-beta.1 post for up-to-date instructions.
If you haven’t already been using the GemTools 2.3.1 Preview for all platforms (which is based on Pharo), then you should download the preview GemTools client and follow the instructions for setting up your session to verify that you can connect to your stone. You’ll need the session information and the gci files from the Preview to get things running with the either Squeak or Pharo.
I’ve tested the installation procedure using Squeak3.10.2-Trunk-090912 and pharo1.0-10470-BETAdev09.10.2.
To load GemTools into a client image:
- Load the latest version of the GemTools-Configuration package from http://seaside.gemstone.com/ss/GLASSClient. GemTools-Configuraton-dkh.12 is currently the most recent version.
- Execute the following expression in a workspace:
GemToolsConfiguration loadLatestVersion.
- Execute the following expression to open the GemTools launcher:
OGLauncher open
- Copy the session information from your old GemTools Client to the new GemTools Client in your image. Use the Edit session menu item on the Session Menu in the launchers.
- Save the image.
- Copy the gci files (gciForWindows.dll, gciForLinux.so, and gciForMacintosh.so) from GemTools-2.3.1-preview.app/Contents/Resources in the one-click into the directory containing your image and changes files.
- Press the Login button on the GemTools Launcher and you should be in business.
Last December when I first introduced the GemTools Launcher, it took 6 steps to install the GemTools Client code:
In July I announced the GemTools Client for Pharo (based on version 0.9 of Metacello), it took 4 steps:
Today it takes only 2 steps:
The configuration class bootstraps Gofer and Metacello, then loads FFI and finally loads the OGLauncher application code. Danged close to a one-click install:)
Update
To update the GemTools Client to a later version, you can follow the instructions for the Update…menu.
If you have any trouble join and send mail to the GLASS Beta Mailing List.
—–
[1]Photo by Okinawa Soba (Creative Commons).
7 comments
Comments feed for this article
October 17, 2009 at 8:06 pm
Terse Guide to the (new) GLASS Tools « (gem)Stone Soup
[…] client or want to use a later version of Pharo then follow the instructions below. on this page. [Updated […]
October 17, 2009 at 8:11 pm
GemTools Client for Pharo 1.0 beta « (gem)Stone Soup
[…] [Updated: 10/17/2009] Updated instructions for installing the GemTools Client in Pharo and Squeak can be found here. […]
November 4, 2009 at 2:06 pm
GemTools Client 1.0-beta.1 « (gem)Stone Soup
[…] you’ve already installed the GemTools Client 1.0-beta.0, then you want to follow the Update instructions. To install the GemTools Client in a virgin Squeak […]
December 30, 2009 at 7:43 pm
Ian Gilchrist
Hi Dale,
I downloaded GemTools-2.3.1-preview and managed to successfully login a DataCurator session. However, upon trying to save my image as GemToolsX.image I was informed in a popup . . .
Squeak cannot locate the sources file named /Users/iangilchrist/Downloads/GemTools.sources.
Anything I can easily do to remedy this situation and save off my new image? I’m running on an iMac under MAC OSX and have downloaded GemStone/S 64 Bit 2.4.0 as provided by james Foster for the MAC.
On another subject . . . anyway to easily change the font to something more readable and or larger?
regards,
iang
December 30, 2009 at 8:08 pm
Ian Gilchrist
Hi Dale,
Perhaps my request for clarification was a tad bit premature, as I have now understood that GemTools.app is a directory under which the sources file resides!
Ian-Gilchrists-iMac:Resources iangilchrist$ ls
GemTools.changes SqueakFFIPrims.bundle libgs64-231.dll
GemTools.icns gciForLinux.so package-cache
GemTools.image gciForMacintosh.so
GemTools.sources gciForWindows.dll
Ian-Gilchrists-iMac:Resources iangilchrist$ pwd
/Users/iangilchrist/Documents/Seaside.gsdb/GemTools.app/Contents/Resources
Ian-Gilchrists-iMac:Resources iangilchrist$
This being said I still think that a “save as” should be delivering a copy of the sources file along with the GemToolsX.changes and GemToolsX.image file that ended up being written to
/Users/iangilchrist/Documents/Seaside.gsdb
What is the proper way to proceed in order to get myself a saved image?
regards,
iang
December 31, 2009 at 3:51 pm
Ian Gilchrist
Hi Dale,
Feel free to purge my previous 2 posts concerning my install issues. James Foster has me up & running with his MacOS specific install.
regards,
iang
January 2, 2010 at 12:39 pm
Dale Henrichs
Sorry Ian, I was taking somewhat of a holiday from GLASS support:) I’m glad James stepped in and solved you issues