Introducing: RoboToDo
Jack Jennings
Posts: 151
Hi all;
Today I'm happy to announce the first public release of RoboToDo.
RoboToDo builds basic task management functionality directly into RoboFont, allowing you to add To-Do items to individual glyphs, as well as to the font as a whole.
When I'm working on drawing a new typeface, I work pretty frenetically. I usually notice things that I'd like to change on some glyphs over there, while I'm working on getting the curves right on some glyphs over here.
I've tried too many ways of keeping track of all of the things that I need to do, but none have felt right to me:
Disclaimer: As this is the first release of RoboToDo, please consider this beta quality software, and is provided as-is. It is currently tested only on RF 1.4, but probably works in lower versions as well. I've done my best to iron out the bugs, but there may still be some lurking. If there are more experienced Python developers out there than I who would like to contribute, please submit a pull request.
GitHub repository: https://github.com/jackjennings/RoboToDo
Download .zip: https://github.com/jackjennings/RoboToDo/archive/master.zip
Also: Special thanks to Frederik Berlaen and Tal Leming for quick responses to my RoboFont and Vanilla inquiries
Today I'm happy to announce the first public release of RoboToDo.
RoboToDo builds basic task management functionality directly into RoboFont, allowing you to add To-Do items to individual glyphs, as well as to the font as a whole.
When I'm working on drawing a new typeface, I work pretty frenetically. I usually notice things that I'd like to change on some glyphs over there, while I'm working on getting the curves right on some glyphs over here.
I've tried too many ways of keeping track of all of the things that I need to do, but none have felt right to me:
- a dedicated task management software is powerful, but it's also another environment to manage;
- a .txt file is better in the same directory can be checked in to source control, but the figuring out the syntax is hard;
- written notes are handy, but I can't keep track of them when the drawing has moved onto the computer;
- the .ufo file format specifies a note attribute for both the font and individual glyphs, but their interface isn't convenient (hidden away in RF, and non-existant in Glyphs[?])
Disclaimer: As this is the first release of RoboToDo, please consider this beta quality software, and is provided as-is. It is currently tested only on RF 1.4, but probably works in lower versions as well. I've done my best to iron out the bugs, but there may still be some lurking. If there are more experienced Python developers out there than I who would like to contribute, please submit a pull request.
GitHub repository: https://github.com/jackjennings/RoboToDo
Download .zip: https://github.com/jackjennings/RoboToDo/archive/master.zip
Also: Special thanks to Frederik Berlaen and Tal Leming for quick responses to my RoboFont and Vanilla inquiries
6
Comments
-
Nice, thanks for sharing.0
-
non-existant in Glyphs[?])
It is hidden in Glyphs, too. You can enable a notes column in the list view:
2 -
Good to know Georg. I guess I missed it after poking around for a couple of minutes…0
-
Nice one!0
Categories
- All Categories
- 40 Introductions
- 3.7K Typeface Design
- 796 Font Technology
- 1K Technique and Theory
- 615 Type Business
- 444 Type Design Critiques
- 539 Type Design Software
- 30 Punchcutting
- 136 Lettering and Calligraphy
- 83 Technique and Theory
- 53 Lettering Critiques
- 482 Typography
- 301 History of Typography
- 114 Education
- 67 Resources
- 495 Announcements
- 79 Events
- 105 Job Postings
- 148 Type Releases
- 162 Miscellaneous News
- 269 About TypeDrawers
- 53 TypeDrawers Announcements
- 116 Suggestions and Bug Reports