The MarkUs Team is proud to present MarkUs 0.7.0!
Posts Tagged ‘MarkUs’
Posted by Mike Conley on 2010/04/29
Posted by Mike Conley on 2010/03/20
The MarkUs Team is proud to present 0.6.3! Full details here.
Posted by Joseph on 2010/03/19
- Brainstormed ideas for the Dashboard.
- Went through draft Dashboard contents with Karen and Farah and got some good and constructive feedback
- With the feedback I got back regarding the potential Dashboard contents, come up with a preliminary prototype — one that we can take apart and help establish a better idea as to how we’d like to design the Dashboard.
- Swamped with work (from my full-time position).
- Applied 0.6 patches to trunk
- Also caught some missing translations and brought them over from 0.6
- Reviewed a bunch of code
- Email / IRC development support
- Same as always – review, review, review. Answer email. Help where I can.
- Finished implementing the ability for an instructor to release/unrelease the marks for grade entry forms
- Submitted a review request (in two parts) for the student UI and releasing the marks (see http://review.markusproject.org/r/458 and http://review.markusproject.org/r/459/)
- Modified the table view so that the text boxes for entering grades are smaller
- Worked on unit tests for the student UI and releasing the marks and submitted a review request (see http://review.markusproject.org/r/473/)
- Work on functional tests for the student UI and releasing the marks
- Implement CSV upload/download for grade entry forms
- Tests for CSV upload/download
- None this week
- Met with Mike on Tuesday to discuss how to test the server side pagination
- renamed ajax pagination helper to pagination helper ( http://review.markusproject.org/r/470/ )
- migrate the submissions_controller_test from fixtures to machinist ( http://review.markusproject.org/r/474/ )
- continue with the testing
- finish of the suggestions from reviewers
- get a start on the detailed submissions view
- Wrote a draft version of user stories: assigning graders to criteria.
- Introduce factory data preloader, which can be used in conjunction with Machinist and improve its speed. Modified the results_controller_test.
- Finish the class diagram and database schema for the feature “assigning graders to criteria”
- Plan how to use single table inheritance to implement flexible and rubric criterion
- Find a good pattern for factory data preloader
- The ability to create Notes on Assignments, and Students from the new notes page is complete and awaiting final approval.
- Added tests for the new noteables to the Notes Controller Test
- Converted Notes Controller Tests to Machinist
- Added a Machinist blueprint for Notes.
- Add the notes dialog links to the Student pages and the Assignment pages.
- Convert the Student and Assignment tests to Machinist and Shoulda.
- Fix a small bug Ticket #622
- Working on refactoring database, doing some test
- Improving flexible schemes
- make flexible scheme ready to ship
- make prototype of new database design
Posted by Mike Conley on 2010/03/06
The MarkUs team is plowing forward, fleshing out some fantastic new features, and kicking a bunch of bugs to the curb! You can read our meeting minutes here.
Posted by Joseph on 2010/03/01
Things I have learned:
- Ruby and Rails
- Shoulda 
- Mocha reminds me of mocking JUnit tests in Java  
- will_paginate: an elegant plugin for performing pagination 
- keeping state with in URL when doing AJAX calls 
- Word Press and Blogging: I have blogging fever. I cannot stop blogging about everything I have learned. I just hope someday a stranger will comment on how helpful it was.
Things I have completed:
- when the Markus webserver boots up, it verifies that the settings inside the configuration file located at: <markus_root>/config/environments/<env>.rb are valid. For instance, if the password validation script is not executable, a message will be printed to the console and the webserver will stop starting up.
- got the AJAX calls from ahrefs to to save state into the URL 
- implemented a mock submissions page that used serverside pagination to compare the performance with AJAX pagination
- since the performance was similar, Markus has decided to go with the serverside pagination because of all the loops we would have to jump through to get the AJAX pagination to work with the back button and bookmarks
Things I am working on:
- switching from AJAX pagination to serverside pagination so that bookmarks and the back button will work again
- encountered a large speed bump dealing with nested forms
- going to blog about the work around after I have verified that it works
Things to work on in the future:
- verifying that the serverside pagination has not changed the behaviour of the submissions page
- detailed view for the marker’s or admin’s submissions page
- cleaning up the serverside pagination code to take advantage of the conciseness of will_paginate . This will involve implementing a custom link render so that the submissions page’s UI does not change. The links generated by will_paginate looks like: “Previous Page 1 2 3 4 5 6 7 Next Page”. The links on the submissions page looks different.
 – Nested Contexts – http://josephmate.wordpress.com/2010/01/31/nested-contexts/
 – Mocking Modules with Mocha – http://josephmate.wordpress.com/2010/01/31/mocking-modules-with-mocha/
 – Weird Behaviour of Mocha- http://josephmate.wordpress.com/2010/01/31/weird-behaviour-of-mocha/
 – Will Paginate and Markus – http://josephmate.wordpress.com/2010/02/15/will_paginate-and-markus/
 – Rails, AJAX, Back Buttons, and Bookmarks – http://josephmate.wordpress.com/2010/02/20/rails-ajax-back-buttons-and-bookmarks/
 – will_paginate – http://railscasts.com/episodes/51-will-paginate
 – Hofstadter’s law – http://en.wikipedia.org/wiki/Hofstadter’s_law
Posted by victoria on 2010/02/28
Expectations, Status & Progress
Coming into this UCOSP project course, my ultimate goal was to be able to utilize the human-computer interaction (HCI) and user experience (UX) design knowledge that I’ve acquired from both school and work to enhance the usability of MarkUs. Through this experience, I’m hoping to solidify my understanding of various usability concepts and familiarize myself with more projects out there.
Up until now, I feel that I’m on track with the work that I’m doing with MarkUs. I’ve been spending most of my time redesigning and reorganizing a lot of features and functionality MarkUs currently offers. There’s no better way to do this than to keep prototyping and getting user feedback through usability sessions. Because of my full-time position, I have not been able to collect as much usability feedback that I’d like to in person. But I’ve found that running these designs by the team is often just as helpful. But most importantly, having a supportive supervisor to help collect the user feedback certainly helps me since I am working remotely most of the time.
In short, I think I’ve stayed on track because: I have already redesigned quite a few views; and have made various suggestions to the overall MarkUs interface.
Things I’ve learned thus far
In the past, I’ve done very little usability work for web-based applications, and I’m also very new to designing interfaces from scratch. Thanks to my team, I’ve learned quite a few things about designing web interfaces in particular. For example, small things like screen resolution will have a huge impact on the usability and presentation of the entire user interface. So it’s certainly something that needs to be considered early in the design cycle, and kept in mind at all times.
Another key thing that I’ve learned up until now is the prototyping tool, OmniGraffle. Instead of seeing the tool as being a burden, it has now saved a significant amount of my time. For example, I am now more comfortable using new canvases and layers in my prototypes wherever I see fit.
In the remainder of the course, I plan to continue working on the UI of MarkUs. I focused on the Grader Assignment and Group Formation views for the first half of the term, but those have now been addressed. Next, I am planning to tackle the Properties view – our goal is to make the Properties view intuitive to not just regular users, but also those that are using MarkUs for the first time. New designs for the MarkUs Dashboard are also to come.
I’d also like to maintain the good communication and coordination we’ve had as a team in the weeks to come.
I’ve had an awesome time working with the team, and I’m looking forward to the rest of the term!
Posted by jerboaa on 2009/11/24
Thumbs up: Our great teamwork. Although we are working in a distributed setting, I do find it astonishing how well everything worked out. People are doing a great job in terms of communication.
Thumbs down: Having a pretty tight schedule, I think there was hardly time for one or two developers to go for a spike (i.e. looking into an unknown technological area) and create an example solution to a problem.
Posted by Mike Conley on 2009/09/11
The MarkUs team had their first IRC meeting today.
Or you can read the transcript here. (Meeting starts around 16:04)