January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] WorkingSet

by Mariano Martinez Peck

Wow!!! I don't know what you said. I have been playing 10 minutes since you sent the email and it is really EXCELLENT!!!! I love it. Please +999999999999999^^999999 to put them in PharoDev image :) A little "bug" I found is that in the text field, when you put a class, and OCompletion brings the popup, you HAVE to use TAB, not enter. I am use to use enter key. But the problem in this case is that the one who captures the even is WorkingSet, not OCompletion, so the classbrowser is shown with that class, but the OCompletion popup is still alive. Thanks a lot for this tool. Mariano On Mon, Jan 11, 2010 at 4:42 PM, Romain Robbes <romain.robbes(a)gmail.com>wrote: > Dear list, > > I've been working on a small tool to help people navigate their code in > Pharo. > WorkingSet tracks the entities you've changed recently, and lets you access > them quickly. > > Load WorkingSet with: > Gofer new > squeaksource: 'WorkingSet'; > package: 'WorkingSet'; > load. > > Once loaded, press CMD-1 to activate or dismiss it. A User interface pops > up, with the following key mappings: > -H to get this help message. > -1-9 to select a recently changed class or method (depending on which list > is highlighted). > -TAB to select methods, or the text field. > -Left/Right arrow keys to select classes, methods, or text field. > -Up/Down arrow keys to select an item in the list of classes or methods. > -ENTER in the text field to navigate to the entity you typed. > -ENTER or SPACE in a class or method list to select the selected item. > -U to browse the users of an entity (methods: senders, classes: > references). > -S to browse the siblings of an entity (methods: implementors, classes: > hierarchy). > -K to close all windows opened by WorkingSet. > -L & R to shift the WorkingSet window left or right. (in case you use > several screens). > -ESC or CMD-1 to dismiss WorkingSet. > > The text field allows you to enter classes and methods which are not > present in your working > set. You can enter multiple classes/methods at once by separating them with > spaces. > > Enjoy! > Romain > -- > Romain Robbes > http://www.inf.unisi.ch/phd/robbes > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 11, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Alexandre Bergel

It absolutely rocks!!!!! Excellent!!! Alexandre On 11 Jan 2010, at 12:42, Romain Robbes wrote: > Dear list, > > I've been working on a small tool to help people navigate their code > in Pharo. > WorkingSet tracks the entities you've changed recently, and lets you > access them quickly. > > Load WorkingSet with: > Gofer new > squeaksource: 'WorkingSet'; > package: 'WorkingSet'; > load. > > Once loaded, press CMD-1 to activate or dismiss it. A User interface > pops up, with the following key mappings: > -H to get this help message. > -1-9 to select a recently changed class or method (depending on > which list is highlighted). > -TAB to select methods, or the text field. > -Left/Right arrow keys to select classes, methods, or text field. > -Up/Down arrow keys to select an item in the list of classes or > methods. > -ENTER in the text field to navigate to the entity you typed. > -ENTER or SPACE in a class or method list to select the selected item. > -U to browse the users of an entity (methods: senders, classes: > references). > -S to browse the siblings of an entity (methods: implementors, > classes: hierarchy). > -K to close all windows opened by WorkingSet. > -L & R to shift the WorkingSet window left or right. (in case you > use several screens). > -ESC or CMD-1 to dismiss WorkingSet. > > The text field allows you to enter classes and methods which are not > present in your working > set. You can enter multiple classes/methods at once by separating > them with spaces. > > Enjoy! > Romain > -- > Romain Robbes > http://www.inf.unisi.ch/phd/robbes > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 11, 2010

Re: [Pharo-project] definition or getSource for Class and CompiledMethod

by Gary Chambers

Saw that too. One or the other! Defniniton perhaps (also on PackageInfo would do the lot). Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, January 11, 2010 2:57 PM Subject: [Pharo-project] definition or getSource for Class and CompiledMethod > Hi > > I was looking at the video of laurent and what stroke me is that > getting the source of class or a compiled method is not polymorphic. > It would be good to support that. > aClass getSource? > aCompiledMethod definition? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 11, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Marcus Denker

On Jan 11, 2010, at 4:37 PM, Mariano Martinez Peck wrote: > > > Also, the changes files, shouldn't be compressed for each RC and for the > final release? > > > In addition to do a Smalltalk condenseChanges is it necessary to do also a Smalltalk condenseSources ? I ask because I have really no idea. > No, we did that when going RC1... there is already a PharoV10.sources. Marcus

Jan. 11, 2010

[Pharo-project] [ANN] WorkingSet

by Romain Robbes

