Changes between Version 6 and Version 7 of Ticket #4421, comment 35
- Timestamp:
- 2012-03-06T12:49:32+01:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4421, comment 35
v6 v7 10 10 XPath is also not so well-known for writers of configuration files :). I cannot include support for advanced XML processing now, because XML-fragments with preferences are parsed by Preferences class and then all modifications are done for Java objects, not XML. Only some preprocessor can be called (like XSLT for whole preferences.xml or matching tags), but it can not help in complex cases. 11 11 12 So I tried to make a simple copy-paste-style language with limited number of commands (for partial import/export, not for scripting - I started from shortcut schemas), which I can document and support. 12 So I tried to make a simple copy-paste-style language with limited number of commands (for partial import/export, not for scripting - I started from shortcut schemas), which I can document and support. "<if>" and var were introduced only to ask "which style dou you prefer?" and similar questions. 13 13 14 14 I do not see real need for scripting to do simple preference modifications. If some project or plugin need advanced processing (like renaming, numbering, rearranging of layers), why they could not edit preferences manually from their plugin code? :)


