Add internal CD/DVD burning to TC? (FoxBurner SDK)

Stitscher · Post by *Stitscher » 2007-11-30, 11:13 UTC

Promising conversation.

Stitscher

StickyNomad · Post by *StickyNomad » 2007-11-30, 11:48 UTC

indeed!

kajoj1 · Post by *kajoj1 » 2007-11-30, 12:55 UTC

I support whole idea!

2Ghisler

This would give me a very good starting point, but also allow me to integrate it better into TC than it can be done with external plugins.

I think you could improve user interface in "burning mode" and add some extra elements in it, like here in this fake screenshot.

D1P · Post by *D1P » 2007-11-30, 14:57 UTC

I do not support idea.

CD/DVD burning feature must be implemented as external tool only. Why?
Let's have to look an TC internal FTP tool. It is quite easy and convenient, so it very useful for simple operations. But for some operations, like large data automatic downloading, multithreaded uploading/downloading, etc, this tool absolutely useless. So, i compelled to install and use more perfect tools anyway.

I fear that burning tool will be implemented in this manner. Of course, this tool sometimes can be useful, but if it does not satisfy my needs, i am still going to use more sophisticated programs.

This would give me a very good starting point, but also allow me to integrate it better into TC than it can be done with external plugins.

Maybe it was better to improve plugins interface?

Lefteous · Post by *Lefteous » 2007-11-30, 16:34 UTC

2D1P
Even with an internal solution you can still use a more sophisticated external solution - the same as with FTP.

I have my doubts but for other reasons. The 1st is the already mentioned additional development time for the author. The 2nd is the old problem which affects more and more parts of the program: Encryption. The FoxBurner SDK offers many cryptography functions. It would be really a pity if they would have to be left out.
Anyway I'm of course happy that something happens about burning.

Loc2262 · Post by *Loc2262 » 2007-11-30, 17:24 UTC

Yes, I agree with Lefteous, what D1P is suggesting doesn't make sense. Why not implement burning support in TC, even if some more advanced techniques can't be implemented? Burning from within our favourite file manager is very convenient, and if advanced stuff is needed, I can still use Nero etc.

D1P · Post by *D1P » 2007-11-30, 18:06 UTC

Why not implement burning support in TC, even if some more advanced techniques can't be implemented?

Why not implement a web browser to TC?
Why not implement a mail reader?
Why not implement a text editor?

But if all this tools will be implemented as internal tools, TC become to fat, monstrous program. It is first reason.
Second: at this moment all this external tools already can be used with TC. Any burning tools too. So, it will be preferably for me, if developer spent his time to increase overall compatibility (improve plugins interface, for example).

Yes, i understand: adding burning tool is a good advertisement for TC. I just want to say: any developer must need to think seven times before implement any tool like this.

Loc2262 · Post by *Loc2262 » 2007-11-30, 18:16 UTC

Burning support can, due to FoxBurner SDK, be added with relatively little additional code logic in TC itself. The file size of the TC executable will increase only marginally. All the heavy-duty burning work is done in FoxBurner, and things like file management to compose your burning projects is already present in TC.

And for those people who worry about the additional download size for the FoxBurner DLL (about 500 kB), Christian could offer two download versions, with and without burning support. The exe can simply query if the FB DLL is present and (de)activate burning features accordingly.

D1P · Post by *D1P » 2007-11-30, 19:35 UTC

Burning support can, due to FoxBurner SDK, be added with relatively little additional code logic in TC itself.

I hope to that.

And for those people who worry about the additional download size for the FoxBurner DLL (about 500 kB), Christian could offer two download versions, with and without burning support. The exe can simply query if the FB DLL is present and (de)activate burning features accordingly.

This change situation view for me. Thanks for information.

Stevie1 · Post by *Stevie1 » 2007-12-02, 23:07 UTC

woohoo! Locutus! you are back

im very happy that things develop that way.
looking forward!

fenix_productions · Post by *fenix_productions » 2007-12-03, 00:41 UTC

I am against this feature too. Imho the better would be giving more extensible plugins interface. Maybe creating new plugins types could help. The most important thing should be making already implemented features completed (e.g. files extensions assignment) or more user friendly (e.g. Options dialog redesign). There are many glitches with layout itself but sometimes Christian seems to not see them.
There are many threads where Christian said nothing (e.g. IrfanView and XnView simultaneous work support) or was against (e.g. Breadcrumb)...

Sosna · Post by *Sosna » 2007-12-03, 13:18 UTC

I see that there are some people who don't want or don't need internal burning feature. Well, people, that's your business, don't use it if you don't like it, but there are many people, that can use internal burning instead of huge monstrous packets like Nero. (Don't offer free tools, I'd like to burn from TC). We have archive plugins, it is the same staff (CD/DVD instead of file on HDD). As you can see, those topics with another plugins has lesser responses than this one (since Locutus return).
Anyways, let mr. Ghisler decide what to do.

Postkutscher · Post by *Postkutscher » 2007-12-03, 13:41 UTC

Das wird nicht mehr "my business" sein an der Stelle, wenn ich den "nackten" TC mit einem Floppy transportieren moechte , oder diese neue unbekannte Funktion ueberall in den Einstellungsfenstern sehen werde und nicht mehr entfernen kann, wie die Plugins.

Can anybody translate my post clear into English? Andernfalls es muss zu deutschen Foren

[EDIT] Translation by Hacker (Moderator):
This will not be my business anymore when I want to copy the naked TC on a floppy or when I see this new function all over the config dialogs and I cannot remove it as opposed to plugins.

Lefteous · Post by *Lefteous » 2007-12-03, 13:46 UTC

Even if the solution is provided by Ghisler it doesn't have to be part of the total commander executable. It could be a filesystem plug-in which could be removed just like any other file-system plug-in. Implementation as a filesystem plug-in of course requires some improvements of the plug-in interface.

It would be very interesting to hear the authors' opinion on that.

Loc2262 · Post by *Loc2262 » 2007-12-03, 13:53 UTC

Indeed several improvements of the FS plugin interface would be necessary: e.g. a deinitialization call before the DLL is unloaded, and the plugin must have the chance to cancel the deinit/TC shutdown, otherwise users can close the program in mid-burning.

For me, both would be acceptable solutions. As I explained earlier, TC itself would get only marginally larger by implementing FoxBurner based burning functions! So when you leave out the FB.DLL, file size will barely increase, and you don't need to use the new functions.