[Pharo-project] OB's icon support improved
Hi there, taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this: - Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested) - Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;) - Explaining labels for all icons (keep the mouse over them) - Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension. - Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable. To load the latest version of OB, you can use this Installer script: Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'. Cheers, David
this is cool! Works well. Stef
Hi there,
taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this:
- Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested)
- Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;)
- Explaining labels for all icons (keep the mouse over them)
- Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension.
- Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves
If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable.
To load the latest version of OB, you can use this Installer script:
Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'.
Cheers, David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
This is an excellent news. Cheers, Alexandre On 29 Sep 2008, at 11:36, David Röthlisberger wrote:
Hi there,
taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this:
- Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested)
- Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;)
- Explaining labels for all icons (keep the mouse over them)
- Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension.
- Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves
If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable.
To load the latest version of OB, you can use this Installer script:
Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'.
Cheers, David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
David, Very nice indeed! One quick suggestion: classes without a comment need to have an icon, and really really ugly one, for obvious reason: to get rid of it by writing a comment ASAP :) Janko David Röthlisberger wrote:
Hi there,
taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this:
- Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested)
- Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;)
- Explaining labels for all icons (keep the mouse over them)
- Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension.
- Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves
If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable.
To load the latest version of OB, you can use this Installer script:
Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'.
Cheers, David
-- Janko Mivšek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si
I made a new version of Scriptloader that reflect the new version of OB ScriptLoader-AlexandreBergel.516 is now in the Pharo rep (and not PharoInBox). Cheers, Alexandre On 29 Sep 2008, at 11:36, David Röthlisberger wrote:
Hi there,
taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this:
- Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested)
- Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;)
- Explaining labels for all icons (keep the mouse over them)
- Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension.
- Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves
If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable.
To load the latest version of OB, you can use this Installer script:
Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'.
Cheers, David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Janko,
One quick suggestion: classes without a comment need to have an icon, and really really ugly one, for obvious reason: to get rid of it by writing a comment ASAP :)
Indeed, this is something we should add. The reason to not add it so far was that almost every class would get this icon in most packages. ;) But we will prepare an icon for it. David
David Röthlisberger wrote:
Hi there,
taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this:
- Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested)
- Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;)
- Explaining labels for all icons (keep the mouse over them)
- Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension.
- Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves
If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable.
To load the latest version of OB, you can use this Installer script:
Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'.
Cheers, David
On Mon, Sep 29, 2008 at 2:25 PM, Alexandre Bergel <alexandre@bergel.eu> wrote:
I made a new version of Scriptloader that reflect the new version of OB
Hi Alex. You should stop doing that manually. I already maintain the universe version. Please update your method to look like ScriptLoader>>installingRB. Moreover, future pharo releases will contain OB. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
Hi Alex. You should stop doing that manually. I already maintain the universe version. Please update your method to look like ScriptLoader>>installingRB. Moreover, future pharo releases will contain OB.
Excellent! In that case, how can I load OB? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Mon, Sep 29, 2008 at 3:31 PM, Alexandre Bergel <alexandre@bergel.eu> wrote:
In that case, how can I load OB?
ScriptLoader new universalInstaller universe install: 'OB-Enhancements' If it does not install the very latest version, it's because David does not think it is ready yet. You can still update using monticello if you want. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
One quick suggestion: classes without a comment need to have an icon, and really really ugly one, for obvious reason: to get rid of it by writing a comment ASAP :)
Indeed, this is something we should add. The reason to not add it so far was that almost every class would get this icon in most packages. ;) But we will prepare an icon for it.
Please don't add such an icon. This is the most horrible thing in VisualWorks, I always disable it as a first action. There will always be tons of classes in the system that have not been commented and that you don't want to comment, because this is not your library. Nothing will change that. Adding another icon there will just add a horrible noise and is totally orthogonal to the kind-icon that classes already have. Again (as I did for the method icons) I vote not to mix different concerns in a single icon. If really needed, add an exclamation mark to the question mark button for example. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch
You know I would really like to see if this is worth pressing the ? So I miss the pane showing the comment under the class def. May be a good way also would be to have the question mark with a different color when there is a comment. David we are starting to use manifesto for package so it would be also great to show them. Stef
another point why the down cyan arrow is not a down cyan arrow with a down orange arrow? (may be this is ugly but it would be more consistent). Stef
So I miss the pane showing the comment under the class def.
yes, true. I need to how to to that. What we have in the multiple selection browser is the mechanism to automatically get the class comment on the right of the class def panel in a second panel.
May be a good way also would be to have the question mark with a different color when there is a comment.
Or in red when there's no comment.
David we are starting to use manifesto for package so it would be also great to show them.
Ok. Do you have an example of a package using it? Moose? David
why the down cyan arrow is not a down cyan arrow with a down orange arrow? (may be this is ugly but it would be more consistent).
well, we have a cyan square for an abstract method without sub-implementation, so for those with sub-impl., we could have a small cyan square with an orange down arrow. But I think the current cyan down arrow looks much better. David
Why not put that information in the ? button itself? E.g., bold font if there is something there, and italic if there is nothing. - on On Sep 29, 2008, at 18:57, Stéphane Ducasse wrote:
You know I would really like to see if this is worth pressing the ?
So I miss the pane showing the comment under the class def. May be a good way also would be to have the question mark with a different color when there is a comment.
David we are starting to use manifesto for package so it would be also great to show them.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sep 30, 2008, at 10:18 AM, David Röthlisberger wrote:
So I miss the pane showing the comment under the class def.
yes, true. I need to how to to that. What we have in the multiple selection browser is the mechanism to automatically get the class comment on the right of the class def panel in a second panel.
May be a good way also would be to have the question mark with a different color when there is a comment.
Or in red when there's no comment.
David we are starting to use manifesto for package so it would be also great to show them.
Ok. Do you have an example of a package using it? Moose?
Yes we started with Moose. In FAMIX2-Importer for example/ But have a look at the comment of the class in the DrDoc package. Stef
David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sep 30, 2008, at 10:20 AM, David Röthlisberger wrote:
why the down cyan arrow is not a down cyan arrow with a down orange arrow? (may be this is ugly but it would be more consistent).
well, we have a cyan square for an abstract method without sub- implementation, so for those with sub-impl., we could have a small cyan square with an orange down arrow. But I think the current cyan down arrow looks much better.
but what does mean down arrow? I have subclass implementing it (when the arrow is orange). Am I correct? I'm confused with a down up inconsistency. Stef
David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stéphane Ducasse wrote:
On Sep 30, 2008, at 10:20 AM, David Röthlisberger wrote:
why the down cyan arrow is not a down cyan arrow with a down orange arrow? (may be this is ugly but it would be more consistent).
well, we have a cyan square for an abstract method without sub-implementation, so for those with sub-impl., we could have a small cyan square with an orange down arrow. But I think the current cyan down arrow looks much better.
but what does mean down arrow? I have subclass implementing it (when the arrow is orange). Am I correct?
yes. Any down arrow means that at least one subclass is implementing a method with the same name. Orange down arrow means just that, a cyan down arrow additionally means that the method you are looking at is abstract, but subclasses do implement the method. David
participants (7)
-
Alexandre Bergel -
Damien Cassou -
David Röthlisberger -
Janko Mivšek -
Lukas Renggli -
Oscar Nierstrasz -
Stéphane Ducasse