[Libburn] get_sectors clean and up global namespace

[Derek Foreman]

On Sun, 14 Dec 2003, Tiago Cogumbreiro wrote:

> Hi again.
> I started by adding funcs for getting sector of a dsic and session but i
> have a question, do i count lead-out/in? If so how do i know if the disc
> will open/closed

We'll have to count lead-in and lead out, probably even if the disc isn't
closed... it would suck to burn a disc with too much data to allow closing
it later.

Also, we might need to eventually pass the write_type to the get_sectors
functions, because if we're burning TAO, there are mandatory 2 second gaps
between tracks. :/

> Then i looked carefully to the namespace and took the liberty to make
> the following changes:
> + added: burn_disc_get_sectors, burn_session_get_sectors

Cool

> Major changes:
>
> With the idea of OOP i changed the following funcs:
> old function name -> new function name
> burn_get_disc_status -> burn_disc_get_status
> burn_get_drive_status -> burn_drive_get_status
> burn_erase_disc -> burn_disc_erase
> burn_read_disc -> burn_disc_read
> burn_write_disc -> burn_disc_write

These are good, thanks

> Because we are adding a session to a disc why not:
> burn_session_add -> burn_disc_add
> burn_session_del -> burn_disc_del
> The same thing applies to adding tracks to sessions:
> burn_track_add -> burn_session_add
> burn_track_del -> burn_session_del
>
> Comments, correction, flames? :D

I think I'm going to change it to
burn_session_add_track/burn_session_remove_track instead

> Btw, when the lib is somewhat stable i'll start making bindings to it, I
> can do Python, Java and maybe C# (little new on that lang), might be a
> good improvement on the lib to be cross language ;)
> This way we will have .BURN :P haha

Sounds great :)

I made it compile, then merged it with some small changes. ;)

> Tiago Cogumbreiro
>