- oXygen-user - www.oxygenxml.com

Custom action to process a document and update an element?
by Eliot Kimber 02 Dec '13

02 Dec '13

For the DITA RelaxNG support that will be in DITA 1.3 I want to implement an action that can be applied to RNG document type shell grammars that looks at each referenced module, gets its domains attribute contribution (which will be in a specific subelement within the referenced module, and add it to the right place in the shell (a pattern named “domains-att”). This is of course easy to do with XSLT. My question: what’s the best way to set this up in Oxygen so that I can just do an “update domains attribute” action when editing a document type shell schema? Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

8 15

Re: [oXygen-user] scripted creation of MarkLogic data sources?
by Alex Jitianu 22 Nov '13

22 Nov '13

Hi Jakob, Please see my answers below. Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 21-Nov-13 3:34 PM, Jakob Fix wrote: > Hi Alex, > > thank you for your reply. You are right, I was talking about the > connections, not the data sources. > Also, I didn't think about the passwords, hmmm. > > I was actually thinking of generating the fragment for the options > file using XSLT as you suggested; using xmltask in ant we could > probably even insert or update it automatically. But how do I encrypt > the password though? It seems to be a sequence of integers, separated > by semicolons and dots... We encode the password dependent on the local machine so a password encrypted on your machine will not be decrypted on another machine. So you must leave the password field empty and the user will have to edit them and input the password. Another solution that comes to mind is to implement an WorkspaceAccess plugin extension. When the plugin starts it can overwrite the connections settings of the user (the Java API offers this option). With a little more work you could read the XML options file and merge the connections. For passwords you can present a dialog to the user. The plugin can be packed as an add-on so it will be very easy for the user to install it. If you want to go on this path I can offer more insight. It might involved more work then just using XSLT but might be easier for the user use it. Your call... > > Another question would be: when updating the options file would it be > a good thing that Oxygen is not running, because it might be saving > its in-memory options on shutting down? I think you are correct. Oxygen shouldn't be running when it's options are being altered. > > > cheers, > Jakob. > > > On Thu, Nov 14, 2013 at 10:04 AM, Alex Jitianu <alex_jitianu(a)sync.ro > <mailto:alex_jitianu@sync.ro>> wrote: > > Hi Jakob, > > Are you referring to Data Sources or Connections? A data source > contains the jar libraries while the connection contains the data > needed to connect to a specific MarkLogic AppServer. Assuming that > you have configured the MarkLogic related options once, what you > can do is share the Oxygen options file with all other users that > want the same level of access. > > The options file is named something like oxyOptionsSa15.0.xml and > depending on the platform the options folder is located as follows: > - Windows XP - [user-home-folder]\Application Data\com.oxygenxml > - Windows Vista/7 - [user-home-folder]\AppData\Roaming\com.oxygenxml > - Mac OS X - [user-home-folder]/Library/Preferences/com.oxygenxml > - Mac OS X - ~/Library/Preferences/com.oxygenxml > - Linux - [user-home-folder]/.com.oxygenxml > > One thing to bear in mind is that the passwords are encrypted so > they are not portable. All those that import the options file must > manually insert the passwords in the connections. > > Since the options file is an XML file you could also take a look > and see how a MarkLogic data source and connection are saved and > write an XQuery or XSLT to automatic add the connections so that > you skip the manual insertion entirely. > > Once you have an options file you can send them to all interested > and they can use Options->Import Global Options... Another > possible approach is to give them the options file as default > options: > http://oxygenxml.com/doc/ug-editor/#topics/default-options.html > > I'm also thinking about a possible Wizard that will let you select > the AppServers for which you want to create connections. But I > don't think this Wizard will be able to create Data Sources since > the jars are not on the server (it would involve downloading them > from the MarkLogic site). Do you find this kind of wizard to be > useful and if yes do you have any suggestions about what > interaction we should offer in this wizard? > > Best regards, > Alex > > > On 13-Nov-13 4:55 PM, Jakob Fix wrote: >> Hi, >> >> right now we're creating our MarkLogic data sources manually, >> using the UI. Is there a way to create them by modifying a >> configuration file, or an API to send setup requests to? >> >> We're having a quite a lot of these data sources, but creating >> them by hand gets cumbersome. And we really like the possibility >> to inspect the database's contents via WebDAV from within OxygenXML. >> >> cheers, >> Jakob. >> >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com <mailto:oXygen-user@oxygenxml.com> >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user > >

1 0

Feature request: Improvement of Japanese search for WebHelp
by Naoki Hirai 19 Nov '13

19 Nov '13

Hi, I like Oxygen WebHelp very much and recommend it to Japanese users. The WebHelp is sophisticated online manual solution, but one issue has still remained for Japanese users. That is a Japanese search. For Japanese it's difficult to extract words from sentences. Because the words are not separated by spaces. Therefore, in general, a morphological analyzer is used to extract the words from the sentences. Recently, an open source Japanese morphological analyzer which is called "Kuromoji" has become popular. The Apache Solr has introduced Kuromoji as the morphological analyzer. So, my feature request is that Oxygen WebHelp plug-in will incorporate Kuromoji as the morphological analyzer. And add a parameter which selects a stemmer for generating a WebHelp output. I can help the development and the evaluation. Please have a thought. Best regards, Naoki

2 1

scripted creation of MarkLogic data sources?
by Jakob Fix 14 Nov '13

14 Nov '13

Hi, right now we're creating our MarkLogic data sources manually, using the UI. Is there a way to create them by modifying a configuration file, or an API to send setup requests to? We're having a quite a lot of these data sources, but creating them by hand gets cumbersome. And we really like the possibility to inspect the database's contents via WebDAV from within OxygenXML. cheers, Jakob.

2 1

ftp?
by Reaves, Timothy 12 Nov '13

12 Nov '13

Is there an ftp site for downloading maintenance builds?

2 1

Multiple but independent inline editors
by Felix Sasaki 12 Nov '13

12 Nov '13

Hi all, another newbie question I assume. I want to add a set of inline editors. With a dedicated CSS style and given <span its:translate="no">... an editor for editing the "translate" attribute, a combo box editor should be available for editing the attribute. The issue is that there are many of such attributes, e.g. <span its:translate="no" its:locNote="..." its:storageSize="..." its:term="..."> ... First I thought of creating a combobox for each of these. But CSS selectors don't allow you to match several rules at once. So if I have *[its|translate]:before { combobox def here } and later in the stylesheet *[its|term]:before { combobox def here } an element like above that contains both attributes will only show the combox for "its:term". I can write *[its|translate][its|term]:before { combobox def here } but this will show comboxes for all attributes even if they are not present. I tried a workaround: defining CSS rules for all potential combinations, that is: only translate, only term, both translate+term, ... but since there are a lot of attributes to consider, the CSS stylesheet looks really bad. Maybe there is a workaround that does not rely on CSS selectors? Thanks, Felix

2 3

[Ann] New maintenance build available for oXygen 15.1 (2013110816)
by Oxygen XML Editor Support 12 Nov '13

12 Nov '13

Dear oXygen users, We announce the release of a new maintenance build (2013110816) for oXygen 15.1 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2013110816 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

Removing or adding two attributes at the same time
by Felix Sasaki 11 Nov '13

11 Nov '13

Hi all, For an oXygen framework (DocBook), I would like to exectue an operation that removes or adds two attributes at the same time after the user has clicked on a button. The use case is that in my DocBook customization these attributes need to appear at the same time. Adding or removing just one of them would make the file invalid, and having two buttons is not an option, because there are many such combined attributes, the GUI would get too full. The ChangeAttributeOperation at http://www.oxygenxml.com/doc/ug-oxygen/index.html#topics/dg-default-author-… didn't work for me since I cannot have two of these operations associated with one button. Looking at http://www.oxygenxml.com/doc/ug-oxygen/index.html#topics/the-action-dialog.… it seems not possible to trigger two operations via one action: "An action has one or mode operation modes. The evaluation of an XPath expression activates an operation mode. The first enabled operation mode is activated when you trigger the action." I also tried to evoke an XSLT transformation via XSLTOperation that removes the attributes. But although the "script" value IMO opinion points to the right location of the XSLT and that XSLT file is valid, I get an error from evoking the action, saying: "Couldn't exectute operation ro.sync.ecss.extensions.commons.operations.TransformOperation because ... cannot create Transformer: failed to compile stylesheet." Any ideas how to move forward? If the XSLTOperation is the way to go: is there an example in an existing framework that demonstrates how the operation is used? Thanks, Felix

4 4

Chapter Numbering feature request
by KAATMAN Matthew 11 Nov '13

11 Nov '13

One feature that would be nice would be an option to turn on the numbering for the chapters in the Dita maps manager. This would be especially useful for managing translated content since I generally can't read the chapter titles. Each time I have to count them from the top to find the one I am looking for. Bonus points if a second option to skip counting chapters marked as toc="no"! (Please excuse my poor photoshop skills) http://i.imgur.com/YKku1tP.png AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 1

Displaying empty elements (or not)
by Wendell Piez 07 Nov '13

07 Nov '13

Hi folks, oXygen supports the CSS3 selector :empty, so (for example) we can hide an element that has no content styled, in the Author View, for "preview", while showing it in an editing style. This is useful when, for example, editing documents whose schemas require elements in places where the user has no content for them. So if we have <sect><head/><p>Headless section</p></sect> we don't have to see anything where the empty 'head' element is, at least when oXygen Author is set to "No Tags". Unfortunately, however, since CSS isn't XPath, there's no way to suppress the 'sect' element, when we have <sect><head/></sect> (We can make the 'head' disappear but then we see a placeholder for the 'sect'.) I know the correct solution is not to deploy schemas that require elements that are not always used. But I wonder if anyone has a CSS workaround or an oXygen extension to suggest so that my oXygen XML Author preview can show something more like what the document will look like when it is formatted and the offending elements are dropped. Any ideas? Thanks, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

2 2