2015-04-25 11:16 GMT+02:00 Nicolai Hess <nicolaihess@web.de>:

2015-04-25 9:00 GMT+02:00 Peter Uhnák <i.uhnak@gmail.com>:

...

Hi,

is there some (API) way to control the icons for methods in Nautilus? I would like to show an icon for methods that contains "self shouldBeImplemented". Something like what is shown when there is "self halt" in the method. Is this possible without overriding something inside Nautilus?

Just implement a new subclass of AbstractMethodIconAction and implement #privateActionIcon #actionStateToCache #isActionHandled #actionOrder

(and of course, once you will have to call "AbstractNautilusUI resetIconCaches" )

...

(Possibly through Nautilus Plugin Manager, but I have no idea how that works.)

Thanks, Peter

On Sun, Apr 26, 2015 at 12:23 AM, Peter Uhnák <i.uhnak@gmail.com> wrote:

Do you have a fogbugz issue number you are working on for that?

...

This was for my personal use

This is not how Pharo improves ;)

(It makes "refactoring > realize" more relevant to me),

I am not familiar with this. Can you describe it.

but there is no Pharo issue (afaik).

I guessed this :) -- it was an obtuse hint...

It would be simple enough to add it to Pharo

cool. Would you do this?

but:

1. it needs a relevant icon (I used breakpointIcon for myself)

Scratch your own itch first. Other icons can be suggested as part of the review process once once there is a slice submitted.

2. it needs a meaningful priority (for me it is important, but some may prefer up/down icons, etc.)

Priority is mostly important if you report a bug and leave it for someone else to fix. A "resolved" priority 5 issue will likely be looked at before most "work needed" priority 3 issue. Now the personal advantage for yourself of trying to push such things into Pharo is that you do not need to migrate it to every fresh image you download. Of course not all personal features are suitable, but its often worth trying. cheers -ben

Thanks Peter. I understand your focus. Push DynaCase I know some other potential users since last week :)

What is the saying? "You either build tools or you use them." :)

All jokes aside if I am focused on something different and just want to quickly resolve a semi-problem I don't want to waste all day doing unimportant stuff (why is Spotter freezing the image every hour, why is there race condition when displaying Spec, why am three clicks away from encountering debugger, why is emphasis not working, why athens positions at half pixels, and million others...); I have short attention span so I prefer to get low priority things out of my mind asap or just ignore them. So when I am contributing to Pharo (Spec mostly) I focus only on that.

(It makes "refactoring > realize" more relevant to me),

I am not familiar with this. Can you describe it.

Nautilus -> right click on a class -> Refactoring > Class refactoring

...

Realize It adds stubs for all methods specified as abstract (subclassResponsibility) in superclass(es).

2. it needs a meaningful priority (for me it is important, but some may prefer up/down icons, etc.)

Priority is mostly important if you report a bug and leave it for someone else to fix. A "resolved" priority 5 issue will likely be looked at before most "work needed" priority 3 issue.

By priority I mean the icon priority — there can be displayed only one icon at a time so each icon has a priority aka should there be "isHalt" icon, or "is a test icon", etc.

Now the personal advantage for yourself of trying to push such things into Pharo is that you do not need to migrate it to every fresh image you download. Of course nt all personal features are suitable, but its often worth trying.

Startup script is still faster than properly going through the context and making sure it actually makes sense. I'll open an issue though.

Peter