Community
Participate
Working Groups
While playing around with the bug #179031 to see in how weird of a state I could end up, I came to realize that having detachable view toolbars could actually be a useful thing. In my precise example, I ended up with the search view toolbar overlaid at the bottom of my editor (see screenshot attached) and I found it really useful to traverse the results: it takes much less screen real estate, I don't have to move my mouse as far as (and it could probably be made available closer), and it carries all the things that I want to do quickly. Of course there are cases where the view is still useful but not most of the time. One could argue that this behavior should be specific to the search view, however I would rather have an implicit support in the workbench for that for consistency. Then of course, there are views for which this behavior is stupid (e.g, the navigator), but I still believe that whether the toolbar is detachable should be a user preference where the default should be set to something reasonable. In general I think that the views where this would make the most sense are the "peripheral views" that have feedback in the editor or another more central view.
Created attachment 61835 [details] Screenshot of the idea.
Created attachment 61854 [details] Floating toolbars in OOo I really think this is a great idea to have similar features like many other common programs. The best way to implement it would be to drag the toolbar outside of the workbench like detached views. I've attached a screenshot from open office which shows some floating toolbars.
Hmmm, I sort of like this. We could have some sort of 'fly out' (i.e. opens on 'hover') area that causes the TB to appear above it. This would save space under most circumstances... "It's not a bug, it's a feature" -- All of us at one time or another...;-)
+1
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
