Hi PhiHo,
I should have been clearer, this fix was for running ModSqueak on SWT0.6. Your problem looks like the createIfNecessary method on FileSystemRepositoryAccessor is failing. It turns out there is a FileSystemRepositoryAccessorTest but it isn'r fully testing the creation part. I would recommend that you fix the TestCase to fully test this situation. This would help all of us.
cheers, Rob
-----Original Message----- From: PhiHo Hoang [mailto:phiho.hoang@home.com] Sent: Thursday, August 30, 2001 2:05 PM To: squeak-dev@lists.squeakfoundation.org Subject: Re: Essen ESUG experience report day 2
Hi Rob,
Your fix let me install the Ginsu to SWT0.6 and gave me'Module Manager' and 'Module Browser'.
If your fix is not intended for SWT0.6, please ignore therest (and I am sorry for wasting the bandwidth :-(
But when I tried to install 'Repository' with: url := (RepositoryUrl fromString:'repos://SqueakBase/RepositoryConfig/0.3'). url resolve build.
I got 'Error: Fully qualified path expected' walkback. Please find attached the log file. I was able to install 'Repository' without installing 'Ginsu'. Cheers, PhiHo. ----- Original Message -----From: "Rob Withers" rwithers12@mediaone.net To: "joseph pelrine" jpelrine@balcab.ch; CampSmalltalk@mojowire.com; squeak-dev@lists.squeakfoundation.org; "Paul McDonough" wnchips@yahoo.com Cc: vwnc@cs.uiuc.edu Sent: Thursday, August 30, 2001 8:19 AM Subject: Re: Essen ESUG experience report day 2
Joseph, one problem was that EventHandler is gone. These
files fix the
ginsu. The other problem I noticed is that the
SWTVolume.txt is now in XML,
so if you create a repository, the base SWT won't be able
to read this file
anymore.
Thank You!
- Rob
----- Original Message ----- From: "joseph pelrine" jpelrine@balcab.ch To: CampSmalltalk@mojowire.com;
squeak-dev@lists.squeakfoundation.org
Cc: vwnc@cs.uiuc.edu Sent: Thursday, August 30, 2001 4:02 AM Subject: Re: Essen ESUG experience report day 2
I'd like to sincerely thank John McIntosh for his
write-up of my talk. I
hope it will serve to eliminate some of the FUD
surrounding my/our work.
I'll try to post some additions and comments to his
article in the next
few days. Sometimes the simplest ideas are the hardest to
understand;-)
I was also very happy after talking to Hans-Martin, where
we realized
that all his wishes and plans (layering modules, rollback
to previous
versions of methods etc.) could be very easily
implemented within the
ModSqueak "framework".
The code for the June 29 ModSqueak code drop (the latest
version that
Paul and I worked on) has been available on the Stable
Squeak swiki at
http://swiki.squeakfoundation.org/stablesqueak. I will start describing/documenting it there. If people are interested
AND if I have
time, I could probably post the code for the remote
installation demo
too. Let me know if you want it.
cheers
- Joseph
At 02:17 30.08.2001 , Les Tyrrell wrote:
I loved the stuff about ModSqueak, but where can I get
it? Don't tell
me to
download SWT 0.6- I've already checked, and it appears
that ModSqueak
is not in that.
- les
-- Joseph Pelrine
RE: Essen ESUG experience report day 2Hi Rob,
Your problem looks like the createIfNecessary method on FileSystemRepositoryAccessor is failing. It turns out there is a FileSystemRepositoryAccessorTest but it isn'r fully testing the creation part I would recommend that you fix the TestCase to fully test this situation. This would help all of us.
What ! Me fix ModSqueak ? You must be kidding. Anyway, encouraged by your hints and recomendation, I just put an order for 3 books. The bookshop promised to deliver the first within 5 weeks, the second and third within 5 what (my cellphone went nut here). The books in order are 'Smalltalk-80: The Language', 'Squeak: The Image' and 'ModSqueak: The Framework'.
I will try to fix the TestCase when I got them all ;-). In the mean time ...
I should have been clearer, this fix was for running ModSqueak on SWT0.6.
Do you think, instead of '0.1' (for SWT0.5) should we use '0.2' (for SWT0.6) instead:
| url | url := (RepositoryUrl fromString: 'repos://SqueakBase/SUnitConfig/0.2'). url resolve build. url := (RepositoryUrl fromString: 'repos://SqueakBase/RefactorAndLintConfig/0.2'). url resolve build
Have you tried this ?
Cheers,
PhiHo
Sure, why not? You have the image, which is where all the book writers get their ideas from. :) Check out this method from the test:
testCreateAndDestroy "Was created already" self assert: (FileDirectory default directoryExists: self repositoryRelativePathName). accessor createIfNecessary. self assert: (FileDirectory default directoryExists: self repositoryRelativePathName). accessor destroy. self deny: (FileDirectory default directoryExists: self repositoryRelativePathName)
Doesn't it look like something isn't being tested? (Especially with the comment) So you should be able to pick a directory name that you know doesn't exist (how do you know - see if it exists and delete it first.). Then you can build your own accessor, same way that the setUp method does it, but with your special directory name, and test creation and deletion.
you wrote: Do you think, instead of '0.1' (for SWT0.5) should we use '0.2' (for SWT0.6) instead:
| url | url := (RepositoryUrl fromString: 'repos://SqueakBase/SUnitConfig/0.2'). url resolve build. url := (RepositoryUrl fromString: 'repos://SqueakBase/RefactorAndLintConfig/0.2'). url resolve build
Have you tried this ?
The 0_1 that you see in these strings are the version numbers from the FileSystemRepository. They have nothing to do with the SWT version...Some of the directories have multiple versions, so browse under SqueakBase.
- Rob
squeak-dev@lists.squeakfoundation.org
-
PhiHo Hoang -
Rob Withers -
Withers, Robert