Hello all, I'm looking for a real tutorial (step by step or How to) for creating skins and template for XWiki ... I'm Looking for the Xwiki Documentation ... and it's not really understable ... Someone have some knoewledge about ? Thanx, Azz .. PS : If someone write a good Tutorial, I'll paid him/her beer in a wonderfull pub in Paris ... _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

Hi, I was also looking for such a tutorial without success. To acheive the goal in order to make my custom skin, I just tried to copy the toucan skin files to a new folder and modify classes (or add new ones for special cases) using Firebug to detect each block assigned class or id. The CSS architecture is very complex and very difficult to understand. Hope this will help. -- Hoani CROSS Globotraders Tahiti Founder [http://globotraders-tahiti.com] 2008/10/14 Azzedine Ait Khelifa <aaitkhelifa(a)yahoo.fr> _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

Vincent Massol wrote: I think we should first have a _much_ cleaner and modular skin. To be done once we have all the extension mechanisms in place. After that, a tutorial will be easy.

> On Oct 15, 2008, at 6:30 AM, Hoani Cross wrote: > >> Hi, >> >> I was also looking for such a tutorial without success. To acheive >> the goal >> in order to make my custom skin, I just tried to copy the toucan >> skin files >> to a new folder and modify classes (or add new ones for special >> cases) using >> Firebug to detect each block assigned class or id. The CSS >> architecture is >> very complex and very difficult to understand. Hope this will help. >> >> -- >> Hoani CROSS >> Globotraders Tahiti Founder [http://globotraders-tahiti.com] >> >> 2008/10/14 Azzedine Ait Khelifa <aaitkhelifa(a)yahoo.fr> >> >>> Hello all, >>> >>> I'm looking for a real tutorial (step by step or How to) for >>> creating skins >>> and template for XWiki ... I'm Looking for the Xwiki >>> Documentation ... and >>> it's not really understable ... >>> >>> Someone have some knoewledge about ? >>> >>> Thanx, >>> >>> Azz .. >>> >>> PS : If someone write a good Tutorial, I'll paid him/her beer in a >>> wonderfull pub in Paris ...

--- En date de : Ven 17.10.08, Sergiu Dumitriu <sergiu(a)xwiki.com> a écrit : De: Sergiu Dumitriu <sergiu(a)xwiki.com> Objet: Re: [xwiki-users] A Real tutorial for creating Skins and Template ... À: "XWiki Users" <users(a)xwiki.org> Date: Vendredi 17 Octobre 2008, 11h31 I think we should first have a _much_ cleaner and modular skin. To be done once we have all the extension mechanisms in place. After that, a tutorial will be easy. Great Idea but when can we have a "_much cleaner and modular skin" ? __________________________________________________ Do You Yahoo!? En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités http://mail.yahoo.fr Yahoo! Mail _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

On Tue, Mar 17, 2009 at 10:49 AM, Remi &lt;remi.pierrard(a)conseiltechno.com&gt;wrote;wrote: I don't know if it's worth understanding from scratch. What about "understanding" it from firebug, in firefox, on a working xwiki page. This includes changing the stylesheet live to make it look like you want it to. Once you've got some things working, figure out how to make your settings work as !override forms in a standalone CSS file. Then just go to Administrate Wiki->Presentation, andadd the following to "HTTP Meta Information": <link rel="stylesheet" href="$xwiki.getURL("Macros.MyStyleOverride","view","xpage=plain")" type="text/css" /> The above will override for the whole site. To be safe, I suggest trying out stylesheet override changes on a specific space where you can do experiments w/o messing up the site for everybody else. This is done by using Administrate Space->Presentation->"HTTP Meta Information" Once you've decided the location, create a stylesheet as a document called for example, Macros.MyStyleOverride /* place all overrides to default stylesheet here */ (suggest starting out with an empty Macros.MyStyleOverride then adding new styles individually, and shift-reloading to force all the stylesheets to reload on each test). Of course I haven't tried the above yet, other than for a different example that uses the same technique/hack but locally rather than globally... but I plan to do this some more soon. ......................... Date: Mon, 16 Mar 2009 18:04:07 -0700 Subject: generalizing Radeox RSS:FEED macro in Xwiki From: Niels Mayer &lt;nielsmayer(a)gmail.com&gt; To: XWiki Users &lt;users(a)xwiki.org&gt; (1) Create a stylesheet http://nielsmayer.com/xwiki/bin/view/Macros/styledRSS?xpage=plain Which is a document http://nielsmayer.com/xwiki/bin/view/Macros/styledRSS?viewer=code with following wikicode: > .rssfeed > {border:0px!important;padding:0px!important;width:100%!important;} > {/pre} (2) Refer to that stylesheet wherever you want/need the RSS:FEED macro to appear sized to the container displaying it, e.g. to make a "Panel" display feed contents: <link rel="stylesheet" The results: http://morgellonswiki.info/xwiki/bin/view/Panels/Twitter+Lyme http://morgellonswiki.info/xwiki/bin/view/Panels/Twitter+Morgellons http://morgellonswiki.info/xwiki/bin/view/Panels/Google+News+Lyme http://morgellonswiki.info/xwiki/bin/view/Panels/Google+News+Morgellons (3) You can change the way your feed presents in your XWiki user page, e.g. http://nielsmayer.com/xwiki/bin/view/XWiki/NielsMayer is done by placing the following in the "Description" field of the User document: <link rel="stylesheet" (4) Using the same stylesheet hack along with documented information on the radeox RSS macro ( http://code.xwiki.org/xwiki/bin/view/Macros/RssMacro ) one can assemble numerous feeds in one page, fully expanded, with space for images, etc: http://morgellonswiki.info/xwiki/bin/view/Main/FeedsOfInterest ..................................... Niels http://nielsmayer.com _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

On Wed, Mar 18, 2009 at 3:29 AM, Remi &lt;remi.pierrard(a)conseiltechno.com&gt;wrote;wrote: I think the difference between "my hack" suggestion and the one in http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Skins is that my approach is simpler, less prone to leaving you with an unreadable site if you make a mistake, and more immune to changes in the underlying skin as you upgrade XWiki versions. The problem with developing from scratch is that you have to develop from scratch... I prefer standing on the shoulders of giants, and if you take a look at the CSS involved in xwiki, you need to stand on the shoulders of giants... :-) But just like we don't go off creating new organisms from scratch, we modify existing one's DNA, the same goes for software. It also doesn't help that there's no formal way of defining, enforcing, or testing the semantics occurring between DOM/CSS and javascript and velocity... other than poking at it in different browsers and looking at how it behaves under the microscope of 'firebug.' Also, "my hack" can be done "interactively" by editing a xwiki document containing the css data, whereas the correct approach requires editing XWikiSkins in the class editor, or the installation of a skin either as files at the apache level (assuming you front your xwiki with httpd), or into the servlet container itself requiring a relaunch for each iteration of what is supposed to be rapid prototyping. "My hack" enables rapid prototyping, but is less efficient as it requires all the overhead of an extra xwiki document (the override css file) getting created or loaded from the cache for each page. There's no question that if you're building http://idiva.com or http://www.bestventes.com then "my hack" is not the way to go. However, it might be the way to make incremental changes to the existing CSS before rolling the changes back into the skin and pushing out a new release. One question is could the "overriding" approach suggested by "my hack" be integrated directly into Admin->Presentation by having an wiki-specific area in which CSS overrides reside. From there, some of the more common customizations (e.g. changing the header-image and dimensions, changing the background fill/color/pixmap, transparency on/off, etc) could be done in the web-GUI by a wiki-owner, rather than becoming a sysadmin task. FYI, here's the approach suggested in the documentation: To start, the best is to copy-paste the original content and make a slight Niels http://nielsmayer.com _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users