![]() I wrote a comment in a previous post (Considering TaskPaper 3) to describe how I could add information to my TaskPaper files with Siri using Reminders and Drafts. It’s all plain text, and relatively quick.įor now, I’m trying the first: Markdown headings, then making sure to indent the relevant tasks I’d like the group. Now that I consider it, the second option isn’t that big of a deal. Move them to another file weekly, to keep things tidy. I’d need to open the Archive TaskPaper file.Don’t use them as projects, but Markdown headings. I can still fold the text under that header-that’s what I want.Getting messy after four days in!ĭaily work “projects” means that the Archive projects displayed in the sidebar will be extremely long if I don’t do something. When migrating some stuff to TaskPaper, I created those two projects from Things as projects in TaskPaper-which are also shown in the sidebar. This is a hold over from an idea in my previous post, “ Things: Repeating Projects!“ 1 The tree structure would help with the folding/focus features, but it seems to make the schema and copy/pasting parts more difficult.I’ve been using a couple of “Projects” for grouping daily work in various ticket queues: one for triaging, and the other for regular ticket smashing. Each line of plain text will be a node in the document, but I’m torn on whether they should be organized as a flat list or tree based on indentation.Augment the basic text editor with TaskPaper features like syntax highlighting similar to the ProseMirror linting example.Is there any value to a custom Taskpaper schema that does know about these concepts?) (The schema doesn’t know about concepts like projects, tasks, tags, and notes. ![]() Use a simple text schema that only enforces indentation with tabs.However, ProseMirror lists don’t maintain indentation when copy/pasting to a plain text file.īased on my current understanding of ProseMirror this seems to be the best approach: Since a Taskpaper file is just a list, I also considered starting with just the ProseMirror list schema for a base. Then I could just decorate stuff like tags and projects a la the linter example. Schemas seem to enforce what type of content is allowed Taskpaper files allow just about any sequence of text it’s just that the interpretation of the text might change if you add/remove the right special characters ( Maybe just enforcing the rule that all lines start with (optional) tabbed indentation (and not spaces) would be enough. However, perhaps a custom schema is not required. However, there doesn’t seem to be a simple way to convert these nodes back to plain “note” nodes when they no longer match the proper syntax (for example when the is deleted from a tag or inserted in the middle of a tag name). “Task” and “tag” nodes could be created when - or is typed. With this Taskpaper schema, input rules could be used to convert a “note” node to a “project” node when : is typed. So I tried to come up with a BNF grammar here. I will describe them below:Īt first, I thought I needed to write a ProseMirror schema for TaskPaper files. Then, what is the best approach? The first idea I had no longer seems to be the best route I thought of other ways that might work better. For more background, is a related project using CodeMirror where you can explore the TaskPaper format and associated API.įirst question: is this possible? Or am I trying to use ProseMirror for something it not suited for? At least one person tried to do something similar with markdown. The TaskPaper app already has most of these features, but it’s Mac-only and there are some additional features I would like to add like sorting by tag. Syntax highlighting of projects and tags.My goal is add functionality on top of a regular text editor. The TaskPaper format is plain text that gives special meaning to certain sequences of text. I am creating a TaskPaper editor using ProseMirror.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |