of course we need some user feedback on a spinner
- refactoring for better long term use

When I 1st started with OOP I would often build components in to a class
like this form we've been using. Then later we'd need it again, and like
an idiot I'd build it again.

Pain ensues.

Now I'd actually start out building forms (and other parts we've already
built) in to a template-taps.php file so that I can call them from any
class that I need them in later.

This refactor moves our forms out of the main class and puts them in a
template tags file.
of course we fix our documentation like awesome people
of course we should be checking caps here to make sure that a user can read the tasks
making sure that our ajaxin form looks right
- refactoring to show our form

Now we can show our form in the frontend of the site.
- calling our form and refactoring for existing data

Now we actually call our edit form and at the same time refactor it so
that:

1. It can take existing data in a task
2. It has a cancel button if we want to cancel the edit of a task
- refactor our single task so that we can place the form

Now we have refactored our single task so that we have a great spot to
put the form and we can hide the existing task data when/if we have a
form.