the server might be down sometimes (generally during the night) so don't be surprised if it doesn't answer. Right now it works until tonight (French time) Pascal On Sat, Jul 12, 2008 at 12:30 AM, <guillaume(a)xwiki.com> wrote:

Hello, nice to see that somebody is interested in this :) In fact, I really have been pragmatic and I have answered to the issues I've encountered while working with XWiki with simple means... Good idea about the "many" properties... I haven't tested that but I will think about it! did you see the object editor which has also changed? br Pascal On Mon, Jul 14, 2008 at 8:11 PM, Guillaume Lerouge <guillaume(a)xwiki.com> wrote:

Hello again On Mon, Jul 14, 2008 at 10:34 PM, Ludovic Dubost <ludovic(a)xwiki.org> wrote: thanks :) I'm happy because I haven't chosen this topic by chance: I found it could be useful and I needed it. I'm going to think about this asap... I agree that it might be disturbing... How could it be explained better? (I have added some title attributes so, if you keep the mouse on buttons, you should see some raw explanation popups) In the object editor, I made a difference between the "single property deletion" and the synchronization (object level or class level)... synchronization involves a more global and automatic mechanism of comparison and update of the object according to the class state... This might be disturbing... I'm not sure about this choice... For deprecated properties, synchronization is simple: you remove a property from the class then you want to delete deprecated properties from the object because these properties don't mean anything with respect to the current class state. So you synchronize the object with the class... For disabled properties, I think that, when you begin to create a class, you will add a property, and then one more and etc... Then you will create objects and give values to the properties... And then, you discover one property is no more useful, so you disable it. But you are not sure so you prefer keeping the valued property in the object... Later you may synchronize the object with the class in order to optimize the DB while keeping the property as disabled... I think this might happen quite often... But we could propose the synchronization only when it is possible... when there is a disabled or deprecated property... Not exactly... it won't be added until you edit the objects... If you add a new property to the object, it is automatically added to the object by the object editor with the default value (by the way, I have seen a strange behaviour with the "static list" type and I will take a look at it). Do you think the property should be added automatically to all the objects of the class in all documents as soon as the property is added? Concerning disabled properties, they are not added in any case. But when they are valued in the object, you can continue to change the value... Concerning deprecated properties, you can't even change the value in the objects. I'm not a CSS expert so I do what I can with my little fingers ;) (I haven't added any other JS lib) The changes to the UI could be improved but I think it's already "usable and practical"... The code is really simple. I will try to publish a patch on my site but I have been working on a XWiki-1.5-SNAPSHOT and I have seen that lots of things are being modified due to the new modular architecture... On what version should I work? I'm going to study a bit on your test architecture to see if I can develop some tests (this week I will work a bit but next week I'm on holidays) regards Pascal