Nice that you settled it out. When Metacello finishes, it usually writes
...finished baseline
into the Transcript.
Best wishes,
Tomaz
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Thank you for the explanation. I uninstalled Pharo and removed everything from
AppData\\Roaming and Local and reinstalled Pharo and loaded willow-playground.
I found everything in the system browser and was able to evaluate
“Smalltalks2017Presentation start” and bribg it up in my browser on por
The script is not going to produce nothing visually. You can see some
progress bars during the loading depending on the time it takes to load and
then the code should be available in the system browser.
On Thu, Nov 26, 2020, 11:16 g_patrickb--- via Pharo-users <
pharo-users@lists.pharo.org> wrote:
On my Windows 10 laptop I used image names of 80 and 90 and on OpenSUSE the
image names were 80test and 90test.
Thinking it may have to do with using numbers at the beginning of an image name
I tried OpenSUSE again with an image name of Fish and it failed with the same
error I originally had.
I don’t know what I’m doing wrong. I get the same error on Windows 10 and
OpenSUSE. On Windows I tried with and installation to C:\\Pharo and using an
image name of 80 and 90; on Linux, the installation was to /home/gpb/ as the
top level directory where it was unzipped.
I just tried to load Willow-Playground in the same way with Pharo 8.0
64-bit fresh image on Windows 10 and it works flawlessly.
Seaside package has long filenames and directory names, on Windows this
can be a problem if Pharo images are located deep in the hierarchy - but
the error message in
```
That didn't format like the email, so let me try again here.
Installing Willow-Playground from the instructions:
Metacello new
baseline: 'WillowPlayground';
repository: 'github://ba-st/Willow-Playground:release-candidate/source';
load.
```
I have tried this in 9.0 64
