Hi Nathan, I forgot to mention that I've also added an issue that the editor variables should be resolved inside oxy_url CSS function (built-in and custom alike). Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 13-May-14 3:32 AM, Nathan wrote:
Hi Alex, Here is the use case scenario I am targeting:
In the CSS, I have
*[class~="topic/image"][href]{ content:oxy_url('${frameworkDir}', '../../../../../', 'app/main/core/sfdc/htdocs/img/', attr(href)); }
Here, the built-in variable "frameworkDir" works fine. The above path is valid when the file is in the "main" branch. When the input xml file is in another branch (say "/patch/21"), I would like to change the "app/main/core...." to "app/patch/21/core...". My first idea was to have a custom variable defined (say $BRANCH) which would be set to "/main" by default and could be reset to "/patch/21" by the user when they change the branch.
However, while the built-in variable was accepted, the custom variable is not accepted here. Also, with respect to creating pseudo classes, it would be a maintenance issue since I would need to put in every release number (since theoretically XML files from any release could be opened) in the CSS and also the CSS would need to be updated after every release.
Could you provide some alternatives?
Thanks, Nathan
_______________________________________________ oXygen-sdk mailing list oXygen-sdk@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk