Hello Andre, Sorry for not responding for a long time. Employed diffing algorithm is capable of identifying added and removed XML nodes and nodes text. As for renaming nodes: If you have a <p1>sample text</p1> in one version and <p2>sample text</p2> in the same place in the other version for an XML view it will be treated like deleted "<p1>" tag and added "<p2>", while in the HTML view it will be highlighted as changed content "sample text". Moved nodes identification is not currently supported but I believe could be implemented due to XML model which is capable of identifying nodes order.
While preparing diff the module is putting style attributes according to identified changes directly in an output XML, so you just get an gui representation of diff as you see it in browser. Not really wise in terms of architecture and reusability, but it does it's job. If you want this changes to be somehow collected and presented in a universal format, like unified format or edit script, I don't see any architectural objections or other reasons why this functionality cannot be implemented I'm not really sure of reasons why you experienced such an error. The module worked well on at least to different environments - mine and Richard's. Need to take a look at the code once again. As for XMLUnit - it is not really a tree diffing algorithm as I understand from the first look at it. 2009/12/18 Richard Frovarp <[email protected]> > Florent André wrote: > >> Thanks Richard, >> I understand the licence constraint and it's clearly a good think that >> sucj >> a lib will be into trunk. >> "Problems" I have with this lib is that I don't find docs on witch kind of >> diff do daisyDiff. Clearly it's work on text() modification, but my main >> requirement is : >> I have to distinguish new nodes and nodes that have move (from position 2 >> to 5 for example - idea of the xmlunit's similar function). >> >> Have you informations about that ? If no, I will go to dress my swimsuit >> and dive into daisyDiff lib ! :) >> >> Tchuss >> ++ >> >> > I don't have any information. If XMLUnit fits your needs, and you aren't > looking to contribute the module to the project, then use XMLUnit. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
