Total Commander

The interface is not released ( not ever fully designed ) yet, but there are some controversies already.
It can't be implemented as a current plugin - if it could, it would not be needed. So it has to be an external app. There are 2 (possibly more) ways of doing it.

A launcher - the interface launches TC and makes all important changes.

A service - it runs in background and looks for TC's start, then does everything needed.

Which option do you prefer?

I do not add "I don't care" and similar answers because the result may be scary

ADDED: B means Background. Plugins that start with TC and (if they want to) work as long as TC does.

What plugins will use this WBX interface?
Do you plan some...

Alextp wrote:What plugins will use this WBX interface?
Do you plane some...

Yes, I do. I even have some already
I plan to release 4 (maybe more) simple plugins for some tasks that could be done in another, but usually more dirty way.
- I want to change TC's title bar and provide there information like current memory / CPU utilization
- RClick on the minimize button=minimize to tray
- Autostart some programs with TC (and autoclose)
- For people who use 2-row buttonbars, at startup set a resolution-specific one.

Furthermore, I want to add COMMANDER_FTP environment variable with the interface itself (I have to add the current variables because plugins start before TC does - so why shouldn't I add the missing one?).

EDITED.

Ever tougth about COM Interface?
I think this is very interessting for such things. If it is needed it is loaded by windows. The very best way of on demand.

Nothing has to wait or sit until something happens.

You know interrupt and polling controversial discussion

Ciao Ephraim

Sounds nice. Vote for Launcher.

Ephraim wrote:Ever tougth about COM Interface?
I think this is very interessting for such things. If it is needed it is loaded by windows. The very best way of on demand.

Nothing has to wait or sit until something happens.

You know interrupt and polling controversial discussion

Ciao Ephraim

Nope, I don't know COM. I've heard that is a very bad thing before...but the tricks I'm doing are not so nice
I probably won't move to COM with WBX 1.0 because it's mostly written already, but maybe later, or with another interface... Can you write something more about it's advantager and (or) post a link to a guide better than MSDN?

2m^2
I don't know actually if I spread secret information , but I think you can contact VadiMGP - ha had done some interesting "plugins" like yours.

XPEHOPE3KA wrote:2m^2
I don't know actually if I spread secret information , but I think you can contact VadiMGP - ha had done some interesting "plugins" like yours.

Thank you, I know. He told me about them.

I have some news about the interface.
First, I'd like to apologize for the delay. As writing one of the plugins required significantly more work than I expected, I failed to write it before june. Then I had examination session and I had no time to write anything.
During this, my portable hard drive broke, I had all my sources on it. WBX was too new to have a backup....Yes, I have nothing written.
But fortunately, it's a small thing and, as I wrote it once, it's also easy. I can code the interface in several hours, but plugings will take more, especially as writing them is a boring job
Anyway I hope to write it in 2 weeks.

2m^2
Did you try data restoration tools to rescue files in your portable drive?

No, the drive is physically damaged. It doesn't even start, firmware blocks it.