On Mon, Jul 30, 2001, Robert O'Connor wrote:
> Just as a followup question. Would it be a good time then to settle on a tag
> definition for next plucker HTML page [potentially chapter in an ebook
> context], as David suggested last week.
I'm not sure that this is the solution that should be used. I have
suggested a feature for next/previous page handling and later on
Bill Janssen suggested the tour concept.
When you're on a tour, "page down" would automatically take
you to the next section, if you are at the end of the current
page. You would be able to select any one of the various
available tours for a document.
I think this is a much more powerful solution than just adding a
tag to the data that the viewer should interpret and do something
with. A tag could still be added but in that case it should be
used by the parser to create a specific "tour".
The next/previous page feature (I created a sample viewer and
database to demo it back in January) will only require 4 bytes/
record (can be compressed) and you could have several different
"tours" in a Plucker document.
The biggest problem is to create those "tours", though.
/Mike
