Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

19 -- MVC! MVC! - J. Spencer Hopkins #158

Open
20 of 28 tasks
jspencerhopkins opened this issue Feb 6, 2015 · 1 comment
Open
20 of 28 tasks

19 -- MVC! MVC! - J. Spencer Hopkins #158

jspencerhopkins opened this issue Feb 6, 2015 · 1 comment

Comments

@jspencerhopkins
Copy link

Tasks

  • A WIP Issue in the class repo _(S)_
    • Titled appropriately
    • With check boxes for the tasks and any subtasks you can identify
    • Estimates for the top-level checkboxes
  • Update your TIY-Assignments wiki _(S)_
    • End of Day:
      • Assignment Evaluation
      • Lightbulbs
      • Things I Don’t Get Yet
  • Create a branch in your TIY-Assignments repo, named appropriately _(S)_
  • A Pull Request in your TIY-Assignments folder as on previous assignments _(S)_
  • Comments on your WIP Issue as on previous assignments _(S)_
    • Link to Wiki
    • Link to Pull Request (in Markdown)
  • Build the TodoMVC project in Rails. _(XL)_
    • The functionality should follow the spec, with the following exceptions:
      • New todo - Add a button (don't just press Enter) to create the todo, appends it to the todo list and clears the input.
      • Mark all as complete - Also requires a button for this and the 'clear completed' check box
      • Item - Again, a button alongside the checkbox to mark as complete. You'll also need a link to edit an item.
      • Editing - takes place on its own page; requires a button to save; there's no editing class; have a link to return to the list
      • Persistence - SQLite
      • Routing in Rails
  • You can make use of the HTML in their template and the CSS in the template for that. Use Rails helper methods wherever possible (in the form, for example). _(S)_
  • This project will have multiple levels of difficulty.
    • Level 1: Complete the functionality described above.
    • Level 2: Add due dates to the tasks. Display tasks differently depending on whether they are overdue, due today, or due in the future.
    • Level 3: Add support for multiple users. Each user should be able to view and edit only his/her own task list.
    • Level 4: Add support for multiple task lists for each user. Each list should get its own label, and the user should be able to navigate between all of his/her own lists.
@jspencerhopkins
Copy link
Author

todo wikis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant