CSC/ECE 517 Fall 2017/E1796. Unify Create Assignment and Edit Assignment pages

From Expertiza_Wiki
Revision as of 03:23, 8 November 2017 by Uagrawa (talk | contribs)
Jump to navigation Jump to search

E1796. Unify Create Assignment and Edit Assignment pages

The current new assignment UI is a Rails based From, while the Assignment Edit Form is a multi level JavasScript based form (view/assignment/edit/.*) that consists of multiple inputs and user interactions. When an instructor creates a new assignment, there are only a limited parameters that he can set in the creation page, then (s)he needs to edit the assignment to define the rest of the parameters. This is confusing and needs to be unified. One solution could be ditching the new assignment form (views/assignment/new.html.erb)

Introduction:

Problem Statement:

In the Expertiza portal presently when an instructor wants to create a new assignment then as he selects a new assignment option only a few metrics are asked for while for mentioning the other metrics the professor needs to edit assignment and then under that he is shown the options to edit all the other metrics.

Scope of this Project:

Specific Improvements to assignment creation by navigating the user for creating a new assignment to edit assignment page(view/assignment/edit_assignment). Making sure the edit assignment has blank fields in case of new assignment and saved fields in case of editing. Fixes to tooltips so that it is supported across all the browsers Change the save button to AJAX request instead of HTML form submission so that the page doesn’t need to get refreshed every time the user save the changes.


Current Flow:

This page is displayed in the present system when a professor wants to create a new assignment as we can see there are only very few metrics on this page which are being displayed.




While under Edit assignment the professor can now mention all the various metrics regarding the assignment on this page.


Design Pattern

1.MVC – The project is implemented in Ruby on Rails that uses MVC architecture. It separates an application’s data model, user interface, and control logic into three distinct components (model, view and controller, respectively). 2.Dry Principle – We are trying to reuse the existing functionalities in Expertiza, thus avoiding code duplication. Whenever possible, code modification based on the existing classes, controllers, or tables will be done instead of creating the new one.

Files to be Modified

view/assignment/edit/.* views/assignment/new.html.erb views/assignment/* controller/assignment_controller.rb