Changes between Version 8 and Version 9 of Ticket #4421, comment 37


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

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4421, comment 37

    v8 v9  
    77I also do not want to make all code dependent on preferences.xml format (especially duplicate parsing code).
    88
    9 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). 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).
     9Another 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).