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

[Pharo-project] [ANN] Win32 Installers for 1.0 and 1.1alpha

by astares＠gmx.de

The download page now includes TWO new setups for Win32 - Windows Installer 1.0-10500-rc1dev09.12.1 (Pharo 1.0 RC1) - Windows Installer 1.1-11073-alphadev09.12.1 (Pharo 1.1 Alpha) similar to the ones release by Damien. The splash now also shows if it is the release candidate or the alpha. Now also successfully tested on a Windows7 machine. Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

Dec. 9, 2009

[Pharo-project] Gofer git

by StÃ©phane Ducasse

Hi guys I do not know if you noticed that with the latest version of Gofer you can get a full git behavior Gofer new squeaksource: 'PharoTaskForces'; addPackage: 'RPackage'; pull to pull all the packages pubslihed and fill up your local cache Gofer new squeaksource: 'PharoTaskForces'; addPackage: 'RPackage'; push to push your local saved versions to the repository.... Of course it means that you can build a database and when you run your script the cache is checked first.... so yes you can work in the train :) Tx lukas

Dec. 9, 2009

Re: [Pharo-project] DeprecationHistory

by Henrik Johansen

>From the standpoint of wanting to fix them, I really don't see the point in expanding the tree past the first level, but sure. As long as you have a right-click menu-item on each to open a browser on the method for easy fixing of the deprecated call site ;) Personally, I'd prefer a tree like in the picture attached, to me at least that's more intuitive. Cheers, Henry On Dec 9, 2009, at 12:19 31PM, Alain Plantec wrote: > Henrik Sperre Johansen a Ã©crit : >> +2 >> Even better if there's a button in each row to open a list of the methods that have been recorded as calling the deprecated version :D >> >> Henry >> > Hi Henry, > Maybe something like that (see screenshot): > > Each root shows a deprecated method call. > Here, 3 calls to the same deprecated method but from different paths. > The occurence show how many time the deprecated method has been called with the same caller chain. > 23 times for Try1>>call -> Try2>>call > 2 times for Try2>>call > 3 times for Try3>>call -> Try1>>call -> Try2>>call > > So, you see exactly which deprecated methods were called, from where and how many times. > > Alain > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> > > <DeprecationsTree.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 9, 2009

[Pharo-project] [update 1.1] #11083

by Marcus Denker

11083 ----- Issue 420: Grabbing point and moving windows aroung Issue 1152: HTTPSocket>>#getResponseUpTo: and HTTPSocket>>#getResponseUpTo:ignoring: are ugly and misleading Issue 1381: ClassTestCase relies on some undocumented naming conventions

Dec. 9, 2009

Re: [Pharo-project] DeprecationHistory

by Romain Robbes

That's a great idea! Romain On Dec 8, 2009, at 11:18 PM, Alain Plantec wrote: > Hi all, > One of my recents slice for preferences migration has made pharo > nearly > unusable > because a lot of deprecation dialogs was opened for a single browser. > Then, the user had to forbid the deprecation warnings in order to > avoid > these popups. > > Now, what about a non blocking window which is opened automatically > when > a deprecated method is run, > but showing the list of recents deprecations ? > A double click on a list item, et hop!, a browser is opened on the > deprecated method. > I've tried it on the last pharo image and it seems ok. With it, it is > still always possible to let deprecation warning > without having to close any dialog window. > What do you think ? > > A screenshot is attached. > Cheers > Alain > > > <DeprecationHistory.png><ATT00001..txt> -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

Dec. 9, 2009

Re: [Pharo-project] DeprecationHistory

by StÃ©phane Ducasse

alain this is cool. :) I want to reuse the code to enhance the classBrowser to see the documentation of the class in a file based view this is relate to what laurent is doing in seaside. On Dec 9, 2009, at 12:19 PM, Alain Plantec wrote: > Henrik Sperre Johansen a Ã©crit : >> +2 >> Even better if there's a button in each row to open a list of the methods that have been recorded as calling the deprecated version :D >> >> Henry >> > Hi Henry, > Maybe something like that (see screenshot): > > Each root shows a deprecated method call. > Here, 3 calls to the same deprecated method but from different paths. > The occurence show how many time the deprecated method has been called with the same caller chain. > 23 times for Try1>>call -> Try2>>call > 2 times for Try2>>call > 3 times for Try3>>call -> Try1>>call -> Try2>>call > > So, you see exactly which deprecated methods were called, from where and how many times. > > Alain > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> > > <DeprecationsTree.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 9, 2009

Re: [Pharo-project] DeprecationHistory

by Alain Plantec

Henrik Sperre Johansen a Ã©crit : > +2 > Even better if there's a button in each row to open a list of the > methods that have been recorded as calling the deprecated version :D > > Henry > Hi Henry, Maybe something like that (see screenshot): Each root shows a deprecated method call. Here, 3 calls to the same deprecated method but from different paths. The occurence show how many time the deprecated method has been called with the same caller chain. 23 times for Try1>>call -> Try2>>call 2 times for Try2>>call 3 times for Try3>>call -> Try1>>call -> Try2>>call So, you see exactly which deprecated methods were called, from where and how many times. Alain > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Dec. 9, 2009

[Pharo-project] package documentation viewer

by laurent laffont

Hi, for fun and *for me*, I've made a small Seaside app to quickly browse all documentation in a Pharo image. It's package oriented, all classes and selectors comment on a single page, so I can use search and print functions of my web browser. Someone might have a use of it. It's here: http://www.squeaksource.com/SimpleWebDoc.html Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc Laurent

Dec. 9, 2009

[Pharo-project] [update] #10502

by Marcus Denker

Hi, Two more fixes for 1.0... 10502 ----- Issue 889: MouseOverHandler send messages to nil Issue 1136: DejaVu strinkeFonts render ascii character in WideStrings as black boxes

Dec. 9, 2009

Re: [Pharo-project] ClassTree new openOn: Collection :)

by Tudor Girba

We are already using the MorphTreeMorph in Glamour in a 1.0 image. It's pretty cool. You can get it at: Gofer new squeaksource: 'Momo'; addPackage: 'Morphic-MorphTreeWidget'; load. Cheers, Doru On 8 Dec 2009, at 21:36, StÃ©phane Ducasse wrote: > 1.1 of course :) > I'm riding the wafe :) > > > On Dec 8, 2009, at 9:05 PM, Schwab,Wilhelm K wrote: > >> Stef, >> >> Where does this work? My RC1 image either does not contain the >> classes, or I'm being too dense to see the corrected thing in the >> list of choices. Interested, if only as examples to help me with a >> couple of tasks... >> >> Bill >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >> ] On Behalf Of StÃ©phane Ducasse >> Sent: Tuesday, December 08, 2009 11:08 AM >> To: Pharo-project(a)lists.gforge.inria.fr Development >> Cc: notre liste >> Subject: [Pharo-project] ClassTree new openOn: Collection :) >> >> I started to understand MorphTreeMorph to build a class >> documentation browsing browser and I discovered that >> >> ClassTree new openOn: Collection >> >> ClassList new openOn: Collection >> >> This is really a good start. >> We could have it for package >> and displaying methods.... >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Dec. 9, 2009