On 2 April 2011 03:10, ntrel@users.sourceforge.net wrote:
Revision: 5673 http://geany.svn.sourceforge.net/geany/?rev=5673&view=rev Author: ntrel Date: 2011-04-01 16:10:51 +0000 (Fri, 01 Apr 2011)
Log Message:
add item: filetype-independent run command & keybinding.
Hi Nick,
Just to maybe save you some work.
Remember that a run command in the users geany.conf or the project (not project filetype) is filetype independent, just that there is no GUI, you have to hand edit the conf files. It would of course make the GUI more complex (and maybe less usable?) to be able to do this. I would love to have the time to re-address that !@#$%^& GUI.
The standard execute has a keybinding. IIRC keybindings for variable length things like the build menu was left as an open question since I don't think we knew how it should be handled.
Cheers Lex
On Sat, 2 Apr 2011 10:35:14 +1100 Lex Trotman elextr@gmail.com wrote:
add item: filetype-independent run command & keybinding.
Hi Nick,
Just to maybe save you some work.
Remember that a run command in the users geany.conf or the project (not project filetype) is filetype independent, just that there is no GUI, you have to hand edit the conf files. It would of course make
I remember you mentioning that. But I think it should be a separate command from the filetype run command - i.e. a second menu item and keybinding.
the GUI more complex (and maybe less usable?) to be able to do this. I would love to have the time to re-address that !@#$%^& GUI.
I think if we implement the TODO item we should divide the dialog into 2 notebook tabs:
Filetype commands Independent commands
Another option would be to divide into:
Build commands Run commands
But I prefer the filetype split.
Regards, Nick
On 4 April 2011 21:45, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Sat, 2 Apr 2011 10:35:14 +1100 Lex Trotman elextr@gmail.com wrote:
add item: filetype-independent run command & keybinding.
Hi Nick,
Just to maybe save you some work.
Remember that a run command in the users geany.conf or the project (not project filetype) is filetype independent, just that there is no GUI, you have to hand edit the conf files. It would of course make
I remember you mentioning that. But I think it should be a separate command from the filetype run command - i.e. a second menu item and keybinding.
Ok, don't forget that you already have two execute commands (to handle Latex) and can add more by the hidden preference, and any command can be filetype or filetype independent, whatever you use it as :) Or you can hard code by setting the minimum number of execute commands to 3 in the initialiser for build_groups_count.
I think really we need to be able to set keybindings for all the commands rather than hard wiring extra fixed ones, but IIRC the problem was that none of us could ever think of a quick and easy way of making the keybinding dialog handle variable numbers of commands.
But still, adding run2 and run3 is a short way for now, but that means changing the GeanyBuildType enum which is used to activate the correct menu item. But that enum is used in lots of places. If you do change it, you should check that nothing depends on the order of those (besides the obvious one commented just before the enum :).
the GUI more complex (and maybe less usable?) to be able to do this. I would love to have the time to re-address that !@#$%^& GUI.
I think if we implement the TODO item we should divide the dialog into 2 notebook tabs:
Filetype commands Independent commands
Another option would be to divide into:
Build commands Run commands
But I prefer the filetype split.
Yep, definitely agree with that.
Cheers Lex
On Mon, 4 Apr 2011 23:27:31 +1000 Lex Trotman elextr@gmail.com wrote:
add item: filetype-independent run command & keybinding.
Hi Nick,
Just to maybe save you some work.
Remember that a run command in the users geany.conf or the project (not project filetype) is filetype independent, just that there is no GUI, you have to hand edit the conf files. It would of course make
I remember you mentioning that. But I think it should be a separate command from the filetype run command - i.e. a second menu item and keybinding.
Ok, don't forget that you already have two execute commands (to handle Latex) and can add more by the hidden preference, and any command can be filetype or filetype independent, whatever you use it as :) Or you can hard code by setting the minimum number of execute commands to 3 in the initialiser for build_groups_count.
For build we have a separate group for filetype and independent commands. I think the same would be good for run commands for symmetry, and this makes sense if we split the dialog as I mentioned below.
I think really we need to be able to set keybindings for all the commands rather than hard wiring extra fixed ones, but IIRC the problem was that none of us could ever think of a quick and easy way of making the keybinding dialog handle variable numbers of commands.
This isn't about hard-wiring. The idea was to have a separate independent run command. It would actually be a separate command group.
the GUI more complex (and maybe less usable?) to be able to do this. I would love to have the time to re-address that !@#$%^& GUI.
I think if we implement the TODO item we should divide the dialog into 2 notebook tabs:
Filetype commands Independent commands
Another option would be to divide into:
Build commands Run commands
But I prefer the filetype split.
Yep, definitely agree with that.
Great :)
Regards, Nick
For build we have a separate group for filetype and independent commands. I think the same would be good for run commands for symmetry, and this makes sense if we split the dialog as I mentioned below.
Yes, that would make sense.
I think really we need to be able to set keybindings for all the commands rather than hard wiring extra fixed ones, but IIRC the problem was that none of us could ever think of a quick and easy way of making the keybinding dialog handle variable numbers of commands.
This isn't about hard-wiring. The idea was to have a separate independent run command. It would actually be a separate command group.
Well what I meant is you still have to "hard wire" the keybindings ATM, thats all the keybinding dialog can handle.
The number of build menu items is fixed at startup so I suppose that rows in the keybindings dialog can be made for all those, but it might be confusing having keybindings visible for commands that are not (the empty commands, no point in being able to keybind them :). So we have to hide some of the rows in the keybinding list each time the build commands are updated, and change the text for the visible ones as well. I suppose its all doable, it just needs to be done.
Cheers Lex
On Tue, 5 Apr 2011 02:33:46 +1000 Lex Trotman elextr@gmail.com wrote:
For build we have a separate group for filetype and independent commands. I think the same would be good for run commands for symmetry, and this makes sense if we split the dialog as I mentioned below.
Yes, that would make sense.
Cool.
I think really we need to be able to set keybindings for all the commands rather than hard wiring extra fixed ones, but IIRC the problem was that none of us could ever think of a quick and easy way of making the keybinding dialog handle variable numbers of commands.
This isn't about hard-wiring. The idea was to have a separate independent run command. It would actually be a separate command group.
Well what I meant is you still have to "hard wire" the keybindings ATM, thats all the keybinding dialog can handle.
Yes, this is an existing issue.
The number of build menu items is fixed at startup so I suppose that rows in the keybindings dialog can be made for all those, but it might be confusing having keybindings visible for commands that are not (the empty commands, no point in being able to keybind them :). So we have to hide some of the rows in the keybinding list each time the build commands are updated, and change the text for the visible ones as well. I suppose its all doable, it just needs to be done.
I don't think it's too confusing to have a 'Project Run' keybinding that does nothing by default. The same is true of the filetype build commands when a filetype has none set. I don't think we should hide them.
Regards, Nick