December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Ring - model infrastructure for Pharo

by Igor Stasenko

On 13 December 2010 20:44, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> >> #stringVersionDefault has just one sender (#markMatchingClasses in SelectorBrowser). Do we need that? > > let's happily kill it. > yeah. The less - the more. :) >> >> In general, #stringVersion in MethodReference seems to be strange... >> >> stringVersion: Â Â Â Â Â Â Â Â 'Class>>selector:' format >> >> why is there an iVar for this? Can't this just use the selector and class an build it? >> >> Â Â Â Marcus >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> > > > -- Best regards, Igor Stasenko AKA sig.

Dec. 14, 2010

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

by pharo＠googlecode.com

Comment #3 on issue 1915 by renggli: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915 The monolithic ToolSet is indeed a big problem. I do not understand the proposed solution. I suggest that each of Browser, Debugger, Inspector, Transcript, Workspace, Process get their own AppRegistry subclass. There are already various (mostly unused) AppRegistry subclasses, splitting ToolSet into multiple classes would solve most of the problem. An alternative (and probably even better) would be to make the standard tools unloadable, including their class extensions like Object>>#inspect, Object>>#browse, ... Like this the registry would not be necessary and people could just load whatever implementation they want (the menus are already configurable by other means). Lukas

Dec. 14, 2010

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