Changes between Initial Version and Version 1 of Ticket #4421, comment 30


Ignore:
Timestamp:
2012-03-05T08:39:29+01:00 (13 years ago)
Author:
akks

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4421, comment 30

    initial v1  
    44I thought about XSLT, but current format it rather simple and do not rely on preferences.xml format (all modifications are done by Java API calls). If it is '''really''' needed, I can add XSLT preprocessing step for <preference> tag body
    55(<preferences><xslt>...</xslt><fragment>...<fragment> </preferences>).
    6 
    76
    87>
    … …  
    2019
    2120> * Someone might want to delete files from cache. It should be expected, that cache folder is not a subdirectory of the normal josm pref directory. (E.g. on another disk, shared cache for multiple profiles, etc.).
    22 >
     21I agree, this should be possible. But should we allow to delete any folder by absolute path? If not, only 'basedir=prefs / basedir=cache / ... are possible.
     22 
    2323> * I'd prefer '''${x}''' instead of '''${{x}}'''.
     24I'd prefer too, but what about possible conflicts with URLs, messages and so on? Though if variable x is not defined, ${{x}} (or ${x}) will not be replaced.
     25
    2426>
    2527> * Maybe some kind of summary of the concrete changes in a final confirmation dialog.
    2628>
     29It would be good, but I really can not decide  what to put there (N keys modified, M keys deleted, P items deleted? Or their list? Or list and values (possibly very long)? Or show scrollable log? Or ask on deletion only?). Some action effect is only known when it is performed (asking user/if).
     30
     31This needs two pass analyzing reading in some cases but is realizable. We need to decide what we want to ask.
     32
    2733> * Change wording in the GUI: It seems as if after loading a xml file all my previous preferences might be dropped.
     34I agree - message should be changed.