10 Feb
2008
10 Feb
'08
7:03 p.m.
Hi Sachin,
You're free to do whatever you want of course but please don't ask for
support later on because some xwiki skin you'll want to use doesn't
work for you :) (it won't work but that'll be normal since it'll rely
on files in the templates dir).
You're touching here at XWiki core structure and it's not never a good
thing to change that unless you completely understand what it means.
In the same way you can delete lots of jar files in the WEB-INF/lib
dir but if you do you'll find one day that when you use such and such
plugin it doesn't work.
Thanks
-Vincent
On Feb 10, 2008, at 6:46 PM, Sachin Mittal wrote:
Hi,
I have created a new skin and for all the user actions the vm files,
css and
javascript code is picked up from that skin only.
Thus others are not required. And as per the quote below the files in
template directory are picked up only if vm files are not found in
skin
directory, this won't be the case for us because the vm file should
exist in
the skin directory.
Thus for the custom deployment of xwiki I was streamlining the xwiki
code we
are using and deleting redundant code.
Also based on your comments below, second thing I can do is, keep
all the vm
code under template directory only and have the css, js, images and
other
static resources under the skin directoy.
I feel second approach would be better one.
Thanks
Sachin
vmassol wrote:
>
>
>
> The template files are used when the vm file required cannot be found
> in the skin. The role of templates is to have common vm files located
> in one place and not copied in all skins. Right now this is a bit
> of a
> mess but in the very near future we'll move the Albatross templates
> into the templates directory and remove all vm files in the albatross
> skin so that a skin will consist of only images, css and possibly
> some
> Javascript.
>
> I'd be interested to know what you're working on.
>
> Maybe we can work together to better support your use cases, etc.
>
> thanks
> -Vincent