[VisualWorks top] [English] [Japanese]

Installing VisualWorks on the Macintosh

  1. before Installation
  2. VisualWorks 2.5.2
  3. VisualWorks Non-Commercial 3.0a
  4. after Installation
  5. References

before Installation

Using 3 button mouse?
You can use 1 button or 2 button mouse for Smalltalk environment. But 3 button mouse is much better. Get it and assign Option+Click -> yellow button, Command+Click -> blue button. There are no more irritations.
Enough memory, Enough disk space?
My VisualWorks 2.5.2 takes 36MB, VisualWorks 3.0 40MB. In addition I have some working images (5MB - 12MB). Smalltalk environments access your drive frequently, so fast hard drive is better. Both of them default assigned memory are about 13MB, but I add VisualWorks 2.5.2 over 2 times more.
Large and well-viewing Monitor?
My monitor resolution is 1024 * 768. Sometime I feel "Give me more space!"... But I say, 640 * 480 monitor works as it is.
Is application menu bar there?
I'm using MacOS Japanese Edition. SmalltalkAgents, Squeak and VisualWorks are very sensitive for Keyboard Script on my Macintosh. If you feel so funny at showing popup menu or selecting by no mouse-dragging, check your keybord script and caps lock key. And you can check Keyboard Script by application menu bar.
Have any books about Smalltalk especially VisualWorks?
... Give us More Japanese Smalltalk Books!

VisualWorks 2.5.2

  1. Installing and Updating
  2. preparing Working Direcory and files
  3. placing NetManage WinSock Lib
  4. setting Time Zone
  5. using Online Manual

Installing and Updating

You can install VisualWorks 2.5 by dragging runtime folder onto your hard drive or using the install application. Following after the documments of VisualWorks, update to 2.5.2 via 2.5.1. Notice that 2.5.2 virtual machine cannot read 2.5.1 image or older version.

preparing Working Direcory and files

It is strongly recommended to use not original but copy of virtual image and change file to your working directory. For more details, see Smalltalk Idioms.

When you update VisualWorks, it makes changes file. Don't forget to copy this changes.

placing NetManage WinSock Lib

A shared library "NetManage WinSock Lib" is installed onto Extentions folder. VisualWorks may work fine, moving "NetManage WinSock Lib" to application folder.

setting Time Zone

Setting Time Zone on Power Macintosh platform as,

    TimeZone setDefaultTimeZone:
        (TimeZone null).

using Online Manual

Using online manual;

    work.im
    work.cha
    online/
        cookbook.hlp (alias)
        db_qs.hlp (alias)
        dbcookbk.hlp (alias)
        dllcc.hlp (alias)
        examples/ (alias)
        iug.hlp (alias)

VisualWorks Non-Commercial 3.0a

  1. read VWNC for PowerMac page
  2. getting archives
  3. extracting archives & moving files
  4. How to run
  5. preparing Working Direcory and files
  6. making virtual image Macintosh compatible
  7. doing The Strand with VisualWorks!

read VWNC for PowerMac page

getting archives

At first, you need virtual machine, virtual image and source file at least. Get 2 archives from ObjectShare, Inc., VisualWorks NonCommercial Home Page contains these files.

More files you will be required after. (Is VWNC30-e.ZIP required?)

These files are not used on MacOS.

Does these files work fine on MacOS?

extracting archives & moving files

caution:

You must be cafeful for converting EOL (end of line) control code at extracting *.ZIP files.

StuffIt Expander™ 5.1.2 (freeware)
File -> Preferences... -> Cross Platform -> Convert file to Macintosh format: "Never" must be selected.
ZipIt 1.3.8 ($15 shareware)
at File -> Preferences, check "By default, smart-strip linefeeds from text files."
MacZip 1.0.3 (freeware)
MacZip by default doesn't convert, you don't have to pay attention. When you want to convert, you should write UNZIP= -a at "maczip.env" file.

VisualWorks does not mingle EOL control code although it reads Windows sources (CR+LF) or UNIX sources (LF), it keeps change file's EOL control code as your platform. But if you worry about, you can convert Text file as Macintosh text file.

  1. Yon can convert these files; *.pst, *.st, *.rm.
  2. You should not convert these files; *.hlp, *.pcl, *.pdf.

In the sub-directory src/ in dllcc/ directory, you can convert the files there. They are C sources and headers. Other sub-directories are moved form self-extracting archive or no need at Macintosh platform.

There are many files are able to converted, you can use the tool for it. I'd used TextToMac 1.32 (PPC) by Mr. Sumiya at Hiroshima university, Takahiro Sumiya, Hiroshima Univ. Or you can convert all files and replace the files to be required.

Extracting VWNC30-powerMac.hqx, you can get the files and directory as below,

    ReadMe.txt
    bin/vw30nc, *.lib
    dllcc/
        pmac/ (Sources and objects for MPW)
        vector-pmac/ (Sources and objects for MPW)
    fileIns&parcels/MacExtraGH.pcl, MacExtraGH.pst, VWNCPowerMacSupport.st

You should read "ReadMe.txt" at first.

