It feels/looks like a user-friendly label that I can rename at will. For me the problem is that the Framework name does not feel like an important identifier. Perhaps Oxygen could warn you about the connection between profile set names and the framework name when you attempt to rename a framework. Having profile sets that exist as part of the framework as well as project-level makes sense-that's true for validation and transformation scenarios, but you still have the problem of binding user-defined profile sets to a given framework and framework extensions.įor now I'll do a hotfix to rename my framework to something that matches the pattern. Track Changes (Review) Author Name 15.15.4.6: Change the DOCTYPE of an Opened XML Document.
Oxygen xml editor change project name install#
Because the pattern is stored in the users preferences inside ~/Library/Preferences/com.oxygenxml/oxyOptions*.xml, I have no way to change them short of creating an add-on that manipulates their preferences and has them install it. 4.4.3: Associating a File Extension with Oxygen XML Editor. When I changed the framework name, all of the existing profile sets became unavailable because the pattern no longer matched.
Users apparently built on those, keeping the existing pattern of "DocBook*". In our case, the framework originally had a name like "DocBook - Extension Whatever", so the default profile sets were in play when our extension was used.
Yes, I understand how the mechanism works. We have not yet implemented this but it would probably also help in your case. So once you extend the "Docbook" framework you could set up profiling attribute names and condition sets and save those settings directly at framework level, allowing you to impose those profiling settings to all those using that particular framework. We've had requests in the past to allow for an entire profiling configuration (profiling attribute definitions, defined profiling condition sets) to be saved inside a framework configuration. So if the patterns used in those tables are something like "*DocBook*" you can name your framework extension something like "My Docbook Framework" and it still be matches.Ībout having an ID manually set by the end user (or automatically set by the application) for each framework, once you extend a framework you would need to have a different ID anyway so it would be the same problem as matching on the framework name. If you look in the Oxygen Preferences->"Editor / Edit Modes / Author / Profiling/Conditional Text" page, each table there has a "Document Type" column where you can set a pattern which matches one or more document type names.