February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] please test 2.0

by phil＠highoctane.be

All right. 'nuff Pharo 2.0 for the day for me. Pharo 2.0 looks great BTW. Much cleaner and all. Keep up the good work guys! Phil 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: > thanks, I will try it with that one and see what happens. > > On 2013-02-19, at 23:28, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> Latest PharoVM from the CI >> >> 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: >> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 >> NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: >> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 >> git://gitorious.org/cogvm/blessed.git Commit: >> 05ed728452dc92732f9f23ce24a3c32bfdc0f4b8 Date: 2013-02-15 17:04:09 >> +0100 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14519 >> ' >> >> 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: >>> I start to believe that it might be your VM? >>> Which version are you using? >>> >>> Smalltalk vm version >>> >>> does the trick. >>> >>> On 2013-02-19, at 21:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>> Pharo 2.0 not 1.4 >>>> >>>> The World Menu > System >Software Update started working and then >>>> threw me in teh debugger where I had the error. I inspected several >>>> variables and then did some Restart,, Over, Over, ..Proceed and things >>>> went fine. >>>> >>>> There was a ZnClient in there but I can't figure out why there was a >>>> mention of SmallInteger. >>>> >>>> Phil >>>> >>>> 2013/2/19 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>>>> Even weirder: played with the debugger and sayed Over Over Over then >>>>>> Proceed and it worked. Strange.... >>>>>> >>>>> What do you mean exactly ? You were not able to Proceed after clicking on >>>>> Over several times on Pharo 1.4 ? >>>>> I've just made a fix in the debugger that was integrated today.Give me more >>>>> details to know if I have to look at it. >>>>> >>>>> Clement >>>>> >>>>>> Phil >>>>>> >>>>>> 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>>>> Hi, >>>>>>> >>>>>>> We are almost there for the release, but we still need a little effort >>>>>>> more. >>>>>>> Would be terrific if everyone of you took the latest 2.0 image and test >>>>>>> it with your usual workflows (we cannot imagine all, they are infinite :) >>>>>>> >>>>>>> And please report bugs, and JUST bugs :) >>>>>>> >>>>>>> all the "nice to have" can be reported, but in 3.0 milestone (or not >>>>>>> milestone at all). >>>>>>> >>>>>>> cheers, >>>>>>> Esteban >>>>>> >>>>> >>>> >>> >>> >> > >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Camillo Bruni

aaaaah now I see :) that's that stupid repository dialog |(, it expects the exact type of repository you chose in the first place. So if you select the ss3.gemstone.com entry you have to enter that kind of repository. And yes, I work around that => open an issue for it! On 2013-02-19, at 23:34, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Nope. Same crash. > > 2013/2/19 Max Leske <maxleske(a)gmail.com>: >> I think I know what you might mean Phil, I've seen this myself: >> >> If you enter a username but no password for a repository (like the snippet from ss3 shows) then MC will prompt for username and pw. If you remove the username (empty string), you'll be fine. >> >> Not terribly bad but quite annoying. >> >> Max >> >> >> On 19.02.2013, at 23:11, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> I cannot reproduce this on the latest pharo image.... >>> I added it as a MCGemstoneRepository with the full url and it works... >>> >>> MCGemstoneRepository >>> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >>> user: '' >>> password: '' >>> >>> I can browse and load files. Can you give me more details? >>> >>> On 2013-02-19, at 21:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> >>>> Got this thing biting me while testing the relase: >>>> >>>> I added a project of mine from the ss3.gemstone.com system and the >>>> Monticello registration over there says: >>>> >>>> >>>> MCHttpRepository >>>> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >>>> user: 'PBK' >>>> password: '' >>>> >>>> >>>> I add that into Pharo as a ss3 repository. >>>> >>>> There I am asked for: >>>> >>>> MCGemstoneRepository >>>> location: 'http://ss3.gemstone.com/ss/' >>>> user: '' >>>> password: '' >>>> >>>> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >>>> and copy/pasted as usual. >>>> >>>> Then, error. >>>> >>>> Took a minute to see why and get my mcz back. >>>> >>>> So, either SS3 has to change the registration information or Pharo >>>> does something weird with SS3. I don't know. >>>> >>>> Guess I need to put things in SmalltalkHub :-) >>>> >>>> Phil >>>> >>> >>> >> >> >

