Hi, 1. I mentioned this problem to someone on the list the other week. Would like to know what you folks think. On the Sonera-Zed, British Gas and Philips projects javascript was unneeded (WAP-WML), minimised or banned for security reasons. This might be another barrier to acceptance. I've had to turn javascript on to access XWiki. A standard set of security problems is referenced at: http://www.panix.com/~aahz/javascript.html Do folks reckon the security problems have now been tied up then and these corps should change their policy? Cheers Jim 2. PS Ajax is not the only way of doing asynch before this project adopts yet another technology. FI: List members might enjoy Phil Wadler's 'The next 700 computer languages' http://homepages.inf.ed.ac.uk/wadler/topics/xml.html I regard it as pretty mandatory reading.
Hi Jim, The core of XWiki should not require Javascript. I would be ok to chase the cases where a barebone XWiki would not work without Javascript. I understand the concerns for Javascript in certain environments.. Now there are some issues (like IE not handling CSS Hover correctly) which are more easily solved using Javascript. Finally one of the core requests for adoption is a good interactivity. In these cases JS and AJAX in particular are interesting technologies to provide rich interactivity without going for Flash or other stuff. My opinion, is that XWiki should have all it's content URI addressable, should not requite advanced JS for the core UI to work and especially viewing data, but at the same time can and should have advanced interactivity (using what we can efficiently use) to get good adoption from users. You mention other technologies than AJAX to provide Asynch work.. Don't hesitate to tell us more about this. Ludovic Jim Stuttard a écrit :
Hi,
1. I mentioned this problem to someone on the list the other week.
Would like to know what you folks think. On the Sonera-Zed, British Gas and Philips projects javascript was unneeded (WAP-WML), minimised or banned for security reasons.
This might be another barrier to acceptance. I've had to turn javascript on to access XWiki.
A standard set of security problems is referenced at: http://www.panix.com/~aahz/javascript.html
Do folks reckon the security problems have now been tied up then and these corps should change their policy?
Cheers
Jim
2. PS Ajax is not the only way of doing asynch before this project adopts yet another technology.
FI: List members might enjoy Phil Wadler's 'The next 700 computer languages' http://homepages.inf.ed.ac.uk/wadler/topics/xml.html
I regard it as pretty mandatory reading.
------------------------------------------------------------------------
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic
On Mon, 06 Jun 2005 15:16:49 +0200, Ludovic Dubost <[email protected]> wrote:
I would be ok to chase the cases where a barebone XWiki would not work without Javascript
As I'm still at a primitive stage where I've not got an XWiki package diagram or future roadmap (except in the jira comments etc) I would be happy to try and chase the javascript dependencies. I'll have a look asap. Cheers Jim -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
BTW, I've added some JS in the history page to make sure robots won't follow the link to rollback or view previous version. We need to change the URL so these can be used in the robots.txt file to stop robots from there. Ludovic Jim Stuttard a écrit :
On Mon, 06 Jun 2005 15:16:49 +0200, Ludovic Dubost <[email protected]> wrote:
I would be ok to chase the cases where a barebone XWiki would not work without Javascript
As I'm still at a primitive stage where I've not got an XWiki package diagram or future roadmap (except in the jira comments etc) I would be happy to try and chase the javascript dependencies. I'll have a look asap.
Cheers
Jim
------------------------------------------------------------------------
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic
On Mon, 06 Jun 2005 15:16:49 +0200, Ludovic Dubost <[email protected]> wrote:
Finally one of the core requests for adoption is a good interactivity. In these cases JS and AJAX in particular are interesting technologies to provide rich interactivity without going for Flash or other stuff.
Yes but only maybe best?
My opinion, is that XWiki should have all it's content URI addressable, should not requite advanced JS for the core UI to work and especially viewing data, but at the same time can and should have advanced interactivity (using what we can efficiently use) to get good adoption from users. Right on! You mention other technologies than AJAX to provide Asynch work.. Don't hesitate to tell us more about this.
I started off with Applet for rich, thin clients if that's what you call them. I far prefer Applet java to wsdl and other spaghetti which (like ant scripts) it seems sensible to generate from java and ignore after that (apart from testing of course). Enclose are my meagre preliminary notes, quotes on AJAX if they're of any use to anyone. Cheers Jim
participants (2)
-
Jim Stuttard -
Ludovic Dubost