c78ffbcd18
assignments on the base schedule are shown in the pages for the schedule, read-only. This allows managing things like breaks and misc sessions separately from the regular WG sessions. Base schedules are not allowed to be the base of other base schedules (the hierarchy can only be one level deep) to simplify the mental model and the code. Add link for creating new schedules instead of relying on copying Empty-Schedule and change the meeting creation code to no longer create the special Empty-Schedule. Instead a "base" schedule is created and a first schedule with the name and permissions of the user creating the meeting, using "base" as base. Speed up a couple of the Secretariat/AD agenda views by adding prefetches. - Legacy-Id: 18355
85 lines
3.5 KiB
HTML
85 lines
3.5 KiB
HTML
{% extends "base.html" %}
|
|
{# Copyright The IETF Trust 2015-2020, All Rights Reserved #}
|
|
{% load origin %}
|
|
{% load ietf_filters %}
|
|
|
|
{% block content %}
|
|
{% origin %}
|
|
|
|
<h1>{% block title %}Possible Meeting Agendas for IETF {{ meeting.number }}{% endblock %}</h1>
|
|
|
|
{% comment %}
|
|
<div>
|
|
<p><a href="{% url "ietf.meeting.views.edit_timeslots" meeting.number %}">Edit Timeslots</a></p>
|
|
</div>
|
|
{% endcomment %}
|
|
|
|
<div>
|
|
{% for schedules, own, label in schedule_groups %}
|
|
<div class="panel panel-default">
|
|
<div class="panel-heading">
|
|
{{ label }}
|
|
{% if own %}
|
|
<div class="pull-right" >
|
|
<a href="{% url "ietf.meeting.views.new_meeting_schedule" num=meeting.number %}"><i class="fa fa-plus"></i> New Agenda</a>
|
|
</div>
|
|
{% endif %}
|
|
</div>
|
|
<div class="panel-body">
|
|
<table class="table table-condensed table-striped">
|
|
<tr>
|
|
<th class="col-md-2">Name</th>
|
|
<th class="col-md-2">Owner</th>
|
|
<th class="col-md-1">Origin</th>
|
|
<th class="col-md-1">Base</th>
|
|
<th class="col-md-3">Notes</th>
|
|
<th class="col-md-1">Visible</th>
|
|
<th class="col-md-1">Public</th>
|
|
</tr>
|
|
{% for schedule in schedules %}
|
|
<tr>
|
|
<td>
|
|
<a href="{% url "ietf.meeting.views.edit_schedule" meeting.number schedule.owner_email schedule.name %}">{{ schedule.name }}</a>
|
|
{% if schedule.can_edit_properties %}
|
|
<a class="edit-schedule-properties" href="{% url "ietf.meeting.views.edit_schedule_properties" meeting.number schedule.owner_email schedule.name %}?next={{ request.get_full_path|urlencode }}">
|
|
<i title="Edit agenda properties" class="fa fa-edit"></i>
|
|
</a>
|
|
{% endif %}
|
|
</td>
|
|
<td>{{ schedule.owner }}</td>
|
|
<td>
|
|
{% if schedule.origin %}
|
|
<a href="{% url "ietf.meeting.views.edit_schedule" meeting.number schedule.origin.owner_email schedule.origin.name %}">{{ schedule.origin.name }}</a>
|
|
<a href="{% url "ietf.meeting.views.diff_schedules" meeting.number %}?from_schedule={{ schedule.origin.name|urlencode }}&to_schedule={{ schedule.name|urlencode }}" title="{{ schedule.changes_from_origin }} change{{ schedule.changes_from_origin|pluralize }} from {{ schedule.origin.name }}">+{{ schedule.changes_from_origin }}</a>
|
|
{% endif %}
|
|
</td>
|
|
<td>
|
|
{% if schedule.base %}
|
|
<a href="{% url "ietf.meeting.views.edit_schedule" meeting.number schedule.base.owner_email schedule.base.name %}">{{ schedule.base.name }}</a>
|
|
{% endif %}
|
|
</td>
|
|
<td>{{ schedule.notes|linebreaksbr }}</td>
|
|
<td>
|
|
{% if schedule.visible %}
|
|
<div class="label label-success">visible</div>
|
|
{% else %}
|
|
<div class="label label-danger">hidden</div>
|
|
{% endif %}
|
|
</td>
|
|
<td>
|
|
{% if schedule.public %}
|
|
<div class="label label-success">public</div>
|
|
{% else %}
|
|
<div class="label label-danger">private</div>
|
|
{% endif %}
|
|
</td>
|
|
</tr>
|
|
{% endfor %}
|
|
</table>
|
|
</div>
|
|
</div>
|
|
{% endfor %}
|
|
</div>
|
|
|
|
{% endblock content %}
|