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

Re: [Pharo-project] MergeTool request

by StÃ©phane Ducasse

I did not check if gary published a new version (may be I missed it). Stef On Jul 19, 2009, at 10:17 PM, Nicolas Cellier wrote: > 2009/7/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> nicolas >> >> if you use the old diff tool you get another menu item to install a >> specific method >> >>> Could we have: >>> - an indication of method timestamps (with initials) >>> - a button to select/reject all changes at once (usefull if you >>> merge >>> with a distant fork and want to be very selective) >> >> Now I do not understand the second item since it seems the inverse of >> what you put in () >> > > The idea was reject all changes, but a few selected manually > more or less same functionality as you described in old diff tool... > >> Stef >>> >>> Nicolas >>> >>> _______________________________________________ >>> 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

July 19, 2009

Re: [Pharo-project] MergeTool request

by Nicolas Cellier

2009/7/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > nicolas > > if you use the old diff tool you get another menu item to install a > specific method > >> Could we have: >> - an indication of method timestamps (with initials) >> - a button to select/reject all changes at once (usefull if you merge >> with a distant fork and want to be very selective) > > Now I do not understand the second item since it seems the inverse of > what you put in () > The idea was reject all changes, but a few selected manually more or less same functionality as you described in old diff tool... > Stef >> >> Nicolas >> >> _______________________________________________ >> 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 >

July 19, 2009

Re: [Pharo-project] Senders and implementors WAS: Pharo apparently slow on linux

by Schwab,Wilhelm K

+1 ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Sunday, July 19, 2009 2:58 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Senders and implementors WAS: Pharo apparently slow on linux On Sun, Jul 19, 2009 at 3:25 PM, Adrian Lienhard <adi(a)netstyle.ch<mailto:adi@netstyle.ch>> wrote: On Jul 19, 2009, at 20:14 , Schwab,Wilhelm K wrote: > Documentation is certainly a good thing, but I have been trying to > adapt my behavior to take advantage of these shortcuts, and I notice > two things: (1) deciding between m/n takes _some_ thought; (2) it is > common to be using the mouse to move around among browsers and a > workspace or two, at which point I have to move to the keyboard, > think up the selector, and then get the benefit. > > In an ideal world, I would like to see the menus include these > commands. But they are included in the menu -- just not at the top level (see my previous mail). If we start to add more stuff at the top ('tally it' and 'watch it' are already questionable in my opinion), then we end up again with unusable menus like those of Squeak. Yes, you are right and no one of us want that. I only think implementors and senders were used far more than the others like "tall it", "watch it", etc Adrian > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> > ] On Behalf Of Adrian Lienhard > Sent: Sunday, July 19, 2009 1:08 PM > To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> > Subject: Re: [Pharo-project] Senders and implementors WAS: Pharo > apparently slow on linux > > > On Jul 19, 2009, at 20:05 , Mariano Martinez Peck wrote: > >> On Sun, Jul 19, 2009 at 12:18 PM, Damien Cassou >> <damien.cassou(a)gmail.com<mailto:damien.cassou@gmail.com> >>> wrote: >> >>> 2009/7/18 Mariano Martinez Peck <marianopeck(a)gmail.com<mailto:marianopeck@gmail.com>>: >>>> I don't know you what I use senders and implementors everytime. Too >>>> frecuently. Frecuently enought so that to put them in the first >>>> menu >>>> and >>> not >>>> insidethe "extended search". Don't you rather them to be in the >>>> first >>> menu >>>> ?? >>> >>> Why don't you use keyboard shortcuts if you use them often? ALT+m >>> (iMplementors) ALT+n (seNders) >> >> >> I do that. But I was not thinking in me, but in newbies. > > I think it would be better to document these shortcuts (e.g., as a > FAQ) instead of cluttering the menus. > > Adrian > >> >> >>> >>> >>> -- >>> 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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 19, 2009

Re: [Pharo-project] BlockArgsNode KeyWordNode

by StÃ©phane Ducasse