Feb. 19, 2013

Re: [Pharo-project] Pharo 2.0 UITheme current solidMenuIcon (and for sure some friends) are wrong due to VM problem

by phil＠highoctane.be

OSX Lion 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: > humm that is all strange... > > under which platform are you? > > On 2013-02-19, at 22:49, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> I managed to load my code into Pharo 2.0 without problems. Sweet! >> >> There is some direct use of morphic all looks like to work well. >> Sound also works nicely. >> >> Still an issue with the World Menu where I do use menuCommandOn with >> an icon set to: >> >> UITheme current solidMenuIcon >> >> The icon looks quite warped or plain wrong (looks like a crappy cloud). >> >> The code of the method in 1.4 is >> >> solidMenuIconContents >> "Private - Method generated with the content of the file >> /home/plantec/dvpt/Pharo/Sprint-10-09/Icons/solidMenu.png" >> ^ 'iVBORw0KGgoAAAANSUhEUgAAAA4AAAAQCAYAAAAmlE46AAAABHNCSVQFBQUBSsjp7wAAAE5J >> REFUeF5jgACO/wykA5AmGCZGHVaNxGISNO648AO7RpAEIYxXI8lOJaSRIqeiaSbeRrwaSXAu >> lZxKQsiSEh0oSY+cJEdissORGUjLWgBvFzCDqCcU6AAAAABJRU5ErkJggg==' >> >> and in 2.0 it is >> >> solidMenuIconContents >> "Private - Method generated with the content of the file >> /home/plantec/dvpt/Pharo/Sprint-10-09/Icons/solidMenu.png" >> ^ 'iVBORw0KGgoAAAANSUhEUgAAAA4AAAAQCAYAAAAmlE46AAAABHNCSVQFBQUBSsjp7wAAAE5J >> REFUeF5jgACO/wykA5AmGCZGHVaNxGISNO648AO7RpAEIYxXI8lOJaSRIqeiaSbeRrwaSXAu >> lZxKQsiSEh0oSY+cJEdissORGUjLWgBvFzCDqCcU6AAAAABJRU5ErkJggg==' >> >> Looks like the same to me. So, something isn't right. >> >> I tried the image with the StackVM and there, the icon is right. It >> has the right colors instead of a white cloud. >> >> Maybe due to a plugin, I don't know. The VM I tried is the latest one >> I got with the ciPharoVM.sh script. >> >> My self compiled PharoVM exhibits the same problem. >> >> CogVM shows the right icons (even if it complains that the VM is too >> old for the image) >> >> Smalltalk vmVersion gives: >> >> 'CoInterpreter VMMaker.oscog-eem.264 uuid: >> 64e76092-8af7-449f-9188-e65f3bd1f08d Feb 5 2013 >> StackToRegisterMappingCogit VMMaker.oscog-eem.264 uuid: >> 64e76092-8af7-449f-9188-e65f3bd1f08d Feb 5 2013 >> VM: r2678 http://www.squeakvm.org/svn/squeak/branches/Cog Plugins: >> r2545 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins >> ' >> >> I tried with the code generated to create a cog VM from Esteban and >> there it works fine. >> >> Smalltalk vmVersion gives there: >> >> 'CoInterpreter VMMaker-oscog-EstebanLorenzano.231 uuid: >> a9e39f38-e1fa-4851-a3a3-1a0f1f7a4062 Feb 15 2013 >> StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.231 uuid: >> a9e39f38-e1fa-4851-a3a3-1a0f1f7a4062 Feb 15 2013 >> git://gitorious.org/cogvm/blessed.git Commit: >> 63aa6ed8a070fc730224b496e0dda7c3f8482e10 Date: 2013-02-14 11:43:21 >> +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> >> ' >> >> Here is the version for the problematic VM (latest downloaded from ci) >> >> Smalltalk vm version >> >> 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: >> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 >> NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: >> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 >> git://gitorious.org/cogvm/blessed.git Commit: >> 05ed728452dc92732f9f23ce24a3c32bfdc0f4b8 Date: 2013-02-15 17:04:09 >> +0100 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14519 >> ' >> >> Maybe some NB dark magic going on... >> >> On the other side, loading PNGs from disk worked okay. (As the larger >> icons on the background of the screenshot demonstrate). >> >> Hope you can figure out why there is such an issue. >> >> Phil >> <Capture dâÃ©cran 2013-02-19 Ã 22.27.37.png><Capture dâÃ©cran 2013-02-19 Ã 22.39.43.png><Capture dâÃ©cran 2013-02-19 Ã 22.41.41.png> > >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by phil＠highoctane.be

