jarr0dsz has quit [Remote host closed the connection]
VitamineD has joined #nanoc
VitamineD has quit [Quit: VitamineD]
pavelkunc has joined #nanoc
VitamineD has joined #nanoc
VitamineD has quit [Client Quit]
VitamineD has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
VitamineD has quit [Quit: VitamineD]
VitamineD has joined #nanoc
ics has joined #nanoc
jarr0dsz has joined #nanoc
jarr0dsz has quit [Max SendQ exceeded]
jarr0dsz has joined #nanoc
pavelkunc has quit [Ping timeout: 246 seconds]
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
pavelkunc1 has joined #nanoc
pavelkunc1 has quit [Ping timeout: 240 seconds]
jarr0dsz has joined #nanoc
VitamineD has quit [Quit: VitamineD]
<ddfreyne>
tom[]: By generating items I mean creating in-memory items in the preprocess block that aggregate the contents of several other items
<ddfreyne>
e.g. If you compile C source code, the .o files can be considered output of the .c files, but then you still need to combine the .o files into an executable, which will not have an on-disk source representation, because it is build from other items
jugglinmike has joined #nanoc
VitamineD has joined #nanoc
pavelkunc has joined #nanoc
jaspervd2 is now known as jaspervdj
VitamineD has quit [Ping timeout: 264 seconds]
<tom[]>
@ddfreyne: i see. so you were asking about the "merge DSL command to generate items" thing?
pavelkunc has quit [Ping timeout: 264 seconds]
pavelkunc has joined #nanoc
VitamineD has joined #nanoc
<ddfreyne>
yup
<tom[]>
iiuc, i would probably not use something like that
<tom[]>
because each combined/compressed final asset file is assembled from the same base set of sources
<tom[]>
what i have done is 1. put the sources somewhere with whatever basic compilation they need (eg sass). 2. specify null routing for them. 3. create items for final resource files and run then through erb and a suitable compressor. 4. these files contain likes like: <%= @items['/assets/css/base/'].compiled_content() %>
<tom[]>
this allows me to design a set of optimized final asset files, each specified in terms of it's own language and including content from other files
<tom[]>
simple, clear and gives me the control i want
tantalum has joined #nanoc
<tantalum>
Hi Guys,
<number-six>
tantalum: ddfreyne (19 days ago): How big is your site, in number of pages?
<tantalum>
number-six, ?
<tantalum>
Any way.
<tantalum>
I have a site and we need a desktop and a mobile version, with the same content
<tantalum>
I've used Item Representations to compile a mobile and desktop version
<tantalum>
but how do I route the representations?
<tantalum>
route '/content/pages/*', :rep => :mobile do .... end ?
<tantalum>
would that be it? the docs are a little vague on that subject
pavelkunc has quit [Ping timeout: 250 seconds]
pavelkunc has joined #nanoc
<ddfreyne>
tantalum: yes
<tantalum>
ddfreyne, Thanks... I'm compiling as we speak :-)