2011-02-01 09:57:29 +08:00
<% content_for :page_title do %><%= @section.name %><% end %>
<% content_for :right_side do %>
<div class="rs-margin-all">
2011-04-16 14:22:55 +08:00
<% if can_do(@section, @current_user, :update) %>
Fully adopt Bootstrap & update css to work with it, closes: #CNVS-1344
this commit does the following:
* upgrade bootstrap-sass gem to most recent version
* switches to using bootstrap's normalize.css and forms.css
which fixes a whole bunch of misformatting of how bootstrap
stuff is supposed to look, but changing those 2 affects
a lot of our old stylesheets.
* gets rid of unified_buttons.sass and just uses bootstraps buttons.
.ui-button @extends these because we still have to support .ui-button
for modals & buttonsets. but .button is no longer supported.
* a lot of css file reorganization (there's no more 'blue' and
'normal canvas', there's just canvas)
* a bunch of files had to be tweaked to look good with these changes.
test plan:
This change touches every page in canvas so, no kidding, we need to make
sure every page looks OK. In order to do that:
1. each sprint team needs to give a +1 after they make sure all the
pages in the features they are over look good.
2. the QA person on each team needs to look at the pages for their
teams features for a QA +1
things to look for specifically when testing:
* buttons: this gets rid of all those red 'cancel' links
that are actually buttons, make sure all the buttons you see
look right. if you see 2 plain gray buttons next to each other
like [Save] [Cancel], we should make the primary one blue (by
adding the .btn-primary class)
* Forms: a lot of this change has to do with how form elements look,
especially <select>s, <input>s and <label>s. look at the diffs
for the ones that have the most changes and make sure those look
good, but also check for the ones I missed and make sure those
look good too.
* and just random style changes, if something looks ugly or broken
(and it didn't before), we should fix that.
Also:
just use a link instead of a drop-menu for adding event from sidebar
we used to have a drop down menu for adding events
to cal2 from the sidebar where you'd hit a cog
and it'd ask you if you wanted to add an event or
an assignment. this just simplifies it to an add
icon.
this: http://cl.ly/image/133a2A3q3q1M
instead of: http://cl.ly/image/46463o2s3W0g
Change-Id: I384fe273934bca96bf28423afb1402c7792d8766
Reviewed-on: https://gerrit.instructure.com/15422
Tested-by: Jenkins <jenkins@instructure.com>
Reviewed-by: Ryan Florence <ryanf@instructure.com>
QA-Review: Ryan Florence <ryanf@instructure.com>
2012-12-21 14:46:28 +08:00
<a href="#" class="btn button-sidebar-wide edit_section_link"><i class="icon-edit"></i> <%= t('buttons.edit_section', 'Edit Section') %></a>
2011-04-16 14:22:55 +08:00
<% if @section.nonxlist_course_id %>
2011-11-18 05:38:35 +08:00
<% if can_do(@section.nonxlist_course, @current_user, :manage_sections) %>
Fully adopt Bootstrap & update css to work with it, closes: #CNVS-1344
this commit does the following:
* upgrade bootstrap-sass gem to most recent version
* switches to using bootstrap's normalize.css and forms.css
which fixes a whole bunch of misformatting of how bootstrap
stuff is supposed to look, but changing those 2 affects
a lot of our old stylesheets.
* gets rid of unified_buttons.sass and just uses bootstraps buttons.
.ui-button @extends these because we still have to support .ui-button
for modals & buttonsets. but .button is no longer supported.
* a lot of css file reorganization (there's no more 'blue' and
'normal canvas', there's just canvas)
* a bunch of files had to be tweaked to look good with these changes.
test plan:
This change touches every page in canvas so, no kidding, we need to make
sure every page looks OK. In order to do that:
1. each sprint team needs to give a +1 after they make sure all the
pages in the features they are over look good.
2. the QA person on each team needs to look at the pages for their
teams features for a QA +1
things to look for specifically when testing:
* buttons: this gets rid of all those red 'cancel' links
that are actually buttons, make sure all the buttons you see
look right. if you see 2 plain gray buttons next to each other
like [Save] [Cancel], we should make the primary one blue (by
adding the .btn-primary class)
* Forms: a lot of this change has to do with how form elements look,
especially <select>s, <input>s and <label>s. look at the diffs
for the ones that have the most changes and make sure those look
good, but also check for the ones I missed and make sure those
look good too.
* and just random style changes, if something looks ugly or broken
(and it didn't before), we should fix that.
Also:
just use a link instead of a drop-menu for adding event from sidebar
we used to have a drop down menu for adding events
to cal2 from the sidebar where you'd hit a cog
and it'd ask you if you wanted to add an event or
an assignment. this just simplifies it to an add
icon.
this: http://cl.ly/image/133a2A3q3q1M
instead of: http://cl.ly/image/46463o2s3W0g
Change-Id: I384fe273934bca96bf28423afb1402c7792d8766
Reviewed-on: https://gerrit.instructure.com/15422
Tested-by: Jenkins <jenkins@instructure.com>
Reviewed-by: Ryan Florence <ryanf@instructure.com>
QA-Review: Ryan Florence <ryanf@instructure.com>
2012-12-21 14:46:28 +08:00
<a href="#" class="btn button-sidebar-wide uncrosslist_link"><i class="icon-off"></i> <%= t('buttons.uncrosslist_section', 'De-Cross-List this Section') %></a>
2011-04-16 14:22:55 +08:00
<% end %>
Fully adopt Bootstrap & update css to work with it, closes: #CNVS-1344
this commit does the following:
* upgrade bootstrap-sass gem to most recent version
* switches to using bootstrap's normalize.css and forms.css
which fixes a whole bunch of misformatting of how bootstrap
stuff is supposed to look, but changing those 2 affects
a lot of our old stylesheets.
* gets rid of unified_buttons.sass and just uses bootstraps buttons.
.ui-button @extends these because we still have to support .ui-button
for modals & buttonsets. but .button is no longer supported.
* a lot of css file reorganization (there's no more 'blue' and
'normal canvas', there's just canvas)
* a bunch of files had to be tweaked to look good with these changes.
test plan:
This change touches every page in canvas so, no kidding, we need to make
sure every page looks OK. In order to do that:
1. each sprint team needs to give a +1 after they make sure all the
pages in the features they are over look good.
2. the QA person on each team needs to look at the pages for their
teams features for a QA +1
things to look for specifically when testing:
* buttons: this gets rid of all those red 'cancel' links
that are actually buttons, make sure all the buttons you see
look right. if you see 2 plain gray buttons next to each other
like [Save] [Cancel], we should make the primary one blue (by
adding the .btn-primary class)
* Forms: a lot of this change has to do with how form elements look,
especially <select>s, <input>s and <label>s. look at the diffs
for the ones that have the most changes and make sure those look
good, but also check for the ones I missed and make sure those
look good too.
* and just random style changes, if something looks ugly or broken
(and it didn't before), we should fix that.
Also:
just use a link instead of a drop-menu for adding event from sidebar
we used to have a drop down menu for adding events
to cal2 from the sidebar where you'd hit a cog
and it'd ask you if you wanted to add an event or
an assignment. this just simplifies it to an add
icon.
this: http://cl.ly/image/133a2A3q3q1M
instead of: http://cl.ly/image/46463o2s3W0g
Change-Id: I384fe273934bca96bf28423afb1402c7792d8766
Reviewed-on: https://gerrit.instructure.com/15422
Tested-by: Jenkins <jenkins@instructure.com>
Reviewed-by: Ryan Florence <ryanf@instructure.com>
QA-Review: Ryan Florence <ryanf@instructure.com>
2012-12-21 14:46:28 +08:00
<a href="#" class="btn button-sidebar-wide crosslist_link"><i class="icon-off"></i> <%= t('buttons.recrosslist_section', 'Re-Cross-List this Section') %></a>
2011-04-16 14:22:55 +08:00
<% else %>
Fully adopt Bootstrap & update css to work with it, closes: #CNVS-1344
this commit does the following:
* upgrade bootstrap-sass gem to most recent version
* switches to using bootstrap's normalize.css and forms.css
which fixes a whole bunch of misformatting of how bootstrap
stuff is supposed to look, but changing those 2 affects
a lot of our old stylesheets.
* gets rid of unified_buttons.sass and just uses bootstraps buttons.
.ui-button @extends these because we still have to support .ui-button
for modals & buttonsets. but .button is no longer supported.
* a lot of css file reorganization (there's no more 'blue' and
'normal canvas', there's just canvas)
* a bunch of files had to be tweaked to look good with these changes.
test plan:
This change touches every page in canvas so, no kidding, we need to make
sure every page looks OK. In order to do that:
1. each sprint team needs to give a +1 after they make sure all the
pages in the features they are over look good.
2. the QA person on each team needs to look at the pages for their
teams features for a QA +1
things to look for specifically when testing:
* buttons: this gets rid of all those red 'cancel' links
that are actually buttons, make sure all the buttons you see
look right. if you see 2 plain gray buttons next to each other
like [Save] [Cancel], we should make the primary one blue (by
adding the .btn-primary class)
* Forms: a lot of this change has to do with how form elements look,
especially <select>s, <input>s and <label>s. look at the diffs
for the ones that have the most changes and make sure those look
good, but also check for the ones I missed and make sure those
look good too.
* and just random style changes, if something looks ugly or broken
(and it didn't before), we should fix that.
Also:
just use a link instead of a drop-menu for adding event from sidebar
we used to have a drop down menu for adding events
to cal2 from the sidebar where you'd hit a cog
and it'd ask you if you wanted to add an event or
an assignment. this just simplifies it to an add
icon.
this: http://cl.ly/image/133a2A3q3q1M
instead of: http://cl.ly/image/46463o2s3W0g
Change-Id: I384fe273934bca96bf28423afb1402c7792d8766
Reviewed-on: https://gerrit.instructure.com/15422
Tested-by: Jenkins <jenkins@instructure.com>
Reviewed-by: Ryan Florence <ryanf@instructure.com>
QA-Review: Ryan Florence <ryanf@instructure.com>
2012-12-21 14:46:28 +08:00
<a href="#" class="btn button-sidebar-wide crosslist_link"><i class="icon-off"></i> <%= t('buttons.crosslist_section', 'Cross-List this Section') %></a>
2011-04-16 14:22:55 +08:00
<% end %>
<% end %>
2015-02-03 07:43:37 +08:00
<a href="<%= context_url(@context, :context_settings_url) %>" class="btn button-sidebar-wide"><i class="icon-settings"></i> <%= t('buttons.back_to_course', 'Back to Course Settings') %></a>
2011-02-01 09:57:29 +08:00
</div>
<% end %>
<% content_for :stylesheets do %>
<style>
#course_form .course_form {
display: none;
}
#course_form.editing .course_form {
display: inline;
}
#course_form.editing .course_info {
display: none;
}
#course_form .date_entry {
width: 100px;
}
2012-01-24 08:21:55 +08:00
.user-list-wrapper {
margin-bottom: 32px;
min-height: 32px;
position: relative;
}
2011-02-01 09:57:29 +08:00
ul.user_list {
list-style: none;
padding-left: 0px;
margin-top: 0px;
max-width: 400px;
}
ul.user_list li.user {
padding-left: 10px;
color: #444;
line-height: 1.5em;
-moz-border-radius: 5px;
}
ul.user_list li.user:hover {
background-color: #eee;
}
ul.user_list li.user .email {
font-size: 0.8em;
margin: -5px 10px 5px;
}
ul.user_list li.user .section {
font-size: 0.8em;
margin: -5px 10px 5px;
}
ul.user_list li.user .short_name {
font-size: 0.8em;
margin: -2px 10px 0px;
}
ul.user_list li.user .enrollment_type {
font-size: 0.8em;
margin: -2px 10px 0px;
}
ul.user_list li.user .links {
float: right;
padding-right: 20px;
padding-top: 5px;
visibility: hidden;
}
ul.user_list li.user .links a {
text-decoration: none;
}
ul.user_list li.user:hover .links {
float: right;
padding-right: 20px;
visibility: visible;
}
ul.user_list li.user.pending {
color: #888;
font-style: italic;
}
2014-05-14 07:48:56 +08:00
h3 .tally {
2011-02-01 09:57:29 +08:00
font-family: arial,sans-serif;
font-size: 12px;
padding-left: 5px;
}
.associated_user {
display: none;
}
#edit_section_form {
margin-bottom: 20px;
}
2013-03-13 23:10:33 +08:00
#edit_section_form .form-actions {
background: none;
border: 0;
padding: 0;
text-align: left;
}
2011-02-01 09:57:29 +08:00
</style>
<% end %>
2013-10-09 03:21:53 +08:00
<%= form_for @section, :url => context_url(@context, :context_section_url, @section), :html => {:id => "edit_section_form", :style => "display: none;"} do |f| %>
2011-02-01 09:57:29 +08:00
<table class="formtable">
<tr>
2011-06-22 02:38:28 +08:00
<td><%= f.blabel :name, :en => "Section Name" %></td>
2011-02-01 09:57:29 +08:00
<td><%= f.text_field :name %></td>
</tr>
2012-02-28 23:50:10 +08:00
<% if @section.sis_source_id && can_do(@context.root_account, @current_user, :read_sis) || can_do(@context.root_account, @current_user, :manage_sis) %>
2011-06-01 04:47:28 +08:00
<tr>
2011-06-22 02:38:28 +08:00
<td><%= f.blabel :sis_source_id, :en => "SIS ID" %></td>
2011-06-01 04:47:28 +08:00
<td>
<span class="course_form">
<% if can_do(@context.root_account, @current_user, :manage_sis) %>
<%= f.text_field :sis_source_id, :style => "width: 50px;", :title => "SIS ID", :value => @section.sis_source_id %>
<% else %>
<%= @section.sis_source_id %>
<% end %>
</span>
</td>
</tr>
<% end %>
2011-02-24 13:26:39 +08:00
<tr>
2015-06-17 06:32:52 +08:00
<td>
<%= f.blabel :start_at, en: "Starts" %>
<label class="screenreader-only" id="section_starts_at_label">
<%= t("Section starts at") %>
<%= datepicker_screenreader_prompt %>
</label>
</td>
<td>
<%= f.text_field :start_at,
class: "datetime_field",
2015-08-11 12:36:10 +08:00
value: datetime_string(@section.start_at),
2015-06-17 06:32:52 +08:00
style: 'width: 120px;',
"aria-labelledby" => "section_starts_at_label",
"data-tooltip" => "",
title: accessible_date_format %>
</td>
2011-02-24 13:26:39 +08:00
</tr>
<tr>
2015-06-17 06:32:52 +08:00
<td>
<%= f.blabel :end_at, en: "Ends" %>
<label class="screenreader-only" id="section_ends_at_label">
<%= t("Section ends at") %>
<%= datepicker_screenreader_prompt %>
</label>
</td>
<td>
<%= f.text_field :end_at,
class: "datetime_field",
2015-08-11 12:36:10 +08:00
value: datetime_string(@section.end_at),
2015-06-17 06:32:52 +08:00
style: 'width: 120px;',
"aria-labelledby" => "section_ends_at_label",
"data-tooltip" => "",
title: accessible_date_format %>
</td>
2011-02-24 13:26:39 +08:00
</tr>
<tr>
<td colspan="2">
<%= f.check_box :restrict_enrollments_to_section_dates %>
2011-09-27 05:03:05 +08:00
<%= f.label :restrict_enrollments_to_section_dates, t('access_limit', "Users can only participate in the course between these dates") %>
2011-02-24 13:26:39 +08:00
<div style="font-size: 0.8em; padding-left: 25px;">
2011-06-22 02:38:28 +08:00
<%= t('override_settings', 'This will override any term or course date settings.') %>
2011-06-01 04:47:28 +08:00
</div>
2011-02-24 13:26:39 +08:00
</td>
</tr>
2011-02-01 09:57:29 +08:00
<tr>
<td colspan="2">
2013-03-13 23:10:33 +08:00
<div class="form-actions">
<button type="button" class="btn cancel_button button-secondary"><%= t('buttons.cancel', 'Cancel') %></button>
<button type="submit" class="btn btn-primary submit_button"><%= t('buttons.update_section', 'Update Section') %></button>
2011-02-01 09:57:29 +08:00
</div>
</td>
</tr>
</table>
<% end %>
2011-06-01 04:47:28 +08:00
<h2 id="section_name"><%= @section.name %></h2>
2011-02-24 13:26:39 +08:00
<div style="margin-bottom: 20px;">
2012-03-15 08:01:05 +08:00
<div id="enrollments_div">
<table id="enrollment_table">
2012-03-14 04:08:19 +08:00
<% if @pending_enrollments_count > 0 %>
2012-03-15 08:01:05 +08:00
<tr>
2012-03-14 04:08:19 +08:00
<td class="pending_enrollments"><%= t('pending_enrollment', {:one => '1 Pending Enrollment', :other => '%{count} Pending Enrollments'}, :count => @pending_enrollments_count) %></td>
2012-03-15 08:01:05 +08:00
</tr>
<% end %>
2012-03-14 04:08:19 +08:00
<% if @enrollments_count > 0 %>
2012-03-15 08:01:05 +08:00
<tr>
2012-03-14 04:08:19 +08:00
<td class="active_enrollments"><%= t('active_enrollment', {:one => '1 Active Enrollment', :other => '%{count} Active Enrollments'}, :count => @enrollments_count) %></td>
2012-03-15 08:01:05 +08:00
</tr>
<% end %>
2012-03-14 04:08:19 +08:00
<% if @completed_enrollments_count > 0 %>
2012-03-15 08:01:05 +08:00
<tr>
2012-03-14 04:08:19 +08:00
<td class="completed_enrollments"><%= t('completed_enrollment', {:one => '1 Completed Enrollment', :other => '%{count} Completed Enrollments'}, :count => @completed_enrollments_count) %></td>
2012-03-15 08:01:05 +08:00
</tr>
<% end %>
</table>
2011-02-24 13:26:39 +08:00
</div>
2012-02-28 23:50:10 +08:00
<% if @section && ( @section.sis_source_id && can_do(@context.root_account, @current_user, :read_sis) || can_do(@context.root_account, @current_user, :manage_sis))%>
2011-06-22 02:38:28 +08:00
<div><%= before_label('sis_id', "SIS ID") %> <span class="sis_source_id"><%= @section.sis_source_id %></span></div>
2011-04-09 11:00:46 +08:00
<% end %>
2011-02-24 13:26:39 +08:00
<% if @section.start_at || @section.end_at %>
<div>
2011-06-22 02:38:28 +08:00
<% if @section.start_at && @section.end_at %>
2014-05-14 07:48:56 +08:00
<%= t('run_dates', 'Runs from %{start_date} to %{end_date}', :start_date => friendly_datetime(@section.start_at, context: @context).html_safe, :end_date => friendly_datetime(@section.end_at, context: @context).html_safe) %>
2011-06-22 02:38:28 +08:00
<% elsif @section.end_at %>
2014-05-14 07:48:56 +08:00
<%= t('runs_until', 'Runs until %{end_date}', :end_date => friendly_datetime(@section.end_at, context: @context).html_safe) %>
2011-06-22 02:38:28 +08:00
<% elsif @section.start_at %>
2014-05-14 07:48:56 +08:00
<%= t('run_from', 'Runs from %{start_date} with no end date', :start_date => friendly_datetime(@section.start_at, context: @context).html_safe) %>
2011-06-22 02:38:28 +08:00
<% end %>
2011-02-24 13:26:39 +08:00
</div>
<div style="margin-left: 10px; font-size: 0.8em;">
2011-06-22 02:38:28 +08:00
<%= t('student_access_dates', 'Students can only access the course between these dates') if @section.restrict_enrollments_to_section_dates %>
2011-02-24 13:26:39 +08:00
</div>
<% end %>
</div>
2011-08-16 06:34:57 +08:00
<% if can_do @context, @current_user, :read_roster, :manage_students, :manage_admin_users %>
2012-01-24 08:21:55 +08:00
<div class="enrollments-lists">
2011-08-16 06:34:57 +08:00
<h3><%= t('titles.current_enrollments', 'Current Enrollments') %></h3>
2012-01-24 08:21:55 +08:00
<div class="user-list-wrapper" id="current-enrollment-list">
<ul class="user_list"></ul>
</div>
<h3><%= t('titles.completed_enrollments', 'Completed Enrollments') %></h3>
<div class="user-list-wrapper" id="completed-enrollment-list">
<ul class="user_list"></ul>
</div>
</div>
2011-02-01 09:57:29 +08:00
<% end %>
2011-11-11 00:31:45 +08:00
<% js_bundle :section %>
2011-04-16 14:22:55 +08:00
<div style="display: none;">
2014-08-12 06:30:44 +08:00
<%= form_tag context_url(@context, :context_section_crosslist_url, @section.id), :id => "crosslist_course_form", :class => "form-dialog no-margin-bottom", :title => t('titles.crosslist_this_section', 'Cross-List this Section'), :method => :post do %>
2011-06-22 02:38:28 +08:00
<h2><%= t('titles.cross_listed_sections', 'Cross-List Section') %></h2>
2011-04-16 14:22:55 +08:00
<p>
2011-06-22 02:38:28 +08:00
<%= t('crosslist_description', %{
2011-04-16 14:22:55 +08:00
Cross-listing allows you to create a section in one account and
2014-05-14 07:48:56 +08:00
then move it to a course on a different account.
2011-04-16 14:22:55 +08:00
To cross-list this course, you'll need to find the course you
2014-05-14 07:48:56 +08:00
want to move it to, either using the search tool or by
2011-06-22 02:38:28 +08:00
entering the course's ID. }) %>
2011-04-16 14:22:55 +08:00
</p>
<table class="formtable">
<tr>
2011-06-22 02:38:28 +08:00
<td><label for="course_autocomplete_id_lookup"><%= before_label('search_for_course', "Search for Course") %> </label></td>
2011-04-16 14:22:55 +08:00
<td>
2011-06-09 03:56:27 +08:00
<a href="<%= context_url(@current_user, :context_manageable_courses_url, :format => :json) %>" id="course_autocomplete_url" style="display: none;"> </a>
2011-04-16 14:22:55 +08:00
<a href="<%= context_url(@context, :context_section_confirm_crosslist_url, @section.id, "{{ id }}") %>" id="course_confirm_crosslist_url" style="display: none;"> </a>
<input type="hidden" name="new_course_id" id="course_autocomplete_id"/>
<input type="text" id="course_autocomplete_id_lookup" style="width: 250px;"/>
</td>
</tr><tr>
2011-06-22 02:38:28 +08:00
<td><label for="course_id"><%= before_label('enter_course_id', "Or Enter the Course's ID") %></label></td>
2011-04-16 14:22:55 +08:00
<td>
<input type="text" id="course_id" style="width: 75px;"/>
</td>
</tr><tr>
<td colspan="2">
<div id="course_autocomplete_name_holder" style="margin-top: 20px;">
2014-05-14 07:48:56 +08:00
<%= before_label('labels.selected_course', 'Selected Course') %>
2011-04-16 14:22:55 +08:00
<div style="margin-left: 20px;">
<div id="course_autocomplete_name" style="font-weight: bold;"></div>
2011-06-22 02:38:28 +08:00
<div id="sis_id_holder" style="display: none;"><%= before_label('labels.sis_id', 'SIS ID') %> <span class="sis_id"> </span></div>
<div id="account_name_holder" style="display: none;"><%= before_label('labels.account', 'Account') %> <span class="account_name"></span></div>
2011-04-16 14:22:55 +08:00
</div>
</div>
</td>
</tr>
</table>
2014-08-12 06:30:44 +08:00
<div class="form-controls">
<button type="submit" class="btn btn-primary submit_button"><%= t('buttons.crosslist_this_section', 'Cross-List This Section') %></button>
<button type="button" class="btn button-secondary cancel_button"><%= t('buttons.cancel', 'Cancel') %></button>
</div>
2011-04-16 14:22:55 +08:00
<% end %>
2013-10-09 03:21:53 +08:00
<%= form_tag context_url(@context, :context_section_uncrosslist_url, @section.id), :id => "uncrosslist_form", :title => t('titles.decrosslist_section', 'De-Cross-List this Section'), :method => :delete do %>
2011-06-22 02:38:28 +08:00
<h2><%= t('titles.decrosslist_section', 'De-Cross-List this Section') %></h2>
2011-04-16 14:22:55 +08:00
<p>
2011-06-22 02:38:28 +08:00
<%= t('prompts.are_you_sure_decrosslist', 'Are you sure you want to de-cross-list this section?') %>
2011-04-16 14:22:55 +08:00
<% if @section.nonxlist_course %>
2011-06-22 02:38:28 +08:00
<%= mt('decrosslist_description', 'This will move the section back to its original course, **%{course_name}**.', :course_name => @section.nonxlist_course.name) %>
2011-04-16 14:22:55 +08:00
<% end %>
</p>
2012-03-14 04:08:19 +08:00
<% if @student_enrollments_count > 0 %>
2011-04-16 14:22:55 +08:00
<p>
2011-06-22 02:38:28 +08:00
<%= t('decrosslist_long_description', %{
2012-03-15 08:01:05 +08:00
All grades for students in this course will no longer be visible.
2014-05-14 07:48:56 +08:00
You can retrieve the grades later by re-cross-listing the course,
2011-06-22 02:38:28 +08:00
but in the mean time the grades for these students will come from the original course.
}) %>
2011-04-16 14:22:55 +08:00
</p>
<% end %>
<div class="button-container">
2012-11-09 13:59:16 +08:00
<button type="submit" class="btn submit_button"><%= t('buttons.decrosslit_section', 'De-Cross-List This Section') %></button>
Fully adopt Bootstrap & update css to work with it, closes: #CNVS-1344
this commit does the following:
* upgrade bootstrap-sass gem to most recent version
* switches to using bootstrap's normalize.css and forms.css
which fixes a whole bunch of misformatting of how bootstrap
stuff is supposed to look, but changing those 2 affects
a lot of our old stylesheets.
* gets rid of unified_buttons.sass and just uses bootstraps buttons.
.ui-button @extends these because we still have to support .ui-button
for modals & buttonsets. but .button is no longer supported.
* a lot of css file reorganization (there's no more 'blue' and
'normal canvas', there's just canvas)
* a bunch of files had to be tweaked to look good with these changes.
test plan:
This change touches every page in canvas so, no kidding, we need to make
sure every page looks OK. In order to do that:
1. each sprint team needs to give a +1 after they make sure all the
pages in the features they are over look good.
2. the QA person on each team needs to look at the pages for their
teams features for a QA +1
things to look for specifically when testing:
* buttons: this gets rid of all those red 'cancel' links
that are actually buttons, make sure all the buttons you see
look right. if you see 2 plain gray buttons next to each other
like [Save] [Cancel], we should make the primary one blue (by
adding the .btn-primary class)
* Forms: a lot of this change has to do with how form elements look,
especially <select>s, <input>s and <label>s. look at the diffs
for the ones that have the most changes and make sure those look
good, but also check for the ones I missed and make sure those
look good too.
* and just random style changes, if something looks ugly or broken
(and it didn't before), we should fix that.
Also:
just use a link instead of a drop-menu for adding event from sidebar
we used to have a drop down menu for adding events
to cal2 from the sidebar where you'd hit a cog
and it'd ask you if you wanted to add an event or
an assignment. this just simplifies it to an add
icon.
this: http://cl.ly/image/133a2A3q3q1M
instead of: http://cl.ly/image/46463o2s3W0g
Change-Id: I384fe273934bca96bf28423afb1402c7792d8766
Reviewed-on: https://gerrit.instructure.com/15422
Tested-by: Jenkins <jenkins@instructure.com>
Reviewed-by: Ryan Florence <ryanf@instructure.com>
QA-Review: Ryan Florence <ryanf@instructure.com>
2012-12-21 14:46:28 +08:00
<button type="button" class="btn btn button-secondary cancel_button"><%= t('buttons.cancel', 'Cancel') %></button>
2011-04-16 14:22:55 +08:00
</div>
<% end %>
</div>