Nope. Same crash. 2013/2/19 Max Leske <maxleske(a)gmail.com>: > I think I know what you might mean Phil, I've seen this myself: > > If you enter a username but no password for a repository (like the snippet from ss3 shows) then MC will prompt for username and pw. If you remove the username (empty string), you'll be fine. > > Not terribly bad but quite annoying. > > Max > > > On 19.02.2013, at 23:11, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> I cannot reproduce this on the latest pharo image.... >> I added it as a MCGemstoneRepository with the full url and it works... >> >> MCGemstoneRepository >> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >> user: '' >> password: '' >> >> I can browse and load files. Can you give me more details? >> >> On 2013-02-19, at 21:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> Got this thing biting me while testing the relase: >>> >>> I added a project of mine from the ss3.gemstone.com system and the >>> Monticello registration over there says: >>> >>> >>> MCHttpRepository >>> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >>> user: 'PBK' >>> password: '' >>> >>> >>> I add that into Pharo as a ss3 repository. >>> >>> There I am asked for: >>> >>> MCGemstoneRepository >>> location: 'http://ss3.gemstone.com/ss/' >>> user: '' >>> password: '' >>> >>> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >>> and copy/pasted as usual. >>> >>> Then, error. >>> >>> Took a minute to see why and get my mcz back. >>> >>> So, either SS3 has to change the registration information or Pharo >>> does something weird with SS3. I don't know. >>> >>> Guess I need to put things in SmalltalkHub :-) >>> >>> Phil >>> >> >> > >

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by phil＠highoctane.be

Well, latest Pharo2.0 tells me:MCGemstoneRepository Expected when putting MCHttp... for an ss3 repo. Maybe are you using the HTTP entry, I don't know. Phil 2013/2/19 Frank Shearar <frank.shearar(a)gmail.com>: > On 19 February 2013 22:18, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> Responses in the text below. >> >> 2013/2/19 Frank Shearar <frank.shearar(a)gmail.com>: >>> On 19 February 2013 20:51, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>>> Got this thing biting me while testing the relase: >>>> >>>> I added a project of mine from the ss3.gemstone.com system and the >>>> Monticello registration over there says: >>>> >>>> >>>> MCHttpRepository >>>> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >>>> user: 'PBK' >>>> password: '' >>>> >>>> >>>> I add that into Pharo as a ss3 repository. >>>> >>>> There I am asked for: >>>> >>>> MCGemstoneRepository >>>> location: 'http://ss3.gemstone.com/ss/' >>>> user: '' >>>> password: '' >>> >>> Where/what is "there"? Something's prompting you to fill in repository >>> details and autofilled it with an MCGemstoneRepository declaration? >> >> Where is in Pharo 2.0 Monticello when adding an SS3 repository. >> That's what the text editor area contains as default text. >> >>> >>>> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >>>> and copy/pasted as usual. >>>> >>>> Then, error. >>>> >>>> Took a minute to see why and get my mcz back. >>>> >>>> So, either SS3 has to change the registration information or Pharo >>>> does something weird with SS3. I don't know. >>>> >>>> Guess I need to put things in SmalltalkHub :-) >>> >>> Well, ss3 is just an HTTP Monticello repository service. It's not >>> ss3's fault that something else mentioned MCGemstoneRepository. >> >> As long as both would work, it would be a non issue. But using >> MCHttpRepository >> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >> user: 'PBK' >> password: '' >> >> fails miserably in Pharo 2.0. That's why I had to change it to >> MCGemstoneRepository for it to work. >> >> So, either ss3 isn't just an HTTP Monticello repository service or >> Pharo 2.0 introduced something special... I don't know. > > How very odd. I _always_ use MCHTTPRepository when accessing ss3 projects. > > frank > >>> frank >>> >>>> Phil >>>> >>> >> >

