> 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
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to