Re: [Denemo-devel] Midi device manager tree vs/ list

[alex stone]

Jeremiah, from a user perspective, it would more suitable to have
ports as a "sub-tree" of a device.

Device_jack_1
+ port1
+ port2

Device_jack_2
+ port1
+ port2

alternative with port names:

Device_jack_1
+ 1st_violins
+ 2nd_violins

Device_jack_2
+ flute_1
+ flute_2


When the user removes port "1st_violins", the rest of the ports should
keep their port names, as jack can read these (as an alias),
regardless of their position in the sub-tree.
so the 2nd violins port in this case remains as the 2nd violins port,
as a subtree of Device_jack_1.


Users should only be able to add ports to devices, and not be able to
add ports to ports. With the above suggestion, it's my view you would
avoid this happening, and negate the need for a popup.


Alex.





On Sun, Nov 22, 2009 at 7:38 PM, Jeremiah Benham
<address@hidden> wrote:
> I have been studying gtklist and treeviews. I was wondering which to use for
> the midi device manager. I currently put a list template up. Recently I
> learned how to vreate gtktrees. A list view would have one colum contianing
> device clients and the other contains ports. In tree view it would look
> similar to qjackctl's tree.
> +Jack:0
> -Jack:1
>  --Denemo:0
>
> The problem being with the tree view is that users might select a port and
> select add device. If this happens should a pop up complain that "a port can
> not be added to a port" please select a device to add a port too. There may
> be some way to retrive the parent name but I am not sure now.  I don't want
> to spend much more time on this.
>
> My other question is would a user expect to select a port name and then be
> able to delete that one? If so and the port was in the beginning of the
> list. then I would have to keep the string of names remaining but delete the
> last Jack port then rename all Jack ports. Would this cause any problems? I
> guess it wouldn't if staffs midi is not trying to write to ports via number
> but by name somehow.
>
> Jeremiah
>
>
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel
>



-- 
www.openoctave.org

address@hidden
address@hidden