- Pharo-dev - lists.pharo.org

Re: [Pharo-project] good news of the year

by Geert Claes

StÃ©phane Ducasse wrote: > > For SqueakSource, ESUG is paying the iliad guys to show that their > technology is cool and they will rewrite from scratch. We are negociating > since a couple of months with inria to have a web-dav server so that we > can host all the monticello related host. > More great news then! Since its a complete re-write and assuming it will serve for both Squeak and Pharo projects alike, I am wondering if its just me but I reckon it could do with a nice new name too :) If so it probably deserves a separate thread -- View this message in context: http://forum.world.st/good-news-of-the-year-tp3083142p3086645.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 14, 2010

Re: [Pharo-project] Issue 1213 in pharo: Unable to type some czech characters

by pharo＠googlecode.com

Comment #19 on issue 1213 by stephane.ducasse: Unable to type some czech characters http://code.google.com/p/pharo/issues/detail?id=1213 Yes and I closed it at least two times too, when I integrated it.

Dec. 14, 2010

Re: [Pharo-project] Issue 3410 in pharo: Remove NEwInspector from Dev

by pharo＠googlecode.com

Updates: Cc: guillermopolito Comment #2 on issue 3410 by marianopeck: Remove NEwInspector from Dev http://code.google.com/p/pharo/issues/detail?id=3410 (No comment was entered for this change.)

Dec. 14, 2010

Re: [Pharo-project] Issue 3410 in pharo: Remove NEwInspector from Dev

by pharo＠googlecode.com

Comment #1 on issue 3410 by marianopeck: Remove NEwInspector from Dev http://code.google.com/p/pharo/issues/detail?id=3410 The problem with this is that, I want to let the NewInspector for those who want to use it instead of the default one (like me). But right now, this doesn't work, because of the ToolSet. I can live without the NewInspector, but having fixed issue:1915 would make this one much easier :)

Dec. 14, 2010

[Pharo-project] "Making ToolSet more flexible", any taker?

by Mariano Martinez Peck

Hi guys. I am out of time, but if someone wants to do a nice and not so difficult contribution to Pharo, is to improve the ToolSet support. Issue is here: http://code.google.com/p/pharo/issues/detail?id=1915 And discussion is here: http://forum.world.st/Questions-about-ToolSet-td1460544.html Cheers Mariano

Dec. 14, 2010

Re: [Pharo-project] Issue 1915 in pharo: Making ToolSet more flexible

by pharo＠googlecode.com

Comment #2 on issue 1915 by marianopeck: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915 Here was the discussion http://forum.world.st/Questions-about-ToolSet-td1460544.html

Dec. 14, 2010

Re: [Pharo-project] TODO for 1.2...

by Marcus Denker

On Dec 14, 2010, at 2:35 AM, Guillermo Polito wrote: > Marcus, > > Here we have a "blue" build: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/11/ > How did you manage that? :P > Did you remove the test run from the build? > yes... I was wondering where exactly the process was failing (but then, one can see that fom the console)... Next step: remove the deprecated calls (or change deprecation warning setting) then I will turn on the tests again. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 14, 2010

[Pharo-project] cog and crash.dmp

by Alexander LazareviÄ

Hi! Not my turf, so I'm a little puzzled! Does the latest cog vm for windows (7) also write a crash.dmp file to the vmpath when it crashes? The dialog says so, but I can't find the file in that directory. I have permission to create/write files in that directory.Is there some sort of switch/ini-Setting I have to set to make the vm dump that file on a crash? Alex

Dec. 14, 2010

[Pharo-project] Issue 3411 in pharo: FileDIrectory - search methods - unnecessary code & unclear use of read only

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3411 by rhaw...(a)plymouth.ac.uk: FileDIrectory - search methods - unnecessary code & unclear use of read only http://code.google.com/p/pharo/issues/detail?id=3411 In FileDirectory, category 'search', the method: withAllFilesDo: fileStreamBlock andDirectoriesDo: directoryBlock - has a line that I think does nothing: directoryBlock value: dir. - inexplicably makes reference to read only files for reasons that are not encapsulated in the method title, and which appear to be irrelevant to the purpose. (Well, I can't see the point!) That method is called from the method: filesContaining: searchString caseSensitive: aBoolean - but that is apparently unused (there are no senders).

Dec. 14, 2010

Re: [Pharo-project] TODO for 1.2...

by Guillermo Polito

Marcus, Here we have a "blue" build: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/11/ How did you manage that? :P Did you remove the test run from the build? Guille On Mon, Dec 13, 2010 at 1:54 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Open Bugs: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 > > Failing Tests: > > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… > > > and a failing build of non-Core: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console > > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

Dec. 14, 2010