07:34 <guardian> morning

08:35 <guardian> hmm tempted to give liquid a try instead of erb

08:35 <guardian> currently I have e.g. <%= image('foo', :align => center) %>

08:36 <guardian> not sure {% ... %} makes a difference in fact

08:37 <guardian> any opinion?

11:01 <guardian> ddfreyne: I have Compass.add_project_configuration(File.join(File.dirname(__FILE__), 'compass.rb')) in _factory/Rules

11:02 <guardian> ddfreyne: whenever I change _factory/compass.rb nanoc doesn't see the changes

11:03 <guardian> ddfreyne: anything I can do?

15:43 <tom[]> guardian: a similar question constantly recurs in php. but i've yet to come across a template system for which i can say, it actually makes things easier in the big picture. there's a reduction in visual ugliness for simple stuff but, otoh, <%= ... %> or <?= ... ?> is really not intolerable

19:52 <guardian> tom[]: agreed, I'll stick with erb, I'm not writing an app, erb can't do much harm

20:30 <ddfreyne> guardian: Difficult problem with _factory/compass.rb

20:33 <bobthecow> tom[]: the point of using a templating engine with php isn't that it makes things easier, it's that it enforces a constraint.

20:34 <ddfreyne> guardian: you could read the compass.rb file, hash it and stick it in config

20:34 <ddfreyne> That way there'll be an implicit dependency

20:34 <ddfreyne> (But still icky, I know)

20:35 <ddfreyne> Maybe nanoc needs a depend_on_files() thing.

20:45 <bobthecow> ddfreyne: you could fake "require" and use it for generating file dependencies?

20:47 <guardian> ah guys you're awake, right now I have the following problem: in layout/default.haml I wrote "- toc = toc(@item)" and my toc(item) helper generates a toc from item.compiled_content

20:47 <guardian> and this triggers a recursive compilation exception :/

20:47 <ddfreyne> guardian: You should use yield instead of item.compiled_content

20:48 <ddfreyne> guardian: a page cannot include itself because that'd be infinitely recursive

20:48 <guardian> toc(yield) ?

20:48 <ddfreyne> yes

20:49 <guardian> then that assumes toc(item) becomes toc(html) right?

20:49 <ddfreyne> guardian: Well, that'll only work in a layout, but I am assuming it is a layout

20:49 <ddfreyne> guardian: toc(@item, html) maybe… if you need other parts of the item apart from the content

20:50 <guardian> can't I do toc(rep) ?

20:50 <guardian> this is the toc helper in question: https://gist.github.com/gpakosz/0c279ec14d267fdd26b9

20:50 <ddfreyne> guardian: You can create a snapshot, and then use item.compiled_content(:snapshot => something)

20:50 <guardian> I debbuged it before trying to call it from my layout

20:51 <guardian> ah yeah snapshot, I tried with :snapshot => :pre with same failure

20:52 <ddfreyne> guardian: Maybe :pre is created after the ToC is built?

20:53 <guardian> the only place where I want call, and where I effectively call that toc() helper, is in layout/default.haml

20:54 <guardian> interesting: in layout.haml, I'm calling binding.pry to get an interactive session

20:54 <guardian> and when I call @item.compiled_content for then it complains

20:54 <guardian> Nanoc::Errors::UnmetDependency: The current item cannot be compiled yet because of an unmet dependency

20:57 <guardian> I didn't expect not being able to call compiled_content(:snapshot => :pre) on the very same item being laid out

20:58 <ddfreyne> guardian: When are you calling the toc helper? At what stage in filtering/layouting?

20:59 <guardian> I call the toc() helper from without layouts/default.haml

20:59 <guardian> items are filters, and layout 'default' happens last

20:59 <guardian> actually, after layout 'default' there's filter :rubypants

21:01 <ddfreyne> Hmmmm… I need to investigate that

21:01 <guardian> http://pastebin.com/1vJUFyWX

21:01 <ddfreyne> guardian: Anywya, you can (and should) use `yield` in layouts to get the content of the previous phase

21:01 <guardian> item being laid out is /documentation/basics/analysis/

21:02 <guardian> and calling @compiled_content on @item complains about unmet dependency on /documentation/basics/analysis/

21:02 <guardian> which is the same item

21:02 <ddfreyne> guardian: There are some limitations with when you can call #compiled_content

21:02 <ddfreyne> It's a bit too strict at times

21:03 <guardian> ok

21:03 <guardian> another thing surprising, @item_rep.snapshots is empty

21:03 <guardian> at the time @item is being laid out

21:04 <ddfreyne> guardian: you can use `yield` instead of @item.compiled_content

21:04 <guardian> yeah I understood :)

21:04 <guardian> still, I'm trying to give feedback about what I'm observing

21:06 <ddfreyne> @item_rep.snapshots being empty is weird though

21:14 <ddfreyne> Anyway, sleep time!

21:14 <guardian> good night

21:15 <guardian> I can reproduce @item_rep.snapshots being empty on a stock site created with create-site, with current master branch

21:42 <guardian> ddfreyne: so yeah @item_rep.snapshots only contains snapshots added to Rules, not :raw, :pre, :post and :last snapshots