3 ms·

Well dang! I didn't realize it was that big. That is impressive and definitely changes my opinion a bit. It's quite unfortunate to have such low paid numbers

Well dang! I didn't realize it was that big. That is impressive and definitely changes my opinion a bit. It's quite unfortunate to have such low paid numbers with that many downloads. By logseq's on-disk format, it is local first but it's a stricter subset of markdown with a handful of extensions. The strictness is because Logseq parses all the markdown into an in-memory graph database, and in order to make that work with markdown the top-level has to be a list and needs some IDs and other identifiers in order to properly link/embed blocks and pages and such.

rubymamis 3y ago
Thanks! With Plume I use a tree data structure (just with parent child relationships), although in the future I would probably use Boost::ptree. The things is, the underlying data structure is just plaintext, so having an ID for each block will make the plaintext look out of place (say, if you wanna move your files to another app). But I'll add some special syntax to allow this feature for specialized blocks.
- freedomben 3y ago
  > so having an ID for each block will make the plaintext look out of place (say, if you wanna move your files to another app). Indeed, this is definitely a problem for Logseq. For example here's some of my recent Logseq notes. This is one page where you can see an "ID" (represented by `id:: <guid>` is created. Then helpful images/diagrams are displayed. This is then referenced later: - Parts of a [[Neuron]] id:: 64f4bdc3-29de-4b6c-bc41-20a5f052badf - Dendrite: https://en.m.wikipedia.org/wiki/Dendrite - ![Anatomy_of_neuron.jpg](../assets/Anatomy_of_neuron_1693760694470_0.jpg){:height 411, :width 718} - Axon: https://en.m.wikipedia.org/wiki/Axon - ![Blausen_0657_MultipolarNeuron.jpg](../assets/Blausen_0657_MultipolarNeuron_1693760712899_0.jpg){:height 471, :width 718} Then in a different page, this is referenced by ID. In this case it is "embedded" but you can also reference and other possibilitie: - #vocabulary [[Brain Myths Exploded]] #Notes - {{embed ((64f4bdc3-29de-4b6c-bc41-20a5f052badf))}} - Encephalization Quotient (not a good measurement)
  - rubymamis 3y ago
    That's actually not too bad, and similar to what I plan to do. They only create an ID for a block/bullet-point when necessary. I just noticed Logseq doesn't support selecting and editing text across multiple blocks. It's indeed not easy to do, but Plume does support this, I believe it's an essential feature for a text editor. Notion took a long time until they supported this[1]. I implemented it in less than a month using C++ and QML, a testament more to the strengths of Qt than to my own skills as a developer. [1] https://www.notion.so/releases/2022-01-19 https://www.notion.so/releases/2022-01-19

rubymamis 3y ago

Thanks! With Plume I use a tree data structure (just with parent child relationships), although in the future I would probably use Boost::ptree. The things is, the underlying data structure is just plaintext, so having an ID for each block will make the plaintext look out of place (say, if you wanna move your files to another app). But I'll add some special syntax to allow this feature for specialized blocks.

freedomben 3y ago
> so having an ID for each block will make the plaintext look out of place (say, if you wanna move your files to another app). Indeed, this is definitely a problem for Logseq. For example here's some of my recent Logseq notes. This is one page where you can see an "ID" (represented by `id:: <guid>` is created. Then helpful images/diagrams are displayed. This is then referenced later: - Parts of a [[Neuron]] id:: 64f4bdc3-29de-4b6c-bc41-20a5f052badf - Dendrite: https://en.m.wikipedia.org/wiki/Dendrite - ![Anatomy_of_neuron.jpg](../assets/Anatomy_of_neuron_1693760694470_0.jpg){:height 411, :width 718} - Axon: https://en.m.wikipedia.org/wiki/Axon - ![Blausen_0657_MultipolarNeuron.jpg](../assets/Blausen_0657_MultipolarNeuron_1693760712899_0.jpg){:height 471, :width 718} Then in a different page, this is referenced by ID. In this case it is "embedded" but you can also reference and other possibilitie: - #vocabulary [[Brain Myths Exploded]] #Notes - {{embed ((64f4bdc3-29de-4b6c-bc41-20a5f052badf))}} - Encephalization Quotient (not a good measurement)
- rubymamis 3y ago
  That's actually not too bad, and similar to what I plan to do. They only create an ID for a block/bullet-point when necessary. I just noticed Logseq doesn't support selecting and editing text across multiple blocks. It's indeed not easy to do, but Plume does support this, I believe it's an essential feature for a text editor. Notion took a long time until they supported this[1]. I implemented it in less than a month using C++ and QML, a testament more to the strengths of Qt than to my own skills as a developer. [1] https://www.notion.so/releases/2022-01-19 https://www.notion.so/releases/2022-01-19