> On May 26, 2019, at 11:11 PM, Joel McCracken wrote:
> I have a file build.rkt that first builds all of the possible destinations in
> a hash. However, I need to somehow access that data from the `link` tags I am
> making. Thing is, nothing I have tried works, except for writing the
> desti
Joel and I each shared our approaches to footnotes a while back
(https://groups.google.com/d/msg/pollenpub/laWL4SWx0Zc/bNGZyKpABQAJ)
I now have a more complete citation system running in my Pollen setup:
- https://sanchom.github.io/automating-citations.html
-
https://github.com/sanchom
Why not just construct the links "blind"? For example
(require net/uri-codec)
(define (section name . elements)
`(h2 [[id ,(uri-encode name)]] ,@elements))
(define (xref-link file id . elements)
`(a [[href ,(format "~a.html#~a" file id)]] ,@elements))
(The uri-encode is
On Mon, May 27, 2019 at 1:38 PM Matthew Butterick wrote:
Why doesn't it work to `provide` the hash of destinations from
> "pollen.rkt"?
>
I suppose I might be able to do that, but I don't think it will solve my
overall problem. `pollen.rkt` gets loaded/computed repeatedly, once per
page, so it
> On May 27, 2019, at 3:20 PM, Joel McCracken wrote:
>
> I suppose I might be able to do that, but I don't think it will solve my
> overall problem. `pollen.rkt` gets loaded/computed repeatedly, once per page,
> so it would lose context between pages. I would then have to re-compute it,
>
Looks cool! You should turn this into an installable Racket package with docs &
tests, perhaps? I'm sure others would benefit from your suffering.
> On May 27, 2019, at 12:06 PM, sanc...@gmail.com wrote:
>
> Joel and I each shared our approaches to footnotes a while back
> (https://groups.googl
So yes this might be unnecessary. In my mind, the most efficient way to
implement what I want is to generate the references data up front, and then
render what I need with that data. So, basically I am using a two step
process, step one is analysis, step two is rendering.
Let me try to describe wh
> On May 27, 2019, at 5:24 PM, Joel McCracken wrote:
>
> The point is I was hoping to avoid having to rebuild the entire links table
> every time I process another file.
Here's a perhaps simpler way to do it that you could customize further.
The Pollen sources define metas for each target t
