Outline published in JSON too#
- We already upload OPML, it was a simple matter to have it also maintain a JSON version of the file as well. #
- Here's the OPML version of this file.storage.littleoutliner.com#
- And the JSON version. storage.littleoutliner.com#
- The mapping should be kind of obvious.#
- And the discussion ensues...#
- It's easy to read for sure, but I'm still kind of conflicted about the format. Because it takes something, OPML, that was singular and muddies it up. Which version of OPML should I expect? I have to produce both you say? What's the advantage of two versions over one?#
- I produced it because I reasoned at some point in the process of turning the outline into a blog it's going to probably become JSON. Might as well do it at the beginning, at the source.#
- And all the software I've ever shipped expects OPML not the JSONization. Of course since my software will produce both formats there will be interop. But what happens when someone only produces one? What do I say when someone asks me which one should they support? Or is it ok if they just support .JSON. I want to be agreeable, but I would have to say you need to support both. So how did it get easier? Seems it only got harder.#
Plugins for EO#
- The thing about outlines is that they can be rendered in so many different ways.#
- Presentations, listicles, fact sheets, directories, status centers, blogs and probably a lot more. #
- The question is where do you want to put that code? #
- Best place to put it is EO.#
- No server to run. Yet you have the full power of Node.js right here, and full access to the local system. No fooling around like we had to do with Dropbox. No rules. We're back in the app business, for real.#
- When does the code run?#
Electric Outliner#
- Problem with saving#
- I do a bunch of work in toy.opml, switch back to todo.opml, the content in todo.opml has been replaced with toy.opml.#
- I just changed the saving code to base the file on the tab, not the global currentFilePath. It's likely the bug was related to using that global. Never was a good idea. Keep one thing current the tab data structure. #
- Done#