Re: cdebconf progress bars and debootstrap

2003-03-06 Thread Petter Reinholdtsen
[Martin Sjögren] > Why would you need max in the progress set command if you've got min > and max in progress start (okay I didn't write that, but I meant it) Could you document the current and proposed protocol and API in d-i/docs/ somewhere? > Hrrm, maybe. It could be tricky frontend-ish... In

Re: cdebconf progress bars and debootstrap

2003-03-05 Thread Martin Sjögren
ons 2003-03-05 klockan 22.35 skrev Denis Barbier: > On Wed, Mar 05, 2003 at 07:40:32PM +0100, Martin Sjögren wrote: > [...] > > progress start (can still use this one, and it makes sense) > > progress step (or progress set ) > > progress info > > progress stop > [...] > > The max value is miss

Re: cdebconf progress bars and debootstrap

2003-03-05 Thread Denis Barbier
On Wed, Mar 05, 2003 at 07:40:32PM +0100, Martin Sjögren wrote: [...] > progress start (can still use this one, and it makes sense) > progress step (or progress set ) > progress info > progress stop [...] The max value is missing: progress set The 'set' method is IMO more easily manageable

cdebconf progress bars and debootstrap

2003-03-05 Thread Martin Sjögren
Well, after "discussing" with aj for a while, he had the following comment about the cdebconf progress bar API: "it sucks" ;-) Myself, I am of the opinion that it was a bad idea not to look at what debootstrap and b-f use, when designing the API. Short summary: cdebconf progress bars: progres