show svn:externals as links

TortoiseSVN 1.7.x shows externals in its repository browser. Could SmartSVN be enhanced to show the svn:externals as folders with links (or similar)?    Thanks,    - Mark

Last updated 10 years ago

I second that. I'd like to see that, too. :-)

Fredonia;122586I am always investigating online for tips that can benefit me.

 Ah, the first spammer (see his signature) -> Forum admins: You should harden your logins... (and feel free to delete this post).

M4rtin;122611Ah, the first spammer (see his signature) -> Forum admins: You should harden your logins... (and feel free to delete this post).

   First? There's at least 2-3 a day here.

Yeah, it's annoying, and we're working on it. We try to delete the posts asap. If you spot one we haven't you can report as spam.

I'd vote against this feature or at least make it optional. We have a slow access to our SVN server and would not like to have slowed it down even further by reading the properties of each opened directory.

We've got this suggestion raised (SU-4329). I've added the request to make this an optional feature (there seems to be a lot of criticism about the slowness of TortoiseSVN repo browser and we certainly wouldn't want to make this worse in SmartSVN).

Mand;122847We've got this suggestion raised (SU-4329). I've added the request to make this an optional feature (there seems to be a lot of criticism about the slowness of TortoiseSVN repo browser and we certainly wouldn't want to make this worse in SmartSVN).

  +1 on the feature request being implemented intelligently. -1 on it being an option  Honestly, I don't see why this should slow down repo-browsing. If you click on a directory, than you're already doing at least an "svn ls" on that dir, and adding an "svn propget" on that dir shouldn't be that big of a deal (I realize that's not exactly how it's implemented, but I'm sure it's equivalent). There's no need to expand a linked-in external until the user asks for it by expanding it.  I guess the performance problem people are imagining are the fetching of details from the actual external. I would defer the loading of those (revision, size, mod time, etc.) until the entry is actually clicked on or expanded. You could even put an ellipsis ("...") or a "load" button in those data fields to indicate that they arent' loaded and can be clicked to be loaded.