Proposal: include Brasero by default

[Corey Burger]

On Jan 15, 2008 2:12 PM, David Prieto Ucha <frandavid100 at gmail.com> wrote:
>
> > Removing nautilus-cd-burner wouldn't fix the problem you describe:
> > unnecessary UI inconsistency would still exist with Brasero vs. Nautilus
> > itself. Why is creating a new folder done one way in Nautilus, and
> > another way in Brasero? Why is removing files from a folder done way in
> > Nautilus, and another way in Brasero? Why does the confirmation alert
> > for replacing an item with the same name have different text and buttons
> > in Brasero than it does in Nautilus? Why does Brasero refer to
> > non-existent "projects"? And so on.
>
> I think those would only qualify as inconsistencies if the user happens to
> expect a burning app to have the same interface as the file manager, which I
> think is not the case. I mean, we have a photo management app that does NOT
> look exactly like the file manager and a music management app that does NOT
> look exactly like the file manager, and there was never a problem with
> those. What makes you believe that it would be otherwise with CD burning?
> Why do you think NOT looking and behaving exactly like a file manager makes
> a burning app more complex to use?

The difference here is that burning a cd of files is basically the
same as managing files, as where as managing your music/photos is a
very different thing, with defined tasks, etc. For that matter, Fspot
and RB should make it trivial to burn photo/music/mp3 cds within their
interfaces, leaving NCB for burning random files.

Corey