nycdavid / aristotle-v2 Goto Github PK

User's should be able to go back to a previous calendar and look at how much time was put in that day

As a user
I want to delete my existing Pursuits to keep things organized

• Pursuit deletion is initiated from the Edit pursuit page
• Deleting requires confirmation
• Deleting a Pursuit deletes the pursuit and all related data to it
• Successful deletion returns the user to the Pursuits dashboard

Chrome has an inactive tab policy that runs intervals (of any speed) down to 1000 ms. This causes the timer to run behind when in an inactive tab.

• Reset the cumulative time and pomodori count for daily reports
• There could be a link on My Pursuits page that changes context:
  Today | Total

• Exactly as the title says, via Celluloid or some other concurrency lib.

Aside from the convenience of being able to continue a pomodoro after having navigated away from the page, it solves the odd issue of when a person has opened two (or more) pomodori in the browser. These become two (or more) autonomous timers that will count toward the pursuit.

Bookmarked links, when logged out, give a 404. Probably how the auth currently handles it.

So flow would end up working

1. Access URL

   If this is not a valid URL, 404 else continue to (2)

2. If requires auth, force login

   If success, redirect back to (1) else 401 (and/or redirect to sign-up)

As a User
I want to be able to bookmark pages and be returned to last visited page once I've successfully 
signed back in.

• If the bookmarked page ends but being a 404 it should redirect the user to the login.

  I should not initiate any type of post-login redirecting of anykind

• User is redirected back to the last visited page when required to re-login

• If the last visited page ends up being a 404 or unaccessible it should redirect the user back to the main dashboard

Quit, was a bit misleading, to me at least. Quit should probably be separated into 2 new buttons.

1. To actually quit and log the time. A basic "stop/quit early" option
2. And some kind of "cancel/discard" in case you started a timer by accident.

Fix tests so they don't rely on EDT as the timezone of the environment

A good readme with some setup instructions and how to get the tests running would be nice.

We don't need Angular for just the timer

Timing mechanism is going to be very simple client side JS

The link to whatever is currently chosen should be replaced with text so you immediately know which one you're on.

Should have links that lead to:

• Analytics
• Pursuits

...etc.

When in the daily view, the user:

• Should be able to view a total time/pomodoro completed today

1751dbb#commitcomment-9399831

For breaks or just regular timing.

Timer should have a new design with some sort of clock or timer running out motif.

Too much going in places it shouldn't be.

Title tag should have time remaining

Not exactly a bug, but I would like the Protractor E2E test suite to be run as a part of the Circle CI build chain, for obvious reasons.

There should never be duplicate emails

No need for anything crazy. Just something functional

• Might allow identifying of patterns in productivity

At the turn of every minute, 60 seconds is displayed. i.e.

24:60 instead of 25:00

Pursuit and Default pomodori settings should all be done in one page.

Related issues are #18, #17

As a User
I want to be able to create and edit a pursuit with pomodoro settings in one step.

• Ability to define default pomodoro settings when creating the pursuit itself

• Timer settings take only a Minute value, eg. 25 => 25 minutes

• Minute values can be selected from a dropdown list at 1, 2, 3, 5, 10, 15, 30, 60, etc... or input as like an input value

  This is a mix of dropdown + input text field.

• Successful creation redirects the user to begin the first pomodoro

• A valid pomodoro length/time is required

• Length/time should always be saved in seconds

I've been doing this in a very complicated way but I believe I can just use String.rjust

to take advantage of available NPMs and write in a node (cough io.js) style.

Might event be able to use io.js stuff with a shim (es6 stuff won't be full supported without it).

https://github.com/browserify-rails/browserify-rails

• Include a test for format in integration test for cumulative time
• It should display in the format %h:%m:%s

Github-style grid that changes color according to the pomodori performed in a day.

• How should this look?
• Where does it reside?
• What kind of external hooks should it listen to? Github, bitbucket?