Yes.. we need this to be able to also create valid XHTML since CSS is not allowed in content anyway. MergeCSS does not work well though. We had to roll it back when we have been using it. Ludovic

Well I think this has to be done in steps 1. Remove all the unused js code from the albatross skin like under scriptaculous and also the multiple prototype.js 2. In the javascript.vm and stylesheets.vm conditionally load css and js files based on the action. 3. For better maintainability keep all js under one folder and all css under other and images in other. 4. I am be wrong but doing step 3 would enable someone to put all the static content under a web server say apache and use app server say tomcat to serve only the dynamic content by bridging the two, which in turn would prove to be a good solution for a scalable enterprise deployment. 5. Merge all the css under one or lot fewer files. 6. Also check that style.css under toucan skin is 57 kb large, so the css size should be reduced in the merged css file(s) Thanks Sachin Ludovic Dubost-2 wrote: > > Yes.. we need this to be able to also create valid XHTML since CSS is > not allowed in content anyway. > MergeCSS does not work well though. We had to roll it back when we have > been using it. > > Ludovic > >> Ludovic Dubost wrote: >> >>> Currently the albatross skin loads around 10 js and 10 css, which is >>> quite a lot. >>> We can improve loading time by: >>> >>> - compression and cache (raffaello will provide Apache configs specific >>> to XWiki to help for that) >>> - merging and optimizations of css/js (I've published >>> http://www.xwiki.org/xwiki/bin/view/Code/MergeCSS to help on that) >>> - removing unused css/js (now we need to find which one are unused) >>> - conditional loading of css and js. >>> >>> This last improvement can help us a lot since some of the css/js are not >>> even used in view mode, or are only used by a specific panel. >>> For this my proposal is to add a feature to the core to allow >>> conditional loading of CSS and JS files. >>> The current macros in the header would instead of putting CSS and JS add >>> a placeholder for additional CSS and JS. >>> Then everywhere where we need these CSS/JS (in a panel, in a wiki page, >>> in a template) we would call a macro #includecss or #includejs >>> This macro would add in the context the CSS and JS to add. >>> At the end of the template rendering the placeholder would be replaced >>> by the added CSS and JS. >>> The page would be served. >>> >>> This would allow to manage the way CSS and JS are added. >>> >>> WDYT ? >>> >>> Ludovic >>> >>>

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: > You should read http://dev.xwiki.org/xwiki/bin/view/Design/SkinExtensions > >