Same toolview active multiple times?
ghislain.mary at lunacymaze.org
Thu May 10 14:11:23 UTC 2012
Then from the UI perspective what would be the best?
I imagine these possibilities:
1. Keeping the current "Add Tool View" dialog but listing only the tool views
that are not already present in any dock area.
2. Keeping the current "Add Tool View" dialog but listing only the tool views
that are not already present in the default dock area for the tool view to be
added. A tool view could then be added in its default dock area even if it is
already present in an other dock area.
3. Using an interface similar to the "Configure Toolbars" dialog with two
lists where the tool views could be transferred from the "available toolviews"
list to the "current toolviews" list and the other way around.
For solutions 1 and 2 the user can only remove the tool view from its context
menu. For solution 3 the user can also remove the tool view from "Add Tool
View" dialog (which will then need to be renamed by the way).
The list of tool views that can be added from the dock area context menu must
also be updated to list only the tool views that are not already present in
the dock area (or in any dock area) to prevent adding the same tool view
My preference would go for solution 1. What do you think?
Maybe it would be great also to be able to drag&drop a toolview from one dock
area to an other but I don't know if that's possible to do so.
Le mercredi 9 mai 2012 23:55:21 Andreas Pakulat a écrit :
On Wed, May 9, 2012 at 11:19 PM, Ghislain MARY <gmary at lunacymaze.org> wrote:
By trying to solve the bug 165969, the question of the relevance of being able
of adding a toolview several times was raised.
What do you think? Should the user be able to add a toolview any times she
wants? Should she be limited to add each toolview only one time per area?
Should she be limited to add each toolview only one time globally?
Definetly 1 toolview per area, or maybe rather a toolview should be able to be
shown in all areas and not limited to only one.
Regarding having multiple instances of a toolview-type in one area, thats a
questionable thing. We didn't want to impose that restriction in the initial
design, thinking that it may make sense for some toolviews. But frankly I
haven't ever had the need for this in either KDevelop or other IDE's which
have a toolview concept. I think one of the ideas was that some toolviews may
be useful to have in different configurations, one could imagine two instances
of the project view with different filterings applied. I'm not convinced anymore
though that this is a very widespread usecase that warrants the effort
necessary for supporting multiple instances of a toolview.
Restricting kdevelop to 1 instance per area per toolview type would also make
it a lot easier to store toolview-configuration like the selection/expansion
state of trees or filters.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel