>>> Subversion only knows a property status for *all*
>>> properties of an item. Sure, we could create our
>>> own status for this (modified, unchanged,
>>> added, deleted).
>> I imagine that would be valuable for people who
>> are working a lot with properties.
> Sounds good, but maybe a lot of work?
That's another matter. :-)
But if we agree that the principle is good, maybe an entry in the
issue-tracker would be a good way to start?
>>> * should we show deleted properties in that dialog?
> I think this is manageable. Maybe use the
> Added/Modified/Deleted icons in the new column.
> Deleted properties could be shown greyed and cannot
> be edited.
Ok. Using icons would probably make it a bit more visual. That the
property is "marked for deletion" and will be deleted on the next
commit. Maybe not that bad after all.
> If we (who's we? I mean Stefan) do this then maybe there
> should be a per-property revert for all of these too.
Yes. Definitely. Being able to show per-property differences is less
valuable if there's no way to roll those changes back on a per-property
level.
>> That could work: Having the check-for-modifications dialog with a
>> property list (including a property status column) below the file
list,
> That sounds more confusing to me. You can already access the standard
> property dialog from within check-for-modifications, and it seems
> Not-Too-Scary(TM) to add diff functionality to that.
Yes, but it's more clicks. I don't think it would be confusing or
disturbing there. But it's just a suggestion. Don't know if it's worth
the effort. I made a small mock-up in gimp to illustrate what I meant,
just for the sake of it. :-)
> But I think the property dialog should show only the current value and
> not attempt to show old and new in columns. As Stefan says, multi-line
> properties will not show up well, so using Tmerge sounds as good a way
> as any for diffing properties.
I agree completely.
> I am not too sure what happens if there are remote property changes.
We
> can diff remote file changes, so in theory we should do the same for
> props. In practice, does anyone really want to do this?
Good question. I don't know how difficult it would be to implement, but
regardless I don't think it makes my top-ten-new-dream-features-in-TSVN
by a long shot. But basically it does make sense to be able to...
Hans-Emil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Aug 4 09:21:07 2006