[Libburn] Thoughts about writting writting progress

[Tiago Cogumbreiro]

On S=E1b, 2003-12-06 at 21:52, Derek Foreman wrote:
> On Sat, 6 Dec 2003, Tiago Cogumbreiro wrote:
>=20
> > Hi again,
> > I was trying to develop the writting progress for libburn, while
> > browsing throughout each part of the write_disc code i encountered a
> > minor sitback, how would i describe the progress of writting when we =
are
> > writting the lead-out and lead-in, could the user have access to
> > detailed status of the progress?
>=20
> struct libburn_progress sucks pretty bad, eh? :)
Lol, not that much ;)

>=20
> > On a lesser imporant issue, maybe users would like to know when they =
the
> > drive is performing lead-in/out so maybe a more detailed progress cou=
ld
> > be implemented with a status for describing the device work.
>=20
> Yeah, we should definately provide that information.
>=20
>=20
> leadin and leadout (for raw modes) are just seperate "tracks", and we d=
o
> know their sector lengths and extents (first leadin varies in length fr=
om
> disc to disc)
But for a user a track contains lead-in and lead-out, when they are
implementing it they won't understand that while they've created a
session with 3 tracks it will appear as 9 tracks in the progress...

>=20
> We could just add an enum to the progress struct... lead_in,
> user_data_area, lead_out...  (session_close?  erase?)
Agreed, i think that would be an important implementation

I am online now (freenode.net and gnome.org) and available for a
brainstorm ;)

Tiago