- Pharo-dev - lists.pharo.org

[Pharo-project] about Object>>step
by stephane ducasse Oct. 21, 2010

Oct. 21, 2010

Hi guys Object>>stepIn: aWindow ^ self step but step is not defined in Object. I have the i

1 0

[Pharo-project] About Project
by stephane ducasse Oct. 21, 2010

Oct. 21, 2010

Hi guys It would be good to take some decisions about Project. It seems that we need a place to host some information about the current graphical space but we should clean it. I was checking CUIS and Cuis only have 6 class side methods. S.

1 0

[Pharo-project] Issue 3130: MethodReference >> #isLocalSelector should not be part of Monticello package
by Pavel Krivanek Oct. 21, 2010

Oct. 21, 2010

This fix makes PackageInfo independent on Monticello. See http://code.google.com/p/pharo/issues/detail?id=3130 -- Pavel

1 0

[Pharo-project] ^ character in ubuntu
by Diogenes Moreira Oct. 21, 2010

Oct. 21, 2010

hi falks. I'm using Pharo 1.1 OneClick Package in Ubuntu 10.4 with the follow locale. when press ^ character in the pharo editor i get "?" symbol.. What configuration I need change? Other data, if i using the cut & paste from othe application, that work fine. Thank in advance. iogenes@diogenes-desktop:~$ locale LANG=es_AR.utf8 LC_CTYPE="es_AR.utf8" LC_NUMERIC="es_AR.utf8" LC_TIME="es_AR.utf8" LC_COLLATE="es_AR.utf8" LC_MONETARY="es_AR.utf8" LC_MESSAGES="es_AR.utf8" LC_PAPER="es_AR.utf8" LC_NAME="es_AR.utf8" LC_ADDRESS="es_AR.utf8" LC_TELEPHONE="es_AR.utf8" LC_MEASUREMENT="es_AR.utf8" LC_IDENTIFICATION="es_AR.utf8" LC_ALL= cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS diogenes@diogenes-desktop:~$ uname -a Linux diogenes-desktop 2.6.32-25-generic-pae #44-Ubuntu SMP Fri Sep 17 21:57:48 UTC 2010 i686 GNU/Linux

4 7

Re: [Pharo-project] [Pharo-users] [ANN] Continue working in SimpleLogger
by StÃ©phane Ducasse Oct. 21, 2010

Oct. 21, 2010

and another guy will come and repeat again the same.... sounds to loop here... My point is that why do we extend something that apparently is just done for not been extended else it will be complex and somebody else will restart. Because if toothpick would have been called simpleLogger then may be people would have looked at it the first time. Sorry to be boring this morning but you are wrap in a moebius trick. Tell us when SimpleLogger will not be simple so that we start another simpleloggerBis :) Stef > This was my point when I wrote SimpleLogger, not time to understand > nor port other framework and needed simething really basic. > > I documented it on Pharo book chapter, we should extend now such > chapter with the doc of new features. > > Cheers. > > > 2010/10/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Thu, Oct 21, 2010 at 7:24 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> why don;t you look look at toothpick? >>> >> >> Because I don't have time to learn a new logging framework, nor to make it >> work on Pharo. I don't plan to be part of a logging framework. I just needed >> something really EASY for my projects. So, I remembered GermÃ¡n doing that, I >> know it was working in Pharo, and it took me 5 minutes to understand. 2 >> hours more to add my features, and that's all :) I just make it public for >> other users. >> >> Chees >> >> Mariano >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] [update 1.2] #12203
by StÃ©phane Ducasse Oct. 21, 2010

Oct. 21, 2010

12203 ----- - Issue 654: inconsistent highlight color. Thanks Alain Plantec - Issue 3101: Wrong Monticello packages initialization order. Thanks Pavel Krivanek

1 0

Re: [Pharo-project] [ANN] Continue working in SimpleLogger
by StÃ©phane Ducasse Oct. 21, 2010

Oct. 21, 2010

why don;t you look look at toothpick? On Oct 21, 2010, at 3:23 AM, Yanni Chiu wrote: > On 20/10/10 9:36 AM, Mariano Martinez Peck wrote: >> What I did basically is to define SimpleLogger like the public API. But >> then, this class delegates to a LoggerStrategy. I created the following >> implementations: TranscriptLoggerStrategy, NullLoggerStrategy, >> FileLoggerStrategy and FixesFileNameLoggerStrategy. In addition, I >> created a superclass for them, marking the API with SimpleLogger. This >> class is LoggerStrategy. >> >> So, now you can: >> >> - Enable and disable easily the logging (thanks to NullLoggerStrategy). >> - Change on runtime WHERE or HOW to log (just change the strategy). >> - Be able to write into a File, a Transcript, a FixedFileName, or nothing. >> - Extend to you own strategy (FileAppendLoggerStrategy?? >> SocketLoggerStrategy? etc...) > > My 2cents. I've not used or looked at SimpleLogger, but recall that it was a single class, plus a metacello config class. > > The new functionality sounds very useful, but is it still simple. It sounds like it was simple to add extra features - maybe because SimpleLogger was simple. Will the next person who comes along find a similarly simple implementation that can be easily adapted to specific needs. > > A hierarchy of strategy classes no longer sounds simple. What if I don't need all the different strategies loaded, will the configuration then allow multiple build targets for various individual or groups of strategies. Starting to sound complicated. > > IMHO, it should be a fork: SomewhatSimpleOnItsWayToComplicatedLogging :) > > -- > Yanni > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 2

