fluid-work IRC Logs-2013-04-02

[08:27:35 CDT(-0500)] <michelled> yzen: do you need any help with the self voicing work?

[08:28:14 CDT(-0500)] <colinclark> yzen: How'd it go last night?

[11:55:26 CDT(-0500)] <brick__> Hi Justin_o, I have missed catching you quite a few times now.

[11:55:45 CDT(-0500)] <Justin_o> brick__: hello

[11:56:28 CDT(-0500)] <brick__> I was here yesterday to discuss about, the 'CMS plugins for Infusion components' project.

[11:56:36 CDT(-0500)] <brick__> I came to know that it was your idea.

[11:57:31 CDT(-0500)] <michelled> colinclark please take a look at the build site

[11:57:39 CDT(-0500)] <michelled> the borg issue should be fixed now

[11:57:59 CDT(-0500)] <michelled> I would like more eyes on this before we ask avtar to push to the actual demo site

[11:58:07 CDT(-0500)] <michelled> jessm ^

[11:58:36 CDT(-0500)] <brick__> I hope you are aware of Jekyll, the static blog-aware generator; I was of the question whether a,static-site generator like jekyll, albeit widely used, would it be considered a CMS..

[11:59:17 CDT(-0500)] <jessm> michelled: url?

[11:59:48 CDT(-0500)] <Justin_o> brick__: actually that was anastasiac project idea

[11:59:51 CDT(-0500)] <Justin_o> sorry to say

[11:59:57 CDT(-0500)] <avtar> jessm: http://build.fluidproject.org/floe-infusion-demo/integration-demos/uiOptions/ClimateChange.html

[12:00:14 CDT(-0500)] <Justin_o> brick__: anastasiac is here today and should have some thoughts

[12:00:29 CDT(-0500)] <avtar> michelled: no echo

[12:00:45 CDT(-0500)] <brick__> I see, hello anastasiac.

[12:00:45 CDT(-0500)] <brick__>

[12:01:12 CDT(-0500)] <brick__> Thanks Justin_o.

[12:01:19 CDT(-0500)] <anastasiac> brick__, I'm not really familiar with Jekyll. Could you explain a bit what it is, what it does?

[12:01:49 CDT(-0500)] <avtar> anastasiac: https://gist.github.com/davatron5000/2254924

[12:01:58 CDT(-0500)] <avtar> there are quite a few static site generators now

[12:02:48 CDT(-0500)] <colinclark> It's too bad Festival's default voice sucks

[12:02:56 CDT(-0500)] <avtar> anastasiac: this https://github.com/mojombo/jekyll is the one brick__ is referring to

[12:02:57 CDT(-0500)] <colinclark> but it's working nicely enough

[12:03:18 CDT(-0500)] <jessm> michelled: it looks great to me

[12:03:21 CDT(-0500)] <jessm> i was in chrome

[12:03:27 CDT(-0500)] <jessm> is that where i should be?

[12:03:31 CDT(-0500)] <brick__> Alright jekyll, written in ruby is a blog-aware static site generator; it takes layouts written in liquid syntax and generates appropriate HTML files, according to the specified YAML config.

[12:03:38 CDT(-0500)] <michelled> yep, chrome is where we've done most of our testing and fine tuning

[12:03:58 CDT(-0500)] <michelled> we'll get other browsers as we move stuff from demo to master

[12:04:06 CDT(-0500)] <anastasiac> brick__, what does it mean to be "blog-aware" in this context?

[12:04:15 CDT(-0500)] <brick__> You can even extend it, using other plugins, JS, ruby, etc.. I have my jekyll site here: fatman.in

[12:04:34 CDT(-0500)] <michelled> alright then, avtar can you please push to the demo site?

[12:04:50 CDT(-0500)] <colinclark> +1, ship it

[12:05:14 CDT(-0500)] <brick__> blog-aware, would mean that it is blogger friendly; you can easily maintain categories, pagination, an archive, tags, erc, etc...

[12:05:20 CDT(-0500)] <jessm> +1

[12:05:30 CDT(-0500)] <avtar> michelled: doneskys

[12:05:33 CDT(-0500)] <avtar> http://demo.floeproject.org/integration-demos/uiOptions/ClimateChange.html

[12:05:45 CDT(-0500)] <michelled> AWESOME! fluid-everyone - thanks for all the hard work

