Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-12T09:15:55Z

Xli47:

__TOC__
'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure. '''
==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
:If student ID is not provided, the system will randomly select an student ID from all the students in the database, and impersonate the selected student view. This is useful when the instructor doesn't remember the specific student ID.
:Required changes in 1 file : 
:[https://github.com/chaitanya91k/expertiza/blob/master/app/controllers/impersonate_controller.rb Impersonate_controller.rb] 
<pre>
if params[:user][:name]==""
students = User.all.where(role_id: Role.student)
user = students[rand(students.length)]
until original_user.can_impersonate? user
user = students[rand(students.length)]
end
end
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-12T09:14:19Z

Xli47:

__TOC__
'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure. '''
==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
:If student ID is not provided, the system will randomly select an student ID from all the students in the database, and impersonate the selected student view. This is useful when the instructor doesn't remember the specific student ID.
:Required changes in 1 file : 
:[https://github.com/chaitanya91k/expertiza/blob/master/app/controllers/impersonate_controller.rb Impersonate_controller.rb] 
<pre>
if params[:user][:name]=="" # if user id is not provided, assign an user id randomly
students = User.all.where(role_id: Role.student)
user = students[rand(students.length)]
until original_user.can_impersonate? user # make sure the random selected user could be impersonated by the original user
user = students[rand(students.length)]
end
end
</pre>
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-12T09:12:49Z

Xli47:

__TOC__
'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure. '''
==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
:If student ID is not provided, the system will randomly select an student ID from all the students in the database, and impersonate the selected student view. This is useful when the instructor doesn't remember the specific student ID.
:Required changes in 1 file : 
:[https://github.com/chaitanya91k/expertiza/blob/master/app/controllers/impersonate_controller.rb Impersonate_controller.rb] 
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors

2016-11-12T09:10:51Z

Xli47:

__TOC__
'''NOTE: The pull request will not pass the build.Its not due to our changes but due to some unrelated test failure. '''
==Background==
[http://expertiza.ncsu.edu/ Expertiza] is a web based open source peer reviewing tool based on [http://rubyonrails.org/ Ruby on Rails] developed and maintained by current and past students of [https://en.wikipedia.org/wiki/North_Carolina_State_University North Carolina State University], Raleigh. Students will be able to manage all their project submissions, project teamups, topic selections etc. Few of the notable features include:
* Instructor can control most of the stuff that is related to each course.
* Student can control who he/she wants to team up with etc.
* They can provide feedback to each of the topics.
* Instructor can make use of the various submission phases available.
== Introduction ==
Our project is to introduce a Student view to the instructors.The goal of this project is to provide instructor with a functionality using which an instructor can switch to student view and see how the student view looks like. The instructor will also be able to go to future date and see how student view looks like in future date.

==Project Requirements==
* Introduce a "Student View Button" on Instructors UI to switch to student view.
* Introduce a Revert to instructor View" on Instructor's Student UI
* Time travel in Student View.

==Working==
On the right top, left to the logout button , anyone having access to view as instructor gets a textbox and a button saying "Student View". in-order to view as a student you have to type in the students ID and press '''Student View''' button. You can exactly see what the student's page looks like.
[[File:HomeK6.jpg]]
 
If you need to revert back to instructor view you just have to leave the text box empty and press the '''Revert''' button. This takes you to the instructors view again. Else if you need another students view, just type in the students ID and press '''Revert'''.
[[File:HomeK3.jpg]]
 
We also have implemented a time travel feature where you can go to a particular date and see what a student see on that day. You can find this feature as soon as you go to a student ID. You have to select a day you need to travel to, type in the student ID and submit. Boom! you got he student view as on the date given.
[[File:HomeK4.jpg]]

==Implementation==
* Introduce a "Switch to Student View Button" on Instructors UI
:A 'Student View' button was added in the top right portion of menu-bar for instructor. This button allows instructor to see the student view. This button is linked to impersonate action of [https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller]. The button was simply added in menu-bar view. When the button is clicked, it calls <code>impersonate</code> method in <code>impersonate controller</code> which loads new view as student for provided student id. 

:Required changes in 1 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<pre>
<% if current_user.role.name == "Instructor" or current_user.role.name == "Administrator"%>
<%= form_for :user, url: '/impersonate/impersonate' do |f| %>
<TABLE>
<TR>
<TD><%= f.text_field :name, {:size => 10,:class => 'form-control input-sm', :autocomplete => "off",placeholder: "User ID"} %></TD>
<TD><%= f.submit 'Student View', :class=>"btn btn-primary input-sm"%></TD>
</TR>
</TABLE>
<% end %>
<% end %>
</pre>
:If student ID is not provided, the system will randomly select an student ID from all the students in the database, and impersonate the selected student view. This is useful when the instructor doesn't remember the specific student ID.
:Required changes in 1 file : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller.rb] 
* Introduce a Revert to instructor View" on Instructor's Student UI
:Once instructor impersonate to a student view, a Revert button appears which when clicked revert back to instructor view from impersonated student view. Once the student view is loaded by instructor,<code>session[:superuser]</code> is set and based on this flag a revert button will be displayed. 

* Time travel in Student View.
:Required changes in 4 files : 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/views/shared/_navigation.html.erb navigation.html] 
<div class="field">
<%= f.date_field :goto_date, :order => [:month,:day, :year],:value => Date.today %>
</div>
:First, we introduced a date box where you can select a date from the UI. 
[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/controllers/impersonate_controller.rb Impersonate_controller] 
if !params[:impersonate][:goto_date].empty?
User.goto_date=params[:impersonate][:goto_date]
end
:In this controller, we took the value from UI and store the same in User model. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/user.rb user.rb] 
attr_accessible :goto_date
def self.goto_date=(val)
@goto_date=val
end
def self.goto_date
@goto_date
end
:The value from the above controller is stored in Users model object (not instance) as goto_date. Thus you can access this date through out the sessions. 
:[https://github.com/chaitanya91k/expertiza/blob/93a9cd0a77a40383e26e90784d368e5d236ad74e/app/models/due_date.rb due_date.rb] 

def self.get_next_due_date(assignment_id, topic_id = nil)
(User.goto_date.nil?)? goto_date = Time.now : goto_date = (User.goto_date)
if Assignment.find(assignment_id).staggered_deadline?
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, Time.now]).first
next_due_date = TopicDueDate.where(['parent_id = ? and due_at >= ?', topic_id, goto_date]).first
topic_due_date_size = TopicDueDate.where(parent_id: topic_id).size
following_assignment_due_dates = AssignmentDueDate.where(parent_id: assignment_id)[topic_due_date_size..-1]
following_assignment_due_dates.each do |assignment_due_date|
if assignment_due_date.due_at >= Time.now
if assignment_due_date.due_at >= goto_date
next_due_date = assignment_due_date
break
end
end
end
else
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, Time.now]).first
next_due_date = AssignmentDueDate.where(['parent_id = ? && due_at >= ?', assignment_id, goto_date]).first
end
next_due_date
end

