Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
I was talking with a developer yesterday and the question came up, what about huge outlines? How does OPML handle those? That gave me a chance to tell the story about how i'm archiving Scripting News, and how "include" nodes work.
First it's basically the same thing that happens when a piece of software gets big -- you break it up into components and link them together in a single document. That makes the code more manageable, and makes it possible to reuse the pieces. Every serious system has to provide for breaking big things up into smaller, reusable bits. For example...
const fs = require ("fs"); Then you can refer to exported bits from the "fs" package in your app as if they were part of it, because they are. An example. I archive my blog, which is written in an outliner, and saved as OPML, at the beginning of every month. I save the previous month in a repository on GitHub, and empty out the outline I edit. The CMS that builds the HTML rendering and the RSS version of my blog is able to jump month boundaries. So I have a convenient-size outline for editing, and everything else just hums along.
But what if I wanted an outline of all my blog posts going back to May 2017? I would do that with include nodes. And just for fun, I did exactly that.
Here's an OPML file that contains includes for each of the months of 2018, 2019 and 2020. If you have an outliner that can expand includes, then you can view all the writing for those years in one outline
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.