On Fri, Aug 13, 2010 at 07:23, Tei oscar.vives@gmail.com wrote:
On 13 August 2010 10:27, Lars Aronsson lars@aronsson.se wrote: ...
If we applied this web 2.0 principle to Wikibooks and Wikisource, we wouldn't need to have pages with previous/next links. We could just have smooth, continuous scrolling in one long sequence. Readers could still arrive at a given coordinate (chapter or page), but continue from there in any direction.
Examples of such user interfaces for books are Google Books and the Internet Archive online reader. You can link to page 14 like this: http://books.google.com/books?id=Z_ZLAAAAMAAJ&pg=PA14 and then scroll up (to page 13) or down (to page 15). The whole book is never in your browser. New pages are AJAX loaded as they are needed.
You are not thinking "web" here.
The "web" way to solve a problem like easy access to "next page" or "different chapters" is to have a "next page" link or have all the chapters as tabs, or something like that. Make the wiki aware of the structure of a book, and make it render these nextpage link / chapters tabs.
Well, "to make the wiki aware of the structure of a book" is essentially what is requested in bug 15071 [1], which is open since 2008 and blocking 6 other requests which would solve Wikisource/Wikibooks (but non-Wikipedia) specific issues...
Helder
[1] Wikibooks/Wikisource needs means to associate separate pages with books: https://bugzilla.wikimedia.org/show_bug.cgi?id=15071