Dear list, I've been working on a small tool to help people navigate their code in Pharo. WorkingSet tracks the entities you've changed recently, and lets you access them quickly. Load WorkingSet with: Gofer new squeaksource: 'WorkingSet'; package: 'WorkingSet'; load. Once loaded, press CMD-1 to activate or dismiss it. A User interface pops up, with the following key mappings: -H to get this help message. -1-9 to select a recently changed class or method (depending on which list is highlighted). -TAB to select methods, or the text field. -Left/Right arrow keys to select classes, methods, or text field. -Up/Down arrow keys to select an item in the list of classes or methods. -ENTER in the text field to navigate to the entity you typed. -ENTER or SPACE in a class or method list to select the selected item. -U to browse the users of an entity (methods: senders, classes: references). -S to browse the siblings of an entity (methods: implementors, classes: hierarchy). -K to close all windows opened by WorkingSet. -L & R to shift the WorkingSet window left or right. (in case you use several screens). -ESC or CMD-1 to dismiss WorkingSet. The text field allows you to enter classes and methods which are not present in your working set. You can enter multiple classes/methods at once by separating them with spaces. Enjoy! Romain -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

Jan. 11, 2010

Re: [Pharo-project] definition or getSource for Class and CompiledMethod

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=1775 >> Hi >> >> I was looking at the video of laurent and what stroke me is that >> getting the source of class or a compiled method is not polymorphic. >> It would be good to support that. >> aClass getSource? >> aCompiledMethod definition? >> > > Indeed. > Btw it would be cool to have a class definition also be stamped as > well as any methods do. > Because at the end, they're all about same thing: making a changes > into the system. > And as any well-logged change, it apparently, should carry the source > text and having an author and date stamp. > I guess, that class could store the sourcePointer to its own change > recond in class organizer, > in same way as it currently storing a comment there. > Actually, i think we could use the comment's source pointer to also > store a class definition in a single chunk: > > Object subclass: #Blabal > variablabla: > ... > poolVars: '' > <empty line> > "Here starts the class comment > ... > ... > ... > ... > .. > " << end of comment > >> 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

Jan. 11, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

Also, the changes files, shouldn't be compressed for each RC and for the > final release? > > In addition to do a Smalltalk condenseChanges is it necessary to do also a Smalltalk condenseSources ? I ask because I have really no idea. Thanks Mariano > Also, the packages.txt file talks about PharoCore1.0 (#10505). Has > someone thought about the name shown in System->About: > > PharoCore1.0rc1 > Latest update: #10505 > > Because this is not a PharoCore image. Shouldn't this read something > like > > Pharo 1.0 Dev image. > Based on PharoCore1.0rc1 > Latest update: #10505 > > What about the disabling of software updates in the Pharo dev/web > images? Will this be implemented or a careful update stream will be made > in order to not break a dev image with overrides (real difficult I > think). > > Maybe all this setup can be put in a post-script in the > ConfigurationOfPharo class. > > That's all for now. I'm going to use this image to work the following > days. > > Cheers and keep the good work. > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 11, 2010

Re: [Pharo-project] definition or getSource for Class and CompiledMethod

by Igor Stasenko

2010/1/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi > > I was looking at the video of laurent and what stroke me is that > getting the source of class or a compiled method is not polymorphic. > It would be good to support that. > Â Â Â Â aClass getSource? > Â Â Â Â aCompiledMethod definition? > Indeed. Btw it would be cool to have a class definition also be stamped as well as any methods do. Because at the end, they're all about same thing: making a changes into the system. And as any well-logged change, it apparently, should carry the source text and having an author and date stamp. I guess, that class could store the sourcePointer to its own change recond in class organizer, in same way as it currently storing a comment there. Actually, i think we could use the comment's source pointer to also store a class definition in a single chunk: Object subclass: #Blabal variablabla: ... poolVars: '' <empty line> "Here starts the class comment ... ... ... ... .. " << end of comment > 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.

Jan. 11, 2010

Re: [Pharo-project] Package names

by StÃ©phane Ducasse

Yes Yes yes >> And that leads to very strange effects > > Yes, especially if you have only "MyPackage". > > I typically have "MyPackage-Core" and other "MyPackage-..." > packages to avoid this. > > Stef wrote >> Compiler-Core >> Compiler-SystemSettings > > So +1 > > Maybe we can also switch to just "Settings" instead of "SystemSettings": > > Compiler-Core > Compiler-Settings > > Any voting machinery around? ;) > > Bye > T. > > -- > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - > sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 11, 2010

Re: [Pharo-project] Package names

by StÃ©phane Ducasse

yeap On Jan 11, 2010, at 3:47 PM, Torsten Bergmann wrote: >> We adopted the same naming rule as for tests. >> We have NetworkSystemSettings as we have NetworkTests > > If you want to write a script that throws things out > it would be easier to have "-" as a seperator: > > Without "-" you would have two options: > > "Network" "SystemSettings" > "NetworkSystem" "Settings" > > So "Network-SystemSettings" is more explicit compared > to a "NetworkSystem-Settings". > > Bye > T. > > -- > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - > sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 11, 2010