| | 6 | |
| | 7 | update: |
| | 8 | |
| | 9 | This is certainly not a duplicate of #8958 as such. |
| | 10 | |
| | 11 | In #8958, a preset writer X, say of defaultpresets.xml, notices that he is writing things multiple times and he first makes a library of which he can reuse the elements down to the deepest key, a combo in the example. |
| | 12 | |
| | 13 | In #9066, a plain user Y wants to ease his or anybody's life by bundling together for fast access the items or groups, no deeper, that are most used for a particular activity, say street survey, e.g. not the waterways, paths or motorways, but certainly all kinds of streets, Z crossings, traffic calming etc... He certainly does not want to ask writer X to establish a library before being able to do that. |
| | 14 | |
| | 15 | But if you want #9066 to go down to copy the deepest key level and override values too, then writer X will notice that he can use an extended |
| | 16 | URL/group-name.../[item-name[/key-name]] to address the elements from any element and hence that a library is not really needed. |
| | 17 | Note that if removing the library hurts, you can call a dummy <group name="library"... with the property to accept any tree of keys and addressed with the extended URL or a simplified form thereof. If you really want to create a new data type called <library> then it probably ought to have a name and the URL specification has to be extended beyond groups and items. |
| | 18 | |
| | 19 | In short, the two enhancements work differently to do two different things, but they can be merged to do both using a single method. |
| | 20 | |
| | 21 | Ask me to copy this text as an comment of #9066 if everybody prefers a merge. |
