March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] SmalllineManifestCheckerTest class >> DoIt

by Ben Coman

March 21, 2014

Re: [Pharo-dev] Voyage cannot be load

by Norbert Hartl

What should be changed in order to solve it? Norbert Am 20.03.2014 um 17:09 schrieb Johan Brichau <johan(a)inceptive.be>: > Found it: > > Magritte3 references Grease1.1.5 explicitly > MongoTalk references Grease #stable > > Looks more like a Metacello bug to me... there clearly is a load conflict and Metacello should decide on a version rather than load them both sequentially. > But I have not looked any deeper.... > > Johan > > On 20 Mar 2014, at 17:02, Johan Brichau <johan(a)inceptive.be> wrote: > >> I can reproduce the problem. >> For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo). >> >> The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6. >> Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning. >> >> I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred. >> So, this is nothing specific to Grease / Magritte / Seaside / ... >> >> I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone. >> But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process. >> >> Johan >> >> On 20 Mar 2014, at 16:39, Johan Brichau <johan(a)inceptive.be> wrote: >> >>> Norbert, >>> >>> From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. >>> My first question is: why is it dirty? Can you check that? >>> >>> The package version you are loading is the one that is referenced by Grease 1.1.6 >>> >>> I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this. >>> >>> Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here. >>> >>> Johan >>> >>> On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >>>> >>>> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >>>> >>>> Any ideas? >>>> >>>> Norbert >>>> >>> >> > >

March 21, 2014

pharo on Debian

by Ralph Boland

On Debian I can install Squeak vis-a-vis apt-get install squeak. But I cannot do this for Pharo with Debian 7.0. Would it be a good idea to get this to work for Debian 8.0? Ralph Boland

March 21, 2014

Re: [Pharo-dev] Pharo on Debian 7

by phil＠highoctane.be

On my blog http://philippeback.be Works with some tweaks. Le 20 mars 2014 21:49, "jannik laval" <jannik.laval(a)gmail.com> a Ã©crit : > Hi, > > I tried to load Pharo portable on a Debian. It seems to not work. > Anyone can confirm that this is not my config that is broken ? > > Cheers, > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ >

March 20, 2014

Re: [Pharo-dev] Pharo on Debian 7

by Sergi Reyner

2014-03-20 21:16 GMT+00:00 jannik laval <jannik.laval(a)gmail.com>: > Ok, any solution ? or deb package ? > > Cheers, > Jannik > I can think of a number of ugly workarounds that defeat the purpose of having a portable package in the first place. Debian was my first choice for my VPS, but I ended up shoving Ubuntu into it after going through the list of available distros and being left with Ubuntu and Gentoo as the only choices with a new enough glibc. I have Gentoo on my desktop but I donÂ´t feel like maintaining it on the server. In the end the real solutions are either: 1- build the Pharo vm against an older glibc (though IÂ´m not sure how, IIUC you need to be able to run Pharo in order to build Pharo), or 2- build a statically linked vm, if possible, in another distro capable of running Pharo (again not sure :D) Cheers, Sergi

March 20, 2014

Re: [Pharo-dev] Pharo on Debian 7

by jannik laval

Ok, any solution ? or deb package ? Cheers, Jannik 2014-03-20 22:07 GMT+01:00 Sergi Reyner <sergi.reyner(a)gmail.com>: > 2014-03-20 20:45 GMT+00:00 jannik laval <jannik.laval(a)gmail.com>: > > Hi, >> >> I tried to load Pharo portable on a Debian. It seems to not work. >> Anyone can confirm that this is not my config that is broken ? >> > > Debian has an older libc than what the pharo binary links to (the Ubuntu > one, I guess). Or at least it was so a few weeks ago. > > Cheers, > Sergi > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

March 20, 2014

Re: [Pharo-dev] Pharo on Debian 7

by Sergi Reyner

2014-03-20 20:45 GMT+00:00 jannik laval <jannik.laval(a)gmail.com>: > Hi, > > I tried to load Pharo portable on a Debian. It seems to not work. > Anyone can confirm that this is not my config that is broken ? > Debian has an older libc than what the pharo binary links to (the Ubuntu one, I guess). Or at least it was so a few weeks ago. Cheers, Sergi

March 20, 2014

Re: [Pharo-dev] [Pharo-users] Tiling Window Manager in 3.0: working but still issues with WorldMorph

by Laurent Laffont

Done Laurent Le mercredi 19 mars 2014, 17:23:06 phil(a)highoctane.be a Ã©crit : > Would you mind putting the configuration in the 3.0 Metarepo? > > Phil > > > > > On Wed, Mar 12, 2014 at 6:52 PM, Laurent Laffont > <laurent.laffont(a)gmail.com>wrote: > > > Hi Phil, > > > > with latest ConfigurationOfTilingWindow manager World management (almost) > > works. Still a little display issue when creating a new world (need to > > change back and forth, seems to be some World repaint issue). > > > > I've also merged some experiments with GrowlMorph. > > > > Laurent > > > > > > Le mardi 11 mars 2014, 13:27:57 Laurent Laffont a Ã©crit : > > > Thanks a lot Phil. I will try to have a look. > > > > > > Laurent > > > > > > > > > Le samedi 8 mars 2014, 11:57:30 phil(a)highoctane.be a Ã©crit : > > > > TWM works in 3.0 after some work on icons and updating menus. > > > > > > > > Gofer new > > > > smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; > > > > configuration; > > > > load. > > > > > > > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > > '3.0') > > > > load > > > > > > > > You can also use > > > > > > > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > > > > #development) load > > > > > > > > but this will for sure change over time. > > > > > > > > There is the World management icon which is still there and it looks > > like > > > > it can create worlds but switching between them just breaks havoc. > > > > > > > > Maybe should we just remove that feature from TWM as 3.0 doesn't seem > > to be > > > > multiworld friendly. > > > > > > > > Nothing done on tests nor themeing (which appears to be not that > > working > > > > well in 3.0 either due to theming changes); > > > > > > > > At least the thing is back :-) [I missed it...] > > > > > > > > Phil > > > > > > > > > > > >

March 20, 2014

Re: [Pharo-dev] Weird indenting with #with:

by Sven Van Caekenberghe

On 20 Mar 2014, at 20:37, Camille Teruel <camille.teruel(a)gmail.com> wrote: > No that's definitively a bug. > It seems to happen to blocks that are arguments in cascaded messages. Ah, that makes some sense. Next question: can we fix it ;-)

March 20, 2014

Re: [Pharo-dev] Weird indenting with #with:

by Sven Van Caekenberghe

Thanks, it makes a difference indeed, but it does not yet quite solve it. I would want the contents of the #with: block to be treated the same as for example inside an #ifTrue:ifFalse: with just one tab (level) more. I just don't understand why it is different. On 20 Mar 2014, at 20:47, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > 2014-03-20 19:38 GMT+00:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I have been using the auto formatter with Seaside rendering code too, and I found it weird at times as well. The problem seems to be related to blocks. It is of course hard to argue with something automatic that is quite complex and over which there are many opinions. I have basically given up to worry about it and just accept it. It is either that or manual formatting, but that is hard when doing lots of source code refactorings. > > I just found out that adding #with: to the array in the 'Multi line messages' setting reduces the number of tabs to 2, which is somewhat more acceptable. IÂ´m not sure about it breaking some other formatting or not. I guess I will find out it thatÂ´s the case :) > > Cheers, > Sergi >

March 20, 2014