Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#480 SVN code viewer (web)

assigned
Chris Tsai
https://sourceforge.net/p/blacknova/code/2463/tree/
https://sourceforge.net/projects/blacknova/
2013-01-07
2012-09-09
The Kabal
No

Hello! On one of the projects that I contribute to ( https://sourceforge.net/projects/blacknova/ ), we recently were upgraded to the 'new' subversion code view. (What is the name for the old and new viewer, other than old/new?)

By which I mean, when you go to the project page, and choose "Code" it directs you to https://sourceforge.net/p/blacknova/code/2463/tree/ . The old system ( http://blacknova.svn.sourceforge.net/viewvc/blacknova/branches/ ), is still accessible, and has several advantages over the 'new' code view.

Specifically, the old code viewer lets you sort by date so you can quickly look through the latest changes. It also lets you have a side-by-side diff view, instead of a above-below diff view. I use both of those daily, and don't see a suitable replacement in the new code viewer.

Will the old code view remain available? If so, is it possible for us to have the "Code" button link to that instead of the new view? And finally, is there a chance that the 'new' code viewer will add these features (and if so, when)?

If you'd like me to open a feature request ticket for the new code viewer, I'm happy to do so if that will help move things along.

Discussion

  • The Kabal
    The Kabal
    2012-09-09

    I should also mention that the classic viewer seems to have a more obvious way of selecting diffs to compare against (inside a single file), and the new system seems to want for a revision to only display as multiple files (if multiple files were affected during that revision).

    These are really deeply annoying differences, it feels like the 'new' system is several steps backward in usability - although it is "prettier" in some subjective sense.

     
  • Yura
    Yura
    2012-09-10

    i am having the same problems

     
  • Chris Tsai
    Chris Tsai
    2012-09-11

    • labels: --> engr, nf-4903, forge, p3
    • status: unread --> assigned
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2012-09-11

    Thank you for the feedback, I think sort by date is certainly a "no brainer" type addition. As such, I'm escalating this to our engineering team here: [allura:tickets:#4903]

    As for the side-by-side diff vs. above-below, seems to me that's in large part an aesthetic choice, and there may not be a clear consensus over which folks prefer. So for this, I think this would be best logged as a feature request. I've recently set up a new feature requests tracker, that this should go in. And don't forget to vote up your idea once you've logged it.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2012-09-13

    Also FYI, we now have a ticket for diff improvements here: [allura:tickets:#4929]

     
  • Dave Brondsema
    Dave Brondsema
    2012-10-01

    Is the "History" view, e.g. https://sourceforge.net/p/blacknova/code/2566/log/ sufficient for viewing latest activity? Or are you requesting to be able to sort the file/folder view also?

     
  • The Kabal
    The Kabal
    2012-10-01

    The History view is good for viewing latest revision activity, but not for seeing a specific file. So yes, I'm requesting to be able to sort the file/folder view also. That will make it much easier to see when a specific file has changed.

     
  • DRC
    DRC
    2012-10-11

    If the new code viewer is in fact intended to replace ViewVC and there will be no way to access ViewVC after the upgrade, then I would add that the new code viewer desperately needs the following:

    (1) The ability to click on a file and pull up the commit history for only that file, and to diff between revisions.

    (2) The ability to view the entire tree (it may already do this, but thus far, all I can make it do is show me a tree containing only the revised files for a particular revision. That's not what I want. I want a full-tree view as ViewVC provided.)

    (3) +1, emphatically, on side-by-side diff.

    (4) More friendly history view. In ViewVC, I can scroll through the history using a single page for each commit, and the page shows me the full commit log as well as what files were changed. To do that in the new code viewer requires way too many clicks.

    Or, just allow those who prefer ViewVC to continue using it.

     
  • DRC
    DRC
    2012-11-26

    It appears that (2) and (4) above have been addressed. Thus, I would say that the most critical functionality that remains to be implemented in the new code viewer is the ability to view the history of just one file and diff between arbitrary revisions, and side-by-side diff would be next.

     
  • Peter Åstrand
    Peter Åstrand
    2012-12-03

    Hi, any estimated time frame for fixing these shortcomings? They are blocking the migration of the TigerVNC project.

     
  • DRC
    DRC
    2012-12-30

    I discovered another limitation of the new code viewer. In several projects I maintain, the documentation is maintained in HTML format so that we can link to the latest & greatest version of it on the SVN repository. This works beautifully and seamlessly with ViewVC, but there is no way to do it with the new code browser. I am becoming increasingly frustrated with this new browser and do not understand why SourceForge is trying to cram it down our throats when we're perfectly happy with the old one.

    Maybe you should just let users continue to use ViewVC if they choose? This is fastly turning into an Apple Maps sort of situation, and this feature is so critical to my workflow that I would seriously consider moving all of my SVN repositories elsewhere just to get back ViewVC. I rely on open source development for my livelihood, and thus I am happy to pay for the ability to continue my old development workflow without disruptions.

    I have already migrated one of my projects to Allura. I have regretted it ever since and am resisting migration of my other projects until/unless these code browser issues are addressed.

    SourceForge, please understand that people rely on your platform to keep vital software infrastructure moving forward. You can't just pull the rug out from under us like this.

     
  • Yura
    Yura
    2012-12-30

    you can link to the latest code by replacing the number with HEAD like this:
    https://sourceforge.net/p/blacknova/code/HEAD/tree/
    hope that helps

     
  • DRC
    DRC
    2013-01-07

    Please look at the way ViewVC does a file/dir history and copy that. For starters, it lets you see the entire commit message for each entry, as well as the full date/timestamp, as well as telling you how long ago that date/timestamp is, as well as the file length, as well as links to view or download the file, as well as the ability to diff between revisions.

    Why can't you continue providing ViewVC? No one seems to want to answer that question.

    As far as side-by-side diff, too many clicks! Why would you assume that users want a vertical diff by default, when side-by-side has been the norm ever since SourceForge was created?