I recommend sorting this out in the REPL, and then moving back to the template.
For instance, it should be possible to preview the result like so (where `doc` is imported from "your-source.poly.pm"): #lang racket (require pollen/core "your-source.poly.pm") (select 'line-image doc) Though as to "line-image is a tag defined in my pollen.rkt file" — keep in mind that `select` works on the output, not the input. So if `line-image` doesn't actually create a `line-image` tag in the output, then `select` indeed will not work. > On Mar 15, 2019, at 9:33 AM, Brendan Stromberger > <brendanstromber...@gmail.com> wrote: > > Google Groups glitched out on me. To finish my post, is there a way to > ◊(select) entire txexpr's from a document that are defined in Pollen.rkt? The > only way I can seem to get a return value from ◊(select) is when the contents > of the tag are a simple string. > > On Friday, March 15, 2019 at 11:31:51 AM UTC-5, Brendan Stromberger wrote: > Hi there, I'm trying to use ◊select in my template, but no matter what I try > to select, it returns nothing when rendered. > > Here are some facts: > My template file is called hexagram-template.html.p > My .pm files that use this template are in the same directory, with the > extension (unsure if this matters) *.poly.pm <http://poly.pm/> > I am certain that this template is being used by my .pm files. > The tags that I am trying to select from my template are unnested (not sure > if that matters) > I am trying to use select in the following manner from my template file: > ◊(select 'line-image doc) > line-image is a tag defined in my pollen.rkt file and used in my .pm files. > It returns a txexpr. I want to use (select) to include this txexpr in my > template. I want to use select this way, because I have 64 individual pages > that all have the exact same structure, and I want to pare those pages down > to a bare minimum, and use my template to describe the layout entirely, so I > can easily shift the layout of elements around within each page all at once. > If I use ◊(->html doc) on its own, I lose a lot of that flexibility in this > particular case. > I notice that if I have a tag in my document, for instance ◊hello{world}, and > then use ◊(select 'hello doc) from my template, "world" is rendered > correctly. Does select only handle cases where the tag returns a simple > string? Is there a way to > > > -- > You received this message because you are subscribed to the Google Groups > "Pollen" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pollenpub+unsubscr...@googlegroups.com > <mailto:pollenpub+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to pollenpub+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
