On 19 October 2011 23:43, Nick Treleaven <[email protected]> wrote: > On 18/10/2011 17:30, Nick Treleaven wrote: >> >> On 18/10/2011 00:36, Matthew Brush wrote: >>> >>> On 11-10-17 04:27 PM, Lex Trotman wrote: >>>> >>>> Yes, the build tab is generated at runtime because it has variable >>>> length (set by the number_xx_menu_items prefs). >>>> >>>> Possibly it could be a treeview, but that would change the whole >>>> operation of the build tabs and would need discussion with Nick who >>>> has strong ideas on the subject :) >> >> Not really, I'm just opposed to replacing groups of commands with a list >> of commands as I think this is worse usability. >> >> I think a treeview for each command group wouldn't really change things >> and might look better. Is there a way to show a label with mnemonic in a >> treeview column? Not crucial but nice to have. > > Actually one treeview would be better, but I think the error regex fields > would need to be separate from the tree. Perhaps grouped underneath it. It > could look something like: > > Current filetype: C > > Label Command Directory Reset > ----- ------- --------- ----- > \/ Filetype build commands > ... > \/ Independent build commands > ... > \/ Execute commands > ... > > Error regular expressions: > Filetype: [ ] > Independent: [ ] >
WARNING, WARNING !!!! Thats exactly what I was thinking Nick, we AGREE!!!! :D > > I've added a label for current filetype above (this could be done > separately). This is to avoid repeating the filetype name in multiple > places, and I think it's clearer. Good idea. And of course the extra non-filetype execute group we want to add just tacks on the end :) Now to get enough time. Cheers Lex _______________________________________________ Geany-devel mailing list [email protected] https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
