Re: windows to Macintosh collaborative writing problem
- From: "esj" <esj@xxxxxxxxxx>
- Date: 21 Jun 2006 07:18:44 -0700
Dave Hinz wrote:
On 20 Jun 2006 20:42:38 -0700, esj <esj@xxxxxxxxxx> wrote:
Frédérique & Hervé Sainct wrote:
This means using a software that's very adapted to your need. An
alternative I was thinking about is almost opposite: share a wiki with
your editor. A wiki *will* handle changes (actually, remember all
that's a great idea except for the fact that we both detest wikis.
Perhaps you're using them wrong?
possible but not terribly likely. The user interface sucks for hands
or for speech recognition. All of the special characters for markup
are easy to get wrong and/or are difficult to speak.
Yes, you seem to have missed the whole point, sory. The whole point of
using a wiki is that you can just type the info, and if you need a link,
type that word LikeThis and it's a link. All the other stuff is
optional. If someone wants to fancy it up they can.
thank you for highlighting one of the issues I consider a fundamental
flaw of wikis. If you're using speech recognition, browser textareas
reduced performance and accuracy of recognition. Firefox, at the very
least, starts randomly consuming lots of CPU time which again reduces
performance and accuracy of recognition.
the second problem with textareas is that they are a bitch to work with
beyond the couple thousand characters. You've got no searching
capability no command and control, you can't even use a tab character
because it puts you to the next part of the HTML form.
As for links <cap>like<no space><cap>this is really ugly to say once
let alone multiple times. Recognition accuracy for that particular
sequence is moderately low and you need to put lots of second long
spaces between commands in order to make it work reasonably correctly.
Additionally, for that particular construct, it's virtually impossible
to correct anything, you need to delete the whole sequence and start
over.
this is the typical clash between speech recognition and geek friendly
techniques.
And, well,
JavaScript steals more cycles from a machine that a proof of work
antispam stamp generator ever thought of doing.
A javascript wiki? Hm, haven't seen one.
sorry, I wasn't clear. I should've said a JavaScript applications in
any form steal more cycles... JavaScript interpreter implementations
are cruelly horrific.
anyway, this is getting a bit far afield of the original topic. thanks
for your feedback. It is appreciated.
.
- Follow-Ups:
- Re: windows to Macintosh collaborative writing problem
- From: Dave Hinz
- Re: windows to Macintosh collaborative writing problem
- References:
- windows to Macintosh collaborative writing problem
- From: esj
- Re: windows to Macintosh collaborative writing problem
- From: Erik Richard Sørensen
- Re: windows to Macintosh collaborative writing problem
- From: esj
- Re: windows to Macintosh collaborative writing problem
- From: Frédérique & Hervé Sainct
- Re: windows to Macintosh collaborative writing problem
- From: esj
- Re: windows to Macintosh collaborative writing problem
- From: Dave Hinz
- windows to Macintosh collaborative writing problem
- Prev by Date: Re: windows to Macintosh collaborative writing problem
- Next by Date: Re: windows to Macintosh collaborative writing problem
- Previous by thread: Re: windows to Macintosh collaborative writing problem
- Next by thread: Re: windows to Macintosh collaborative writing problem
- Index(es):
Relevant Pages
|