tracksapp / tracksapp.github.io Goto Github PK

The homepage currently shows a screenshot dated January 2008. Furthermore, some UI details in the other screenshots are outdated by now.

Originally reported by @C-Otto as TracksApp/tracks#1895

As of May 1st, GitHub Pages will no longer support textile. Our Textile pages will need to be converted to Markdown. Pandoc can do the bulk of the work.

https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

The A-records for getontracks.org are not current with GitHub's recommendation. See https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages

This seems to be a bit tricky, because some Compass features are used which don't seem to be too easily compatible with Jekyll. I'll push the current version in a working branch, but it doesn't really work right now.

I hit a bug in nokogumbo due to Gemfile.lock lock the version at 1.1.12

rubys/nokogumbo#25

Example: https://github.com/TracksApp/tracksapp.github.com/blob/master/development/index.html#L88

This error is baked into the source in many places.

irc://chat.freenode.net/tracks

Feels like creating recurring_todos from sidebar would be more intuitive than from page header menu - a personal preference of placement. Maybe a link in the sidebar next to the 'Due' field to open the create recurring_todo popup?

https://github.com/blog/1452-new-github-pages-domain-github-io

Not necessary, but perhaps it could be done as part of a batch of other administrative changes, or at the time the website is redesigned.

when viewing recurring_todos the 'due in x days' value is not updated with the recurring_todo model values.

For example. Set up a recurring payment - 1st of every month - create it through the recurring_todos form. Then, change the 'starts on' field - either from the recurring_todo form or the javascript form offered on the contexts page. Refresh root path or calendar and 'due in x days' has not changed.

Don't know if this is a caching/session/model/javascript problem. I'm running tracksapp on localhost with Apache and Phusion Passenger using Opera.

I know an admin user can create different users, and each can have their own Projects and Contexts, but can one user share tasks with another user? It seems like a Project's tasks should be distributed among several users, each user being a Context - but how is this done?

The configuration option "subdir" in config/site.yml has no effect.

My install (linux, opera, sqlite3).

Root path (contexts/index) pre-fills new actions sidebar form-field 'context name' with name of first context in db.

I think leaving the field blank is better. Fine if the order the user works with contexts is the order they were created. Don't think this is likely, though. Having to delete pre-filled value every time is work that could be avoided.