:When ever the system calculates due dates, the time is taken from goto_date that we have stored above in Users model. 

==Testing via UI==
* Login in as Instructor.
*Create assignment. I have created one with name Test_Changes with submission deadline Nov 09 and review Deadline Nov 14. Add all the student in course for this assignment
[[File:Svk1.jpg]] 
 
 
*Switch to student view. Once switched to student view you can see the assignment with submission deadline Nov 09.
[[File:Sv2.jpg]] 
 
 
*Go to future date and view the assignment list. I went to Nov 10 in future and we can see that the current phase for our assignment is review.
[[File:Svk3.jpg]] 
[[File:Svk4.jpg]]

==Why These Changes?==
* Requirement: Add a “student view” button for instructors.
:As we were required to add a button , it makes more sense to add a similar button used across the application. Thus we choose class="btn btn-primary" for buttons and :class => 'form-control input-sm' for textboxes.

* Requirement: Introduce a revert button to go back to instructor:
:After an instructor enters a student ID of a student and enters student view, there should be a way to go back to instructors . Thus we have introduced a revert button. Also if the instructor wants to go to a different student’s view he should be able to do so as well. Making these two tasks possible with single textbox and button was better instead of an extra button to go back to instructors view. Now to go back to instructors view, instructor has to leave the textbox blank and click “revert”, if the instructor wants to go to a different student’s view he just need to enter the new student’s id and click on “revert”.

