IRC channel logs

<daviid>,use (rnrs enums (6)) -> error While executing meta-command: ERROR: In procedure symbol->string: Wrong type argument in position 1 (expecting symbol): (6)

<daviid>is ,use (rnrs enums) in this particular case equivalent?

<paroneayea>hello everyone!

<rain1>hi :)

<amz3>héllo guilers!

<rain1>hello!

<fhmgufs>In GOOPS there are keywords for slot initialization. How can I test whether the function call provides these?

<sneek>Welcome back fhmgufs, you have 1 message.

<sneek>fhmgufs, daviid says: I pushed a fix for gtk-tree-path-new-from-string to the guile-gnome git repo, devel branch

<fhmgufs>Ok, good!

<fhmgufs>sneek: botsnack

<sneek>:)

<fhmgufs>^ I just want to call a function if the slot is initialized by keyword.

<paroneayea> http://dustycloud.org/gfx/goodies/8sync-site-mockup.png

<paroneayea>wingo: davexunit: ^^^ site mockup

<stis>heya guilers!

<paroneayea>hi stis

<davexunit>paroneayea: looks nice!

<davexunit>more super low resolution fun with sly https://media.dthompson.us/mgoblin_media/media_entries/51/lowrezjam-3.gif

<paroneayea>davexunit: :D :D

<ArneBab>paroneayea: that looks great!

<ArneBab>davexunit: cool!

<paroneayea>ArneBab: :)

<davexunit>thanks :)

<paroneayea>davexunit: got time to explain some things about Huant to me?

<paroneayea>davexunit: I'm working on the 8sync site, as you may have guessed.

<davexunit>paroneayea: I can try

<paroneayea>davexunit: good-enough :)

<paroneayea>davexunit: I'm trying to understand builders

<paroneayea>it looks like they just return lists of procedures

<paroneayea>is this so?

<davexunit>ACTION refreshes memory

<davexunit>one sec while I page some things into my brain cache

<paroneayea>:)

<paroneayea>.o$% ~=LOADING=~ %$o.

<davexunit>paroneayea: yeah, a builder is just a procedure that accepts 2 arguments: site and posts

<davexunit>the procedures you are looking at *return* builders

<davexunit>static-directory, blog, etc.

<davexunit>and when run, they return lists of pages or assets

<paroneayea>davexunit: got it!

<paroneayea>davexunit: and pages are plaintext things

<paroneayea>and assets are blobby file locations?

<davexunit>paroneayea: yeah

<paroneayea>ACTION misuses blobby maybe but you know what I mean

<davexunit>pages are objects that hold some sxml

<paroneayea>haunt-libre: removes all asset blobs from your sites

<davexunit>that get rendered as html

<davexunit>;)

<paroneayea>"where did my images go...?"

<davexunit>but yeah, assets are arbitrary files that are copied verbatim from source to destination

<paroneayea>davexunit: cool.

<davexunit>I often wonder how long it will take haunt to have a dependency structure like guix or make...

<paroneayea>:)

<paroneayea>davexunit: you could even keep the same layers you have

<paroneayea>and add a dag layer that "builds" the list

<davexunit>part of me is like "oh no what I am doing with my life" and the other part of me is like "well now I can figure out which parts of the site *really* need rebuilding"

<paroneayea>:)

<davexunit>because rebuilding everything every time is pretty silly.

<paroneayea>dag, yo.

<davexunit>at the same time, it's hard! how could you know that a page references a static asset?

<davexunit>you'd still have to read it and then scan it for the file name in question, but it might never be a literal string in the document if it is computed programmatically.

<davexunit>so there might not be as much of a win as I once thought.

<davexunit>changing a single post requires so many things to be rebuilt anyway, might as well just do the whole damn thing.

<paroneayea>davexunit: it's an optimization that can be worried about at a future time

<davexunit>yeah

<paroneayea>I think there are more important needs in haunt right now

<paroneayea>like complete docs :)

<davexunit>agreed

<davexunit>right now I'm happy that things are super flexible.

<davexunit>can generate atom feeds and stuff. I have my syntax highlighter hooked up to my WIP site.

<davexunit>paroneayea: in your opinion, what would be the most important documentation to write?

<davexunit>I'd like to release 0.2 before too long, and while I can't promise to have *complete* docs, I'd like to at least write something adequate for people to get started.

<davexunit>paroneayea: pushed your patch that you sent me awhile ago, btw. thanks!

<paroneayea>davexunit: yay!

<paroneayea>davexunit: hm, I'm not sure what's the most important docs. Maybe adding a section on "How Haunt works" would help, so you know what the builder and stuff does

<paroneayea>i'm not sure though.

<davexunit>okay

<paroneayea>davexunit: I'll look further later and think :)

<davexunit>I think explaining the basic architecture is a good idea

<paroneayea>davexunit: notably the "programming inteface" section is totally missing

<davexunit>so thanks!

<paroneayea>davexunit: yeah

<paroneayea>davexunit: right now it's a "lisp/scheme hacker's website tool"

<paroneayea>which is pretty cool

<paroneayea>davexunit: so I think focusing on that is fine

<davexunit>that's roughly the target audience

<paroneayea>there are a lot of other "friendlier" site tools out there