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... yep, that would be something...

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.

I found a way to make apple-F search for classes in text panels too. Adding it to the other columns besides class cat was easy too.

I went over the shortcut list and lot of them are not working and it would be good to check and rethink them. yes, we need to do this. Would be good if we could agree on a list of shortcuts we want to have everywhere in our tools. Because for apple-F I had to overwrite the behavior this shortcut normally has in a text editor, namely searching for a pattern in this text. So some people used to this behavior might be confused now and start to complain... ;) PS: David the inheritance pane is now working extremely well. It is really cool to be able to double click on it to see the new inheritance tree and the switch between the smart group selection and the package view is really great. Thanks, I'm happy to hear that. :))

David

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

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