mfoster / breeze Goto Github PK

The ability to administrate the models in a simple edit/view interface. Use django's built in admin.

Let's put a tiny bit of time against this every so often and we will make something happen and hopefully it won't be too shitty.

Basic layout with django templates and css/js included through asset pipeline.

Use django settings structure to correctly configure the breeze application.

One of the ways we can save people time in entering tasks is to guess at the task type. Eventually it would be great if this was more flexible, but for now a basic list of types, and words that are associated with those types will be a great place to start.

Basic Types I'm envisioning:
social
create
resolve
obtain
plan
improve
maintain
research
decide
organize

Sure I'm missing some, but trying to keep these generic, then we can start making some more specific ones.

nom nom nom

breeze works great for a wip name, but definitely want to keep names in mind we can use for the final!

Couple to get us started:

taskorama
taskagogo
shuffledo
upnext
uber achiever
whatsfordoing
w4d
dodo
tasksat
task 'o matic
do 'o matic
plan 'o matic
Feel free to add more, rather have too many, and a hard time choosing the perfect one, than settle for the ok one!

Make it so Activities can be clicked, and then can be edited or started in place of the current Activity.

Initial form contains text field for title
assumes:
time: 25 minutes
due in: 1 week
category: create (unless it contains special keywords)

secondary section of the form contains options for editing those attributes.

Actually write tests for breeze specific operations.

Server up the next activity, accept, add time, complete activities.

NOTE: open to calling tasks actions, or tracks, or item, etc.

A task has:

a name, such as "Pluck nose hair"
a type, such as "Grooming", "Communication", "Creating", etc. May be tags, and may have multiple.
an estimated time amount, possibly called "chunk" as in: 5min chunk, 25min chunk, 50min chunk
a day and time it becomes available
a day and time it is due
the ability to be scheduled at a specific time, as in a meeting
a creator
a person/people who are responsible for it
a day and time when it is started
possibly a number of times when it is paused and restarted
a day and time when it is completed
Nice to haves:

repeat interval for repeating tasks
ability to be grouped in a project
ability to be assigned to a group
pre-requisite tasks
the ability to track how many times it has been deferred to later
the data on how many times and by how long its time estimate has been lengthened
awareness of its context, which may include location, time, etc.
a parent to track a tasks ancestry, and can be used to see when one task sparks more tasks
These are some just general thoughts, so we can start thinking about what this app needs to be able to do. From a UX perspective, I want to make as many safe assumptions for things like due dates and categories as possible, while giving people the ability to quickly change anything they need to.

Make it so the list can be reordered by dragging items in the list.

prototype application that Greg created needs to be merged with breeze