How many times have you copied something from point A to point B within a document, only to realize you messed up something in point A, and have to fix both A and B?
Personally, I’ve done that lots of times. It’s annoying. If I did that, I’d much rather fix A and let my editor detect the fix, and propagate it to B. It’s the sort of optional feature that would make an editor into a killer app, I think.
Having not yet done any formal research into how others have approached this, I decided to start writing up a spec on how I would do it for a XML editor such as Verbosio. I know I am extremely stubborn and want to try to figure this out – so I’m posting now (before I waste too much time) to see if anyone else has looked into this, and hopefully, written up specs for this before.
In short, I’m starting to design two specs. One for storing metadata about a document that XML editors can commonly use, and one for recording copy/paste histories in that metadata, in order to propagate fixes from early content to later similar content.
Please, someone stop me with some great ideas others have already written about! Otherwise, I will post a blog article later describing the start to a new approach.
UPDATE: Wow, this is hard. I had an idea I was starting to formulate, but then I started trying to simulate it…