while we are waiting how do users read/edita Bike data on iOS?
Zavala as OPML?
what else?
Bike 2 also supports Markdown (bike subset) now. It wouldn’t be outliner experience, but you could open that in text editor and round trip it.
I went as far as vibe coding a TUI that runs in a-Shell terminal on iOS. That’s a nuclear option if I desperately needed to address .bike files, but I don’t like how it handles file writing and did not find time to further work on it (besides, it works reasonably well only on iPad).
I’ve since given up on dedicated Bike outlines if I need iOS support. Obsidian handles outlining reasonably well with bikeMD but I like Bike because of the extra features it adds on top of just plain text, and those can’t really be replicated on iOS at the moment. I default to either MindNode or OmniOutliner.
Is this something I might be able to easily add into PaperTrail?
Maybe? I think if you focused on the Markdown format then it might make sense. Then you could round trip all of Bike’s special attributes/formatting, without having to build them in to PaperTrail directly?
PaperTrail would provide the the outline folding, navigation, etc.
When I get a minute I’ll look at the attributes.
AFAIK PaperTrail can read OPML if only it could write them…!
1 Like
As I explained when I added OPML reading to PaperTrail, writing is easy, the issue is during editing we’d need to keep and manipulate all the formatting or attributes (hidden information) that Jessie mentioned.
Think of it like loading a book with chapters, margins, and layouts that PaperTrail (TaskPaper format) doesn’t have an equivalent of. We have to track that invisible structure while you edit, otherwise saving the file would strip out that hidden data and ruin the formatting.