Client-side validation the signup form fields?

Based on static_pages/thumbnail.html.haml

Rails relative time methods?

The implementation of the access controls on all the controllers needs to be completed.

Now that the model refactoring has been performed, MC questions need to be fixed to work again, including correct handling of attempt/answer recording. Use the current coding prompt/answer structure as a model.

Replace the roll-your-own "url_part" support in various model classes with FriendlyId support instead. Also, move from having all models use top-level urls, to providing scope-based urls that match logical breadcrumbs instead.

Need to import the CodingBat exercises from @s-edwards' CodingBat exercises. Should be done through creating the YAML file containing all these coding exercises and using the importer to upload them on PROD.

Priyanka did some prototype screens that included breadcrumbs, a feature we had discussed as useful. These should be included for Torch. We need to figure out the appropriate strategy and build it into our pages/controllers now, instead of trying to add it later.

Redo the breadcrumbs done in #16 so that they will work in a consistent manner with the new organization of entities.

Get rid of the custom tag model and use this gem instead. Refactor tag support to use different tag fields for different types, and use the gem's features to build an appropriate filterable tag cloud.

They currently don't display any useful info. These need to be fixed so that appropriate feedback is generated. This probably involves updating the coding prompt answer class to include this error feedback when no test case results are available.

Currently, when a student practices an exercise, the exercises_controller sleeps a fixed delay (3s) before returning (line 610). This is because immediately after the answer submission, the client code attempts to retrieve the results via an ajax call. The sleep is broken, since there is no guarantee the results will be ready after that time is up, and it effectively is a broken strategy to turn the async answer processing into a synchronous call (!). The sleep should be removed, and instead feedback results should be pushed from the server via HTML5 server-side push, instead of pulled from the client after submission.

The exercise edit page does not correctly work with the current exercise versioning scheme. After editing, the newly created version does not receive copies of any relationships or nested objects (e.g., tags, coding question). Further, the editing page takes the browser right back to the same (starting) version instead of the newly produced version, making it appear that changes are unsaved. In addition to directing the browser to the correct page, a flash notice should probably be included to make it clear that changes were saved and a new version was created.

During the practice of the exercise, the CodeMirror area is display in a funky manner instead of the horizontal scrolling being done in a graceful manner. Probably need to fix how we are doing it with CodeMirror.

Need to redo the way that a student navigates through the exercises in the workout. Currently, the list of 'remaining' exercises are maintained in params/session but this does not safeguard against situations where students might be jumping around workouts exercises. Need to develop a consistent mechanism that will suggest the next exercise that a student is led to by the 'Next exercise' link.

Probably be ought to be done as a model class method rather than a controller method.

Use bootstrap css to cause two-column displays of thumbnails fall back to single-column for narrow screens.

The record_workout_score method is present in two different places (mainly in CodeWorker) and needs to be refactored so that it made as a class method of WorkoutScore instead. Need to redo it so that it takes into consider the workout_id while recording attempts, so this entails redoing the relationships between Attempts and Workouts. Any other comments?

Workouts are missing a small thumbnail view, and have a broken large thumbnail view.

On the pages that show lists of course offerings, we need to add self-enrollment links for those offerings that the current user is not enrolled in, if those offerings do allow self-enrollment. These pages include:

/courses
/courses/<organization>
/courses/<organization>/<term>

In addition, we should modify the course show page (which is at /courses/<organization>/<term>/<course>) so that, if the current user is not enrolled, it shows the list of offerings including self-enrollment links/info, for those where self-enrollment is available.

Also, we need to update the course offerings model to include an optional cut-off date for self-enrollment. New course offerings that allow self-enrollment should use use the end date of their associated term as the default cutoff date, but the instructor should be able to change this date. After the specified date, self-enrollment should be closed (no longer available).

How should VT users login? Perhaps we should just use VT G-mail credentials for logging in students? We need to figure out the procedure and instructions so students can begin using CodeWorkout in summer.

There is already some setup for this on the page, but the problem is when multiple course sections are shown. If there are multiple sections, they currently all use the same dom ID names for the tables, and for the paging controls. That won't work. Instead, those ID names need to be specific to each course offering. Also, I ended up removing the roster partial, since it didn't seem to be doing anything useful--instead, we can probably go with just the row partial like Pythy. However, this means the show.js.coffee view is out of sync and paging doesn't work at the moment.

It should be implemented as a modal, using the ajax-based progressive refinement approach used on Pythy's front page.

There is already an "X", but it needs to be turned into an action that deletes the corresponding course enrollment and refreshes the corresponding table on the page. Note that there may be multiple tables on the page if multiple sections are available, and the correct table must be refreshed.

This role shouldn't exist. All instructor-level permissions should be role-based, relative to the user's course role in the relevant course offering. There should not be any "global" permissions for instructors.

Effectively, the only "global" role should be for admin accounts, and all other accounts should be globally "equal", and use only role-based permissions.

Need to validate the CanCan permissions on CodeWorkout in a systematic role-based way before Husky after the core system is completed for Torch. Need to both test it ourselves and use some 'student/instructor' role-players to test it around.

with user_id, workout_offering_id, soft_deadline, hard_deadline.
(for exceptions)

Update the evaluate action to use the new model for attempts. The evaluate action should create the attempt, and create the corresponding prompt answer(s) from the field values, storing the answers. Then the id for the newly created attempt is what get posted for the worker to process.

