eyebex
Hi,
I have several suggestions related to Custom Commands:
1) The window you get when clicking "Edit Custom Commands..." should be renamed to "Custom Command Editor". (Same goes for the "Favorites" window and probably other windows that are invoked by a menu entry with the word "Edit" in it.)
2) I'd like to suggest to be a little bit more detailed in the tooltips for the toolbar icons: "Insert" -> "Insert Command", "Clear" -> "Clear Commands", "Reset" -> "Restore Defaults" (others unchanged).
3) Replace the "Help" box with a (nested) right-click context menu in the "Command" box that allows to directly inserting the placeholder variables.
4) Rename the "Command" box title to "Commands".
5) Allow to execute commands on the local machine from within the command script. Instead of SITE, e.g. a prefix called LOCAL could be used to identify commands that should be executed locally. This could be used to e.g. execute an SSH script that performs actions on the server that cannot be done via FTP.
That's it for now
I have several suggestions related to Custom Commands:
1) The window you get when clicking "Edit Custom Commands..." should be renamed to "Custom Command Editor". (Same goes for the "Favorites" window and probably other windows that are invoked by a menu entry with the word "Edit" in it.)
2) I'd like to suggest to be a little bit more detailed in the tooltips for the toolbar icons: "Insert" -> "Insert Command", "Clear" -> "Clear Commands", "Reset" -> "Restore Defaults" (others unchanged).
3) Replace the "Help" box with a (nested) right-click context menu in the "Command" box that allows to directly inserting the placeholder variables.
4) Rename the "Command" box title to "Commands".
5) Allow to execute commands on the local machine from within the command script. Instead of SITE, e.g. a prefix called LOCAL could be used to identify commands that should be executed locally. This could be used to e.g. execute an SSH script that performs actions on the server that cannot be done via FTP.
That's it for now