Re: [xwiki-devs] [proposal] JS and CSS improvements

Hi, I read that posting. I have a doubt though, how would having a separate extension class would solve the purpose of faster loading of static content. Over the time I can add lot of css and js files to be loaded by these extension classes thus brining back to square 1. Alternately in current javascript.vm and stylesheets.vm I can have a conditional load by calling few needed files only based on xwiki action, thus making the page load faster. The problem is that the css and js code is very fragmented which makes it difficult to collect place the static content in say web server. Next many time css and js code needs to be parsed by velocity context to evaluate certain variables which in most case refer to the image url. We cannot put these dynamic files into web container and I believe loading such files (static but dynamic) also increases the page load time. Thus collecting all the js, css and images files and placing them into three separate pre determined directories would avoid use of velocity code inside the static content. This then can be moved to web server thus achieving the desired result. Also when the files are same type are grouped together, it is lot easy to manage and make further improvements on it. Thanks Sachin Sergiu Dumitriu-2 wrote: ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/-proposal--JS-and-CSS-improvements-tp12806140p1602158… Sent from the XWiki- Dev mailing list archive at Nabble.com.