Any planned features for the next FS-Plugin API?

[shocquer]

I was just browsingthis forum to get the current informations and saw somewhere that a nice feature could get it in version 7.0.
So what are the planned features? Is there a public list of them?

I would like to have 3 things:
Initialising the plugin with current HWND.
Registering plugin to receive a command, like Show Hidden Files.
Extending popup menu to add some items, just to have more than only "properties" entry

I'm sure that it could be a longer list. So what's the secret?

Thanks.

[ghisler(Author)]

I want to keep the plugin API as simple as possible, but I'm open for suggestions. One thing I plan to add is the ability to get thumbnails from file system plugins. TC will send the name to the plugin, and the plugin could return either a bmp directly, or the location of a file from which TC could get the plugin (permanent or temporary).

[shocquer]

Well, some users of SFTP Plugin want's equivalent features to FTP support in TC, so it's not as easy to keep the API simple.

Another problem I would like to solve is to integrate some multilanguage support to SFTP4TC. Do you have a hint, how to read the language setting from TC and notice its change?

[CoMiKe]

I want to see custom columns for FS plugins (I wrote about this earlier). In a way in which the plugin author should decide whether the plugin needs custom columns or not.

For example, registry plugin, uninstall plugin, pop/smtp plugin would need custom columns, but other plugins wouldn't.

I think it's not very hard to implement, as custom columns are already there for other tasks. You only need to extend the FS plugin API with a pair of functions, so TC asks the plugin for custom columns.

[djorge]

I think it's not very hard to implement, as custom columns are already there for other tasks. You only need to extend the FS plugin API with a pair of functions, so TC asks the plugin for custom columns.

Agree

[Unjoanqualsevol]

... TC will send the name to the plugin, and the plugin could return either a bmp directly, or the location of a file from which TC could get the plugin (permanent or temporary).

Great,
Just do some similar about custom plugins (and contents related features) in FS plugins.
Ask to the plugin if it can handle special columns and what columns (as an usually content plugin). If yes then the plugin must return the value of this columns on request, or a file from which TC could get the value.

An extra option: In the case of plugin return a file, then it also could be used with any other content plugin.

I think its easy to implement (the great work is done) and power the TC features a lot.

I have in mind some FS plugin, but with only the standard columns doesn't have sense do it.

Thanks.

[CoMiKe]

I have in mind some FS plugin, but with only the standard columns doesn't have sense do it.

Exactly, totally agree.

[ghisler(Author)]

The problem with custom columns is that they aren't directory-specific - storing all kind of information separately per directory would mean a lot of overhead and possible slowdown. Any ideas?

[djorge]

Hello,

from all the FSPlugins i have seen, none of them would benefit with directory-specific custom columns. In my opinion it would not be dramatic if the custom columns were implemented as flat custom columns.

However, new ideas could be implemented with the introduction of directory-specific custom columns.

[CoMiKe]

The problem with custom columns is that they aren't directory-specific - storing all kind of information separately per directory would mean a lot of overhead and possible slowdown. Any ideas?

Sorry, I don't completely understand this statement.

Are directory-specific columns really needed for custom columns in FS plugins?

I thought it was just a matter of asking the plugin at initialization what custom-columns are needed. Then, when reading a folder from a FS plugin, for every object, TC should ask the plugin for the data of every column.

Am I wrong? What's up with directory-specific columns?

Sorry for my not so vast intellect

[Hacker]

Sorry for my not so vast intellect

LOL

Roman

[ghisler(Author)]

I thought it was just a matter of asking the plugin at initialization what custom-columns are needed. Then, when reading a folder from a FS plugin, for every object, TC should ask the plugin for the data of every column.

If it only were that easy.

There are many many open problems:
1. When should these plugin-specific columns be shown? When the user has chosen some other custom columns view? In full view?
2. To which view to switch after leaving a content plugin.
3. How to auto-adjust the column widths? This is font- and resolution-specific.

These are just the problems which came into mind during the last 5 minutes - there are certainly more...

[CoMiKe]

I don't know if you were actually searching for answers, but this is what comes to my mind:

1. When should these plugin-specific columns be shown? When the user has chosen some other custom columns view? In full view?

I believe they should be only shown in full view mode. I wouldn't make custom view available for FS plugins, so leave it as it is now.
Also, the user should choose what custom colums to show through the plugin configuration. So the plugin should tell TC if he must show custom columns, and what custom columns to show (if any).

2. To which view to switch after leaving a *content plugin*.

*I think you are referring to FS plugin, and not content plugin.*
According to last point, I think TC must return to full view after leaving a FS plugin, as that's the view in which FS custom-colums are shown.
But I think TC should be able to remember the view that was selected for later use before entering any FS plugin directory.

3. How to auto-adjust the column widths? This is font- and resolution-specific.

That should be the real problem. But perhaps this can also be configured in the plugin setup, so the plugin informs TC of column widths.
Or perhaps it's not such a great idea. Let the user adjust column widths, then TC should be able to remember them in a config file.

These are just the problems which came into mind during the last 5 minutes - there are certainly more...

If you have found any other problems, write them down here, so we can think any solutions. I think this feature would make TC almost perfect (at least IMHO).

[White Wind]

Yes! And maybe FS plugin should inform TC when user changes column list while browsing this plugin.

This is the most needed feature at the moment, please don't ignore it.