Feb. 19, 2013

Re: [Pharo-project] please test 2.0

by Camillo Bruni

thanks, I will try it with that one and see what happens. On 2013-02-19, at 23:28, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Latest PharoVM from the CI > > 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 > git://gitorious.org/cogvm/blessed.git Commit: > 05ed728452dc92732f9f23ce24a3c32bfdc0f4b8 Date: 2013-02-15 17:04:09 > +0100 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14519 > ' > > 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: >> I start to believe that it might be your VM? >> Which version are you using? >> >> Smalltalk vm version >> >> does the trick. >> >> On 2013-02-19, at 21:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> Pharo 2.0 not 1.4 >>> >>> The World Menu > System >Software Update started working and then >>> threw me in teh debugger where I had the error. I inspected several >>> variables and then did some Restart,, Over, Over, ..Proceed and things >>> went fine. >>> >>> There was a ZnClient in there but I can't figure out why there was a >>> mention of SmallInteger. >>> >>> Phil >>> >>> 2013/2/19 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>>> Even weirder: played with the debugger and sayed Over Over Over then >>>>> Proceed and it worked. Strange.... >>>>> >>>> What do you mean exactly ? You were not able to Proceed after clicking on >>>> Over several times on Pharo 1.4 ? >>>> I've just made a fix in the debugger that was integrated today.Give me more >>>> details to know if I have to look at it. >>>> >>>> Clement >>>> >>>>> Phil >>>>> >>>>> 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>>> Hi, >>>>>> >>>>>> We are almost there for the release, but we still need a little effort >>>>>> more. >>>>>> Would be terrific if everyone of you took the latest 2.0 image and test >>>>>> it with your usual workflows (we cannot imagine all, they are infinite :) >>>>>> >>>>>> And please report bugs, and JUST bugs :) >>>>>> >>>>>> all the "nice to have" can be reported, but in 3.0 milestone (or not >>>>>> milestone at all). >>>>>> >>>>>> cheers, >>>>>> Esteban >>>>> >>>> >>> >> >> >

Feb. 19, 2013

Re: [Pharo-project] please test 2.0

by phil＠highoctane.be

Latest PharoVM from the CI 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 git://gitorious.org/cogvm/blessed.git Commit: 05ed728452dc92732f9f23ce24a3c32bfdc0f4b8 Date: 2013-02-15 17:04:09 +0100 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14519 ' 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: > I start to believe that it might be your VM? > Which version are you using? > > Smalltalk vm version > > does the trick. > > On 2013-02-19, at 21:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> Pharo 2.0 not 1.4 >> >> The World Menu > System >Software Update started working and then >> threw me in teh debugger where I had the error. I inspected several >> variables and then did some Restart,, Over, Over, ..Proceed and things >> went fine. >> >> There was a ZnClient in there but I can't figure out why there was a >> mention of SmallInteger. >> >> Phil >> >> 2013/2/19 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>> Even weirder: played with the debugger and sayed Over Over Over then >>>> Proceed and it worked. Strange.... >>>> >>> What do you mean exactly ? You were not able to Proceed after clicking on >>> Over several times on Pharo 1.4 ? >>> I've just made a fix in the debugger that was integrated today.Give me more >>> details to know if I have to look at it. >>> >>> Clement >>> >>>> Phil >>>> >>>> 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> Hi, >>>>> >>>>> We are almost there for the release, but we still need a little effort >>>>> more. >>>>> Would be terrific if everyone of you took the latest 2.0 image and test >>>>> it with your usual workflows (we cannot imagine all, they are infinite :) >>>>> >>>>> And please report bugs, and JUST bugs :) >>>>> >>>>> all the "nice to have" can be reported, but in 3.0 milestone (or not >>>>> milestone at all). >>>>> >>>>> cheers, >>>>> Esteban >>>> >>> >> > >

