Oliver Zeigermann wrote:
Christophe Lombart wrote:
Oliver Zeigermann wrote:
LOMBART Christophe wrote:
This would involve having a list of all links to the links
pointing to this object, right? Otherwise you would have to
traverse *all* nodes to collect now invalid links, is this what
you are saying?
See on the ObjectNode, there is a vector "links" but no method
addLink (for children, there is a method addChild). If we have this
method addLink, it is quite easy to modify the ExtendedStore to fix
this bug. I can send you a patch if you want.
I am not quite sure how to proceede here. If this patch can fix
links for now, send it to the news group along with your other
patches. I will check them in for you. Although, the future
direction should be binding, shouldn't it?
Yes, maybe I have to replace my code with binding. I will make some
experience with binding methods.
Can we use now Binding or is it still on development ?
Maybe if binding replace links, it should be nice to set link related
methods as deprecated.
Well, certainy the stores will have to be adapted to support it. I was
on my way to do it, but decided pushing out a release as soon as
possible was more important. I suggested to postpone binding to 2.1 or
so, let's keep it like this and let us work with links for now. Ok?
Ok so I will send on this mailing list a small patch for the Extended
store and links.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
