I think that Javascript shouldn't be necessary, but would be a good addition.
I've seen it put to good use.
Think about things like this:
When listing a directory of a thousand files.. it would be a nightmare to move
a file from the bottom to the top. I can think of a way of presenting the
files in a textual manner which would work just as well as a javascript-enabled
gui .. at least for me.
Your example of moving a file is also good.. although I could easily see a
simple input box which allows the user to type in the name of the folder to
move the article to. If that folder is not found, then cowiki would respond
with a list of partial matches to choose from.
I can see lots of places where javascript would make for excellent eye-candy,
but unless we have a javascript guru on-hand, I personally think your services
are better spent on core functionality and not pretty extras.
I personally wouldn't care if there were parts of cowiki which were accessible
only via javascript-enabled functionality. However, continuing to ensure that
the common stuff doesn't require javascript would be a Good Thing.
Sy,
-----Original Message-----
From: "Daniel T. Gorski" <daniel.gorski@xxxxxxxxxxxx>
To: coWiki dev <cowiki-dev@xxxxxxxxxxxx>
Date: Mon, 18 Oct 2004 04:16:36 +0200
Subject: [cowiki-dev] coWiki and JavaScript
Hi folks,
a few days ago, I restarted my brain-storming on coWiki (yet in small steps
of course, keep calm). As I was thinking about it, one important and basic
issue came to my mind. An issue that could/would change the all over
behaviour of future coWiki releases. The question is just simple with wide
consequences:
"Is JavaScript in the coWiki user interface an option for you?"
So far, coWiki didn't need any JavaScript to make it work - except a
few rollover-and-highlight gimmcks on its buttons. The coWiki code claims
accordingly "Never use JavaScript for essential functionalities".
The problem we run into is: coWiki is primarily a tool one want to work
with, it is not a content management system nor is it just a simple website,
it's a tool.
What I've in my mind for the future is e.g. the visualisation of movement of
documents within the hierarchy (expandable DHTML-trees without an extra
request), visualisation of CHMOD/CHOWN-functionalies or proposal of
related/linkable document names to the user while he is editing a document,
etc.
What is your attitude to JavaScript in coWiki at all?
regards dtg
--
This is the coWiki developer mailing list (http://develnet.org)
Unsubscribe: send an empty email to <cowiki-dev-unsubscribe@xxxxxxxxxxxx>
ML commands: send an empty email to <cowiki-dev-help@xxxxxxxxxxxx>
--
This is the coWiki developer mailing list (http://develnet.org)
Unsubscribe: send an empty email to <cowiki-dev-unsubscribe@xxxxxxxxxxxx>
ML commands: send an empty email to <cowiki-dev-help@xxxxxxxxxxxx>
|
