changeset 6942:46bc7191e1e4

files: use same parent/child navigation as on changeset page There are different reasons to do this. First, be consistent. Second, steping through the revisions by revision number is problematic. It means jumping between branches (I think even with the 'Follow current branch' checkbox this is not obvious to all the users). Also if we'd continue to use it, it'd require some special handling of hidden revisions.
author domruf <dominikruf@gmail.com>
date Wed, 16 Aug 2017 17:34:44 +0200
parents d39fcf27fa44
children c504e3af9ee8
files kallithea/templates/files/files_browser.html
diffstat 1 files changed, 3 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/kallithea/templates/files/files_browser.html	Sun Oct 22 04:01:28 2017 +0200
+++ b/kallithea/templates/files/files_browser.html	Wed Aug 16 17:34:44 2017 +0200
@@ -1,3 +1,5 @@
+<%namespace name="base" file="/base/base.html"/>
+
 <%def name="file_class(node)">
     %if node.is_file():
         <%return "browser-file" %>
@@ -26,14 +28,7 @@
 </%def>
 <div id="body" class="panel panel-default">
     <div class="panel-heading clearfix">
-        <span class="browser-nav form-inline">
-            <span class="info_box">
-              <span class="info_box_elem rev">${_('Revision')}</span>
-              <span class="info_box_elem"><a class="btn btn-default btn-xs ypjax-link" href="${c.url_prev}" title="${_('Previous revision')}"><i class="icon-left-open"></i></a></span>
-              <span class="info_box_elem">${h.text('at_rev',value=c.changeset.revision,size=5,class_='form-control input-sm')}</span>
-              <span class="info_box_elem"><a class="btn btn-default btn-xs ypjax-link" href="${c.url_next}" title="${_('Next revision')}"><i class="icon-right-open"></i></a></span>
-            </span>
-        </span>
+        ${base.parent_child_navigation()}
     </div>
 
     <div class="panel-body">