- Pharo-dev - lists.pharo.org

[Pharo-project] 10164 Image freezing

by StÃ©phane Ducasse

Hi all I loaded OB shout ecompletion and we were apply coding with damien. And the image froze (deeply) when we redefined a class. So the thread changes may be a problem. Stef

Nov. 21, 2008

[Pharo-project] Issue 310/311

by Pavel Krivanek

Hi, I created a patch for issue 310/311 that categorizes all Pharo tests in own packages. So all tests in Pharo are then unloadable. http://code.google.com/p/pharo/issues/detail?id=310 -- Pavel

Nov. 21, 2008

Re: [Pharo-project] About browsers

by Simon Denier

On 21 nov. 08, at 13:32, Simon Denier wrote: > > On 21 nov. 08, at 11:48, CÃ©drick BÃ©ler wrote: >> >> yes we need to list them... and make sure it works on all keyboard >> layout (I'm thinking espacially to shortcuts for brackets, quotes, >> etc... that only work properly on qwerty's) > > > Is there a Pier or wiki already set and publicly available, so we > can do this collaboratively? > Or we can open an issue on the Pharo site. > > Another idea would be to have a meta shortcut, ie a shortcut to list > all shortcuts available in the current context (I shamelessly take > it from eclipse) > > Any hints about how key shortcuts work in Squeak? Because it looks > like each pane has its own list, but do they rely on the same > mechanism? > Stef told me about ParagraphEditor. As a side note, the new Mac menu with its quit command masks the shortcut for the querySymbol (or hippie completion, or whatever you like to call it), because they both map to cmd-q. So we need to find a replacement :) -- Simon

Nov. 21, 2008

Re: [Pharo-project] About browsers

by Simon Denier

On 21 nov. 08, at 11:48, CÃ©drick BÃ©ler wrote: >> I have another question >> >> why are we forced to click on a method category to define one? >> We could click on the class and paste a method body >> then select a category... > > Yes I totally agree... > I'd also like a quick way to create a class (at least go to the class > definition view) when a package is selected... > > Some more complex features I'd like are: > -being able to move class by mouse, drop the on its (new) > superclass... > -select two classes and create a common superclass... or delete a Interesting. My current work could more or less leads to thaht, although this is not the current objective. > superclass and adapt subclasses... > >> >> I would really like to see an IDE where we limit the number of modes. >> For example it would be great to maximize the number of shortcut >> that are >> transparent = >> that are not linked to a pane. >> right now apple-F is linked to look for a class in the class >> category. >> but this would be great to have it working anywhere. >> apple-w to close a window only work on the pasteUpMorph >> >> I'm sure that there are a lot more of such case. >> > > yes we need to list them... and make sure it works on all keyboard > layout (I'm thinking espacially to shortcuts for brackets, quotes, > etc... that only work properly on qwerty's) Is there a Pier or wiki already set and publicly available, so we can do this collaboratively? Or we can open an issue on the Pharo site. Another idea would be to have a meta shortcut, ie a shortcut to list all shortcuts available in the current context (I shamelessly take it from eclipse) Any hints about how key shortcuts work in Squeak? Because it looks like each pane has its own list, but do they rely on the same mechanism? Stef told me about ParagraphEditor. -- Simon

Nov. 21, 2008

[Pharo-project] [update] #10163

by Marcus Denker

-> added loading script for polymorph UI (Torsten Bergmann) -> clean up cass "TheWorldMenu" a little (me) -> Issue 339: Process stuck in 10156+OB?, 100% cpu load after ScriptLoader loadOB on macintosh only -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 21, 2008

Re: [Pharo-project] SUnit: history support and OB icons

by Simon Denier

On 21 nov. 08, at 10:17, StÃ©phane Ducasse wrote: > I have the not run green/red icons > but not the green ones when the tests are run. > Even if once it worked because I saw it. > Stef What Stef is talking about is the ability to run tests in the browser with the cmd-t shortcut. Indeed, test status is not updated in this case. Test status are only updated when ran through the *TestRunner*. But, it makes perfect sense that running tests through the browser should update the status. I can work out something. Any hint about how it works in OB? PS: I have been bothered by the password box being asked twice too. Worse, when I load both Polymorph and my slice, if I try to move the cursor to type in my name, it produces a new box, see screenshot. Be aware. > > > On Nov 20, 2008, at 11:00 PM, David RÃ¶thlisberger wrote: > >> >>> Now I do not understand since when I run the tests the icons do >>> not change. >> Strange. So you always get the not run icon (circle with green and >> red)? >> For me this is not the case, the icons do change. Can you check >> whether it saved a history in the class variable of TestCase? >> >> david >>> Stef >>> >>> On Nov 20, 2008, at 8:17 PM, David RÃ¶thlisberger wrote: >>> >>>> >>>>> I loaded the fix of John for the menu >>>>> and the changes for SUnit icons and my image freshes when I open >>>>> the Package browser and run the tests >>>>> in 10162 >>>> >>>> which tests? All tests? >>>> >>>> David >>>> >>>> _______________________________________________ >>>> 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 > -- Simon

