ddfreyne changed the topic of #nanoc to: 3.6.11 (may 9th) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
jugglinmike has quit [Quit: Leaving.]
ddfreyne has quit [Ping timeout: 252 seconds]
ddfreyne has joined #nanoc
alerante has quit [Remote host closed the connection]
alerante has joined #nanoc
alerante has quit [Ping timeout: 252 seconds]
cDlm has quit [Quit: Lingo - http://lingoirc.com]
cDlm has joined #nanoc
prxq has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 252 seconds]
cDlm has quit [Quit: Computer has gone to sleep.]
cDlm has joined #nanoc
prxq has quit [Remote host closed the connection]
alerante has joined #nanoc
alerante has quit [Ping timeout: 255 seconds]
<guardian> o/
<guardian> currently my nanoc setup generates html, I think I'll favor something that compiles html into pdf
<guardian> instead of generating tex
<guardian> bobthecow: you would favor phantomjs over pdfkit?
<guardian> ddfreyne: what was a blocker with prawn?
<guardian> ddfreyne: also could you detail the content pipeline you use? Currently I have $ NANOC_TARGET=offline|www nanoc compile
<guardian> ddfreyne: offline target produces urls ending in .html, this is for zipping the doc and shipping that to a customer
<guardian> ddfreyne: www target produces clean urls, this is for web hosting
<guardian> ddfreyne: so far, all pipeline is the same, only paths differ in routing rules
<guardian> ddfreyne: and now I'm wondering whether I could (or should) have NANOC_TARGET=pdf and make nanoc output a single pdf file in output/ folder (hereby routing everything to nil, but the compiled pdf item)
<guardian> ddfreyne: not sure if it's a wise approach, nor whether it's feasible
<guardian> I would appreciate insight and ideas on this :) thanks!
alerante has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
jugglinmike has joined #nanoc
DarkOrb has quit [Ping timeout: 245 seconds]
stbuehler has quit [Quit: leaving]
<ddfreyne> guardian: I personally would not use different targets, but rather have nanoc compile everything at the same time
<ddfreyne> guardian: PRawn is nice, but writing something that generates nice PDFs is a lot of work nonetheless
alerante has joined #nanoc
stbuehler has joined #nanoc
alerante has quit [Ping timeout: 265 seconds]
alerante has joined #nanoc
prxq has joined #nanoc
<guardian> ddfreyne: well nanoc compile everything at the same time even doesn't fly for www vs offline modes
<guardian> ddfreyne: that would create both output/foo/bar/index.html and output/foo/bar.html
<guardian> ddfreyne: from there it's painful to split and package properly
<guardian> now that I think about it, how can I make sure nanoc sees my NANOC_ENV or NANOC_TARGET environment variables and trigger full recompile upon change?
cDlm has quit [Ping timeout: 260 seconds]
jugglinmike has quit [Ping timeout: 255 seconds]
alerante has quit [Remote host closed the connection]
cDlm has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
alerante has joined #nanoc
alerante has quit [Ping timeout: 276 seconds]
cDlm has quit [Quit: Computer has gone to sleep.]
<bobthecow> guardian: i'm with ddfreyne. have everything compile at the same time, and have your output directory split into output/www, output/offline, output/pdf
VitamineD has joined #nanoc
prxq has quit [Remote host closed the connection]
<bobthecow> guardian: i've never done pdfkit, tbh.
jarr0dsz has joined #nanoc
prxq has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 255 seconds]
<guardian> sorry been afk for a while
<guardian> well having output/www output/offline output/pdf requires compiling 3 times though
<guardian> when for output/offline and output/www only routing changes
<guardian> well actually no everything changes because links change
<bobthecow> no, compile them all in one pass.
<bobthecow> use item reps to route to both sets of paths.
<guardian> 1 rep == 1 compile right?
<guardian> currently reading Prawn readme... it says it's not for HTML + CSS and will never be. Which makes me thing it doesn't fly in my case because I'm already generating tons of HTML with inline SVG
<guardian> bobthecow: how can I have a single compile but route to 2 paths? in nanoc 3.x
<guardian> can a rep steal the content of another rep? maybe with a :steal_rep filter
<bobthecow> you can use compiled content.
<guardian> yeah through a filter I guess
<guardian> like for :rep => :www I have a filter chain, and for :rep => :offline I have a single :steal filter that returns @item.compile_content(:rep => :www)
<guardian> that could work
<guardian> if someone has another idea I'm all ears :)
<bobthecow> or you could dynamically create items (rather than reps) that just reference the original item and steal its compiled content?
<bobthecow> oh, for your first thing don't use a filter, use a layout.
<bobthecow> <%= @item.compiled_content :rep => :www %>
jugglinmike has joined #nanoc
<guardian> what do you mean by "your first thing"
<bobthecow> "<guardian> can a rep steal the content of another rep? maybe with a :steal_rep filter"
<guardian> k
<guardian> not sure what's better between creating items and using reps
<guardian> using reps sounds more logical
<guardian> if the two solutions involve a :steal_rep filter, then I guess reps make more sense
prxq has quit [Ping timeout: 255 seconds]
gregkare has joined #nanoc
gregkare has left #nanoc [#nanoc]
alerante has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]