yeap quite emtpy. Stef On Jul 19, 2009, at 9:14 PM, Igor Stasenko wrote: > 2009/7/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Hi >> >> I'm wondering why these classes are the only one of Compiler-Syntax >> and not Compiler-ParseNodes. >> And why nobody use them. >> > > Looks like a leftovers from something.. > No methods, no refs to them. > >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > 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 19, 2009

Re: [Pharo-project] MergeTool request

by StÃ©phane Ducasse

nicolas if you use the old diff tool you get another menu item to install a specific method > Could we have: > - an indication of method timestamps (with initials) > - a button to select/reject all changes at once (usefull if you merge > with a distant fork and want to be very selective) Now I do not understand the second item since it seems the inverse of what you put in () Stef > > Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 19, 2009

Re: [Pharo-project] Senders and implementors WAS: Pharo apparently slow on linux

by Mariano Martinez Peck

On Sun, Jul 19, 2009 at 3:25 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > On Jul 19, 2009, at 20:14 , Schwab,Wilhelm K wrote: > > > Documentation is certainly a good thing, but I have been trying to > > adapt my behavior to take advantage of these shortcuts, and I notice > > two things: (1) deciding between m/n takes _some_ thought; (2) it is > > common to be using the mouse to move around among browsers and a > > workspace or two, at which point I have to move to the keyboard, > > think up the selector, and then get the benefit. > > > > In an ideal world, I would like to see the menus include these > > commands. > > But they are included in the menu -- just not at the top level (see my > previous mail). If we start to add more stuff at the top ('tally it' > and 'watch it' are already questionable in my opinion), then we end up > again with unusable menus like those of Squeak. Yes, you are right and no one of us want that. I only think implementors and senders were used far more than the others like "tall it", "watch it", etc > > > Adrian > > > > > Bill > > > > > > > > -----Original Message----- > > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto: > pharo-project-bounces(a)lists.gforge.inria.fr > > ] On Behalf Of Adrian Lienhard > > Sent: Sunday, July 19, 2009 1:08 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] Senders and implementors WAS: Pharo > > apparently slow on linux > > > > > > On Jul 19, 2009, at 20:05 , Mariano Martinez Peck wrote: > > > >> On Sun, Jul 19, 2009 at 12:18 PM, Damien Cassou > >> <damien.cassou(a)gmail.com > >>> wrote: > >> > >>> 2009/7/18 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >>>> I don't know you what I use senders and implementors everytime. Too > >>>> frecuently. Frecuently enought so that to put them in the first > >>>> menu > >>>> and > >>> not > >>>> insidethe "extended search". Don't you rather them to be in the > >>>> first > >>> menu > >>>> ?? > >>> > >>> Why don't you use keyboard shortcuts if you use them often? ALT+m > >>> (iMplementors) ALT+n (seNders) > >> > >> > >> I do that. But I was not thinking in me, but in newbies. > > > > I think it would be better to document these shortcuts (e.g., as a > > FAQ) instead of cluttering the menus. > > > > Adrian > > > >> > >> > >>> > >>> > >>> -- > >>> 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 > >>> > >> _______________________________________________ > >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 19, 2009

[Pharo-project] Fwd: feedback on Issue 860: Accelerate MulitByteFileStream

by StÃ©phane Ducasse

Hi would be good to have feedback on http://code.google.com/p/pharo/issues/detail?id=860 Stef

July 19, 2009

[Pharo-project] MergeTool request

by Nicolas Cellier

Could we have: - an indication of method timestamps (with initials) - a button to select/reject all changes at once (usefull if you merge with a distant fork and want to be very selective) Nicolas

July 19, 2009

Re: [Pharo-project] BlockArgsNode KeyWordNode

by Igor Stasenko

2009/7/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi > > I'm wondering why these classes are the only one of Compiler-Syntax > and not Compiler-ParseNodes. > And why nobody use them. > Looks like a leftovers from something.. No methods, no refs to them. > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

July 19, 2009

[Pharo-project] BlockArgsNode KeyWordNode

by StÃ©phane Ducasse

Hi I'm wondering why these classes are the only one of Compiler-Syntax and not Compiler-ParseNodes. And why nobody use them. Stef

July 19, 2009