Changes between Version 4 and Version 5 of Ticket #4421, comment 37


Ignore:
Timestamp:
2012-03-06T20:03:41+01:00 (15 years ago)
Author:
akks

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4421, comment 37

    v4 v5  
    11I am not going to rewrite the whole thing from scratch, it is not '''that''' bad (you can do it if needed) :)
     2I used xml formats like '''ant''' build.xml.
    23
    34Though we can add scripting for 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).
    … …  
    56I also do not want to make all code dependent on preferences.xml format (especially duplicate parsing code).
    67
    7 Another 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).
     8Another 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 eved IDs of elements (we do not want another self-made JavaFX 1.0, I hope).