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

Re: [Pharo-project] Keyboard Shortcuts in Pharo?

by Adrian Lienhard

I agree, the current key bindings could be improved... We would need somebody that thinks this through and makes a proposal, find a consensus, and implement it. Cheers, Adrian On Dec 11, 2009, at 09:05 , Bart Gauquie wrote: >> The problem is that Pharo already binds all possible keyboard >> shortcuts to something, which leaves no space for other tools like >> the >> refactoring engine. >> > > Is it not possible to throw away some of the shortcuts defined? I'd > rather > have a limited set of shortcuts which are used often, than defining > a lot > which are almost never used. I noticed for instance in the list that > there > is a shortcut Ctrl+T which inserts ifTrue:[] ; to my humble opinion, > that is > way to specific; and I'm not sure anybody is using this one. I'd > rather use > Ctrl-T then to open a new Type (class) or something. > > Another one is Alt - t pressed no the world view to 'find a > transcript'. Is > it not better then to find a way to quickly navigate between windows > in > general, so for instance, hit a shortcut anywhere, you get a list of > all > windows, and by just typing t for Transcript, and hit Enter, you are > already > in the transcript window. > > > Kind Regards, > > Bart > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 11, 2009

[Pharo-project] [update 1.1] #11087

by Marcus Denker

11087 ----- Issue 1572: fix all 80 senders of ifNotNilDo: to use ifNotNil: Issue 1569: Fixed Typo In Settings Issue 1075: Clean officialClass and isSystemDefined

Dec. 11, 2009

Re: [Pharo-project] Keyboard Shortcuts in Pharo?

by Bart Gauquie

> The problem is that Pharo already binds all possible keyboard > shortcuts to something, which leaves no space for other tools like the > refactoring engine. > Is it not possible to throw away some of the shortcuts defined? I'd rather have a limited set of shortcuts which are used often, than defining a lot which are almost never used. I noticed for instance in the list that there is a shortcut Ctrl+T which inserts ifTrue:[] ; to my humble opinion, that is way to specific; and I'm not sure anybody is using this one. I'd rather use Ctrl-T then to open a new Type (class) or something. Another one is Alt - t pressed no the world view to 'find a transcript'. Is it not better then to find a way to quickly navigate between windows in general, so for instance, hit a shortcut anywhere, you get a list of all windows, and by just typing t for Transcript, and hit Enter, you are already in the transcript window. Kind Regards, Bart

Dec. 11, 2009

Re: [Pharo-project] Keyboard Shortcuts in Pharo?

by Lukas Renggli

> [snip] Yeah, I agree on all ;-) > will with every next hit on left arrow select a larger block of code. So if > my cursor is on a message send, it will first select the message send, next > the receiver and the message send, next: if this was a nested, select the > part out of that, and so forth. This is very handy if you for instance want > to do a extract method refactoring on some part of the code. Just quickly > select it using this Alt-Shift selection and extract it. That's a cool idea. I will add it to the refactoring tools. > - Which brings me to the refactoring shortcuts, which I'm missing the most. > * The most important one is rename. In Eclipse if I select a field, a > temporary var,Â a message, a class, anything that can be renamed; I can > always hit Alt-Shift-R to rename it. I don't have to go into a menu, > refactor class, or refactor method, or refactor source with the mouse to > select rename. Just click on it, hit the shortcut, type the new name and hit > Enter. The problem is that Pharo already binds all possible keyboard shortcuts to something, which leaves no space for other tools like the refactoring engine. > How are experienced Smalltalkers feeling about this? Safara was an attempt to implement a replacement for the current text editor, where nothing was hardcoded but everything could be configured by the tool (highlighting, completing, shortcuts, ...). Unfortunately this project never made it into a useable state. Writing a text editor is difficult. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 11, 2009

[Pharo-project] Strange behaviour of Class Browser in 1.0/1.1

by Guido Stepken

Hi folks! When i open Classbrowser (Windows XP 1.0+1.1 recent Pharo, all updates installed), <crtl>-rightclick into the categories field, a "OBPluggable List" pops up. When i select "duplicate", i can move the text window out of the browsers context ... difficult to delete that stuff :) Wrong behaviour in class definitions ... what about design patterns? tnx, keep up the good work, regards, Guido Stepken -- View this message in context: http://n2.nabble.com/Strange-behaviour-of-Class-Browser-in-1-0-1-1-tp414981… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 11, 2009

