1) JSPWiki should be able to run without JS active; you'll only miss some ''not-essential'' functionality, such as presentational enhancements, table sorting, etc. Browser specific stuff runs on the client. All gui stuff relies on html and css to a maximum extend.
Yup, this is exactly correct. As it should be.
And I know, documentation could be improved :-)
I guess this is my gripe. I can see *what* is being done, but not *why* :-)
I agree that in some cases the current JS weight of the CORE jspwiki is to much. Especially imho some of the dynamic styles should not be part of the core jpswiki package. I would like to see a kind of pluggable approach to allow users to add js-pieces they need. (similar to server side plugins)
Yup, we're in agreement here. Of course, adding a lot of small JS files can have a performance hit when they are loaded from the server (opening new connections can be expensive). But we could keep them separate for coding, and then have the build process create a concatenation.
/Janne