Nov. 21, 2008

[Pharo-project] [10164] SUnit icons support + MorphE->I etoy cleanup

by StÃ©phane Ducasse

[10164] SUnit icons support + MorphE->I etoy cleanup

Nov. 21, 2008

Re: [Pharo-project] List of Type entry

by StÃ©phane Ducasse

Yes please suggest what we can do Tasks -Work item that doesn't change the code or docs Todo was related to code and I would remove other because looks like a trashcan Stef On Nov 21, 2008, at 11:14 AM, Norbert Hartl wrote: > On Thu, 2008-11-20 at 21:34 +0100, StÃ©phane Ducasse wrote: >> Hi guys >> >> I added two type entries >> >> Type-Defect = Report of a software defect >> Type-Enhancement = Request for enhancement >> Type-Task = Work item that doesn't change the code or docs >> Type-Patch = Source code patch for review >> Type-Mantis = Ticket on bugs.squeak.org to integrate >> Type-Squeak = Squeak version to integrate >> Type-Other = Some other kind of issue >> Type-ToDo = To list some todo for the coming versions >> Type-NextMilestone = To remember some actions for the next >> milestones >> >> I would like that we used them to sort well the items > > What's the difference between task and todo? I find todo > always too generic. "Others" is the same for me. That places > are supposed to collect cruft :) I'm just arguing because > I'm confident that less categories is better most of the > times. > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 21, 2008

Re: [Pharo-project] tx...

by StÃ©phane Ducasse

I would love :) >> I just wanted to tell you that I really like what we are doing. I >> was so sad >> in the past. I find really important >> that our (marcus and me) little flame inside did not die after 3.9. >> >> I would really pharo to be able to move forward even Smalltalk >> (first class >> slots for example)! >> I still have the idea that the system should be beautiful and that >> one >> person can understand it. >> > > Don't forget to remove SystemDictionary along the way, while carving > out Etoys ;) > >> 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

Nov. 21, 2008

Re: [Pharo-project] About browsers

by CÃ©drick BÃ©ler

> I have another question > > why are we forced to click on a method category to define one? > We could click on the class and paste a method body > then select a category... Yes I totally agree... I'd also like a quick way to create a class (at least go to the class definition view) when a package is selected... Some more complex features I'd like are: -being able to move class by mouse, drop the on its (new) superclass... -select two classes and create a common superclass... or delete a superclass and adapt subclasses... Concerning extensions that go beyond smalltalk, I think I'd like: -method categories as first class objects with several standard one well defined (with specific responsabilities and a documentation) + multi categorisation (tagging). I find this could be very useful. -documentation everywhere, not only classes (packages, methods categories...) Also something that I find will help me go quicker is being able to give a class some context to test it... A bit like in SUnit but without the indirection of having to lunch a test or debug the full app. I often find myself needing to inspect some code inside the class definition... but self is then the class itself. If we could affect some context to test instances (and trigger that form the browser - it could be a pane with several instance definitions)... Not sure it would "help" everybody though... > This is another illustration that the UI of Smalltalk browser is full of > modes. Maybe we could enforce two different modes - browsing code vs. writing code > > I would really like to see an IDE where we limit the number of modes. > For example it would be great to maximize the number of shortcut that are > transparent = > that are not linked to a pane. > right now apple-F is linked to look for a class in the class > category. > but this would be great to have it working anywhere. > apple-w to close a window only work on the pasteUpMorph > > I'm sure that there are a lot more of such case. > yes we need to list them... and make sure it works on all keyboard layout (I'm thinking espacially to shortcuts for brackets, quotes, etc... that only work properly on qwerty's) -- CÃ©drick

Nov. 21, 2008