Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 10 11:46

    ddfreyne on master

    Upgrade Nanoc (compare)

  • Nov 10 11:39

    ddfreyne on 4.11.14

    (compare)

  • Nov 10 11:39

    ddfreyne on nanoc-core-v4.11.14

    (compare)

  • Nov 10 11:38

    ddfreyne on nanoc-cli-v4.11.14

    (compare)

  • Nov 10 11:38

    ddfreyne on master

    Set version to 4.11.14 Add release notes for 4.11.14 (compare)

  • Nov 10 10:42
    josepegea commented #1462
  • Nov 10 09:33

    ddfreyne on fix-dep-bug

    (compare)

  • Nov 10 09:32

    ddfreyne on master

    Let dep tracker properly recogn… Merge pull request #1464 from n… (compare)

  • Nov 10 09:32
    ddfreyne closed #1464
  • Nov 10 09:32
    ddfreyne closed #1463
  • Nov 08 19:50
    ddfreyne edited #1464
  • Nov 08 19:50
    ddfreyne labeled #1464
  • Nov 08 19:50
    ddfreyne opened #1464
  • Nov 08 19:49

    ddfreyne on fix-dep-bug

    Let dep tracker properly recogn… (compare)

  • Nov 08 19:47
    ddfreyne opened #1463
  • Nov 08 19:47
    ddfreyne labeled #1463
  • Nov 08 19:43
    ddfreyne labeled #1462
  • Nov 08 19:43
    ddfreyne labeled #1462
  • Nov 04 16:13
    Fjan opened #1462
  • Nov 02 12:19

    ddfreyne on master

    Upgrade packages (and Nanoc to … (compare)

Denis Defreyne
@ddfreyne
I’d suggest against that; if it turns out that configurability is needed because 0.1 does not work for everyone, we can revisit that
(Otherwise, you end up with something that is so configurable that the config file becomes overwhelming)
Andri Möll
@moll
If it's only to bounce back a delete-and-create, you could then go with 50ms probably, too.
I've used LiveReload generally for a long time and I remember it requiring quite a bit of tweaking to find the sweet spot for each project — sometimes compiling JavaScripts or CSS to the output directory took a long time and having the browser constantly reload during that time was annoying. :P
Ideally Nanoc should signal a reload only once it has actually finished its compile cycle.
But with LiveReload being part of adsf instead of Nanoc, that may be more difficult practice than in theory.
Denis Defreyne
@ddfreyne
Hm yeah, good point… that’d be good to have
Denis Defreyne
@ddfreyne
@moll If you’re willing to add support for that to adsf, I’d be happy to help!
Andri Möll
@moll
I'm totally willing in principle, but unfortunately given how long my own OSS backlog is, it's unlikely I'll get to it soon. :innocent: I think I've got PRs on some projects open for a couple of years now. :P
I got my personal Nanoc powered site up a few weeks ago, too, and am trying to write for it. Took me only about 6 years I think. :P
Nanoc's been around for quite some time, hasn't it. :)
Thanks for still maintaining it!
Denis Defreyne
@ddfreyne
Haha :)
12.5 years now…
Predates RSpec 1.0, the iPad, Pluto being a planet, Obama becoming president, etc. It’s ancient
Andri Möll
@moll
Uh-oh, that means it took me longer to get my site up, too. :P I remember I've had two "coming soon" style personal sites before this final one.
Denis Defreyne
@ddfreyne
My site (https://denis.ws/) is now so simple that I could probably whip up something far simpler than Nanoc to maintain it, haha
Andri Möll
@moll
2010 is my earliest commit.
Haa, it is. You could've done that with... React. React with isomorphic server side rendering and three megs of client side JavaScript.
Denis Defreyne
@ddfreyne
I like React and I’d love to use its concept of components more, throughout all the sites I create.
I’ve been thinking about what Nanoc-with-components could look like — it’d probably involve revamping the rendering helper significantly.
Andri Möll
@moll
I just use JSX in JavaScript because it's lintable via ESLint, but don't use React. I use JSX on the server side with a few dozen lines to render HTML directly with https://github.com/moll/js-j6pack/. Works far better than the nonsense that is React on the server side.
Denis Defreyne
@ddfreyne
Oh nice — I really like that
Anyway, sleep time!
Andri Möll
@moll
Here's an Estonian site built in that fashion should you want a real life example: https://github.com/rahvaalgatus/rahvaalgatus. The JSX is in views, e.g. https://github.com/rahvaalgatus/rahvaalgatus/blob/master/views/error_page.jsx.
Nightie!
giodestone
@giodestone

should the has_key?("key") work for items in layouts? i.e. @item.has_key?("useImageCarousel") gives me NoMethodError: undefined method `has_key?' for <Nanoc::CompilationItemView identifier=/article-index.html>:Nanoc::CompilationItemView

If it helps its inside of a layout

giodestone
@giodestone
Nevermind, replacing has_key?() with key?() worked...
giodestone
@giodestone
Another rookie mistake key?() takes a :key not a 'string'
Denis Defreyne
@ddfreyne
The difference between symbols (:stuff) and strings in Ruby is so small that it wouldn’t make sense to have both anymore… but that’d involve changing Ruby as a programming language, which is not going to happen soon
Daniel Aleksandersen
@da2x
I’m looking at my nanoc -VV output. Is there any documentation for how to read it? https://pastebin.com/raw/9JACfj7x All the stages adds up to 10 sec, but site still takes 62 sec to compile? What is nanoc doing for the remaining 52 seconds? and how do I troubleshoot the memoization cache misses? (Or is it expected to have a high percentage of misses?) What causes misses? Result doesn’t change with repeated runs and no modified content or layouts.
Denis Defreyne
@ddfreyne
@da2x Most of this stuff is intended for myself to debug potential issues. It’s not documented, because I don’t want people to rely on this exact format and this exact information
@da2x The information in the stages table doesn’t contain all timing information in Nanoc; it only contains compilation itself (excluding loading the site from data sources, exluding preprocessing). This is something I’ve been meaning to change, but I imagine that loading and/or preprocessing is slow in your case, not compilation
The memoization cache misses should be fine. They’re more informative rather than indicating a problem.
Daniel Aleksandersen
@da2x
@ddfreyne ok, I had hoped the data would be more actionable.
My build time has more than doubled and I can’t quite figure out why.
Daniel Aleksandersen
@da2x
What happens after Compiling site…appears on screen and before Stage started: LoadStores when running nanoc -d? There’s where 47 of my missing 52 seconds are spent.
Denis Defreyne
@ddfreyne
@da2x I think that could be preprocessing
Daniel Aleksandersen
@da2x
@ddfreyne puts Time.nowat the start and end of my preprocessing block is only 1 second apart, though.
Denis Defreyne
@ddfreyne
Huh, hmmmm.
@da2x There should be a Stage started: BuildReps — how long does that take?
Daniel Aleksandersen
@da2x
@ddfreyne where should that be?
Denis Defreyne
@ddfreyne
It’ll also be in the output with nanoc -d
Unfortunately the debug output has no timestamps… I guess that would be useful to have
Daniel Aleksandersen
@da2x
Indeed.
@ddfreyne maybe half a second?
I’ve disabled cli output buffering and no line other than "Compiling site…" stays on screen for more than a second or two.
Denis Defreyne
@ddfreyne
@da2x The slowness is even before BuildReps then, correct?
Daniel Aleksandersen
@da2x
@ddfreyne yes, Stage started: LoadStores is the first line after its been stuck onCompiling site… for 47 seconds
Denis Defreyne
@ddfreyne
Does Stage started: BuildReps come after that?