← Back to team overview

clicompanion-devs team mailing list archive

Re: Structuring the command library

 

On Thu, Nov 17, 2011 at 3:42 AM, Jonathan Marsden <jmarsden@xxxxxxxxxxx>wrote:

> One more thought for today:
>
> Bug #622063 asks for "more commands".  Well, OK, I could probably spend
> a few hours one weekend and come up with a few hundred more quite easily.
>
> But at some point, surely, the commands need to be categorized, or
> structured into a tree, or something, so you can find the one command
> you need.  An unsorted list of say 300 commands would be pretty
> unwieldy, wouldn't it?
>
> How can clicompanion structure its command library so that it remains
> easy to find commands, as the size of the library grows?
>
> Jonathan
>
> --
> Mailing list: https://launchpad.net/~clicompanion-devs
> Post to     : clicompanion-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~clicompanion-devs
> More help   : https://help.launchpad.net/ListHelp
>



I worked on a branch for awhile that replaced the liststore with a
treestore so we could have 'sections'. I was never able to get it to work
properly. If it could be made to work I think that would be a good choice.
To have folders with the commands inside them. I'll try and dig up the
branch and see what the blocker was on that.
Thanks,
Duane

References