In addition, the code worker needs to be updated to use the new attempt model.

Exercise thumbnails need to include meaningful point displays even when the exercise is not associated with the current workout, and need to include meaningful points earned info if the current user has completed (or attempted) it. At present, the logic for displaying points earned + total points in thumbnails is incomplete and needs to be redone. It does not appropriately tie into XP when exercises are outside of assigned workouts.

The exercises_controller#random_exercise method limits results to id numbers >= 200. This is an artifact of the test database used during development, and should be fixed to use the full range of available exercises. Also, double-check that it only pulls from public exercises.

Ensure that the scores being calculated for individual exercises and for workouts are correct. This needs to be tested with exercises where different test cases have different weights, and for workouts where different exercises are worth different numbers of points, and for workouts where some exercises are partially correct but not fully correct.

Make sure the gradebook views on the course show page work correctly for students, as well as for staff. Also, make sure they do not show for individuals who are not enrolled.

The Workout model has a validation rule that requires workout names to be between 1-50 characters in length. The corresponding validation error message describes the same thing, and limits the characters that can appear in workout names. However, the database schema does not have this length limit.

Is this length limit necessary for some reason, or can it be removed? Similarly, is the character set limitation necessary for some reason, or can it be removed?

Both for exercises and for workouts. We also need to ensure the overall workout "show" pages correctly show both individual exercise scores and also the total score for the whole workout correctly.

There are currently two styles of thumbnails for both exercises and workouts. The original intent was for one to be a smaller sidebar-only version, while the other would perhaps contain more content/detail for use in the main content area.

However, at present, these two are virtually identical except for the css tag of the main element. It would be possible to merge these pairs into one view per model instead of having two. An additional view parameter could be used for indicating lg vs. sm, for customizing css tags, adjusting teaser text length, etc., if there are no significant logic differences between the two views. Should we do this?

Currently, the exercise controller is the center of activity for exercises, but base_exercise is actually the central entity, with "exercise" objects actually being versions of the exercise along a history trail of edits. It would probably be better to make BaseExercise the center for editing exercises, although we still want "exercise" to be the word used in routes. This would require some refactoring, however.

The add/remove links in subforms for things like the exercise editing page appeared to stop working at some point. I think this is because the link construction is incorrect and doesn't follow formtastic conventions. Double-check whether these work correctly, since we need them so that full editing can be achieved.

See the export comments. We eventually want to be able to do effective round-trip export/import in a consistent way, both to support external authoring, to support other tools, and to provide for convenient external storage.

You know what I mean :-).

On pages where the sidebar has workout contents, or on search results pages that show thumbnails of exercises or workouts, a large number of DB fetches are generated. This is because of the cascading nature of the relationships involved. Showing one thumbnail requires accessing many objects--for each tag, as well as for the user's latest attempt or score, etc. However, if this results in 1/2-1 dozen fetches for one thumbnail, that is multiplied by the number of thumbnails being rendered. We should consider preloading tags (at least) in the fetches that generate the list of thumbnails to render.

Ideally, the relationships that lead to the displayed lists of thumbnails should be defined to include the tags relation as preloaded.

Use the rough prototypes created by Priyanka as a guide.

Need to figure out how to do server-side push to students to receive feedback on their exercise practice on development. This is done to give indications for issue #15.

The "Create your course" button on the homepage should be revised to be a modal with a progressive refinement-style search interface (it really means creating a course offering, with the addition of creating the associated course if necessary). This part of the UI also needs to include conditional registration if the user hasn't registered yet.

Fix displaying of scores in thumbnails, as well as overall workout scores in workout show pages.

The error is:

ActiveRecord::RecordNotFound (Couldn't find Exercise without an ID):
app/views/layouts/sidebar.html.haml:14:in `app_views_layouts__sidebar_html_haml_...'

The sidebar needs to be fixed so that it does not assume a current workout is actively being practiced.

Add a pythy-style button that supports manual enrollment of individual accounts or bulk upload of CSV files to the roster tab on the courses page. There should be one button per course section, when multiple sections are shown (inside the loop over @course_offerings).

I added csv shaper for doing the csv export support for exercises. We should use it for other csv generating tasks, since it does make the code nicer and cleaner. It is currently implemented so you can write "views" that produce pure csv.

The code in this method assumes that all of a user's attempts in a workout are stored sequentially by id, and that they are contiguous with no other user's attempts in between. This is plainly flawed, and the method needs to be rewritten. Overall, it looks like the whole attempts infrastructure needs to be rewritten :-(.

Currently, time/date display is done through default rendering only. We need to provide appropriate user/profile settings so that users can choose their preferred time zone (and/or display format?), and provide more appropriate displays of dates and times on pages that show them. We need a convenient way to manage this so we don't have to put bulky code in every view that displays time info.

We need to provide for appropriate permissions enforcement, but it would be good to have a useful JSON-based export format, instead of (or in addition to) CSV.

Boolean checkboxes for attributes in formtastic forms don't seem to work correctly. Is there javascript missing, or is it some other problem?

According to Krishnan, this could be due to javascript code that auto-clears all checkboxes. See application.js line 79. This should be removed (and the root problem fixed).

Exercise thumbnails (both small and large) currently include an icon. Right now, there is one fixed icon for all thumbnails, but the icon should be based on the exercise type (MC = glyphicon-th-list, coding = fa-file-code-o or fa-keyboard-o?) instead.