[12:06:11 CDT(-0500)] <brick__> While being completely static..

[12:06:59 CDT(-0500)] <anastasiac> interesting. how does that work, brick__? would tags, categories etc. be written into the layouts??

[12:09:01 CDT(-0500)] <brick__> anastasiac: here's my Jekyll site, again: fatman.in There is a config file, in it you would specify a categories directory, and any folder in that would be considered a category

[12:09:53 CDT(-0500)] <brick__> As for tags you mention them in YAML front matter, jekyll automatically detects that and builds your posts, written in markdown, or a markup language of your choice...

[12:09:59 CDT(-0500)] <anastasiac> so brick__, how would you add a new blog post to your site? just edit a static file, and regenerate?

[12:10:47 CDT(-0500)] <brick__> Yes there is a special folder for that called _posts; you write posts in markdown, generally, with corresponding YAML front matter..

[12:11:04 CDT(-0500)] <brick__> and a 'jekyll' command does all the magic

[12:11:46 CDT(-0500)] <brick__> I would love to share my jekyll site source code with you anastasiac.

[12:12:06 CDT(-0500)] <colinclark> fluid-everyone: I echo michelled's thanks. You guys did an amazing job with this demo. I'm really looking forward now to taking a breath and refining these features so they can get into master soon!

[12:14:23 CDT(-0500)] <brick__> anastasiac, this is how a post text looks, https://dl.dropbox.com/u/19284765/2012-07-01-The_One_that_I_always_wanted.md

[12:15:11 CDT(-0500)] <brick__> https://dl.dropbox.com/u/19284765/_config.yml; that is the config file that goes in the root

[12:15:43 CDT(-0500)] <brick__> hope it gives you a vague idea what jekyll is, and you can mention how a page is going to look in _layouts

[12:16:11 CDT(-0500)] <brick__> you may see, that I have mentioned in the post text file, layout; as post

[12:16:38 CDT(-0500)] <anastasiac> brick__, what kinds of plugins can you use?

[12:16:38 CDT(-0500)] <brick__> In _layouts directory I have a file called post.md, which includes all the html that this post should contain

[12:17:59 CDT(-0500)] <brick__> You see, there is an _includes folder which you can keep in your root, anything that you build in that will be included all over the side...; also people build ruby plugins to make their blogs more the way they want

[12:18:38 CDT(-0500)] <brick__> for example I use a different category_generator

[12:18:43 CDT(-0500)] <brick__> and page_preview plugin

[12:19:02 CDT(-0500)] <brick__> To just give a preview of my posts before the actual thing..

[12:19:55 CDT(-0500)] <brick__> I generate a tag page using this liquid syntax

[12:19:57 CDT(-0500)]

[12:20:22 CDT(-0500)] <brick__> That works because of tag_iterator plugin written in ruby

[12:21:03 CDT(-0500)] <brick__> this is the html, complete:

[12:21:04 CDT(-0500)]

[12:21:33 CDT(-0500)] <brick__> is it making any sense, anastasiac; I have never explained this to anyone efore?

[12:21:37 CDT(-0500)] <brick__> *before

[12:21:52 CDT(-0500)] <brick__> so maybe I am bad at it

[12:26:39 CDT(-0500)] <brick__> so, anastasiac?

[12:36:07 CDT(-0500)] <anastasiac> sorry, brick__, I was distracted by a conversation here. This makes some sense, though I'm still learning.

[12:36:45 CDT(-0500)] <anastasiac> brick__, have you had a chance to learn a little bit about Infusion components? do you have any ideas on how infusion components might be made available to someone using Jekyll?

[12:39:55 CDT(-0500)] <brick__> Yes, anastasiac, I have browsed through the Infusion components, I have some ideas on how to incorporate the, maybe through an 'extension' or through an include, by including it in a folder it would automatically come over all the pages that are being built by jekyll; or I could put it in the form of an extension, which is more intuitive; and which would take work...

[12:40:47 CDT(-0500)] <brick__> I am quite adept at HTML and CSS though I am a little backward when it comes to JS, so I am building up on that...

[12:41:32 CDT(-0500)] <brick__> I plan to release a complete Jekyll setup, called fusion which would include fusion components for jekyyl

[12:42:36 CDT(-0500)] <brick__> Along with that I plan to also build an include file or an extension for the existing jekyll users who wouldn't want to move away from their setups, but would like to incorporate infusion

