Re: Documentation - Questions to the dev

[Philippe Rouquier <rouquier p wanadoo fr>]

Hi,

Le samedi 01 mars 2008 à 16:46 +0100, Milo Casagrande a écrit :
> Hi all,
>
> I'm almost done with my part of the documentation for Brasero, but I
> would like to have some more informations from the developers on a
> couple of things.
Excellent news. Thanks for your work. Brasero really needed a documentation.
> Let's start:
>
> - Integrity check -
>
> * When I insert a previously burned CD and click on "Check" without a
> MD5 file, what is Brasero doing? What is it actually checking?
In fact if the md5sum-file plugin was enabled at burning time it adds to your disc a small file with md5 sum for each and every file on the disc. So basically if you don't provide a md5 sum for the whole CD/image in the check dialog, brasero will use this file: it will try to mount the CD, look for the file containing all md5 sum for every file on the CD and if there is on, it'll  check every file on CD. That's why it's usually longer.
> * Is the integrity check performed after every burn session?
Yes, if the plugin are enabled (though reading the end of your mail there seems to be a problem =)).
> - Plugins -
>
> It seems I'm not able to have all the plugins Brasero can use. I've only
> the default ones (local-track and md5sums).
Yes, if a plugin can image or burn, then brasero will not present it to the user since he could mess up and disable important plugins. Those plugins are managed automatically by brasero. Only non essential plugins are shown.
There are still ways to interfere with plugin management but that should be for advanced users only. From the README :

>From the UI you can only configure (choose to use or not to use mostly) non essential plugins; that is all those that don't burn, blank, or image.
If you really want to choose which of the latters you want brasero to use, one simple solution is to remove the offending plugin from brasero plugin directory ("install_path"/lib/brasero/plugins/) if you're sure that you won't want to use it.
You can also set priorities between plugins. They all have a hardcoded priority that can be overriden through Gconf. Each plugin has a key in "/apps/brasero/config/priority".
If you set this key to -1 this turns off the plugin.
If you set this key to 0 this leaves the internal hardcoded priority - the default that basically lets brasero decide what's best.
If you set this key to more than 0 then that priority will become the one of the plugin - the higher, the more it has chance to be picked up.

> * What are the other plugins?
Mostly one plugin per image/burning app/library (one for growisofs, one for cdrecord, one for wodim, one for libburn ... and so on)

> * Is it possible to have some more description of these plugins to use
> in the documentation? I've been using the small description that comes
> with each plugin, I would like to write something more to the final
> users.
I don't think they should be mentioned. As I said each of these plugins is to manipulate a particular backend. They don't provide a functionality that the user should turn on and off.

> - Issue -
>
> This is something I stumbled upon: if I disable the md5sums plugin in
> the "Plugins" dialog, I'm still able to see the "Check integrity" menu
> entry and still able to perform the integrity check, but obviously
> Brasero complains that the action is not supported. Wouldn't be better
> to hide the menu entry if the plugin is disabled?
agreed. Could you open a bug on bugzilla.gnome.org so I remember this idea before 0.8.X comes out please?

> If I enable only the md5sum and not the md5sum-file plugin and perform a
> integrity check, Brasero exits with a segmentation fault. Re-launching
> it, try to perform another integrity check and it says that "the drive
> can't be locked (ongoing checksuming operation)".
Ok, the first one is obviously a bug (a nice trace could be useful if you report the bug but apparently that should be reproducible).
The second one is linked to the first. brasero locks his drive through HAL before any operation. Once it is done it unlock them. Now if it crashes, the drive remains locked since brasero didn't have the possibility to unlock it. so you have to tell HAL that it isn't anymore. My usual workaround when I run into this problem is that I restart HAL.
> The same happens if I disable all the md5sums plugins and the enalbe
> only the md5sum-file plugin, Brasero exits with a segmentation fault,
> and then I can't perform another integrity check.
Same as above =).
> The version I tested is 0.7.1, the one in Ubuntu 8.04.
>
> Bye!
If I missed something or I was not clear enough, please let me know.

Thanks again to you and all other contributors for your work. It's much appreciated.

Philippe
> _______________________________________________
> Brasero-list mailing list
> Brasero-list gnome org
> http://mail.gnome.org/mailman/listinfo/brasero-list