- Pharo-dev - lists.pharo.org

Re: [Pharo-project] running tests using the method menu

by Fernando olivero

great, much safer placements. But i think now i will force myself to start using cmd-T. Fernando On Apr 8, 2010, at 11:14 AM, Lukas Renggli wrote: > Name: OB-SUnitIntegration-lr.25 > Author: lr > Time: 8 April 2010, 11:12:28 am > UUID: 1cb48cf9-d265-4f04-8146-6a594a1b4ce0 > Ancestors: OB-SUnitIntegration-lr.24 > > - put menu item at the top > > On 8 April 2010 11:02, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Can we alter the placements of the items in the method menu? >> >> Yeah, this is an unfortunate placement, however it logically belongs >> to the group of actions commands. >> >> Personally I didn't notice that problem, because I always use Ctrl+T >> to run the test. >> >> In the latest OB with refactoring tools installed you can undo/redo >> most actions (method definition, class definition, method removal, >> method definition, method change, and of course all refactorings). >> Just click on 'refactor --> undo' in case you accidentally >> deleted/overwrite something. >> >>> The sad part of the story is that we changed all the menus in O2 but O2 will never make it. >> >> Shortening the menus is good, but not to the point where logical >> groups are split into unrelated and messy submenus. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > 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

April 8, 2010

Re: [Pharo-project] running tests using the method menu

by Lukas Renggli

Name: OB-SUnitIntegration-lr.25 Author: lr Time: 8 April 2010, 11:12:28 am UUID: 1cb48cf9-d265-4f04-8146-6a594a1b4ce0 Ancestors: OB-SUnitIntegration-lr.24 - put menu item at the top On 8 April 2010 11:02, Lukas Renggli <renggli(a)gmail.com> wrote: >> Can we alter the placements of the items in the method menu? > > Yeah, this is an unfortunate placement, however it logically belongs > to the group of actions commands. > > Personally I didn't notice that problem, because I always use Ctrl+T > to run the test. > > In the latest OB with refactoring tools installed you can undo/redo > most actions (method definition, class definition, method removal, > method definition, method change, and of course all refactorings). > Just click on 'refactor --> undo' in case you accidentally > deleted/overwrite something. > >> The sad part of the story is that we changed all the menus in O2 but O2 will never make it. > > Shortening the menus is good, but not to the point where logical > groups are split into unrelated and messy submenus. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

April 8, 2010

Re: [Pharo-project] running tests using the method menu

by Lukas Renggli

> Can we alter the placements of the items in the method menu? Yeah, this is an unfortunate placement, however it logically belongs to the group of actions commands. Personally I didn't notice that problem, because I always use Ctrl+T to run the test. In the latest OB with refactoring tools installed you can undo/redo most actions (method definition, class definition, method removal, method definition, method change, and of course all refactorings). Just click on 'refactor --> undo' in case you accidentally deleted/overwrite something. > The sad part of the story is that we changed all the menus in O2 but O2 will never make it. Shortening the menus is good, but not to the point where logical groups are split into unrelated and messy submenus. Lukas -- Lukas Renggli www.lukas-renggli.ch

April 8, 2010

Re: [Pharo-project] [Preview] Help System with new model

by StÃ©phane Ducasse

Torsten do you have a new version that we could integrate to 1.1? Stef On Mar 29, 2010, at 9:21 PM, Michael Roberts wrote: > Hi Torsten, i like a lot of the new features. > > regarding defining help in classes without the help system loaded - i > think it could be simpler. I am not sure how this would work as you > describe in my example where I want to shove some simple help in the > monticello package. I don't understand the asHelpTopic conversion and > which builder to use etc. > > I think it should be possible for help to appear in the global help > browser without having to define a subclass of CustomHelp. This would > make the entry barrier really low for people to be able to document > parts of the system using this help system. For example I have spent > too long on this already ;-) > > > Can you consider the idea of a PragmaHelpBuilder as an extension to > your system? > > I can define a method like this on some class: > > helpForThisPartOfTheSystem > <helpTopic: 'Title goes here'> > > ^'Contents goes here. > foo > bar > wibble' > > And then I can find all of these pragmas: > > | pragmas topics | > pragmas := ((SystemNavigation default allMethodsSelect: [:each | each > pragmas notEmpty]) > select: [:each | each compiledMethod pragmas allSatisfy: [:eachPragma | > eachPragma keyword = #helpTopic:]]) > collect: [:each | each compiledMethod pragmaAt: #helpTopic:]. > topics := pragmas collect: [:each | > HelpTopic > title: (each argumentAt: 1) > contents: (each method valueWithReceiver: nil arguments: #())] > > With a bit more annotation we could build classes just like the simple > subclass case of CustomHelp where you only have a few methods on the > class side. i.e just like your metacello example. Then there is no > dependency on CustomHelp, and help comments can go anywhere in our > various package structures for e.g pharo core, dev image. We would > just need to decide on a set of annotations. > > thanks, > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 8, 2010

Re: [Pharo-project] running tests using the method menu

by StÃ©phane Ducasse

Yes! The sad part of the story is that we changed all the menus in O2 but O2 will never make it. stef On Apr 8, 2010, at 10:05 AM, Fernando olivero wrote: > Can we alter the placements of the items in the method menu? > > Sometimes i click just to pixels above and erase a method instead of running the test! > > <methodmenus.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 8, 2010

