Re: [xwiki-devs] [DEMO] Class/Object management improvement

thanks ;) Don't worry, I wish I could document as well each time but often I can't spend the time to do so well :)... Generally, I spend my time trying to deliver a new version of a server for yesterday :)... Sometimes, I wonder whether documentation is not something like a ancient myth, a forgotten knowledge that our ancestors were mastering but that we have lost :) This time, as I'm beginning with XWiki, digging in a code which doesn't belong to me and doing some reverse engineering and then trying to involve my ideas into existing code, I wanted to document clearly for you and also for me. See below... regards Pascal On 4/17/08, Ludovic Dubost <ludovic(a)xwiki.org> wrote: I totally agree with you... I don't want end-users to be lost in objects and class versions... This is why we should foresee all the usecases and then make everything as easy as possible... But as we say in French:"qui peut le plus peut le moins"=Who can do the more can do the less... Are you speaking about saving the object or the class? Would the upgrade be proposed when you save the object or when you save the modified class ? I agree that adding a property is not a problem for automatic upgrade... you don't lose any existing info... the problem is for property deletion or update... But, in the case of automatic upgrade when saving the class, imagine the case you have a document containing lots of objects and you want to keep these objects as they are... But you add a property to the class and then all the objects are automatically upgraded... Is automatic upgrade good for this case? is adding a property only cosmetic? Woud it be better to control the upgrade from objects or from classes... In fact, I don't have a clear answer: both cases might be useful... Maybe, as you said, when you modify a class, we could propose to the user to upgrade all the objects in a row or maybe to choose which objects he wants to upgrade but if there are lots of objects???... or maybe to choose the documents in which he wants the objects to be upgraded? I wonder if a class/object manager module could not be interesting to provide clever tools... The target is now a problem of ergonomics :)