On Wed, Aug 19, 2015 at 11:12 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: - yes, we can add other functionality, as Franck posted, thatâs why we ask
for those functionality. Now if nobody answers, do not expect we can know what you want :)
I answered :) http://forum.world.st/Buttons-in-Nautilus-td4839034.html Although I wonder whether the question should have been asked in Pharo-Users, because not everybody is reading dev and opinion of users is (more) relevant. Nos:
- no, we are not going to put back buttons in the middle of the browser: what is a toolbar, should be where toolsbars go. I know many if you are used to the older way, but that older way was bad: the original idea was to put functionality close to the coding area⦠no reason to do that this days.
Could you elaborate on this please? Because I don't understand why having it close to the coding area is no longer meaningful. Some others:
- the fact that you never used âScopedâ is actually the reason why we put it in such a relevant place: is one of the most powerful functionalities of Nautilus and we want you to have access to it in a direct and visible place. So you can start to use it. Using âI never used itâ as an argument does not work because in exchange I can say âthis is the function I use the most of nautilusâ. Give it a try, is particularly useful for: a) applying refactors, b) search senders/implementors inside my project and not in all image.
This is for Kilon I assume.
- actually, I would like to remove also the buttons that acts on classes (most of them needs to be tabs in the right places). In my ideal browser, functionality is distributed like this:
⦠but arriving to it is not so easy.
This does look better indeed. Actually it seems similar to VisualWorks, but with tabs (which look/behave much better) instead of buttons. Peter
