Hi Wendell, The nice thing with the extension that Alex implemented is that you can specify also an XSLT script instead of a set of values in the configuration file and thus you can link oXygen to external data sources, all you need is to have the external data source accessible though an URL. You can get the information then with the document() function for example and process it to select what you need and put it in the format this extension expects. We plan to either put this on GitHub or we will include this functionality directly in oXygen for all frameworks - in the later case you will need just to add a configuration file in the framework to get this functionality. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 17/10/14 00:14, Oxygen XML Editor Support (Radu Coravu) wrote:
Hi Wendell,
So one option for this would indeed to use the oxy_xpath CSS function to gather values from some place and then use them in the form control. For example:
link:before{ content: "Managed by:" oxy_editor( type, combo, edit, "@manager", values, oxy_xpath('string-join(//@id , ",") '));
The oxy_xpath could also look in some external file using the document function and then combine all values with the "," character in order to set them as a parameter for the form control.
This approach might lead to performance problems though. So if you hit any performance problems:
We already have API to provide values for attributes and elements via an Java extension. My colleague Alex has been working on such an implementation which picks values from an XML configuration document. So if you contact us directly I could try to give you a JAR library and some instructions to set this up.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 10/16/2014 5:03 PM, Wendell Piez wrote:
Hi,
I think the forms-like editing in Author mode is fantastic. One thing I like being able to do is having a pull-down listing valid values for element or attribute contents.
One thing I have a need for -- to have the choice of valid values specified dynamically, in the document itself or close by.
I can specify a rule in Schematron that checks whether arbitrary (key) relations hold in a document (or across two or more documents), but I wonder how I can get oXygen to read the permissible values (however they are defined and constrained, for example as a set of attribute values in metadata) and pop them up in a picklist.
Essentially this is like an ID/IDREF requirement, only generalized, and specifiable using XPath.
Is there any hope for me? Could I sneak some kind of function into the CSS that oXygen uses to configure the pick lists, and achieve this, using XPath?
Regards, Wendell
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user