![outliner taskpaper vs folding text outliner taskpaper vs folding text](https://cdn.appmus.com/images/e445c81e36f92d0d1fd8c3e5b067ff1b.jpg)
- #Outliner taskpaper vs folding text mac os#
- #Outliner taskpaper vs folding text install#
- #Outliner taskpaper vs folding text pro#
- #Outliner taskpaper vs folding text code#
- #Outliner taskpaper vs folding text license#
#Outliner taskpaper vs folding text mac os#
I don't think the animations are expensive, but it's hard to test because that work happens in Mac OS window server and I'm not an expert there. On the other hand resize is instant and only does work for visible text in Bike. And then after that resize there's lots of background processing to refill a bunch of layout caches I guess. If you open a large document in TextEdit you will see that resize is quite slow and processor and memory intensive. So you pay for that cache and you also pay for the background processing required by pre-rendering.Īlso consider simple things like window resize. For most macOS apps scrolling performance is achieved by pre-rendering before and after the visible scroll area. This means you only pay memory for visible text. In Bike it's fast enough that when you scroll it just updates what you can see on the screen. I think the architecture needed to support them means the total package is less than most apps. Already probably fast enough for 99% of use cases as is. That will be fun, but not sure it’s actually needed. Eventually I may change to augmented b+tree and then should be able to work with gigabytes worth of outline. This is Bike’s performance bottleneck for large outlines. I’m using OrderedDictionary from Swift Collections to store rows. View implementation requires that each row has a unique ID. Each row has a `level` property, outline structure is determined dynamically. Model representation is interesting in that it’s just a flat list of rows. View performance is determined by visible text, not document size.Animations are performed by Core animation and Motion lib.I test performance using the Moby Dick Workout. Architecture needed to support fluid editing also makes Bike faster/more scalable than most (all?) outliners and many text editors.Javascript plugin API also expected in future, though no timing on that. bike file format is HTML subset, so files are easy to parse and manipulate. In outline mode rows are constrained to outline hierarchy. In text mode Bike works like a normal text editor.(movie on home page if you don't have Mac) Lots of text editors have animated some interactions (cursor movement, insert newline, etc), but I think Bike is the first designed from the ground up to support fluid editing.
#Outliner taskpaper vs folding text code#
(If you don't do this, then Markdown will think you're writing code and won't translate the text into a clickable link.) Then TextTool sends the output to Drafts and performs the Markdown: Preview action.Show HN: Bike – macOS Native Outliner ( )ĥ13 points by jessegrosjean 83 days ago | hide | past | favorite | 236 commentsīike’s most original feature is the “fluid” text editing. The above action sends the clipboard contents to TextTool, which strips the tab-dash-space preceding the task. Here is the URL scheme: texttool://x-callback-url/transform?text=&method=delist&style=dash&x-success=drafts%3A%2F%2F%2Fcreate%3Ftext%3D%5B%5Boutput%5D%5D%26action%3DMarkdown%253A%2520Preview
#Outliner taskpaper vs folding text install#
Tap on this link while in LCP to install the action. (You will also need TextTool to make this action work.) Just copy the task in TaskPaper to the clipboard, tap on the LCP action TaskPaper Markdown Preview, and it will open the text in Drafts in Markdown Preview mode. Here is an action that will allow you to preview a link written in Markdown, replicating the functionality of Oak Outliner.
#Outliner taskpaper vs folding text pro#
I've already shared a Launch Center Pro action to open a task that contains an URL. Working with Links in TaskPaper While on iOS If I have a task like this in TaskPaper, - () One benefit of Oak Outliner is that it supports Markdown links. (Also check out Mango Markdown which is to Markdown what Oak Outliner is to outlining.) It appears to be a place where Jesse Grosjean and his team work out their ideas for Folding Text. Oak Outliner uses local storage in the browser, it does not sync. Recently, I've been using TextDrop - a browser-based Dropbox text editor - to copy the complete text file of my todo list, and then I paste the clipboard contents into Oak Outliner, which is a browser-based outliner developed by the same team that makes TaskPaper. Regardless, if I want to work with my todo.taskpaper file, I have to somehow get it from Dropbox and put the text file into a desktop or web app.
#Outliner taskpaper vs folding text license#
Although I have a license for the Mac version of TaskPaper - which I've installed on my desktop - I cannot use Dropbox for sync at the office. However, I am at an office computer all day. I've moved back to TaskPaper for iOS to manage my todos.