Feature #373
display .xpm icons
| Status: | Closed | Start: | 02/09/2010 | |
| Priority: | Low | Due date: | ||
| To: | Paul Beckingham | % Done: | 100% |
|
| Category: | theming | Spent time: | - | |
| Target version: | 1.9.0 - Kuwagata | Estimated time: | 0.00 hours | |
Description
These are ascii icons from long ago, seen in ancient Windows systems, old window managers and occasionally adorning emacs buffers. This occurred to me on seeing emacs orgmode screenshots featuring tiny icons ! like checkboxes, bullets and all sorts of things. I don't know if this is even remotely possible for task, and it's not particularly important, but I do know that tiny icons rendered via cli or interactive display, would indeed offer very strong visual clues.. and cute !
History
Updated by Paul Beckingham 168 days ago
- File unicode.png added
David, see attached picture. Is that what you mean?
Updated by Paul Beckingham 168 days ago
- Status changed from New to Closed
- To set to Paul Beckingham
- Target version changed from 2.1.x - Wakizashi to 1.9.0 - Kuwagata
- % Done changed from 0 to 100
- Estimated time set to 0.00
Good news, David, that attached picture is real. This is already supported.
If you go find some funky unicode characters (there are lots of web sites dedicated to listing them), you can select them and paste them in the command line, and task will accept it. So will Redmine: ? ? ? ? ? ? ? ? ? ? ? ? ? ?. In the example, I used them as tags, and in descriptions. You can probably use them anywhere. Here is roughly what I did:
$ task add Call Bob about the meeting +? $ task add Book ? flight to conference $ task add Check out the caffe on Harbord +?
That last one is listed as "hot beverage", but it's hard to see at any size. You'll appreciate why I needed to use that one. And that telephone character (I found two of them) is becoming anachronistic. It might also help that I have this in my environment:
export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8
The downside to using unicode characters is that some of them are more than one character wide in the display, despite using a fixed-width font. While this works, task is not smart enough to know this, so it tends to throw off the output table alignment. You may notice in the picture that the tasks don't line up properly - that's going to be addressed in task 2.0, with luck.