Open bashfulrobot opened 6 years ago
Indeed, this flexibility is desirable. However, Turtl would trade off maintaining an Markdown editor for the problem of handling an API to send/receive data to any app editor (including ways to handle editor's failures). Still, it is feasible.
I love the idea. However, this is fairly difficult to do with Turtl's security promise. Temporary files with unencrypted data laying around are pretty far outside the goals of the project. This would have to be done using some kind of inter-app communication (probably via http, like the bookmarking extension). And at that point, I'm not sure how you'd get the editor to talk to the Turtl app without some kind of extension in the editor itself. This needs some very careful thought.
In the meantime, we are planning on implementing some form of WYSIWYG editor (#38) that might satiate users' needs for a better editor than a simple text box (for the time being at least).
Thanks for the responses!
You might want to look at how qutebrowser does it:
@mutagenfork Can you give a little more explanation? It's not immediately obvious from the links how qutebrowser loads the editor and if it does so in a way that works within Turtl's security model.
I don't know enough about Turtl to say whether it will fit with Turtl's security model. I just know that the mechanism works well for editing Turtl's config file and text fields in the browser:
Here's the code which I'd guess does most of the work:
Thanks, I'll take a look!
I have since moved onto other software. Please feel free to close it you wish.
I was reading the FAQ about the reasons for markdown. While I prefer markdown, maybe a way to approach this is to have an option to compose/edit in an external markdown editor.
Workflow
That allows the freedom for people to use any editor they like (some have some great editing capabilities). And offloads the requirement to maintain an editor for you.