Hello Ricardo, Yes, you can use velocity code inside SSX and JSX objects. What you need to do is to set the 'Parse content' property to 'Yes'. You can take a look at the SSX documentation: http://code.xwiki.org/xwiki/bin/view/Plugins/SkinExtensionsPlugin#HTip:Howt… . Example of usage: #if(!$hasEdit) #body{ background-color: red; } #end Raluca. On Mon, Nov 15, 2010 at 12:36 AM, Ricardo Rodriguez [eBioTIC.] <ricardo.rodriguez(a)ebiotic.net> wrote:

On 11/15/2010 01:15 PM, Ricardo Rodriguez [eBioTIC.] wrote: These variables are defined in xwikivars.vm, which is parsed when rendering a document with the surrounding UI. You can either use the API code that was used to set those variables, or you can add this line at the top: #template('xwikivars.vm') -- Sergiu Dumitriu http://purl.org/net/sergiu/

Hi, On Mon, Nov 15, 2010 at 3:05 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: You are right, Sergiu. Another solution would be to use different ssx objects from different documents (supposing that the SSX are being used on demand). For example: * Space1.Page1 having an SSX object - for common styles * Space2.Page2 having another SSX object - for users that have edit rights In the velocity code (a template or a page in wiki mode), you can do this: $xwiki.ssx.use('Space1.Page1')## common styles #if($hasEdit) $xwiki.ssx.use('Space2.Page2')## styles for users that have edit rights #end Raluca.

Sergiu Dumitriu wrote: Thanks, Sergiu. I clearly keeps failing at getting a clear general idea about how XWiki produces the output of a document. Time ago I started to create a kind of "flowchart" showing the relationships among templates, templates and actions and actions. Please, could you tell me if this is an good actual starting point to understanding this process? http://dev.xwiki.org/xwiki/bin/view/Design/FrontEndArchitecture Thanks! -- Ricardo Rodríguez CTO eBioTIC. Life Sciences, Data Modeling and Information Management Systems

Sergiu Dumitriu wrote: I adopted this solution here sacrificing performance as I need the described behaviour (Annotation shown only for registered users). But I still get see some weird thing I've not been able to consistently reproduce yet. I'm using a XE/XEM 2.4.30451 in production and a XE 2.7-SNAPSHOT.32908 as trial environment. I'll keep this thread updated or open new ones as required when I gather more information! An example: Working with a virtual wiki. I've modified AnnotationCode.Style (XWiki.StyleSheetExtension) this way... ## Defining global variables; added by Ricardo Rodriguez on November the 15th to apply conditional rules to CSS #template('xwikivars.vm') /* Menu */ .actionmenu #tmAnnotations { background-image: #imgURL('note') !important; /* Padding, margin and bg-position are adjusted in order to give this element the 'tab' look when active and the settings panel is displayed */ background-position: 0 1px; padding-right: 5px !important; padding-top: 0 !important; padding-bottom: 4px; margin-right: 5px !important; margin-top: 2px !important; #if($isGuest)visibility:hidden;#end } .actionmenu #tmAnnotations a { padding-top: 0 !important; } .actionmenu .active { background-color: $theme.pageContentBackgroundColor; ##$theme.backgroundSecondaryColor; } .actionmenu .active a { color: $theme.menuSelectedEntryLinkColor !important; } I never see "Annotations" in the right side of the action bar when browsing the site as Guest. When I log in, Annotations appears. And it persists consistently throughout the site for all spaces but those set as exceptions in the Annotations configuration panel. BUT, if I reload a page, any page, Annotations disappears. I cleaned the cache, restarted the browser, restarted the computer,... Nothing. By reloading the page several times, it ends appearing again. But I'm not able to find a pattern. ONE "FUNNY" THING: if Firebug Console is on, the reload is OK. Annotations persists. Those are the errors logged by Firebug: ***** xpected end of value but found ':'. Error in parsing value for 'text-transform'. Declaration dropped. [Break on this error] .actionmenu #tmAnnotations{background-...ontent blockquote{margin-bottom:10px;} Style?language=en (line 1) Unknown property 'border-radius'. Declaration dropped. [Break on this error] border-radius: 1.2em; colibri.css (line 205) Unknown property 'border-radius'. Declaration dropped. [Break on this error] border-radius: 1.2em; ***** XE 2.7-SNAPSHOT.32908 doesn't show this behaviour. Please, any idea? I don't know if this relates with any know issue or it relates with any error on my side. Any idea will be welcome! Thanks! -- Ricardo Rodríguez CTO eBioTIC. Life Sciences, Data Modeling and Information Management Systems

Marius Dumitru Florea wrote: I tried but failed to do that. I think I get the point. Even though I'm not able to understand this script now or how to tweak it, I understand that this option blocks the loading process of the annotation feature. It is "cheaper" to do that as it stops a process not required for a given type of users. But, please, one more question. When is this script executed? Each time a document is loaded or even reloaded? Thanks! -- Ricardo Rodríguez CTO eBioTIC. Life Sciences, Data Modeling and Information Management Systems

On 11/16/2010 12:06 AM, Ricardo Rodriguez [eBioTIC.] wrote: A document can have as many ssx or jsx object as it needs, but a skin extension is identified by the name of the document, so in the end an extension is a document. The content of a skin extension is the concatenation of the objects in that document, so it's impossible to write two different extensions in a single document, only different parts of the same extension. -- Sergiu Dumitriu http://purl.org/net/sergiu/

Sergiu Dumitriu wrote: I would like to add this paragraph to... http://platform.xwiki.org/xwiki/bin/view/DevGuide/SkinExtensionsTutorial#HM… ...as an {{info}} block. Do you agree? Thanks! -- Ricardo Rodríguez CTO eBioTIC. Life Sciences, Data Modeling and Information Management Systems

On 11/17/2010 09:24 AM, Ricardo Rodriguez [eBioTIC.] wrote: Exactly. To avoid (re)evaluating/recomputing the edit right multiple times (it may be costly). The value returned by $xwiki.hasAccessLevel('edit') is cached in $hasEdit to speed up the page loading time. $hasEdit (velocity, server-side) is also send to the client side in the value of the "hasEdit" property of XWiki JavaScript object. Hope this helps, Marius

On 11/16/2010 02:05 PM, Ricardo Rodriguez [eBioTIC.] wrote: Sure, go ahead. -- Sergiu Dumitriu http://purl.org/net/sergiu/