##// END OF EJS Templates
spelling
spelling

File last commit:

r5037:bd722d6e default
r5133:0ea0ce62 default
Show More
repo_group_add.mako
121 lines | 4.3 KiB | application/x-mako | MakoHtmlLexer
templating: use .mako as extensions for template files.
r1282 <%inherit file="/base/base.mako"/>
<%def name="title()">
${_('Add repository group')}
%if c.rhodecode_name:
&middot; ${h.branding(c.rhodecode_name)}
%endif
</%def>
<%def name="breadcrumbs_links()">
audit-logs: introduced new view to replace admin journal....
r1758 ${h.link_to(_('Admin'),h.route_path('admin_home'))}
templating: use .mako as extensions for template files.
r1282 &raquo;
repo-groups: moved to pyramid
r2175 ${h.link_to(_('Repository groups'),h.route_path('repo_groups'))}
templating: use .mako as extensions for template files.
r1282 &raquo;
${_('Add Repository Group')}
</%def>
<%def name="menu_bar_nav()">
${self.menu_items(active='admin')}
</%def>
admin: show admin menus in add pages, and edit pages for users/groups/user groups
r3585 <%def name="menu_bar_subnav()">
${self.admin_menu(active='repository_groups')}
</%def>
templating: use .mako as extensions for template files.
r1282 <%def name="main()">
<div class="box">
repo-groups: moved to pyramid
r2175 ${h.secure_form(h.route_path('repo_group_create'), request=request)}
templating: use .mako as extensions for template files.
r1282 <div class="form">
<!-- fields -->
<div class="fields">
<div class="field">
<div class="label">
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 <label for="group_name">${_('Group name')}:</label>
templating: use .mako as extensions for template files.
r1282 </div>
<div class="input">
${h.text('group_name', class_="medium")}
</div>
</div>
<div class="field">
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 <div class="label">
<label for="group_parent_id">${_('Repository group')}:</label>
</div>
<div class="select">
create: fixed case for repo groups that didn't pre-fill the repo group from GET param....
r4424 ${h.select('group_parent_id', request.GET.get('parent_group'),c.repo_groups,class_="medium")}
% if c.personal_repo_group:
<a class="btn" href="#" id="select_my_group" data-personal-group-id="${c.personal_repo_group.group_id}">
${_('Select my personal group ({})').format(c.personal_repo_group.group_name)}
</a>
% endif
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 </div>
</div>
<div class="field">
templating: use .mako as extensions for template files.
r1282 <div class="label">
<label for="group_description">${_('Description')}:</label>
</div>
<div class="textarea editor">
${h.textarea('group_description',cols=23,rows=5,class_="medium")}
meta-tags: cleanup support for metatags....
r2091 <% metatags_url = h.literal('''<a href="#metatagsShow" onclick="$('#meta-tags-desc').toggle();return false">meta-tags</a>''') %>
descriptions: show mention of metatags only if they are enabled.
r4241 <span class="help-block">
% if c.visual.stylify_metatags:
${_('Plain text format with {metatags} support.').format(metatags=metatags_url)|n}
% else:
${_('Plain text format.')}
% endif
</span>
meta-tags: cleanup support for metatags....
r2091 <span id="meta-tags-desc" style="display: none">
<%namespace name="dt" file="/data_table/_dt_elements.mako"/>
${dt.metatags_help()}
</span>
templating: use .mako as extensions for template files.
r1282 </div>
</div>
<div id="copy_perms" class="field">
<div class="label label-checkbox">
<label for="group_copy_permissions">${_('Copy Parent Group Permissions')}:</label>
</div>
<div class="checkboxes">
${h.checkbox('group_copy_permissions', value="True", checked="checked")}
permissions: show user group count in permissions summary, and unified some text labels.
r3385 <span class="help-block">${_('Copy permissions from parent repository group.')}</span>
templating: use .mako as extensions for template files.
r1282 </div>
</div>
<div class="buttons">
dan
templates: use explicit named actions like "create user" instead of generic "save" which is bad UX.
r4118 ${h.submit('save',_('Create Repository Group'),class_="btn")}
templating: use .mako as extensions for template files.
r1282 </div>
</div>
</div>
${h.end_form()}
</div>
<script>
$(document).ready(function(){
var setCopyPermsOption = function(group_val){
js: fixed some JS syntax.
r3379 if(group_val !== "-1"){
templating: use .mako as extensions for template files.
r1282 $('#copy_perms').show()
}
else{
$('#copy_perms').hide();
}
js: fixed some JS syntax.
r3379 };
templating: use .mako as extensions for template files.
r1282 $("#group_parent_id").select2({
'containerCssClass': "drop-menu",
'dropdownCssClass': "drop-menu-dropdown",
'dropdownAutoWidth': true
});
js: fixed some JS syntax.
r3379 setCopyPermsOption($('#group_parent_id').val());
templating: use .mako as extensions for template files.
r1282 $("#group_parent_id").on("change", function(e) {
setCopyPermsOption(e.val)
js: fixed some JS syntax.
r3379 });
templating: use .mako as extensions for template files.
r1282 $('#group_name').focus();
create: fixed case for repo groups that didn't pre-fill the repo group from GET param....
r4424
$('#select_my_group').on('click', function(e){
e.preventDefault();
$("#group_parent_id").val($(this).data('personalGroupId')).trigger("change");
})
templating: use .mako as extensions for template files.
r1282 })
</script>
</%def>