##// END OF EJS Templates
u » pc » rhodecode-enterprise-ce-fork-pc
RSS

Fork of rhodecode-enterprise-ce

vcs: Minimal change to expose the shadow repository...
vcs: Minimal change to expose the shadow repository Based on my original research, this was the "minimal" starting point. It shows that three concepts are needed for the "repo_name": * From the security standpoint we think of the shadow repository having the same ACL as the target repository of the pull request. This is because the pull request itself is considered to be a part of the target repository. Out of this thought, the variable "acl_repo_name" is used whenever we want to check permissions or when we need the database configuration of the repository. An alternative name would have been "db_repo_name", but the usage for ACL checking is the most important one. * From the web interaction perspective, we need the URL which was originally used to get to the repository. This is because based on this base URL commands can be identified. Especially for Git this is important, so that the commands are correctly recognized. Since the URL is in the focus, this is called "url_repo_name". * Finally we have to deal with the repository on the file system. This is what the VCS layer deal with normally, so this name is called "vcs_repo_name". The original repository interaction is a special case where all three names are the same. When interacting with a pull request, these three names are typically all different. This change is minimal in a sense that it just makes the interaction with a shadow repository barely work, without checking any special constraints yet. This was the starting point for further work on this topic.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r887:175782be default
Show More
form-inline.html
174 lines | 4.7 KiB | text/html | HtmlLexer
/ rhodecode / templates / debug_style / form-inline.html
History | Annotation | Raw |Copy content |Copy permalink
## -*- coding: utf-8 -*-
<%inherit file="/debug_style/index.html"/>
<%def name="breadcrumbs_links()">
${h.link_to(_('Style'), h.url('debug_style_home'))}
&raquo;
${c.active}
</%def>
<%def name="real_main()">
<div class="box">
<div class="title">
${self.breadcrumbs()}
</div>
<div class='sidebar-col-wrapper'>
${self.sidebar()}
<div class="main-content">
<h2>Inline form elements</h2>
<p>A few places have a button close to an input element or similar.</p>
<h3>Submit button after select element</h3>
<div class="bs-example">
## TODO: johbo: not sure if we should add a class like .form-inline
## here. Seems to work good enough right now.
<form method="post" action="">
<div class="form">
<div class="fields">
<select id="example_select" >
<option value="#">${_('Templates...')}</option>
<option value="ga">Google Analytics</option>
<option value="clicky">Clicky</option>
<option value="server_announce">${_('Server Announcement')}</option>
</select>
<input type="submit" value="Set" id="example_save" class="btn">
</div>
<script>
$(document).ready(function() {
$('#example_select').select2({
containerCssClass: 'drop-menu',
dropdownCssClass: 'drop-menu-dropdown',
dropdownAutoWidth: true,
minimumResultsForSearch: -1
});
});
</script>
</div>
</form>
</div>
<h3>Submit button after input element</h3>
<div class="bs-example">
## TODO: johbo: not sure if we should add a class like .form-inline
## here. Seems to work good enough right now.
<form method="post" action="">
<div class="form">
<div class="fields">
<input type="text" id="example_input" placeholder="Placeholder...">
<input type="submit" value="Set" id="example_save" class="btn">
</div>
</div>
</form>
</div>
<h3>Submit and Reset button after input element</h3>
<div class="bs-example">
## TODO: johbo: not sure if we should add a class like .form-inline
## here. Seems to work good enough right now.
<form method="post" action="">
<div class="form">
<div class="fields">
<input type="text" id="example_input" placeholder="Placeholder...">
<input type="submit" value="Set" id="example_save" class="btn">
<input type="reset" value="Reset" id="example_reset" class="btn">
</div>
</div>
</form>
</div>
<h3>Checkbox wrapped in the label itself</h3>
<div class="bs-example">
<div class="field">
<label><input id="example_label_checkbox" type="checkbox">Checkbox with label around it</label>
</div>
<div class="field">
<label><input id="example_label_checkbox" type="radio">Radio with label around it</label>
</div>
</div>
<h3>Checkbox wrapped in the label itself</h3>
<div class="bs-example">
<div class="form">
<div class="fields">
<label>Label</label> <input type="text">
</div>
</div>
</div>
<div class="bs-example">
<div class="form">
<div class="fields">
<label>Label</label>
<select id="02_example_select1" >
<option value="#">${_('Templates...')}</option>
<option value="ga">Google Analytics</option>
<option value="clicky">Clicky</option>
<option value="server_announce">${_('Server Announcement')}</option>
</select>
<label>Label</label>
<select id="02_example_select2" >
<option value="#">${_('Templates...')}</option>
<option value="ga">Google Analytics</option>
<option value="clicky">Clicky</option>
<option value="server_announce">${_('Server Announcement')}</option>
</select>
</div>
</div>
<script>
$(document).ready(function() {
$('#02_example_select1').select2({
containerCssClass: 'drop-menu',
dropdownCssClass: 'drop-menu-dropdown',
dropdownAutoWidth: true,
minimumResultsForSearch: -1
});
$('#02_example_select2').select2({
containerCssClass: 'drop-menu',
dropdownCssClass: 'drop-menu-dropdown',
dropdownAutoWidth: true,
minimumResultsForSearch: -1
});
});
</script>
</div>
</div>
</div>
</%def>