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>
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|