MarkUs Blog

MarkUs Developers Blog About Their Project

MarkUs February 26th Punchlines

with one comment

Brian

Status:

  • Finished ticket #531
  • Flexible scheme prototype is created
  • All views including admin/grader/students are created/modified for both flexible and rubric schemes
  • database migration is updated (float number mark can be input now)

Next Steps:

  • warning info for switch between different marking schemes (other related UI issues)
  • “disconnect” old records after switch to different scheme
  • more css files will be modified
  • Bryan is working on test with me, test cases will be done at the same time we finish the components.

Roadblocks:

  • Traveling back to Canada

Robert

Status:

  • Converting Assignment and Student unit tests to shoulda and Machinist

Next Steps:

  • Make the required changes to the Notes system. AKA be able to add notes to the new noteables, and their modal dialog invocations.

Roadblocks:

  • Midterms sucked up more time this week than I wanted.
  • Converting tests to shoulda requires more work than simply converting them to machinist. The tests need to be in a sensible order.
  • I’m in California for 4 nights this coming week interviewing with companies that rhyme with Placebook and Bluegle. [Then again… I’ll be stuck on a plane and in airports, with nothing to do but  whatever I’ve got on my laptop, which does include MarkUs….]

Victoria

Status:

  • Together with Nelle, we discussed how to make the Sections feature more usable.  Suggested that we create a new top-level view/tab called “Sections” where the user can create and manage course sections.  This has been approved by Karen in last night’s UI/UX meeting.
  • Also suggested that we move the “Sections” column in Users > Students view to the left of the “Grade Credit” column.
  • Collected usability/design issues currently found in the Assignments > Properties page.  Again, discussed these with Karen in last night’s meeting and they have been approved/reassured.

Next Steps:

  • UCOSP midterm blog post.
  • File tickets for usability issues in “Properties” page.
  • Rework Grade Formation tab prototypes according to usability feedback we got from Diane and Jen.
  • Brainstorm ideas for Dashboard view.

Roadblocks:

None.

Mike

Status:

Next Steps:

  • Same as always – continue to review code as it comes in.  Answer questions and help where I can.

Roadblocks:

  • None

Farah

Status:

Next Steps:

  • Changing “out_of” for grade entry items to type float (see http://review.markusproject.org/r/391/) has introduced some test failures so I need to investigate and update the tests
  • Finish the student UI and take a look at how marks are currently released/unreleased for assignments in order to implement something similar for grade entry forms
  • Remaining smaller tickets related to CSS, AJAX (#600-#602)

Roadblocks:

None this week

Bryan

Status:

  • Manually tested Brian’s implementation of flexible marking scheme and gave him some feedback
  • Studying and updating the existing functional and unit tests for rubrics and flexible marking scheme

Next Steps:

  • Test the views related to flexible marking scheme

Roadblocks:

  • None this week

Joseph

Status:

  • wrote a couple blog posts about maintaining state between AJAX calls inside the URL using hrefs and document.location.href
  • came up with two possible ways to fix the nested form issue on the submissions page
  • easier way, use javascript on the dropdownlist’s onchange to set document.location.href. This will redirect the page, similar to a form’s GET method. As a result, the form around the dropdownlists are no longer required. We will not longer have the nested form issue.
  • harder way, use javascript on each checkbox’s oncheckchange inside the table to update a hidden field in the unrelease/release mark form. This way, the form no longer has to contain almost the whole page. As a result, the form will not longer be nested with the dropdownlist’s forms.
  • working on the easier idea to verify that it works

Next Steps:

  • at the meeting verify that the solution is not too big of a hack
  • ask about ways to test this. Should it be whitebox tests using Selenium?
  • finish off the implementing the easier one
  • if it does not work, try out the other idea

Roadblocks:

  • None this week

Written by bryanshen

February 25th, 2010 at 9:15 pm

Posted in Uncategorized

One Response to 'MarkUs February 26th Punchlines'

Subscribe to comments with RSS or TrackBack to 'MarkUs February 26th Punchlines'.

  1. […] Posted by brianxu on 2010/03/01 The MarkUs team’s status punchlines for this week can be found here. […]

Leave a Reply