[12:43:30 CDT(-0500)] <brick__> Also; Table of Contents as infusion puts it would be a little different for blogs; if I am getting it right, I would want to explore on how they can be changed to suit jekyll..

[12:45:21 CDT(-0500)] <anastasiac> brick__, our goal would be to make it very easy for someone using Jekyll to include Infusion components. So, for example, to add UI Options to the entire site, or to use the Infusion Video Player for videos embedded in a page. We'd like for Jekyll users to not have to learn all about infusion and JS coding. Do you imagine that an extension or an include could do that? (I don't know enough about Jekyll yet to judge)

[12:48:04 CDT(-0500)] <brick__> Yes, ansatasiac, you wouldn't have to learn anything new to have infusion set up for Jekyll; for instance, I don't know enough ruby, but I use powerful ruby plugins to extend my site; any jekyll user would have to be little familiar with jekyll, for adding extensions or having an include; it is akin to a wordpress user knowing how to change the font size in his post.

[12:49:32 CDT(-0500)] <brick__> Also, my internet speed is terrible; it has downgraded to 10 KBPS from 5 Mbps, because of a cable cut somewhere in an ocean; or else I would have made a video explaining Jekyll, which would have been great.

[12:50:08 CDT(-0500)] <brick__> Are you GMT - 5:0, anastasiac?

[12:51:46 CDT(-0500)] <anastasiac> normally, brick__, yes, but right now we're in Daylight Saving Time, so I'm GMT - 4:00

[12:51:56 CDT(-0500)] <anastasiac> where are you?

[12:52:39 CDT(-0500)] <brick__> I am GMT + 10:30, India; where I am, we don't know what DST is.

[12:54:57 CDT(-0500)] <anastasiac> brick__, jekyll may not be a CMS, but it still seems like something that would be useful to have Infusion component plugins/extensions/includes/whatever for. It seems like an interesting platform. I will certainly play around with it

[12:55:13 CDT(-0500)] <brick__> Also, I hope you might have looked at my site; there are in fact a lot of people who use Jekyll, it was built for GitHub.

[12:55:28 CDT(-0500)] <anastasiac> yes, I'll definitely do some research

[12:56:23 CDT(-0500)] <brick__> Sure, anastasiac, I hope you like it.

[12:58:23 CDT(-0500)] <brick__> However this may go, I will get around to building a sample jekyll site including the infusion components, or better I will give my own site a taste of infusion.

[12:59:31 CDT(-0500)] <brick__> Thanks a lot, anastasiac, you were very helpful, I appreciate it a lot. See you.

[15:13:01 CDT(-0500)] <Bosmon> Hi cindyli1 - are you there?

[15:13:24 CDT(-0500)] <cindyli1> yes, Bosmon

[15:16:05 CDT(-0500)] <Bosmon> cindyli1 - great - is there a branch of work I should look at at the moment?

[15:16:23 CDT(-0500)] <Bosmon> Also, I had a comment about an old revision of your enactors work I remembered, that I should pass on before I forget it again

[15:16:39 CDT(-0500)] <cindyli1> not yet, Bosmon, justin and i are still writing up unit tests for the refactored UIO branch

[15:16:47 CDT(-0500)] <Bosmon> When you had the version which attached a "guard" function which was resolved as an invoker, before you converted over to "source tracking"

[15:17:15 CDT(-0500)] <Bosmon> You had a comment which stated that the invoker was not resolved because of the early execution of the guard registration

[15:17:37 CDT(-0500)] <Bosmon> These cases are just the ones I was referring to when I sent the mail about "overinjection" a few weeks back, initially to justin_o

[15:17:57 CDT(-0500)]

[15:18:07 CDT(-0500)]

[15:18:23 CDT(-0500)] <Bosmon> cindyli1 - yes, the solution is to refer to it yourself

[15:18:33 CDT(-0500)] <Bosmon> As one of your own invoker arguments

[15:19:08 CDT(-0500)] <cindyli1> ya, understood

[20:11:54 CDT(-0500)] <supungs> Hi giuys

[20:12:00 CDT(-0500)] <supungs> I'm new here

[20:14:29 CDT(-0500)] <supungs> Can anybody suggest me some easy bugs to fix? So I can get familiar with the source.