Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More styling to due dates #13

Closed
geebru opened this issue Apr 23, 2014 · 5 comments
Closed

More styling to due dates #13

geebru opened this issue Apr 23, 2014 · 5 comments
Assignees

Comments

@geebru
Copy link

geebru commented Apr 23, 2014

http://cl.ly/image/1r230F24290b

Currently due dates are a little iffy looking. "Due:" touches the date and there's no way to style the dates (would love a custom color for them).

A stretch goal might be to allow us to edit how the date is shown (year isn't relevant for my uses so something like "Friday, April 26" would be better or just "Apr 26".

@mjdescy
Copy link
Owner

mjdescy commented Apr 23, 2014

I could see adding a customizable color to due dates, to set them off like contexts and projects are set off.

I am pretty adamant at requiring the due date format to be "due:YYYY-MM-DD". The reason is that the goal of the project is to be compliant with the todo.txt format spec, and to be compatible with the Windows app Todotxt.net and the command-line tools. The due date tag is defined as an addition to the spec on the Todo.txt format specification page. That's about as far from the canonical spec as I would like to go.

@mjdescy mjdescy self-assigned this Apr 23, 2014
@geebru
Copy link
Author

geebru commented Apr 23, 2014

That's reasonable - I also might not mind the format as much if that
space is added and I can make them grey instead of black!

Thanks for the quick reply!

On 4/23/14, mjdescy notifications@github.com wrote:

I could see adding a customizable color to due dates, to set them off like
contexts and projects are set off.

I am pretty adamant at requiring the due date format to be "due:YYYY-MM-DD".
The reason is that the goal of the project is to be compliant with the
todo.txt format spec, and to be compatible with the Windows app Todotxt.net
and the command-line tools. The due date tag is defined as an addition to
the spec on the Todo.txt format specification
page
.
That's about as far from the canonical spec as I would like to go.


Reply to this email directly or view it on GitHub:
#13 (comment)

Greg Bruening
Lynchburg College Alum
Major - Graphic Design, Minor - English

@mjdescy
Copy link
Owner

mjdescy commented Apr 23, 2014

@geebru I am working on the due date coloring. The "due:" text has to touch the date, however, because that is how the tag spec addition to todo.txt is structured. Sorry, but I can't change that aspect of it. We have to maintain compatibility with similar todo.txt apps.

@geebru
Copy link
Author

geebru commented Apr 23, 2014

Interesting - that's a strange spec to have. Anywho, thanks for working on the coloring! Awesome app!

mjdescy added a commit that referenced this issue Apr 23, 2014
@mjdescy
Copy link
Owner

mjdescy commented Apr 23, 2014

This feature was added in Version 1.1.3.

@mjdescy mjdescy closed this as completed Apr 23, 2014
mjdescy added a commit that referenced this issue Apr 30, 2014
Version 1.1.3

Added:

Customizable highlight color for due dates. Closes Issue #13: More styling to due dates.

Fixed:

Font selector did not update the font displayed in the Preferences window when that font text box was focused (i.e., the first responder). Closes Issue #12: Font selector does not change the font.
mjdescy added a commit that referenced this issue May 1, 2014
Added:

Customizable highlight color for due dates. Closes Issue #13: More styling to due dates.

Fixed:

Font selector did not update the font displayed in the Preferences window when that font text box was focused (i.e., the first responder). Closes Issue #12: Font selector does not change the font.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants