Re: new module proposal: brasero

[Bastien Nocera <hadess hadess net>]

On Sat, 2008-11-01 at 23:55 +0000, Luis Medinas wrote:
> On Sat, 2008-11-01 at 23:07 +0000, Bastien Nocera wrote:
> > On Sat, 2008-11-01 at 19:27 +0100, Philippe Rouquier wrote:
> > > Hi,
> > > 
> > > We'd be interested in having brasero integrated into the GNOME
> > > desktop.
> > 
> > Having something like Brasero directly in the desktop would completely
> > change the current usage pattern for burning, and copying discs.
> > 
> > Either brasero should be trimmed so as to make it clear that
> > nautilus-cd-burner is still the way to do "easy" CDs, or it should take
> > over nautilus-cd-burner completely whilst offering the same
> > functionality and integration.
> > 
> > So, which way will you be taking brasero?
> > 
> The idea is to replace completely N-C-B

Did you talk to the nautilus-cd-burner devels about it? I guess not...

>  it offers the same features and
> integration (besides the hardcoded link CD/DVD Creator on
> gnome-panel[1-2]),

That's means it doesn't use the same features. It doesn't integrate with
the burn:/// usage pattern.

>  the same easy way to burn files and plus lot's of
> features that could be expected from a application like this.
> Currently besides nautilus, brasero is also the default burning
> application for Banshee and Exaile. Maybe Rhythmbox, Totem and lots of
> other apps could adopt it as well.

Totem doesn't burn anything yet (though integration to get it to burn
video-dvds or video-cds could be useful), and Rhythmbox use
nautilus-cd-burner's libraries, not its interface (except for the simple
"copy cd" functionality).

I'd like to see some documentation (a Wiki page would be just fine), on
what you want the usage pattern for CD burning to be (I'd be happy to
write the current n-c-b usage pattern, along with how we want to behave
in the near future[1]), but I wouldn't want Brasero to be accepted in
the desktop until the integration and the usage pattern reach a better
level.

Cheers

[1]: I'll take the executive way and fix:
http://bugzilla.gnome.org/show_bug.cgi?id=119991#c25
once the dust has settled on 2.24.