[Pharo-project] Keyboard Shortcuts in Pharo?

by Bart Gauquie

Dear all, On my job I'm using Java; and Eclipse as an IDE. I'm discovering Pharo since a year now. I find it in almost every way superior. But not on the following way. I use keyboard shortcuts heavily in Eclipse. I use them to quickly select parts of code, extract methods, rename methods, fields, classes, switch browsing windows, delete a line of code, copy and move lines of code. I tend to miss these shortcuts in Pharo. There are actually a lot of shortcuts (http://news.squeak.org/2007/01/26/looking-for-a-shortcut/ - Andreas comment). But I still find that I have to leave the keyboard way to often and use the mouse to navigate to another window / or part of the browser I'm working in. Let me explain that a bit further. I will try to give some examples of behaviour I'm missing in Pharo. - If I'm editing a class and working in the source view. I'm done, I want to run the tests again I just ran. I have to take the mouse, navigate to the class and hit Alt-t. Or use the test runner. In Eclipse there is a global shortcut Alt-F11 which just runs the test (or even better: the suite of tests) which ran previously. It moreover runs it in the background and if everything is still ok, does not bother you again. It only pops up if something broke. This behaviour is very handy if you're refactoring. You can then with every small change run all relevant tests in matter seconds and continue. - If I'm editing in the source pane. I'm done editing, and I want to navigate for instance to another method. I have to take the mouse to navigate to the methods, scroll and click on the new method. Again had to take the mouse. In Eclipse, there is a Ctrl-O shortcut which brings up a list of all methods in this class. At the top there is an input field in which I can start typing; while typing the list is restricted. I can then using the arrow keys navigate to the method and hit Enter, and I'm in the method. - For switching between browser windows Eclipse also does have a handy mechanism. Eclipse keeps in memory a list of files you're editing ordered by latests usage. I can then quickly navigate through the list by hitting Ctrl-F6. Just hitting Ctrl-F6 navigates to the previous window visited. Hitting it again gets back. If you however hit Ctrl - F6, keep the Ctrl pressed in, and hit F6 again, you navigate the the second last window edited. I use this behaviour constantly to navigate back and forth between the test you're writing and the implementation. - Eclipse also has very keyboard shortcut integration to select/delete parts of the code. Ctrl D deletes the current line. Alt arrow up / down moves the current line (or selection) up or down (while keeping the clipboard selection). Alt-Shift-arrow up/down copies the current line (or selection) up or down (while keeping the clipboard selection). Alt Shift Left arrow / right arrow does a nifty code selection: if the code compiles properly, it will with every next hit on left arrow select a larger block of code. So if my cursor is on a message send, it will first select the message send, next the receiver and the message send, next: if this was a nested, select the part out of that, and so forth. This is very handy if you for instance want to do a extract method refactoring on some part of the code. Just quickly select it using this Alt-Shift selection and extract it. - Which brings me to the refactoring shortcuts, which I'm missing the most. * The most important one is rename. In Eclipse if I select a field, a temporary var, a message, a class, anything that can be renamed; I can always hit Alt-Shift-R to rename it. I don't have to go into a menu, refactor class, or refactor method, or refactor source with the mouse to select rename. Just click on it, hit the shortcut, type the new name and hit Enter. * The next one is Extract Method. After quickly selecting I just hit Alt-Shift-M, give a name (Eclipse guesses a name) and I extract. * Another very useful one is Extract Local Variable using Alt Shift L. I'm very well aware of the fact that in Smalltalk you typically only need half of the lines of code to achieve the same, but still I'm missing this kind of behaviour to quickly navigate, adapt code, run tests, ... All the tools are there in Pharo, but I just feel that they need a little better keyboard integration. How are experienced Smalltalkers feeling about this? Are there any solutions available already that I haven't found ? If not, I'm more than happy to implement some of these, but my knowledge of Morphic is still rather limited. Can anyone provide me with some pointers how to achieve that? Kind Regards, Bart -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein Gravitation is not responsible for people falling in love. - Albert Einstein

Dec. 11, 2009

Re: [Pharo-project] Inspector broken ...

by Frederic Pluquet

You lose time only if you expand the child "Instances" If it doesn't make sense, why do you expand it ? I think also there is no sense to inspect "Instances" of Integer class. But it is useful for some other classes I think and I want to be homogeneous throughout all classes. Finally, it is relatively rapid: on my macbook, inspecting the all 16800 instances of LargeInteger takes only 1 second. FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet On Fri, Dec 11, 2009 at 3:42 AM, Guido Stepken <gstepken(a)googlemail.com>wrote: > > Ahhh! Works fine! Happy again! > > That Menu "All Instances" when inspecting a integer value in 'Shout > Workspace' doesn't really make sense and causes Pharao to hang a few > minutes. That really should be improved :) > > tnx, keep up the good work! > > regards, Guido Stepken > > > Frederic Pluquet-3 wrote: > > > > You can retreive the childs 'Class', 'Methods' and 'Possible types': go > to > > the preferences browser, go to the category 'Inspector' and enable what > > you > > need. > > > > FrÃ©d > > ---- > > FrÃ©dÃ©ric Pluquet > > UniversitÃ© Libre de Bruxelles (ULB) > > Assistant > > http://www.ulb.ac.be/di/fpluquet > > > > > > On Thu, Dec 10, 2009 at 5:59 PM, Damien Cassou > > <damien.cassou(a)gmail.com>wrote: > > > >> On Thu, Dec 10, 2009 at 4:47 PM, Guido Stepken <gstepken(a)googlemail.com > > > >> wrote: > >> > When i open up "Shout Browser", type in "2" and inspect that number > >> with > >> > Inspector "alt-i" ... it won't show the features of that object any > >> > longer in 1.1 alpha and - thats new - also in 1.0! (newest version, > all > >> > updated installed) ... > >> > >> what do you mean by "features"? The methods have been removed from the > >> inspector view to avoid clutering it. > >> > >> -- > >> 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 > > > > -- > View this message in context: > http://n2.nabble.com/Inspector-broken-tp4146029p4149169.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 11, 2009

