I have thoughts (no plans yet) about plugin API that can use web view as output layer. The idea being that an outliner can be used for many things. For example you can create a calendar where the hierarchy is year/month/day. Neat, but not really a perfect solution for a calendar. So the idea with plugin API + Web View is that you could use that outliner calendar data to generate a nicer view. This keeps the outliner simple and uniform, but also gives you data specific view.
I think that same solution might work for Tree style view, or Harvard bullet list view. It would be sorta like a markdown app, content on one side (the outliner), generated polished result on the other.
No promises, but that's how I think I would implement those features in Bike.
I have thoughts (no plans yet) about plugin API that can use web view as output layer. The idea being that an outliner can be used for many things. For example you can create a calendar where the hierarchy is year/month/day. Neat, but not really a perfect solution for a calendar. So the idea with plugin API + Web View is that you could use that outliner calendar data to generate a nicer view. This keeps the outliner simple and uniform, but also gives you data specific view.
I think that same solution might work for Tree style view, or Harvard bullet list view. It would be sorta like a markdown app, content on one side (the outliner), generated polished result on the other.
No promises, but that's how I think I would implement those features in Bike.