#524 Allura svn code browser lacks features

fixed
https://sourceforge.net/p/oorexx/code-0/8401/tree/
ooRexx
2013-08-12
2012-09-11
No

The svn code browser for Allura does not seem to have any of the nice features of the previous svn browser we had before we moved to Allura.

I don't know if I just don't know how to use it, if it is not working correctly, or that's just the way it is.

With the old browser you could browse in the tree to any single file and when you clicked on it you saw all the commits for that file. You could click on any commit and you had options to diff that commit with the previous. In addition there was an option to donwload a tarball of an entire subdirectory.

I can not seem to do any of that with the current browser. Is it not working as planned, or is there some thing I'm not doing correctly.

The other thing I don't understand is: I was trying to give a user the URL to go to, to download just some specific files. Go to say this URL:

https://sourceforge.net/p/oorexx/code-0/8401/tree/main/trunk/platform/windows/install/

But, that has the 8401 commit number in it. What happens if 2 commits are made before the user goes to the URL?

Also, back to my original description, in that subdirectory are about 11 files. The user wants to get just those files without have to install a svn client. In the old browser, even if he couldn't use a tarball, it was easy to just download the 11 files individually. But now, if you click on say orange.bmp, you get the bitmap displayed in the browser.

It has nothing to indicate that you can download it. I see now that if I right click on the image, I get a menu option to save the image. This was not very intuitive for me. But, for people not used to Windows, they simply can not figure this out. In the old browser, how to download a file was very easy to figure out.

I guess my point here is that I thought the Allura interface would be better than the old interface. But, at least for the svn code browser, it seems several steps backwards. So, I don't know if there is something else we need to do to set things up correctly, if I just can't figure out how to use the tool correctly, or what.

Discussion

  • Chris Tsai
    Chris Tsai
    2012-09-13

    Thank you for the feedback, I've shown this to our engineering team and we think that there are a lot of good suggestions here. Some of these we already have tickets for, and others, I'll be logging new tickets for.

    With the old browser you could browse in the tree to any single file and when you clicked on it you saw all the commits for that file. You could click on any commit and you had options to diff that commit with the previous.

    Escalating this to our engineering team here: [allura:tickets:#4929]

    In addition there was an option to donwload a tarball of an entire subdirectory.

    We have an existing ticket for this here: [allura:tickets:#2840]

    The other thing I don't understand is: I was trying to give a user the URL to go to, to download just some specific files. Go to say this URL:

    https://sourceforge.net/p/oorexx/code-0/8401/tree/main/trunk/platform/windows/install/

    But, that has the 8401 commit number in it. What happens if 2 commits are made before the user goes to the URL?

    Existing ticket here: [allura:tickets:#4130]

    The user wants to get just those files without have to install a svn client. In the old browser, even if he couldn't use a tarball, it was easy to just download the 11 files individually. But now, if you click on say orange.bmp, you get the bitmap displayed in the browser.

    It has nothing to indicate that you can download it. I see now that if I right click on the image, I get a menu option to save the image. This was not very intuitive for me. But, for people not used to Windows, they simply can not figure this out. In the old browser, how to download a file was very easy to figure out.

    There's already a download link on text and binary files, but I've added a ticket to add a link for that for images as well: [allura:tickets:#4931]

    Regards,
    Chris Tsai, SourceForge.net Support

    • labels: engr, nf-4929, nf-4931, nf-2820, nf-4130 --> engr, nf-4929, nf-4931, nf-2820, nf-4130, forge, p3
     

    Related

    Apache Allura: Tickets: #4130

  • Chris Tsai
    Chris Tsai
    2012-09-13

    • labels: --> engr, nf-4929, nf-4931, nf-2820, nf-4130
    • status: unread --> assigned
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2012-09-19

    • labels: engr, nf-4929, nf-4931, nf-2820, nf-4130, forge, p3 --> engr, nf-4929, nf-4931, nf-4130, forge, p3, nf-2840
     
  • Chris Tsai
    Chris Tsai
    2012-09-26

    • labels: engr, nf-4929, nf-4931, nf-4130, forge, p3, nf-2840 --> engr, nf-4929, nf-4931, forge, p3, nf-2840
     
  • I regret I've accepted your recommendation to switch to new site style. I miss the old look and new one is useless in many aspects. GIT browser lacks all things listed above which are REQUIRED. Your new look seems as very early pre-alpha version, why you ever asked people to migrate to such raw product? In addition to listed above it is missed:
    1) details of commit (check GitWeb pages to see what is missed);
    2) git shortlog (big log is too much hard to use when you try to see not only last commit but, let say, last 200 of them).

    Also spacing is too much bigger than it was - both in git log and in git diff. The change is much harder to browse with such spacing. You have either return back old spacing or add option to change it.

    May be the best choice would be let users select browser - your pre-alpha new look or classic GitWeb one.
    Thank you.

     
  • Nate Bargmann
    Nate Bargmann
    2013-01-16

    I agree with the comment on the Git browser above. Believing this new site is ready for prime time I pulled the trigger on my project yesterday and am regretting doing so. The Git browser is poorly done showing the initial creation date and commit for each file rather than the most recent commit and date which is normal in Git Web browsers.

    This poor representation of a Git repository has forced me to set up a mirror on Github which is where I will be directing our users from now on. Thankfully, our mailing list, file repository, and Media Wiki were unchanged.

     
  • Chris Tsai
    Chris Tsai
    2013-03-13

    • labels: engr, nf-4929, nf-4931, forge, p3, nf-2840 --> engr, nf-4929, nf-4931, forge, p3, nf-5956
     
  • Chris Tsai
    Chris Tsai
    2013-03-13

    Much of the work for code snapshot/tarballs is coded, but we still have some follow-up work before we can enable this on the site. I'll keep you posted.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2013-04-02

    • labels: engr, nf-4929, nf-4931, forge, p3, nf-5956 --> engr, nf-4931, forge, p3, nf-5956
     
  • Chris Tsai
    Chris Tsai
    2013-04-02

    Diffs have better links now.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2013-04-04

    • labels: engr, nf-4931, forge, p3, nf-5956 --> engr, nf-4931, forge, p3
     
  • Chris Tsai
    Chris Tsai
    2013-04-04

    There's now a "download snapshot" link in the menu bar of the tree view. The first time it's called for a revision, it will generate a tarball. This tarball is then cached for a time in case it's requested again.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2013-08-12

    • status: assigned --> fixed
     
  • Chris Tsai
    Chris Tsai
    2013-08-12

    Images in code browser now have a download link.

    Regards,
    Chris Tsai, SourceForge.net Support