* Requirement: View on specific date:
:We decided to include a date box which on clicked on the date field a data picker pops up. We have added this picker as it makes sense to just click on which date instead of typing the whole date.

==Repository==
[https://github.com/chaitanya91k/expertiza Expertiza Github link]
==Screencast==
Screencast [https://youtu.be/WrJm6csM3mo link] to our demonstration

CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation

2016-11-10T01:55:16Z

Xli47:

=='''Introduction'''==

==='''Servo'''===
[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] is an open source prototype web browser layout engine that is being developed by Mozilla Research. Its source code can be found [https://github.com/servo/servo here]. Current browser engines are mostly based on the single-thread model. The motivation behind building servo web browser is to build a highly parallel and reliable environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.

==='''Rust'''===
[http://doc.rust-lang.org/book/README.html Rust] is an open source system programming language developed by Mozilla. Rust is a language suited for creating a highly concurrent and safe system. In performance and syntax, rust is similar to C++ but semantically it is very different. Rust emphasis is on speed, safety and control of memory layout<ref>https://en.wikipedia.org/wiki/Rust_(programming_language)</ref>.

=='''Project description'''==
==='''Initial steps'''===
*compile Servo and ensure that it runs on tests/html/about-mozilla.html
*email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions
*uncomment the attributes in ValidityState.webidl and fix the resulting build errors by implementing appropriate stub methods in validitystate.rs
*make the ValidityState constructor take an &Element argument and store it as a JS<Element> member in ValidityState
*add a new enum that represents each possible validity check in ValidityState
*define a Validatable trait that contains a method which accepts this enum as an argument (see the Activatable trait for inspiration)
*implement this trait for the form element types (HTMLInputElement, HTMLSelectElement, HTMLButtonElement, etc.), and define an as_maybe_validatable *method on Element which returns an &Validatable value if the element implements the trait (see as_maybe_activatable for inspiration)
*Use the newly-added JS<Element> member to call these new methods as appropriate in each of the stub methods in ValidityState
==='''Subsequent steps'''===
*a method to HTMLFormElement that implements the steps to interactively validate the constraints of a form element
*Implement the checkValidity API for HTMLFormElement
*Implement the reportValidity API for HTMLFormElement
*Implement each validity state defined in the spec as applicable. This can include implementing support for attributes such as min, max, minlength, etc.
*Modify the implementation of the form submission algorithm to include constraint validation
=='''Design Patterns & OO Practices'''==
=='''Testing'''==

=='''References'''==
<references />

CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation

2016-11-10T01:51:59Z

Xli47:

==Introduction==

===Servo===
[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] is an open source prototype web browser layout engine that is being developed by Mozilla Research. Its source code can be found [https://github.com/servo/servo here]. Current browser engines are mostly based on the single-thread model. The motivation behind building servo web browser is to build a highly parallel and reliable environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.

===Rust===
[http://doc.rust-lang.org/book/README.html Rust] is an open source system programming language developed by Mozilla. Rust is a language suited for creating a highly concurrent and safe system. In performance and syntax, rust is similar to C++ but semantically it is very different. Rust emphasis is on speed, safety and control of memory layout<ref>https://en.wikipedia.org/wiki/Rust_(programming_language)</ref>.

==Project description==
===Initial steps===
*compile Servo and ensure that it runs on tests/html/about-mozilla.html
*email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions
*uncomment the attributes in ValidityState.webidl and fix the resulting build errors by implementing appropriate stub methods in validitystate.rs
*make the ValidityState constructor take an &Element argument and store it as a JS<Element> member in ValidityState
*add a new enum that represents each possible validity check in ValidityState
*define a Validatable trait that contains a method which accepts this enum as an argument (see the Activatable trait for inspiration)
*implement this trait for the form element types (HTMLInputElement, HTMLSelectElement, HTMLButtonElement, etc.), and define an as_maybe_validatable *method on Element which returns an &Validatable value if the element implements the trait (see as_maybe_activatable for inspiration)
*Use the newly-added JS<Element> member to call these new methods as appropriate in each of the stub methods in ValidityState
===Subsequent steps===
*a method to HTMLFormElement that implements the steps to interactively validate the constraints of a form element
*Implement the checkValidity API for HTMLFormElement
*Implement the reportValidity API for HTMLFormElement
*Implement each validity state defined in the spec as applicable. This can include implementing support for attributes such as min, max, minlength, etc.
*Modify the implementation of the form submission algorithm to include constraint validation
==Design Patterns & OO Practices==
==Testing==

=='''References'''==
<references />

CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation

2016-11-10T01:51:13Z

Xli47:

CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation

2016-11-10T01:49:56Z

Xli47:

CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation

2016-11-10T01:47:38Z

Xli47:

==Introduction==
===Servo===
Servo is an open source prototype web browser layout engine that is being developed by Mozilla Research. Its source code can be found here. Current browser engines are mostly based on the single-thread model. The motivation behind building servo web browser is to build a highly parallel and reliable environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.
===Rust===
Rust is an open source system programming language developed by Mozilla. Rust is a language suited for creating a highly concurrent and safe system. In performance and syntax, rust is similar to C++ but semantically it is very different. Rust emphasis is on speed, safety and control of memory layout.
==Project description==
===Initial steps===
*compile Servo and ensure that it runs on tests/html/about-mozilla.html
*email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions
*uncomment the attributes in ValidityState.webidl and fix the resulting build errors by implementing appropriate stub methods in validitystate.rs
*make the ValidityState constructor take an &Element argument and store it as a JS<Element> member in ValidityState
*add a new enum that represents each possible validity check in ValidityState
*define a Validatable trait that contains a method which accepts this enum as an argument (see the Activatable trait for inspiration)
*implement this trait for the form element types (HTMLInputElement, HTMLSelectElement, HTMLButtonElement, etc.), and define an as_maybe_validatable *method on Element which returns an &Validatable value if the element implements the trait (see as_maybe_activatable for inspiration)
*Use the newly-added JS<Element> member to call these new methods as appropriate in each of the stub methods in ValidityState
===Subsequent steps===
*a method to HTMLFormElement that implements the steps to interactively validate the constraints of a form element
*Implement the checkValidity API for HTMLFormElement
*Implement the reportValidity API for HTMLFormElement
*Implement each validity state defined in the spec as applicable. This can include implementing support for attributes such as min, max, minlength, etc.
*Modify the implementation of the form submission algorithm to include constraint validation
==Design Patterns & OO Practices==
==Testing==
===References===

CSC/ECE 517 Fall 2016/ M1653 Implement HTML form validation

2016-11-10T01:40:49Z

Xli47:

==Introduction==
===Servo===
===Rust===
==Project description==
===Initial steps===
*compile Servo and ensure that it runs on tests/html/about-mozilla.html
*email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions
*uncomment the attributes in ValidityState.webidl and fix the resulting build errors by implementing appropriate stub methods in validitystate.rs
*make the ValidityState constructor take an &Element argument and store it as a JS<Element> member in ValidityState
*add a new enum that represents each possible validity check in ValidityState
*define a Validatable trait that contains a method which accepts this enum as an argument (see the Activatable trait for inspiration)
*implement this trait for the form element types (HTMLInputElement, HTMLSelectElement, HTMLButtonElement, etc.), and define an as_maybe_validatable *method on Element which returns an &Validatable value if the element implements the trait (see as_maybe_activatable for inspiration)
*Use the newly-added JS<Element> member to call these new methods as appropriate in each of the stub methods in ValidityState
===Subsequent steps===
*a method to HTMLFormElement that implements the steps to interactively validate the constraints of a form element
*Implement the checkValidity API for HTMLFormElement
*Implement the reportValidity API for HTMLFormElement
*Implement each validity state defined in the spec as applicable. This can include implementing support for attributes such as min, max, minlength, etc.
*Modify the implementation of the form submission algorithm to include constraint validation
===References===