A necessary crosslink:
http://www.ghisler.ch/board/viewtopic.php?t=525
Would you like to see macros for Total Commander?
Moderators: Hacker, petermad, Stefan2, white
-
pdavit
- Power Member
- Posts: 1529
- Joined: 2003-02-05, 21:41 UTC
- Location: Kavala -> Greece -> Europe -> Earth -> Solar System -> Milky Way -> Space
- Contact:
Heh! The first step is done!!! 
Check this out: http://www.ghisler.ch/board/viewtopic.php?t=2499
Thanx Aezay!
Check this out: http://www.ghisler.ch/board/viewtopic.php?t=2499
Thanx Aezay!
"My only reason for still using M$ Window$ as an OS is the existence of Total Commander!"
Christian Ghisler Rules!!!
Christian Ghisler Rules!!!
-
XelaRellum
- Junior Member
- Posts: 2
- Joined: 2004-10-14, 06:22 UTC
Macros? Python scriptable!
I would really like macros, but I hope there wont be YASL (yet another scripting language). So why not use Python? I believe people would love this!
Xela
Xela
Re: Macros? Python scriptable!
YES! Python would be cool!XelaRellum wrote:I would really like macros, but I hope there wont be YASL (yet another scripting language). So why not use Python? I believe people would love this!
Xela
It should be the first choice.
Francesco
-
SanskritFritz
- Power Member
- Posts: 3693
- Joined: 2003-07-24, 09:25 UTC
- Location: Budapest, Hungary
I'd really like to see macros, and I think it's a feature suitable for the TC core. That might help for a cleaner, more flexible design.
A design I'd like to see is to keep pretty much the entire UI intact with the Preferences dialog, *but* with a new feature under the "Misc." options where you define hotkeys. Instead of just adding one command like those built-in cm_* commands, let a user call a custom function. It could use the very same text field.
Next, have a button there for a function/script designer (or it could just open something like Notepad, hehe), and what you add into that Command text field could now be not just the cm_* commands, but also the same as a function that's called in a script.
As for which language -- oh I don't really care much... I'd like to be able to call cm_* commands from within the script though, and have functions with parameters, to for example set pane widths from a script.
That was actually what brought me here -- I'd like one key in TC to expand the thumbnail view to give it a bit extra room at the cost of the other panel, and restore it again once I return to the regular list view.
That's an example of a macro that would ideally only need two lines -- one to call a function to set pane widths, and another to switch view mode in the focused list.
A design I'd like to see is to keep pretty much the entire UI intact with the Preferences dialog, *but* with a new feature under the "Misc." options where you define hotkeys. Instead of just adding one command like those built-in cm_* commands, let a user call a custom function. It could use the very same text field.
Next, have a button there for a function/script designer (or it could just open something like Notepad, hehe), and what you add into that Command text field could now be not just the cm_* commands, but also the same as a function that's called in a script.
As for which language -- oh I don't really care much... I'd like to be able to call cm_* commands from within the script though, and have functions with parameters, to for example set pane widths from a script.
That was actually what brought me here -- I'd like one key in TC to expand the thumbnail view to give it a bit extra room at the cost of the other panel, and restore it again once I return to the regular list view.
That's an example of a macro that would ideally only need two lines -- one to call a function to set pane widths, and another to switch view mode in the focused list.
