>
> TSVN can't interfere with how Subversion handles properties. We can only
> add features to them, but not interfere with them (e.g. during update to
> automatically merge them).
>
Or detect that there was a conflict on this "comment property" and
then do somekind of special resolve procedure (eg. inform the user
about it). But this begins to become more far fetched than realistic
to be implemented.
> > Maybe I didn't express my idea clearly enough. I visioned that at
> > first phase, there would be
> > a new tool (having an UI more or less similar to TortoiseMerge) which
> > shows the comments on the source code (or image). At later phase, we
>
> How?
> Most users have their own editor to edit the files. How would TSVN know
> when one of the files is opened with another application and pop up the
> 'comment window'?
> And if we provide our own file-viewer together with the comments, that's
> not very helpful because users want the tools they're used to.
Yeah that is true. But if we had a context menu entry something like
"read comments / write comments" which would open up the special
comment viewer, it could be done. At that point it is just a matter of
showing that the comments have been added or deleted when doing an
update. The user could then read the comments if he wanted. There
could even a special button "read comments" on the update if the
comments were added/updated. Maybe in the later phase, the editor
tools would support it directly.
But anyway, it is just a thought and maybe it doesn't suit well Tortoise.
Maybe I'll try the idea by myself when I start my next Yet Another
Text Editor For Fun-project ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 16 20:15:24 2006