The next step is to decide what to do with the copious output provided by
wodim while it is doing it's thing. Grant: do you want to weigh in on this
issue? (I believe that yesterday I forwarded a file containing said
output.)
Thank you very much for your work on this. We are definately getting
closer to having something usable soon.
I have the wodim.9 and wodim.11 binaries already checked into the git
repository for different fedora systems that are deployed in the
field. Using yum and dependencies is against the rules for deploying
Activities so anything our Activity needs must be shipped in the .xo
file that gets generated and posted for download via a browser into a
Sugar system.
The output from wodim I was thinking of using is the constantly
updating "Track 01: 686 of 686 MB written" line that gives some kind
of % complete status while it's burning. I agree the stuff before and
after is a bit copious and of little value to an end user. In the log
file you provided yesterday it gets constantly overwritten and only
shows the final result. Much depends on what UI we want to show to
the user which hasn't been designed yet. It's a bit of a chicken and
egg problem. If we can parse out the xyz of pdq MB written data we
can provide some kind of status while the CD is being burned.
I'll be working on Toaster with Jim at 5:00 on Monday. Maybe we can
talk on the phone before then.
Grant