July 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] [update] #10392

by Marcus Denker

#10392 ------ Issue 946: UnicodeCompostitionStream and AttributedTextStream should be removed Issue 408: fix "source" button in the browser Issue 727: testClassDescriptionallSubInstances is yellow but when run individually green Issue 617: SystemNavigation>>allMethodsInCatergory: Issue 891: Bug in MIMEDocument makes ScriptLoader class>>#loadTools failure Issue 938: Text>>copyFrom:to: prevents using a subclasses 200 open reports, 42 for 1.0. Please Help!! http://code.google.com/p/pharo/issues/list Alex and Marcus

July 24, 2009

Re: [Pharo-project] New Pharo based on core 10388

by Schwab,Wilhelm K

Damien, A few random comments on the new image: (1) in the w2k theme, the pressed state of the browser buttons is "backwards." (2) When I open the Seaside image for the first time, it complains about a service already running on port 8080 - this is similar (not exactly the same though) as my working image started doing, but I have not loaded any of my code yet. Something must have changed. (3) I'm not sure about the new inspector. I have more or less adapted to the explorer and inspector; this looks like it's trying to do both jobs, and I will have to use it for a while to give a fair opinion. So far, I _think_ I'll be happier with the current tools. The last time an inspector really got my attention was a "diving inspector" that was ported to Dolphin a while back. The idea is that a double click/enter on an instance variable would alter the contents of the inspector, not open a new one, and there was a way to back up to any previous levels, one at a time. (4) The new default tool selections are greatly appreciated from a performance perspective. I'm on xp in my office at the moment, and it is reasonably snappy. I like for an IDE to be blazing on even remotely reasonable hardware, leaving cycles free to do useful work for me and my victims (make that customers<g>). There is room for improvement, but I think our "marketing" will no longer be swimming upstream. FWIW, I still think you should reconsider fast drag - enabling it makes a HUGE difference when moving and resizing windows. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Damien Cassou Sent: Friday, July 24, 2009 4:09 AM To: Pharo Development Subject: [Pharo-project] New Pharo based on core 10388 I've just released a new Pharo image (as well as a Pharo-web) based on 10388. I've installed NewInspector as the default inspector, please comment on that choice. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 24, 2009

Re: [Pharo-project] New Pharo based on core 10388

by Mariano Martinez Peck

On Fri, Jul 24, 2009 at 8:08 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > I've just released a new Pharo image (as well as a Pharo-web) based on > 10388. I've installed NewInspector as the default inspector, please > comment on that choice. > Damien are you talking about Frederic Pluquet work? I put something in a workspace like Smalltalk, right button, "inspect it" but it opens the default inspector. wasn't new inspector something like those Mac's app (finder?) ? best, Mariano > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 24, 2009

[Pharo-project] [update] #10391

by Marcus Denker

10391 ----- Issue 977: HostSystemMenusTest>> testCharacterChanging fails Issue 974: improve xor: implementation Issue 955: Mantis 7368 1.0 closeTo: 200 factorial -- Marcus Denker - http://marcusdenker.de New! UN-Number 1.2: http://appshopper.com/reference/un-nummer

July 24, 2009

[Pharo-project] [update] #10390

by Marcus Denker

10390 ===== Issue 913: Problem with ob-debugger Issue 488: [Pending Etoy Cleaning] convertToCurrentVersion: varDict refStream: smartRefStrm Issue 864: Socket>>remoteHostAddress sent but not implemented Issue 956: Mantis 7040: remove #asFloatSimply Issue 650: outermostWorldMorph>> "stuff below is really only for MVC" -- Marcus Denker - http://marcusdenker.de New! Skype Credit 2.1: http://2denker.de/skypecredit

July 24, 2009

Re: [Pharo-project] Smalltalk vs SmalltalkImage current woes

by Adrian Lienhard

