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

Re: [Pharo-project] Renaming instance variable

by Lukas Renggli

>> Also I would load AST-lr.160, newer versions of that package do not >> work in my images. > > What are the problems? > > It is related to the changes made by gwenael? I don't exactly know, I only noticed when Alexandre was reporting about the Refactoring Brwoser issues. The AST package seem to have changed a lot and it seems to subtly break the refactoring browser in several ways. I will have a look again. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 4, 2009

[Pharo-project] webpage typo

by Chris Kassopulo

Phrao is free and open source on page http://www.pharo-project.org/license nice website tried the latest pharo-dev image you guys are amazing

Feb. 3, 2009

Re: [Pharo-project] Renaming instance variable

by StÃ©phane Ducasse

Yeap Stef On Feb 3, 2009, at 10:57 AM, Torsten Bergmann wrote: > On Tue, Feb 3, 2009 at 9:35 AM, Lukas Renggli <renggli at gmail.com> > wrote: >>> It looks like the load scripts in Pharo load a very old and >>> incompatible version of the Refactoring Engine. > Damien Cassou wrote >> I already told them to avoid using their own scripts because I keep >> the universe up-to-date... I don't understand. > > > Maybe changing the load scripts to use universe can help here ... > > Bye > Torsten > > -- > Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL > fÃ¼r nur 17,95 Euro/mtl.!* http://dsl.gmx.de/? > ac=OM.AD.PD003K11308T4569a > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 3, 2009

Re: [Pharo-project] Renaming instance variable

by StÃ©phane Ducasse

On Feb 3, 2009, at 9:35 AM, Lukas Renggli wrote: > It looks like the load scripts in Pharo load a very old and > incompatible version of the Refactoring Engine. The package > RefactoringEngine is deprecated for a long time and shouldn't be used > anymore. Load Refactoring-Core instead. Ok we should remove the script from script loader and use the universe instead. > > > Also I would load AST-lr.160, newer versions of that package do not > work in my images. What are the problems? It is related to the changes made by gwenael? Stef > > > Lukas > > On Tue, Feb 3, 2009 at 9:16 AM, Lukas Renggli <renggli(a)gmail.com> > wrote: >>> In a 10204, using OBAlpha (I did not try with OB). >> >> What is OBAlpha? What is the difference to OB? >> >>> I created a class >>> FooBar with a variable 'abc'. Right click on the class, 'Refactor >>> instance variable / rename'. What ever the new name, I get an error. >> >> What kind of Error? Can you provide a stack-trace? I cannot >> reproduce. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 3, 2009

Re: [Pharo-project] Seaside?

by StÃ©phane Ducasse

Yeap Also ScriptLoader is a private class :) Do not use it or only at your own risk. ScriptLoader is our tools to manage the release. Use pharo-dev. Stef On Feb 3, 2009, at 4:43 PM, Adrian Lienhard wrote: > Hi Torsten, > > On Feb 3, 2009, at 16:29 , Torsten Bergmann wrote: > >> Lukas wrote >>> Use PackageUnivsers. >> >> ... which is not included by default in the pharo image. >> Using "ScriptLoader new universalInstaller" is one way to install it. >> >> Is there another more intuitive way? To know about all this >> could be a hard barrier for people who start with Pharo ... > > True, but this is only the current situation. We plan to put a > packaging manager in place that will be shipped with the Pharo image. > It is supposed to provide a "universe" of stable packages. Unlike the > current situation with Universes and SqueakMap, the idea is that these > stable versions actually work together and are stable ;) > > Some patience is needed, though --- or more people that help ;) > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > >> >> >> Bye >> T. >> >> >> >> >> >> >> >> >> -- >> Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit >> allen: http://www.gmx.net/de/go/multimessenger01 >> >> _______________________________________________ >> 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 >

Feb. 3, 2009

Re: [Pharo-project] Monticello Changes Dialog

by StÃ©phane Ducasse

I will integrate soon. On Feb 3, 2009, at 2:39 PM, GARY CHAMBERS wrote: > Remember for trees - you can right-click on an arrow to expand all > at that level. > Pane arrangement - line-by-line comparison isn't really possible in > any other arrangement. > Keys are a problem with ParagraphEditor being all or nothing... > > Polymorph-Tools-Diff-gvc.10 adds a preference: useNewDiffToolsForMC > just for you! > > (apologies for my email name in CAPITALS, the webmail won't let me > change it!) > > Regards, Gary. > > From: Lukas Renggli <renggli(a)gmail.com> > To: Pharo Development <pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, 3 February, 2009 8:44:36 AM > Subject: [Pharo-project] Monticello Changes Dialog > > Is there a clean way to get back the original changes dialog of > Monticello? > > The new dialog looks cool, but for me it is totally inefficient. > > - I don't have an overview of the applied changes anymore. It is very > painful to review a big set of changes where everything is hidden > inside a tree that I have to traverse manually. > > - Another problem is the arrangement of the panes. Even if I work on a > screen that is 2560 pixel wide there are many methods that get clipped > at the right side. It is impossible to review changes in long lines. > > - Also I cannot easily browse the involved classes. In the old dialog > I could press Apple+B on any item and it opened a browser on the > particular class/method. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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

Feb. 3, 2009

Re: [Pharo-project] Renaming instance variable

by StÃ©phane Ducasse

Ok I was not aware of that. The problem is that when you code in the core then you should not have the other packages loaded or they should saved in the pharo repository. Damien could you modify the scriptloader to use the universe to load RB? Stef On Feb 3, 2009, at 9:54 AM, Damien Cassou wrote: > On Tue, Feb 3, 2009 at 9:35 AM, Lukas Renggli <renggli(a)gmail.com> > wrote: >> It looks like the load scripts in Pharo load a very old and >> incompatible version of the Refactoring Engine. > > I already told them to avoid using their own scripts because I keep > the universe up-to-date... I don't understand. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 3, 2009

Re: [Pharo-project] Seaside?

by Lukas Renggli

> I haven't tried, but you can have a look at the class side of the > class ScriptLoader. There is method to load Seaside 2.9 That script does not load an "official" set of packages. To me it does not look like it works. If you want Seaside 2.9 you should use <http://builder.seaside.st/>. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 3, 2009

Re: [Pharo-project] Seaside?

by Damien Cassou

On Tue, Feb 3, 2009 at 4:29 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > ... which is not included by default in the pharo image. > Using "ScriptLoader new universalInstaller" is one way to install it. > > Is there another more intuitive way? To know about all this > could be a hard barrier for people who start with Pharo ... Universe will be included in Pharo as can be seen in http://code.google.com/p/pharo/wiki/Packages -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 3, 2009

Re: [Pharo-project] Seaside?

by Adrian Lienhard

Hi Torsten, On Feb 3, 2009, at 16:29 , Torsten Bergmann wrote: > Lukas wrote >> Use PackageUnivsers. > > ... which is not included by default in the pharo image. > Using "ScriptLoader new universalInstaller" is one way to install it. > > Is there another more intuitive way? To know about all this > could be a hard barrier for people who start with Pharo ... True, but this is only the current situation. We plan to put a packaging manager in place that will be shipped with the Pharo image. It is supposed to provide a "universe" of stable packages. Unlike the current situation with Universes and SqueakMap, the idea is that these stable versions actually work together and are stable ;) Some patience is needed, though --- or more people that help ;) Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/ > > > Bye > T. > > > > > > > > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 3, 2009