2014-09-03 2:39 GMT+02:00 Alexander Klimetschek <aklim...@adobe.com>:
> On 30.08.2014, at 08:19, Carsten Ziegeler <cziege...@apache.org> wrote: > > > If you > > don't provide CRUD writing the UI is much harder and requires knowlege of > > the merging algorithm > > For UIs that try to completely hide the merging fact from the user, yes. > But I don't know how many of those you really need. > > Well, I see the need for a lot of them.... > And in your case there is actually no automatic selection: your UI would > simply always write to /apps (i.e. the first element in your search path). > AFAIU, the UI is geared towards end-users who will only change the most > specific configuration (as opposed to "default" configurations done by a > project implementation or default settings part of the original > product/sling). > > While it's true that all changes go to /apps in my case, the ui logic needs to decide whether to remove a node in apps, whether to create/update the node in apps and whether to add the special hide property. it's not that trivial - a simple post to /apps does not work. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
