Changes between Version 10 and Version 11 of Ticket #4421, comment 37


Ignore:
Timestamp:
2012-03-07T08:22:47+01:00 (13 years ago)
Author:
akks

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4421, comment 37

    v10 v11  
    55Though we can add scripting for more advanced preferences manipulation, if it is already available in JDK. I imagine how to start JS engine and pass objects to it, but have no idea what "API" it should use with complex functions like "parseMapXPath". I am not so familiar with JavaScript, XPath, etc. , so I can not implement it myself (or even write good scripts for it).
    66
    7 I also can not advice to make all code dependent on preferences.xml format (especially duplicate parsing code).
     7I also can not advice to make all code dependent on preferences.xml format (especially duplicate parsing code, though I like StAX too).
    88
    99Another problem - if all actions like asking user confirmations, deleting keys, etc. will be based on JS and XPATH '''only''', the code may be shorter and cleaner, but resulting config file will be unreadable and ununderstandable by non-programmers. We need to find good balance between "declarative syntax" (simple, but harder to extend) and "JS API" (universal, but harder to understand). And JS code is hard to mix with declarative XML syntax without even IDs of elements (we do not want another self-made JavaFX 1.0, I hope).