Development notes

• Putting id attributes on backlink elements don’t work consistently. For instance, plain list items are not wrapped by an element. Perhaps I should add a Target inline element to the AST instead, and rework the backlink preview functionality to be more similar to what it was before (without fancy buggy portals).
• Portal stuff is terrible and should probably be ditched altogether. Transclusion can probably work via walk.query expansions.
• Attachment figures do not get recognized as figures. Related to AST Annotations.
• Anchor links to the same file but to a part with a different ID do not work.
• organon-follow-mode gets confused with headings with the same title.

Use ondim? pageExp could be available inside it, could be used to store stuff like todo states!

Basically: heading-level, element-level and inline-level backlinks.

We already store all the necessary information to provide this.

Also: more general forms of backlinks. For instance, timestamps and citations should be considered links.

Pages generated by metadata queries.

If done right, querying can generalize a bunch of patterns you find in a static site. For instance, creating a list of posts with a given tag or creating a list of tags.

#+attr_query: :from notes :where (in "games" tags)

| Name          | Time Played           | Length           | Rating           |

|---------------+-----------------------+------------------+------------------|

| {{{q:title}}} | {{{q:m:time-played}}} | {{{q:m:length}}} | {{{q:m:rating}}} |

#+attr_query: :from notes :where (in "games" tags) :where (or (in "moba" tags) (in "crpg" tags))

- {{{note:link}}}

• Try ninja-keys
• Activitypub

• Inner links are not working! and they were working before!!

• Note taken on Tue, Jul 25, 2023 19:07
  Some days ago I had a go at this and gave up. Sadly I don’t remember the problem anymore, but in the end I was sure I would have to parametrize with two types, like OrgDocument element object, and I was sure a single type parameter for metadata would not work.

  Acho que o problema era porque o Walk não iria funcionar bem, seria impossível fazer o Walk construir as anotações aos poucos na hora de resolver os links. Mas pensando agora seria perfeitamente viável, só usar a instância Functor pra colocar uma metadata vazia no lugar antes de andar.

Investigate the use of trees that grow (note: certainly overkill. A simple type parameter for metadata is for sure much better) to allow annotations in the AST. Use this to implement precise page following for Organon.

• https://hackage.haskell.org/package/barbies-2.0.3.0/docs/Barbies.html#g:3

Advantages of having the template language built in the target language:

• No need for special editor support; make use of all the existing tools.
• Less prone to errors; In some cases, it is even impossible for the templates to result in invalid documents.
• Context-aware means it’s possible to handle contextual rules like text escaping automatically.
• Easier to understand visually compared a mix two languages.
• More modular: no need to write a parser or writer if there are already existing ones.

• When using withExpansions to bind foo.bar, where foo already exists in the environment, the deletion of foo leaks outside.

• Some profiling shows one of the mostly costly things when rendering pages is text replacement of attrSub. This is because it parses the same text over and over each time the template is run, countrary to the template itself which is already parsed. I could make the loading functions parse the text once and store the AST as another template that attrSub just calls during expansion.

• Note to self: difficulties are

  • How to get the text templates from a document in an elegant way. The current way is to run Ondim with errors disabled.
  • How to store the text templates in a place where they can be unloaded along with the file, or if they should not be unloaded (perhaps a source of memory leaks)
  • Text duplicated in memory: bad?
  • Rendering Whiskers/LaTeX ASTs is very slow for odd reasons. Simpler AST?

Say we want an expansion to run inside a monad with extra state, or even other side effects. We want to do that locally, because this inner state does not make sense outside.

• Note taken on Thu, Feb 9, 2023 13:00
  

  This is tricky because the state is parametrized by the inner monad and used in contravariant position. So there cannot be a mapOndim :: Ondim tag m a -> Ondim tag n a without two functions right :: forall a. m a -> n a and left :: forall a. n a -> m a. Without specifying the right semantics, what we are after does not even make sense.

• Note taken on Thu, Feb 9, 2023 15:00
  

  Not that tricky anymore! There was only contravariance in Filter and now I’ve just removed it.

• Note taken on Thu, Feb 9, 2023 18:26
  

  Well, I was wrong above. The mere presence of StateT (F m) is contravariant in m, because it takes the previous state as input. I’ve spent the entire afternoon attempting to make it work, just to realize this. 😢

  So, it’s impossible/not well defined.