Extracting VWNC30-a.ZIP, you can get the files and directory as below,

    vwnc30/
        bin/
            win/visualnc.exe, *.dll, etc (No required this directory and files)
        image/visualnc.im, visualnc.sou
        parcels/*.pcl, *.pst
            removals/*.rm, *.st

You should move and overwrite that 3 directories: bin/, dllcc/, fileIns&parcels/ from VWNC30-powerMac.hqx, onto vwnc30/. It will be looks like as below,

    vwnc30/
        bin/vw30nc, *.lib
        dllcc/
            pmac/ (Sources and objects for MPW)
            vector-pmac/ (Sources and objects for MPW)
        fileIns&parcels/MacExtraGH.pcl, MacExtraGH.pst, VWNCPowerMacSupport.st
        image/visualnc.im, visualnc.sou
        parcels/*.pcl, *.pst
            removals/*.rm, *.st

When you have already extracted VWNC30-[bcd].ZIP, should move the files contains of that 3 directories: bin/, dllcc/ to same name in vwnc30/. It will be looks like as below,

    vwnc30/
        bin/vw30nc, *.lib
        dllcc/
            pmac/ (Sources and objects for MPW)
            vector-pmac/ (Sources and objects for MPW)
            nt/ (No required this directory and files)
            src/
        fileIns&parcels/MacExtraGH.pcl, MacExtraGH.pst, VWNCPowerMacSupport.st
        image/visualnc.im, visualnc.sou
        parcels/*.pcl, *.pst
            removals/*.rm, *.st
        doc/
        online/
        compat/
        goodies/
        course/
        advanced/
        database/
        ICC/

A shared library "NetManage WinSock Lib" is same as one of VisualWorks 2.5.2.

How to run

Your virtual image and source file are taken from an archive for Windows platform. So they are generic icon, because your Finder of MacOS doesn't know proper type of creator of them. Anyway, you can run VisualWorks NonCommercial by dropping-in virtual image (visualnc.im) onto virtual machine (vw30nc)

preparing Working Direcory and files

It is strongly recommended to use not original but copy of virtual image and change file to your working directory. For more details, see Smalltalk Idioms.

And set "Time Zone" and home directory "VisualWorks" Home. See above.

On Macintosh platform, the path delimitor is ':'. For example, an absolute path including volume name is

    Macintosh HD:vwnc30:bin:vw30nc (on Macintosh)
    C:\usr\lang\vwnc30\bin\win\visualnc.exe (on Windwos95)
    /usr/local/vwnc30/bin/linux86/visualnc (on Linux on Intel i386 box)

The top of path name has not path delimitor. If you want to shout "The virtual image is platform-independent. Why I should know my platform, thinking about file system!?", try

The Secret Incantation of "Using Unix filenaming on Macintosh or PC:" Uni File and its Manual. (in Japanese)

making virtual image Macintosh compatible

  1. fileIns&parcels/VWNCPowerMacSupport.st
  2. fileIns&parcels/MacExtraGH.pcl (MacExtraGH.pst)

Load files as above and save your image. see installed "ReadMe.txt."

doing The Strand with VisualWorks!

You have just finished installing VisualWorks Non-Commercial 3.0a. It's time to play.

Let's do the strand with VisualWorks! (I don't know why I recall the title of Roxy Music here...)


after Installation

What's the matter with generic icons!
You are right. I have changed their type and creator using ResEdit. You can get correct type and creator information by opening vw30nc by ResEdit.
Note: The virtual image corrects own type & creator after saving once. If there is no change file, VisualWorks makes it with correct type & creator. If there is, it does not overwrite and change file's type & creator is not changed. (thanx to Mr. HAMASAKI)
So this is the question. What can I do with other files? <g>
digression: Do you like the virtual image icon of 3.0a? It seems to be more preferred the icon of 2.5.2...
Better Running vw30nc
VisualWorks Non-Commercial 3.0a only user can run it by double clicking at the virtual image (required saving at least one time). But if you have some different versions virtual machines, there is a problem that the Macintosh Finder doesn't know correct set of the virtual machine and image. (thanx to Mr. HAMASAKI)
So Use Alias. Make Aliases of virtual machine and dropp-in virtual image onto them. I'm using a context menu utility. That's good.
My vw30's font is ugly!
Default font seems to be Helvetica.
How about small font from settings?
Or see The Secret Incantation by The Most Revd AOKI
Is there any virtual image or source for Macintosh?
Nein! Think that you have taken them from an archive for Windows and use it on Macintosh. Virtual image or source, etc. is platform-independent. So it is not "there is no platform specification files" but "use same one."
What a ugly monochrome scroll-bar! Am I using System 6!?
You are completely right!
Well, how about another setting of UI-Look?
Or see The Secret Incantation by Mr. Abe.
OK, Let's do it Happy Smalltalking!
From the last word of "Der Rosenkavalier"

References

  1. AOKI Atsushi, "Smalltalk Idioms", Software Research Center, ISBN4-915778-81-9 C3055 P4500E, 1997
  2. Power Macintosh http://wiki.isdn.uiuc.edu:8080/VisualWorks/Power+Macintosh from "VisualWorks : Front Page"

Created: Apr, 1999,
[VisualWorks top] [English] [Japanese]