Martin - I honestly do not see this division of two schools, or ways of doing things.
I have been working for years on PmWiki and always advocating and pioneering more control in the hands of admins. My first skins had about six subpages (zones), when the default skin had one. We developed a script which allowed css to be put into a wiki page, and this page was used as a standard css page, cached as well as wiki editable. Javascript never made it onto editable wiki pages in PmWiki because it is so dangerous. If you hack a css page, you can ruin the display of an entire site. If you hack a javascript page, you can ruin an entire computer system. It is not about a developer having an easy time and wanting to hide anything. Well, maybe there are good reasons for making some scripts not accessible for wiki editing. But as skin designer I do not wish to bloat the HTML page size unnecessary, simply for performance reasons. And having different css files for instance can enhance usability and help the admin. If one of Boltwire's aims is to make most files editable on the wiki, then one should concentrate and find good solutions to do just that. Simply to throw (embed, or what you may call it) the javascript and css code into HTML tags into each page is not the best answer, IMHO. I would like wiki editable css pages which are linked to the skin HTML by <link ...> tags. Same may perhaps be achievable for javascript files. In no way i am opposing ideas to make a website more customisable, and in easier ways. Best, ~Hans --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
