[Kst] Patch for proposed change to Data Manager dialog

George Staikos staikos at kde.org
Sat Jan 6 01:01:01 CET 2007


On 5-Jan-07, at 10:32 AM, Adam Treat wrote:

> Here is how I see it:
>
> The advantages of doing it through the data manager:
>
> 1.  No annoying double dialog when creating plugin based objects.
> 2.  Can list all objects in one area and categorize them by type.   
> The user
> doesn't care if an object is a plugin or if it is built-in, but he/ 
> she might
> care whether it is a fit or a filter or something else.
> 3.  The top-level menu is not so cluttered with actions (arguable I  
> guess ;)
> 4.  The datamanager list mimics designer and consolidates this  
> dialog into a
> kind of builder/editor for data objects.
>
> The advantages of creating them through top-level menu:
>
> 1.  That is how most users are doing it now...
>
> The biggest problem with the top-level menu actions is that it does  
> not scale.
> You end up with one action (New Plugin) which launches a  
> potentially very
> large dialog listing all the plugins.  It doesn't categorize them  
> or make it
> easy to find the object you are looking for and all it does is  
> launch yet
> another dialog once you've selected the one you want.

    That doesn't really matter though.  The user workflow is pretty  
much one of the most important things to preserve.  Enhancing the  
data manager is good and maybe users will eventually start using  
that, but for now we need to continue having the top-level menu.

--
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/





More information about the Kst mailing list