Feb. 19, 2013

Re: [Pharo-project] Continuing weirdness with SS3.gemstone.com and Monticello in Pharo 2.0

by phil＠highoctane.be

Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure. Anyway, cannot send you any image for testing... it was frozen. This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure? I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now. I don't even want to think about life before Monticello ... Yikes! Phil 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: > this is rather strange. > We're using gemstone for all pharo development and we haven't had any problems with it. > > I loaded all the stuff from your test-repository and it worked. > more details? ;) > > On 2013-02-19, at 22:06, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> So, I wanted to merge my stuff from the SS3 project. >> >> When loading it needed to have BitBltPen (which I had somewhere as in >> BitBltPen-MarianoMartinezPeck.4.mcz) >> >> I wanted to put that into my SS3 area and so, added the repository to >> the list of repos in monticello, then took the mcz and then added the >> repository to the package. >> >> Net result: Frozen image. >> >> No amount of Cmd-. could do anything. >> >> See screenshot. >> >> ... now restarting VM... >> >> Phil >> <Capture dâÃ©cran 2013-02-19 Ã 22.01.46.png> > >

Feb. 19, 2013

Re: [Pharo-project] Pharo 2.0 UITheme current solidMenuIcon (and for sure some friends) are wrong due to VM problem

by Camillo Bruni

humm that is all strange... under which platform are you? On 2013-02-19, at 22:49, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > I managed to load my code into Pharo 2.0 without problems. Sweet! > > There is some direct use of morphic all looks like to work well. > Sound also works nicely. > > Still an issue with the World Menu where I do use menuCommandOn with > an icon set to: > > UITheme current solidMenuIcon > > The icon looks quite warped or plain wrong (looks like a crappy cloud). > > The code of the method in 1.4 is > > solidMenuIconContents > "Private - Method generated with the content of the file > /home/plantec/dvpt/Pharo/Sprint-10-09/Icons/solidMenu.png" > ^ 'iVBORw0KGgoAAAANSUhEUgAAAA4AAAAQCAYAAAAmlE46AAAABHNCSVQFBQUBSsjp7wAAAE5J > REFUeF5jgACO/wykA5AmGCZGHVaNxGISNO648AO7RpAEIYxXI8lOJaSRIqeiaSbeRrwaSXAu > lZxKQsiSEh0oSY+cJEdissORGUjLWgBvFzCDqCcU6AAAAABJRU5ErkJggg==' > > and in 2.0 it is > > solidMenuIconContents > "Private - Method generated with the content of the file > /home/plantec/dvpt/Pharo/Sprint-10-09/Icons/solidMenu.png" > ^ 'iVBORw0KGgoAAAANSUhEUgAAAA4AAAAQCAYAAAAmlE46AAAABHNCSVQFBQUBSsjp7wAAAE5J > REFUeF5jgACO/wykA5AmGCZGHVaNxGISNO648AO7RpAEIYxXI8lOJaSRIqeiaSbeRrwaSXAu > lZxKQsiSEh0oSY+cJEdissORGUjLWgBvFzCDqCcU6AAAAABJRU5ErkJggg==' > > Looks like the same to me. So, something isn't right. > > I tried the image with the StackVM and there, the icon is right. It > has the right colors instead of a white cloud. > > Maybe due to a plugin, I don't know. The VM I tried is the latest one > I got with the ciPharoVM.sh script. > > My self compiled PharoVM exhibits the same problem. > > CogVM shows the right icons (even if it complains that the VM is too > old for the image) > > Smalltalk vmVersion gives: > > 'CoInterpreter VMMaker.oscog-eem.264 uuid: > 64e76092-8af7-449f-9188-e65f3bd1f08d Feb 5 2013 > StackToRegisterMappingCogit VMMaker.oscog-eem.264 uuid: > 64e76092-8af7-449f-9188-e65f3bd1f08d Feb 5 2013 > VM: r2678 http://www.squeakvm.org/svn/squeak/branches/Cog Plugins: > r2545 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins > ' > > I tried with the code generated to create a cog VM from Esteban and > there it works fine. > > Smalltalk vmVersion gives there: > > 'CoInterpreter VMMaker-oscog-EstebanLorenzano.231 uuid: > a9e39f38-e1fa-4851-a3a3-1a0f1f7a4062 Feb 15 2013 > StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.231 uuid: > a9e39f38-e1fa-4851-a3a3-1a0f1f7a4062 Feb 15 2013 > git://gitorious.org/cogvm/blessed.git Commit: > 63aa6ed8a070fc730224b496e0dda7c3f8482e10 Date: 2013-02-14 11:43:21 > +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> > ' > > Here is the version for the problematic VM (latest downloaded from ci) > > Smalltalk vm version > > 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Feb 18 2013 > git://gitorious.org/cogvm/blessed.git Commit: > 05ed728452dc92732f9f23ce24a3c32bfdc0f4b8 Date: 2013-02-15 17:04:09 > +0100 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14519 > ' > > Maybe some NB dark magic going on... > > On the other side, loading PNGs from disk worked okay. (As the larger > icons on the background of the screenshot demonstrate). > > Hope you can figure out why there is such an issue. > > Phil > <Capture dâÃ©cran 2013-02-19 Ã 22.27.37.png><Capture dâÃ©cran 2013-02-19 Ã 22.39.43.png><Capture dâÃ©cran 2013-02-19 Ã 22.41.41.png>

Feb. 19, 2013

Re: [Pharo-project] Monticello and SS3 discrepancy in Pharo 2.0

by Camillo Bruni

yes indeed I misread the first time :), tried both now and they work here. On 2013-02-19, at 23:21, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Read again. > > MCGemstoneRepository works. > > But on ss3, what is listed on the project? For sure not that but: > MCHttpRepository. > See screenshot. > > Ese es el problema... > > Phil > > > > 2013/2/19 Camillo Bruni <camillobruni(a)gmail.com>: >> I cannot reproduce this on the latest pharo image.... >> I added it as a MCGemstoneRepository with the full url and it works... >> >> MCGemstoneRepository >> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >> user: '' >> password: '' >> >> I can browse and load files. Can you give me more details? >> >> On 2013-02-19, at 21:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> Got this thing biting me while testing the relase: >>> >>> I added a project of mine from the ss3.gemstone.com system and the >>> Monticello registration over there says: >>> >>> >>> MCHttpRepository >>> location: 'http://ss3.gemstone.com/ss/HO-Experiments' >>> user: 'PBK' >>> password: '' >>> >>> >>> I add that into Pharo as a ss3 repository. >>> >>> There I am asked for: >>> >>> MCGemstoneRepository >>> location: 'http://ss3.gemstone.com/ss/' >>> user: '' >>> password: '' >>> >>> I didn't noticed the MCGemstoneRepository instead of MCHttpRepository >>> and copy/pasted as usual. >>> >>> Then, error. >>> >>> Took a minute to see why and get my mcz back. >>> >>> So, either SS3 has to change the registration information or Pharo >>> does something weird with SS3. I don't know. >>> >>> Guess I need to put things in SmalltalkHub :-) >>> >>> Phil >>> >> >> > <Capture dâÃÃ´eÃÃcran 2013-02-19 aÃÃ 23.19.32.png>

Feb. 19, 2013