selecting each and every component in a list to save can be a lot of work, an option to select all of the different component from one file could save some work.
quote:
Not to belabor the point, but otherwise I don't see how a comparison between file 1 and 2 is somehow different than a comparison between 2 and 1. Same files, same differences. Now an alteration in HOW those differences are displayed, that makes sense. I just haven't seen it so far looking at the two comparison views of 3 different files
try deleting one component from one of the files, and then compare them, 1 to 2 and 2 to 1, there should be a difference in the result.
about editing :
it's easy to implement, right now i've turned off the ability to edit in the display area, i could easily turn this on, i would still have to write some code to save it all. But right now you could only edit all of the components if you compare a normal component.txt file with an empty component.txt file, cos for now, that is the simplest way to see all the component in a file. I think you would still have to have the begin and end tags in the file.
value specific comparing is a lot of work, not difficult, but just much work. I might add this this when there is nothing else to change.
quote:
Lemmy wrote:
It will be saved like a normal component.txt file, with begin and end, plus the header, but with a different extension. The user will have to choose where to save the file.
now that i think of it, a header like in a normal file is useless. Maybe just the info about what files where compared as a header.
------------------
Q: So the date of conception (of the baby) was August 8th?
A: Yes.
Q: And what were you doing at that time?