Re: [Tigervnc-devel] Migration to Allura

2013-02-07 Thread DRC
This is a roll-up of the relevant Allura code viewer features/fixes that I believe are necessary for SF to address in order to provide an environment as usable as ViewVC. If you have a SF account, please consider voting these up so we can get SourceForge's attention. Whenever a user clicks on

Re: [Tigervnc-devel] Migration to Allura

2012-11-27 Thread DRC
On a side note, if anyone knows of a Subversion thick client that has as rich a feature set as this, I'd like to know about it. I am not aware of one that allows you to view a history of a file or a tree in the way that ViewVC does. I really wish SourceForge would just keep ViewVC as an

Re: [Tigervnc-devel] Migration to Allura

2012-11-27 Thread Robert Goley
The closest comparable feature set I have worked with is the WebSVN tool which is similar to ViewVC. I need to find out if or how it can be used on remote repositories though. Might be a hassle to have to setup another web service/site for it but it would be better than

Re: [Tigervnc-devel] Migration to Allura

2012-11-27 Thread Robert Goley
Your requirements may not be the same as mine. I have to deal with several OS installations with some in a multiboot environment. I never found a good cross platform SVN tool that had all of the features I wanted. I haven't tested WebSVN in a none local configuration yet

Re: [Tigervnc-devel] Migration to Allura

2012-11-26 Thread DRC
I added a brief list of critical features that I think are missing from the new SVN viewer on this bug report: https://sourceforge.net/p/forge/site-support/480/ Since posting this, they have fixed (2) [apparently a bug] and addressed (4) with the new Browse Commits feature. However, the

[Tigervnc-devel] Migration to Allura

2012-11-21 Thread Peter Åstrand
Hi. As you perhaps know, Sourceforge is introducing a new platform called Allura. Old projects can quite easily migrate. There are several advantages of doing so: * SF want projects to migrate, and they are not working on the old framework any longer. Support cases are often closed with

Re: [Tigervnc-devel] Migration to Allura

2012-11-21 Thread DRC
My main issue with the new platform at the moment is that they've replaced the repository browser. Instead of ViewVC, it's now their own version that, frankly, sucks. There are a lot of beta users, including me, complaining about this. I am hoping they address that issue or provide a ViewVC

Re: [Tigervnc-devel] Migration to Allura

2012-11-21 Thread Peter Åstrand
Oh, thanks for pointing this out. Can you describe more in detail what features are missing? Have you reported this to https://sourceforge.net/p/forge/site-support/ ? Rgds, Peter On Wed, 21 Nov 2012, DRC wrote: My main issue with the new platform at the moment is that they've replaced the