It is some time since my post reviewing the Bike Outliner. I was pretty busy these times, so I did not interact so much.
I want to say that I am very happy with the current Bike state of the art, and the exporting for pandoc markdown works great for me.
I just want to put this reminder to create a dom object for citations in the .bike native format with the form:
key:
prefix:
sufix:
That will render it in the pandoc style here.
Also, just a reminder for MathJax support (this I think will be hard to implement).
2 Likes
I’ve been delaying responding to this… while I think, but I don’t expect these features in Bike 2.0. They are added to my “Later” todo list.
I expect MathJax will be implemented using some of the same features that attachments use. So I need to design attachments first.
I’m less sure about the correct solution for Citations.
I think the current data model should already be flexible enough to encode what you need. A citation is just a span of text with some custom attributes right?. But that won’t be very useful unless I also build an editor for that attribute. And once I do that then it seems I need a system to manage full citations… it gets complicated unless I’m missing some shortcut.
I think citations are the sort of feature that the extension system would be good for. I would be happy to help sketch out a solution using the extension system, but I need more details on what exactly is needed. What exactly the workflow will be.
Hello Jesse!
Sorry for the late reply.
But that won’t be very useful unless I also build an editor for that attribute. And once I do that then it seems I need a system to manage full citations… it gets complicated unless I’m missing some shortcut.
That is surely a lot of work, but is not my intend here. This would make Bike a citation processer, something beyond the scope now (maybe someday with integration to Pandoc via the plugin system).
The problem with citation is that when I put [@key], the markdown render as \[@key\], escapig the [ ] as expected.
I just want a simple interface to insert the fields, like the link one, for example this pop-up (when I hit Cmd + K):
But with the options:
Prefix:
Key:
Suffix:
When I render, I want to get the correct format, as liked above for the Pandoc syntax.
This is similar to the link case, where we have a dedicated div in the bike format that renders correctly as [description](link). My request is just to add a syntax div citation to bike file, as all the other text specials (italics, bold, link, verbatim) for encoding the information. No need to citation look-up, citation picker, etc. All these are better done, I agree with you, by the plugin system.
1 Like
