Timer javascript is loaded at every page.
If you push spacebar the timer starts in background, this is not the requested behavior.

users should be awarded with badges

a user should be able to select timer layout between

1. fixed timer with progress bar
2. fixed timer without progress bar
3. moving timer with progress bar

Squashing a tomato or a break leaves a grey box in the top left of the screen.

use faye on heroku to put some realtime in tomatoes:

1. realtime ranking updates
2. follow users running tomatoes

documentation:

• http://faye.jcoglan.com/ruby.html
• http://railscasts.com/episodes/260-messaging-with-faye?view=asciicast
• https://github.com/ntenisOT/Faye-Example-Application
• https://github.com/ntenisOT/Faye-Heroku-Cedar-RedisToGo

I do this quite often when a task is going to stretch over multiple pomodoros, but I can no longer get to the text of the page to copy the previously used tags.

tag_list field should have the lowest tabindex number to be the first active when tab is pressed after timer ends.

Looks like the timestamps for tomatoes are behind by an hour in my tz. Could be a summer time thing...

This should be a replacement for "tomatoes by hour" chart using google charts API.

Example:

A website plugin to show tomatoes tracked and other statistics about projects.

TODO list

• Remove ResourceController (#162)
• API documentation
  • Reference manual
• Add API namespace and base controller (#163)
  • Find user by Tomatoes token
    • Add authorizations.token index to users
• API::SessionsController
  • POST /session
    • Login with GitHub
    • Login with Twitter (#186)
  • DESTROY /session
• API::TomatoesController
  • GET /tomatoes
  • GET /tomatoes/:id
  • POST /tomatoes
  • PATCH /tomatoes/:id
  • DESTROY /tomatoes/:id
• API::UsersController
  • GET /user
  • PATCH /user
• API::ProjectsController
  • GET /projects
  • GET /projects/:id
  • POST /projects
  • PATCH /projects/:id
  • DESTROY /projects/:id
• Add new User index, run User.create_indexes on a production console

We could give more importance to the timer (a little larger) and the stats of the logged in user.
Yesterday's and rest of the week's pomodoros dont require the attention they currently get.

A quick mockup with the above ideas: http://pic.twitter.com/JU5FRlXQ

The extension should block major procrastination sources (reddit, facebook, hacker news, etc.).
Procrastination sources should be customizable.

Deprecation of GitHub API version 2 is the cause of this issue.
Solution: update omniauth to latest version.

Since there is the possibility to assign a list of tags to each pomodoro, it would be great having a way to display the pomodoro reports based also on tags (and maybe a chart to see which tag you use the most)

Timer should always stay inside the visible portion of the screen

a user should be able to set timer sounds theme.

a timer sounds theme is composed by 2 sounds:

1. end tomato sound
2. squash tomato sound

While creating a new tomato after the 25th minute, form's submission is not disabled for submissions by using the "Return" key. Mouse click on the button is disabled though.

Holding the Return key, while submitting creates multiple tomatoes.

The 'new tomato' function should check whether it is possible for the logged user to add a new tomato: in particular it needs to check if now() - 25m is greater than the finish time of the last created tomato.

Near the Today's tomatoes list should be visible today's projects list. The list is filled with projects cited by today's tomatoes tags.

a user should be able to control timer volume through a slider

Tomato end notification should disappear when new tomato form is submitted
Tomato break end notification should disappear after 10 seconds

a user should be able to set a custom progress bar color

New user attributes

• work_hours_per_day
• average_hourly_rate
• currency

These three attributes in combination with Project model (see issue #47) give new metrics to analyze tracked tomatoes.

Whenever I log in, it overwrites what I set as my name - with my twitter name.

See https://twitter.com/airnomad/status/222755109132701696

It would be cool to see stats for the whole community... at what time and on which day are people most productive, growth rate, etc...

I'd like to export all my tomatoes. My goal is to import them in order to obtain some statistics and/or perform other calculations.

Any format would do, CSV, yaml, whatever.

Thanks.

Vedere screenshot

See http://dev.chromium.org/developers/design-documents/extensions/inline-installation/

Even if I've completed some tomatoes, it continuosly say that I have 0 tomatoes.

I'm using the latest version of Chrome on Ubuntu Linux.

space = start tomato
esc = squash tomato or break

See #8 and #9

For me, the by_day graph would be much more informative if weekends would be ignored.

In that case, just looking at the shape of the graph would provide a quick feedback about general tendency (valleys, peaks, plateaus, etc). Now it looks very jagged and see those tendencies is more difficult.

It might be a setting (there might be people who inputs tomatoes at weekends, I don't).

A user should see only current week's tomatoes.
A link should show past tomatoes list.

The tomatoes by day chart isn't showing anything after November 5th. The list of individual tomatoes looks ok.

When Tomatoes tab is pinned you can't see your current timer remaining time, using a dynamic favicon you can.
See http://remysharp.com/2010/08/24/dynamic-favicons/

Projects are composed by

• name
• money_budget
• time_budget
• tags

Projects collect tomatoes tagged with at least one of project's tags list.

Projects are useful to get the big picture about any project you're tracking with tomatoes, they collect tomatoes for the project than compare money_budget and time_budget with the total time and price for your project computed using user's work_hours_per_day and average_hourly_rate attributes (see issue #48).

use http://cssgrid.net/ to support fluid layout and small resolutions (mobile devices)

I am not sure what the effect is exactly, but for me it displays lots of pomodoros in the middle of the night, when I don't work....

After a tomato is complete, no form to create the tomato appears, the page remains green, and the timer is stuck at 00:00

Safari reports this error at notifier.js:17:

TypeError: 'undefined' is not an object (evaluating 'window.webkitNotifications.checkPermission')

I'm using Safari Version 5.0.6 (5533.22.3) on Leopard.

A leader board that would update every 15/30 minutes. It would seem more like game mechanics then and give more instant feedback as well as stir a competitive instinct. You are never procrastinating or distracted when you are competitive, like giving a person 100% focus.

See http://devcenter.heroku.com/articles/procfile

What about displaying today tomatoes only? Who really cares about how many tomatoes you did yesterday or three days ago? You better focus on the current day!

I find the actual tomato tagging mechanism very limitating: what about hashtag? Imagine you are fixing a couple of bugs for the tomatoes webapp and, while working you complete a couple of tomatoes.

With hastags, you could tag your tomatoes with '#tomatoes fix bug22' and '#tomatoes work on bug23'. This way those tomateos will be available under the same tag #tomatoes and you won't lose the verbose description about the job done.

With comma separated tags, you will endup having two different tags.

Comments?