Re: [Pharo-project] [Fwd: Issue 1571: automaticPlatformSettings preference]

by Alain Plantec

Henrik Sperre Johansen a Ã©crit : > Is there any time you do *not* want things set automatically for you > based on platform if it's needed? > I vote remove it. > > Cheers, > Henry > > +1 Alain

Dec. 11, 2009

Re: [Pharo-project] Inspector broken ...

by Guido Stepken

Ahhh! Works fine! Happy again! That Menu "All Instances" when inspecting a integer value in 'Shout Workspace' doesn't really make sense and causes Pharao to hang a few minutes. That really should be improved :) tnx, keep up the good work! regards, Guido Stepken Frederic Pluquet-3 wrote: > > You can retreive the childs 'Class', 'Methods' and 'Possible types': go to > the preferences browser, go to the category 'Inspector' and enable what > you > need. > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > On Thu, Dec 10, 2009 at 5:59 PM, Damien Cassou > <damien.cassou(a)gmail.com>wrote: > >> On Thu, Dec 10, 2009 at 4:47 PM, Guido Stepken <gstepken(a)googlemail.com> >> wrote: >> > When i open up "Shout Browser", type in "2" and inspect that number >> with >> > Inspector "alt-i" ... it won't show the features of that object any >> > longer in 1.1 alpha and - thats new - also in 1.0! (newest version, all >> > updated installed) ... >> >> what do you mean by "features"? The methods have been removed from the >> inspector view to avoid clutering it. >> >> -- >> 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 > -- View this message in context: http://n2.nabble.com/Inspector-broken-tp4146029p4149169.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 11, 2009

Re: [Pharo-project] Gofer git

by Adrian Kuhn

StÃ©phane Ducasse <stephane.ducasse@...> writes: > I do not know if you noticed that with the latest version > of Gofer you can get a full git behavior > > Tx lukas > Lukas, this is just plain awesome! --AA

Dec. 10, 2009