Hi all,
Here's what I did: 1. Download fresh etoys-dev-3.0 2. Load code updates (to #1957) 3. Open SqueakMap package loader, and answer yes to the "upgrade to 2.2?" question 4. Answer yes to the "install Monticello?" question I get "error occured when updating map: key not found", in MCWorkingCopy class >> infoFromDictionary:cache: I already tried loading this stuff via LevelPlayingField, but got errors there too. I don't think etoys-dev-3.0 is supported there yet. If I answer no to the "install Monticello?" question, and then try to install Monticello 231 from SqueakMap, I get what looks like the same error. So, how do I load Monticello into etoys-dev-3.0? Any help appreciated! cheers, Simon PS: I see Scott asked the question, would it be worth shipping a dev image with SqueakMap package loader 2.2 and Monticello pre-installed. From my perspective, yes indeed! |
On Mon, Apr 7, 2008 at 3:15 PM, Simon Guest <[hidden email]> wrote:
> So, how do I load Monticello into etoys-dev-3.0? Any help > appreciated! This will work (on a clean 3.0 image anyway). It's a bit hackish, but hey: http://wiki.laptop.org/go/Etoys_Tips_and_Tricks#Installing_Monticello_on_your_Etoys_image |
At Tue, 8 Apr 2008 11:18:18 +0545,
Ties Stuij wrote: > > On Mon, Apr 7, 2008 at 3:15 PM, Simon Guest <[hidden email]> wrote: > > So, how do I load Monticello into etoys-dev-3.0? Any help > > appreciated! > > This will work (on a clean 3.0 image anyway). It's a bit hackish, but hey: > http://wiki.laptop.org/go/Etoys_Tips_and_Tricks#Installing_Monticello_on_your_Etoys_image OK, that explains why I couldn't work it out myself ... ! Thanks for your help. cheers, Simon |
> At Tue, 8 Apr 2008 11:18:18 +0545,
> Ties Stuij wrote: > > > > On Mon, Apr 7, 2008 at 3:15 PM, Simon Guest <[hidden email]> wrote: > > > So, how do I load Monticello into etoys-dev-3.0? Any help > > > appreciated! > > > > This will work (on a clean 3.0 image anyway). It's a bit hackish, but hey: > > http://wiki.laptop.org/go/Etoys_Tips_and_Tricks#Installing_Monticello_on_your_Etoys_image Sigh, just hit the next problem. The wiki says "upgrade Monticello if you like". Having tried to use it as it is, I keep getting "key not found" errors when loading an .mcz file. So I thought to upgrade it. But I can't, as I get more key not found errors. I don't think this stuff is usable by those at my level just yet, so I'm having to give up. My observation is that Etoys-3.0 is the place I want to be. But it's simply too hard to get this working with SqueakMap and Monticello. I need those to load OSProcess, so I can get my LatexMorph working. But it's all too hard, and there are too many pitfalls I don't know how to negotiate. I could go back to squeak-3.10 where this stuff works, but then I lose the really neat OLPC Etoys stuff. Sigh. cheers, Simon |
El 4/8/08 6:29 AM, "Simon Guest" <[hidden email]> escribió: > I could go back to squeak-3.10 where this stuff works, but > then I lose the really neat OLPC Etoys stuff. You don't need lose . 3.10 still have Etoys into. Still lacks how to read OLPC .pr directly, but some of us are working on it. All could be easier is major forks have a common base as I try to have with my proposals of 3.11 (now sleeping until better days). Edgar |
In reply to this post by Simon Guest-2
On Tue, Apr 08, 2008 at 09:29:22PM +1200, Simon Guest wrote:
> > My observation is that Etoys-3.0 is the place I want to be. But it's > simply too hard to get this working with SqueakMap and Monticello. I > need those to load OSProcess, so I can get my LatexMorph working. But > it's all too hard, and there are too many pitfalls I don't know how to > negotiate. I could go back to squeak-3.10 where this stuff works, but > then I lose the really neat OLPC Etoys stuff. Sigh. > Hi Simon, I don't have time right now, but if it would help I'd be happy to put OSProcess and CommandShell into change sets that you could (hopefully) load into Etoys-3.0. Or as a workaround you could just file them out of another Squeak image and file them back in to your Etoys image. Dave |
David T. Lewis wrote:
> On Tue, Apr 08, 2008 at 09:29:22PM +1200, Simon Guest wrote: > >> My observation is that Etoys-3.0 is the place I want to be. But it's >> simply too hard to get this working with SqueakMap and Monticello. I >> need those to load OSProcess, so I can get my LatexMorph working. But >> it's all too hard, and there are too many pitfalls I don't know how to >> negotiate. I could go back to squeak-3.10 where this stuff works, but >> then I lose the really neat OLPC Etoys stuff. Sigh. >> >> > > Hi Simon, > > I don't have time right now, but if it would help I'd be happy to > put OSProcess and CommandShell into change sets that you could (hopefully) > load into Etoys-3.0. Or as a workaround you could just file them out > of another Squeak image and file them back in to your Etoys image. > > Dave > > > > without problems as far as I can tell. Just download it and file it in from FileList Karl |
In reply to this post by Simon Guest-2
On 08.04.2008, at 02:13, Simon Guest wrote: > At Tue, 8 Apr 2008 11:18:18 +0545, > Ties Stuij wrote: >> >> On Mon, Apr 7, 2008 at 3:15 PM, Simon Guest <[hidden email] >> > wrote: >>> So, how do I load Monticello into etoys-dev-3.0? Any help >>> appreciated! >> >> This will work (on a clean 3.0 image anyway). It's a bit hackish, >> but hey: >> http://wiki.laptop.org/go/Etoys_Tips_and_Tricks#Installing_Monticello_on_your_Etoys_image > > OK, that explains why I couldn't work it out myself ... ! > > Thanks for your help. The problem is that the Squeakmap update process tries to install a Monticello version that cannot cope with the stubs left by MCInstaller (at least that's my theory of the problem). I can load it, when the walkback pops up I edit the offending method in place (wrapping the ancestor creation in an #ifError: block) and continue. But I can see how this won't fly with other users ;) We should indeed consider adding Monticello to the -dev image and stripping it out for the release. Or maybe even better, fix the Squeakmap update process so it can be easily installed. - Bert - |
In reply to this post by Simon Guest-2
On Mon, Apr 07, 2008 at 09:30:05PM +1200, Simon Guest wrote:
> Hi all, > > Here's what I did: > > 1. Download fresh etoys-dev-3.0 > 2. Load code updates (to #1957) > 3. Open SqueakMap package loader, and answer yes to the "upgrade to > 2.2?" question > 4. Answer yes to the "install Monticello?" question > > I get "error occured when updating map: key not found", in > MCWorkingCopy class >> infoFromDictionary:cache: > > I already tried loading this stuff via LevelPlayingField, but got > errors there too. I don't think etoys-dev-3.0 is supported there > yet. I fixed LevelPlayingField to work on a fresh eToys 2.3 image, and now I use eToys-dev-2.3 + LPF for my day-to-day development. I can look into what is causing this to not work on EToys 3.0 and update the LPF script appropriately. I'll check this out tomorrow. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ |
In reply to this post by Karl-19
At Tue, 08 Apr 2008 16:07:08 +0200,
karl wrote: > > David T. Lewis wrote: > > I don't have time right now, but if it would help I'd be happy to > > put OSProcess and CommandShell into change sets that you could (hopefully) > > load into Etoys-3.0. Or as a workaround you could just file them out > > of another Squeak image and file them back in to your Etoys image. > > > > Dave > > > > > The OSProcess sar from SqueakMap can be filed into the Etoys-3.0 image > without problems as far as I can tell. > Just download it and file it in from FileList > > Karl Hi Guys, Thanks for the help and encouragement. Yes, I managed to file in the OSProcess sar. Will press on for now ... cheers, Simon |
Free forum by Nabble | Edit this page |