i put the first draft of our collaborative project up:
i'm using the beta-version of an upcoming compiler, so this should work on safari, it might work on chrome and firefox, and it might not work on internet explorer. and it definitely won't work on opera; sorry about that. when you first enter the site/app, it should look like this:
if you don't see the field on the right half of the screen, try resizing your window to see if that makes it appear... the performance is somewhat sluggish at times. sorry. what we have here is the book "the jungle" by sinclair... the z.m.l. version is loaded into the left side, a text-field. the right side displays a crude .html rendering of the text. the book is displayed one section (i.e., chapter) at a time... the popup menu contains a list of the sections in the book, and you can jump to a section by selecting it in the popup. or you can step through the sections via the arrow buttons. as the text for each section is displayed, a rough version of the .html for that text is created on the fly, and displayed... the "save" button lets you save a copy of the book's text. type a 5-letter name (all-lowercase) in the box next to the "save" button first, to specify the name to use for the file... the text is editable. so go ahead and feel free to change it, for one or more chapters. hit "save" after making changes to _any_ chapter (each and every chapter), or else your edits will be lost. when you return to a chapter you have edited, you will see that the changes you made are being displayed. in most circumstances, the field to the right of "save" button is the _search-field. enter a search-term into the field and press [return] and you'll be taken to the next section which contains that search-term. (if the search-routine hits the last section without finding the search-term, it will wrap around to the first section and start searching from there.) again, sometimes the results can be sluggish, so be patient. feedback? -bowerbird
Okay, so I'll jump... How about italics in the rendered text instead of the ugly underscores? How about curly quotes? How about links from the table of contents to the chapters? How about real em-dashes instead of double-hyphens? How about using _any other_ font for the body text? Please? Why not leave it at the user's default rather than force something as ugly as Comic Sans? How about jumping to the right spot in the chapter after the search? Or highlighting the text somehow? It doesn't help me much that I've found some text when I still have to read through the whole chapter to actually find the passage I'm looking for. Why does it only sometimes save my changes? I had to edit the dedication twice to have it pick up my changes. Jana On 2011–02–19, at 22:20, bowerbird@aol.com wrote:
i put the first draft of our collaborative project up:
i'm using the beta-version of an upcoming compiler, so this should work on safari, it might work on chrome and firefox, and it might not work on internet explorer. and it definitely won't work on opera; sorry about that.
when you first enter the site/app, it should look like this:
if you don't see the field on the right half of the screen, try resizing your window to see if that makes it appear...
the performance is somewhat sluggish at times. sorry.
what we have here is the book "the jungle" by sinclair... the z.m.l. version is loaded into the left side, a text-field. the right side displays a crude .html rendering of the text.
the book is displayed one section (i.e., chapter) at a time...
the popup menu contains a list of the sections in the book, and you can jump to a section by selecting it in the popup.
or you can step through the sections via the arrow buttons.
as the text for each section is displayed, a rough version of the .html for that text is created on the fly, and displayed...
the "save" button lets you save a copy of the book's text. type a 5-letter name (all-lowercase) in the box next to the "save" button first, to specify the name to use for the file...
the text is editable. so go ahead and feel free to change it, for one or more chapters. hit "save" after making changes to _any_ chapter (each and every chapter), or else your edits will be lost. when you return to a chapter you have edited, you will see that the changes you made are being displayed.
in most circumstances, the field to the right of "save" button is the _search-field. enter a search-term into the field and press [return] and you'll be taken to the next section which contains that search-term. (if the search-routine hits the last section without finding the search-term, it will wrap around to the first section and start searching from there.) again, sometimes the results can be sluggish, so be patient.
feedback?
-bowerbird
participants (2)
-
Bowerbird＠aol.com -
Jana Srna