On Mar 27, 4:22 pm, Miki <[EMAIL PROTECTED]> wrote:
> Hello Tim,
>
> > that looks nice, simple, and intuitive. thanks for thinking about it.
>
> Thanks, glad I could help.
>
> > Now to dive into some gui coding!
>
> IMO you can pull it off as a web application and then you won't need
> to worry abo
Hello Tim,
> that looks nice, simple, and intuitive. thanks for thinking about it.
Thanks, glad I could help.
> Now to dive into some gui coding!
IMO you can pull it off as a web application and then you won't need
to worry about cross-platform,
upgrades and all that interesting stuff.
HTH,
--
M
"Miki" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello Tim,
>>
>> Any ideas on a simple interface for this?
>>
> How about something like:
>
> Chapter 1 (001-200 200)
> Chapter 2 (200-300 100)
> -- 001-300 300
> Chapter 3 (300-450 150)
> Chapter 4 (450-500 50)
>
On Mar 26, 5:11 pm, Miki <[EMAIL PROTECTED]> wrote:
> Hello Tim,
>
>
>
>
>
> > I want to write a tiny interactive app for the following situation:
> > I have books of many chapters that must be split into volumes before going
> > to the printer.
> > A volume can have up to 600 pages. We obviously b
Hello Tim,
> I want to write a tiny interactive app for the following situation:
> I have books of many chapters that must be split into volumes before going
> to the printer.
> A volume can have up to 600 pages. We obviously break the book into volumes
> only at chapter breaks. Since some chapter
hi,
I want to write a tiny interactive app for the following situation:
I have books of many chapters that must be split into volumes before going
to the printer.
A volume can have up to 600 pages. We obviously break the book into volumes
only at chapter breaks. Since some chapters make a natural