Oct. 21, 2010

Excellent! Good infrastructure will make us all much faster. I like the motto of marcus: fix what we use daily to get faster. On Oct 21, 2010, at 9:40 AM, Fernando olivero wrote: > Great work Alain!Now porting my icon importer is going to be easier! > The idea is to use the Gaucho icon importer to be able to choose amongst different external icon families , greatly improving the look and fell of the tools. > Having a single entry point goes into this direction! > I will create an issue for this. > > Fernando > On Oct 20, 2010, at 11:33 PM, Alain Plantec wrote: > >> Le 20/10/2010 23:13, Alain Plantec a Ã©crit : >>> Le 20/10/2010 22:47, StÃ©phane Ducasse a Ã©crit : >>>> 12201 >>>> ----- >>>> - Issue 1800: MenuIcons and ThemeIcons should be merged. Big >>>> thanks to alain plantec!!! >>> well, too fast, there is a problem with a missing icon. >>> I'm afraid you have to rollback >>> sorry >>> Alain >> well, I can't reproduce the problem. >> finally it's seems ok after having updated again. >> the icon is where it should be. >> alain >>> >>>> _______________________________________________ >>>> 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

1 0

Oct. 21, 2010

come on tooth pick has even documentation and it does not look complex. redoing all over things does not reduce bugs and http://www.metaprog.com/Toothpick/docs/quickstart.html It looks clean and simple. Stef On Oct 21, 2010, at 9:51 AM, Mariano Martinez Peck wrote: > > > On Thu, Oct 21, 2010 at 7:24 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > why don;t you look look at toothpick? > > > Because I don't have time to learn a new logging framework, nor to make it work on Pharo. I don't plan to be part of a logging framework. I just needed something really EASY for my projects. So, I remembered GermÃ¡n doing that, I know it was working in Pharo, and it took me 5 minutes to understand. 2 hours more to add my features, and that's all :) I just make it public for other users. > > Chees > > Mariano > > > On Oct 21, 2010, at 3:23 AM, Yanni Chiu wrote: > > > On 20/10/10 9:36 AM, Mariano Martinez Peck wrote: > >> What I did basically is to define SimpleLogger like the public API. But > >> then, this class delegates to a LoggerStrategy. I created the following > >> implementations: TranscriptLoggerStrategy, NullLoggerStrategy, > >> FileLoggerStrategy and FixesFileNameLoggerStrategy. In addition, I > >> created a superclass for them, marking the API with SimpleLogger. This > >> class is LoggerStrategy. > >> > >> So, now you can: > >> > >> - Enable and disable easily the logging (thanks to NullLoggerStrategy). > >> - Change on runtime WHERE or HOW to log (just change the strategy). > >> - Be able to write into a File, a Transcript, a FixedFileName, or nothing. > >> - Extend to you own strategy (FileAppendLoggerStrategy?? > >> SocketLoggerStrategy? etc...) > > > > My 2cents. I've not used or looked at SimpleLogger, but recall that it was a single class, plus a metacello config class. > > > > The new functionality sounds very useful, but is it still simple. It sounds like it was simple to add extra features - maybe because SimpleLogger was simple. Will the next person who comes along find a similarly simple implementation that can be easily adapted to specific needs. > > > > A hierarchy of strategy classes no longer sounds simple. What if I don't need all the different strategies loaded, will the configuration then allow multiple build targets for various individual or groups of strategies. Starting to sound complicated. > > > > IMHO, it should be a fork: SomewhatSimpleOnItsWayToComplicatedLogging :) > > > > -- > > Yanni > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Oct. 21, 2010

On Oct 20, 2010, at 1:32 PM, Martin Dias wrote: > Hi, > > I really like to use refactoring commands in OmniBrowser, but I would like to access them faster. I think that it would be nice to have: > > - A shortcut that popups a menu with the refactor commands only. > - A unique shortcut for rename (which target is the current selection: categories, class, method, class variable, instance variable, temporary) > > What do you think about it? > Do you know if there is something like that already available to use? Yes I would love to have a better organization with the most used refactoring actions also on the top of the menu. I know lukas does not like that. Now what we can do it to have a package to add these items on top of OB and we load it, after OB-RB and everybody is happy. Can you provide that code? > Martin > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1