# HG changeset patch
# User domruf <dominikruf@gmail.com>
# Date 1502897684 -7200
# Node ID 46bc7191e1e4e7307a355b37e2fa4194681c8c79
# Parent  d39fcf27fa44772f9188c40dcf5f49a5b7cb7d6d
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.

diff -r d39fcf27fa44 -r 46bc7191e1e4 kallithea/templates/files/files_browser.html
--- 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">