I do hope to eventually implement the next version of TaskPaper using Bike’s editor (keeping TaskPaper file format). I don’t expect Bike to replace TaskPaper.
#Taskpaper separators code
This has made debugging and optimizing code easier and faster. This is good for some things, but adds complexity to app development.īike is simpler, it’s all Swift code. TaskPaper is implemented in a combination of JavaScript for the model layer and Swift for the UI layer. I expect to add other such shortcuts going forward.
For example when in outline mode you only need press left arrow to expand an item (in text mode that key moves the cursor left). That means all the normal text editing keybindings can be used for other purposes.
Item movement commands work on the entire outline structure and movements are constrained to that structure.Īnother important feature of outline mode is that it’s not for text editing. TAD-Select and Display Sorted Action Group Separators TAD-Copy Sorted Action Group. When in outline mode Bike works like an outliner. TAD-Taskpaper Toggle Project (Line) TAD-Taskpaper Toggle Project. (Use escape key to toggle between these modes). But Bike also supports a separate outline editing mode. TaskPaper works like a text editor with some special outliner commands added in. The point being again that Bike is more generic and open ended. For example I want to have separator items. In the future I expect other types to begin sneaking in. Most of what I want to do in an outliner doesn’t map cleanly in to projects/tasks/comments.īike is a more open ended and generic tool. I also think it’s limiting and undersells TaskPaper’s strengths and possibilities. This is good in some ways… I think it makes it easier to explain TaskPaper to new people. Your document is made up of tasks, projects, and notes. txt documents metadata, item ids, etc will be lost each time a document is closed. It’s also easy for scripts and plugins to store metadata, track items with persistent ids, generally do many things that are difficult when working with plain text files.īike also supports reading and writing. bike files, they don’t need to parse and understand a custom format. bike format will allow for more powerful scripts and plugins. Bike on the other hand uses a HTML based file format. TaskPaper is inseparable from its plain text file format. This is a tradeoff because I no longer get system editing behavior for free, but it gives me the flexibility to build exactly what I want.īike’s unique feel and performance are enabled by this custom editor. This provides great utility, but has often limited what I’m able to build.īike’s editor is built from the ground up with a focus on performance and fluidity. TaskPaper is built on the standard macOS text editing component. Bike takes a different approach in a number of key areas.
Now place the cursor on a TaskPaper task and select the script in your Scripts menu.Bike and TaskPaper share many of the same goals, but Bike isn’t TaskPaper 4.0. I’d love to hear of anyone using it, I’d even appreciate a bug report.ĭownload the script and put it in your Scripts folder. The default time, 9AM currently, can be changed at the top of the script for those that like their reminders earlier in the day. “Remind me 10:00PM” # script sets to today.Here’s some examples to show you what I mean. So now the script, which can be found here, accepts the time in a much larger range of ways including 24 hour time, the date can use either a ‘-‘ or a ‘/‘ as separator, the time and date can be in either order and if you leave either out then a reasonable default is inserted. The new version took me four hours for about 80 lines of code! It is so awful to work in, if it wasn’t so damn useful I’d never use it. Frankly it just took too much brain power to get it right all the time so I’ve rewritten the script.Īt this point just allow me to let out my usual primal scream required after a few hours of working with AppleScript. The first version of my TaskPaper to Reminders script was more than a little fussy about the format of the task.
0 kommentar(er)
