Open miakramer opened 4 years ago
You can update the metas from within pollen.rkt
. You can't use define-meta
but you can write your own function to do the same thing:
(define (set-meta key val)
(define metas (current-metas))
(unless (not metas)
(current-metas (hash-set metas key val)))
current-metas
is a parameter. So you can either retrieve it using the zero-argument form, or change it using the one-argument form.
Metas added in this way will be included in the cached metas for each source.
My understanding is that this didn't used to be possible, but now is.
In terms of walking over lots of Pollen documents, I've found you can get some decent speed improvements by collecting metas/docs into vectors rather than lists.
Something along the lines of:
(define (get-all-metas page-list)
(for/vector ([page (in-list page-list)])
(get-metas page)))
I was able to get a complete insert of info for 48 Pollen documents into a SQLite database down to about 1.6 seconds on my 2015 laptop with this function which uses all the tricks:
As you can see, I'm doing some pretty heavy post-pollen.rkt
processing of both docs and metas in that file. I'm going to rewrite it so that everything I need is in the metas though.
Thanks for the tips!
I'm working on a book that's heavily cross-referenced, and I'm using LaTeX style references (so you put a
◊label{some-name}
and can refer to it with◊ref{some-name}
, which will put some human-understandable text like "Subsection 3.2.1" or "Table 6.2" as the link text. I have a working system, but it required a separate compilation step (which I calledassemble.rkt
). Essentially, it has two modes: a quick iteration mode using the built-in server that doesn't touch anything cross-page, and a 'full' mode that compiles all pages at once.The reason I did it this way is that it doesn't seem like metas can be modified from within
pollen.rkt
, I assume because they seem to be an immutable hash table that's worked out before the rest of the execution. So, loading other pages for each page quickly becomes an O(n^2) problem (since searching for labels requires traversing the document tree) if only usingpollen.rkt
, so I made a file that loads all of the pages first and then resolves the references. It works pretty well, but I was wondering if there's something obvious I've missed that would make this work better? I'm also using it for citations from a BibTeX database that auto-generates a bibliography page, and for a global table of contents generation.assemble.rkt
works pretty well, actually, but it just feels a little inelegant since I essentially leave 'marker' elements inpollen.rkt
that then are actually processed later.