[Pharo-project] running tests using the method menu

by Fernando olivero

Can we alter the placements of the items in the method menu? Sometimes i click just to pixels above and erase a method instead of running the test!

April 8, 2010

Re: [Pharo-project] How to manage todo?

by StÃ©phane Ducasse

On Apr 8, 2010, at 8:56 AM, laurent laffont wrote: > > On Wed, Apr 7, 2010 at 10:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > tx > I checked the inria task is too complex (the idea is to manage dependency and produce gantt about tasks). > > > Like this: http://trac.edgewall.org/milestone/0.12 ? I do not know I could not understand it I have the iumpression that we tasks with optionally an order notion but not been forced to enter start date, dependency, estimated number of hours. Stef

April 8, 2010

Re: [Pharo-project] How to manage todo?

by laurent laffont

On Wed, Apr 7, 2010 at 10:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > tx > I checked the inria task is too complex (the idea is to manage dependency > and produce gantt about tasks). > Like this: http://trac.edgewall.org/milestone/0.12 ? Laurent Laffont > > Stef > > > In Moose we use mainly: > > Type-Engineering = (Re)engineering the code base to enhance its > quality > > Type-Defect = Report of a software defect > > Type-Enhancement = Request for enhancement > > > > and from time to time: > > Type-Project = Long-term project or autonomous task > > Type-Review = Request for a code review > > Type-Other = Some other kind of issue > > > > Cheers, > > Doru > > > > On 7 Apr 2010, at 16:30, StÃ©phane Ducasse wrote: > > > >>> I propose that we use > >>>> > >>>> Type-Task or Type-ToDo for the management of some items that are not > directly bug. > >>>> Marcus? adrian? is it ok for you? > >>> > >>> As a frist step good. I personally would like to destinguish bugs from > feature requests. Bugs > >>> are bad and I want as little as possible. Feature request are good and > I want as many as possible... > >>> > >>> Another aspect is: Bugs I feel kind of responsible to fix. Feature > request I say: If this is really important, > >>> someone will do it. (someone not me). > >> > >> Ok I like this distinction. I will recategorise. > >> I added some TODO items (like going to the prefecture) > >> > >> Stef > >> > >>> > >>> Marcus > >>> > >>> > >>> -- > >>> Marcus Denker -- http://www.marcusdenker.de > >>> INRIA Lille -- Nord Europe. Team RMoD. > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > > "Sometimes the best solution is not the best solution." > > > > > > _______________________________________________ > > 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 >

April 8, 2010

Re: [Pharo-project] CollabActive book :)

by Tudor Girba

Hi, Aaron and Dale added the missing Shout plugin for Pier. Now, using == at the beginning of the line shows highlighted code. Cheers, Doru On 7 Apr 2010, at 10:36, Simon Denier wrote: > Doru, another missing thing in the current config is the == syntax > for Smalltalk highlighting > See http://book.pharo-project.org/book/announcements/client -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

April 8, 2010

Re: [Pharo-project] Show Actions of a SystemWindow: bug?

by Carla F. Griggio

Whoops! It is Morph>> showActions :P I'll submit the bug and the fix :) I don't usually use that menu either, but I was playing with Morphs and I recalled that I had seen that menu before and it could be usefull. Actually, I didn't remember how to open it, I tried several key combinations until I got it, hehehe. On Wed, Apr 7, 2010 at 10:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > add a bug entry :) > > On Apr 7, 2010, at 3:11 PM, Mariano Martinez Peck wrote: > > > > > > > 2010/4/6 Carla F. Griggio <carla.griggio(a)gmail.com> > > Hello! > > > > I was fooling around with the latest rc3 image and I tried to use the > "show actions" option in the menu of a SystemWindow and got this: > > > > MessageNotUnderstood: ToolSet class>>openMessageList:name:autoSelect: > > ToolSet class(Object)>>doesNotUnderstand: > #openMessageList:name:autoSelect: > > SystemWindow(Morph)>>showActions > > [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > > BlockClosure>>ensure: > > CursorWithMask(Cursor)>>showWhile: > > ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > > ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: > > ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: > > MouseButtonEvent>>sentTo: > > ... > > > > This is the code in SystemWindow>>showActions: > > > > > > Actually, it is Morph >> showActions ;) > > > > > > > > > > ToolSet openMessageList: list name: 'Actions of ' , self > printString autoSelect: false > > > > Shouldn't the last line be MessageSet openMessageList: list name: > 'Actions of ' , self printString autoSelect: nil ? I tried it and it seemed > to work OK, although I never tried that option before so I don't know what > was it's original behaviour. > > > > > > > > I think your change is correct and it works. > > It is funny it is almost the first time in my life I do a ctrl + click > hahaha I saw that menu one or two times in my life :) > > > > Even more, I checked and it is broken since, at least, Squeak 3.9 haha > > > > So..Carla, can you open a bug ticket and submit the fix ? > > > > http://www.pharo-project.org/community/issue-tracking > > > > Thanks and good catch! > > > > Mariano > > > > > > Cheers! > > Carla. > > > > _______________________________________________ > > 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 >

April 8, 2010