I also like the idea since I always loose a few seconds to figure out where some method, like vmStatisticsReportString, is located. There are at least three different selectors used to access a singleton instance: SmalltalkImage current SystemNavigation default SystemChangeNotifier uniqueInstance I just can't remember them. Adrian On Jul 24, 2009, at 12:27 , Igor Stasenko wrote: > I am currently using the Cuis, which doesn't having a 'SmalltalkImage > current' refactoring.. > And this difference is a bit frustrating to me, especially when code > which have to be ported from Squeak, > i need to visit all the places and fix the references. > > I was not here when this change was introduced, and you maybe know , > that i'm a heated enemy of global state. > But i understand the reasoning of dissection the Smalltalk dictionary > of globals from the rest of service methods & additional state, > which is needed and which were putted in SmalltalkImage class. > > But the more i thinking about it, the more i feel that this > 'dissection' can be done in least intrusive way which is much > friendlier to 'old ways' > but also plays well with 'current ways'. > > So, what i'm proposing: > > - make a dictionary of globals a pure dictionary, without any extra > unrelated methods. > - completely move all fat stuff into SmalltalkImage from > SystemDictionary class > - add 'globals' ivar to SmalltalkImage class , and add proxy methods > for accessing the dictionary, like #at: #at:put: etc. > > then simply: > Smalltalk at: #Smalltalk put: (SmalltalkImage current). > > Now, Smalltalk == SmalltalkImage current and everyone is happy: > - dictionary lives in separate ivar, > - fat & boring housekeeping stuff lives in SmalltalkImage instance. > > What you think? > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 24, 2009

[Pharo-project] [update] #10389

by Marcus Denker

#10389 ------ -> remove duplicate/empty packages System, EventRewrite2, DeleteMe, Closure, ThreadSafeTranscript -> force reload dirty packages from repository This means, the image has no dirty repos after this update. Marcus -- Marcus Denker - http://marcusdenker.de New! Skype Forward 2.1.1: http://2denker.de/skypeforward

July 24, 2009

Re: [Pharo-project] squeaksource is down

by Adrian Lienhard

I had to restarted it. Hope, no data was lost this time... Adrian On Jul 24, 2009, at 17:05 , Tudor Girba wrote: > Hi, > > It looks like squeaksource is down. Can anyone take a look? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that > happen. They both matter." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 24, 2009

[Pharo-project] Anyone mixing Matlab/Octave and Pharo?

by Schwab,Wilhelm K

Hello all, Are any of you doing scientific computing on Pharo? I have some seriously old Numerical Recipes code that I altered and compiled, and more recently have used the GNU Scientific Library. All of that is connected to Dolphin, and it will take some time to adapt it to Pharo. Even more recently, I found reason to exceed GSL's feature list, and Octave might be able to do the job. The first thing would be do the minimum work to get some data into Octave and see how it does. Ideally, I would want to pipe data into Octave, get results from it, and then do some post-processing in Pharo. In GSL (dll/so) terms, the idea is to do all of the memory management and algorithm level work in Smalltalk, and the tight loops via the external code, and hopefully to do all of that w/o littering the drive with temporary files. Any experience, good or bad, in those directions? Bill

July 24, 2009

Re: [Pharo-project] Smalltalk vs SmalltalkImage current woes

by David Goehrig

On Fri, Jul 24, 2009 at 6:27 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > Now, Smalltalk == SmalltalkImage current and everyone is happy: > - dictionary lives in separate ivar, > - fat & boring housekeeping stuff lives in SmalltalkImage instance. > > What you think? I particularly like this idea from the standpoint of delivering a modules that exist within their own context. It is actually not that dissimilar from Forth systems that use different vocabs to support multiple incompatible applications at the same time. Something like this would solve one of the problems I've been running into recently, where some code keeps mucking up the SystemDictionary's associations causing the Compiler to error out. Dave -- -=-=-=-=-=-=-=-=-=-=- http://blog.dloh.org/

July 24, 2009