[08:17:00 EDT(-0400)] * apetro (n=apetro@71.0.0.232) has joined #fluid-work
[08:17:27 EDT(-0400)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[08:41:49 EDT(-0400)] * laurel (n=Laurel@142.150.154.178) has joined #fluid-work
[08:51:30 EDT(-0400)] * heidi_ (n=thesumme@142.150.154.101) has joined #fluid-work
[09:04:45 EDT(-0400)] * jsilvaa (n=jsilva@CABLE-72-53-95-24.cia.com) has joined #fluid-work
[09:08:56 EDT(-0400)] * yura (n=yura@142.150.82.64) has joined #fluid-work
[09:17:12 EDT(-0400)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[09:17:23 EDT(-0400)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[09:21:27 EDT(-0400)] * colinclark (n=colin@bas2-toronto09-1176406828.dsl.bell.ca) has joined #fluid-work
[09:37:47 EDT(-0400)] * michelled (n=michelle@CPE001310472ade-CM0011aefd3ca8.cpe.net.cable.rogers.com) has joined #fluid-work
[09:45:36 EDT(-0400)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[09:54:03 EDT(-0400)] * colinclark_ (n=colin@bas2-toronto09-1176131015.dsl.bell.ca) has joined #fluid-work
[09:57:04 EDT(-0400)] * anastasiac (n=stasia@142.150.154.189) has joined #fluid-work
[10:25:12 EDT(-0400)] * apetro (n=apetro@71.0.0.232) has joined #fluid-work
[10:29:03 EDT(-0400)] * anastasiac (n=stasia@142.150.154.189) has left #fluid-work
[10:29:18 EDT(-0400)] * anastasiac (n=team@142.150.154.189) has joined #fluid-work
[10:58:53 EDT(-0400)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[11:03:08 EDT(-0400)] <Justin_o> michelled: just noticed this page in the wiki http://wiki.fluidproject.org/display/fluid/Ant+script+for+Fluid+components
[11:03:28 EDT(-0400)] <Justin_o> i guess we'll have to edit it with the recent changes made
[11:03:46 EDT(-0400)] <michelled> yes
[11:04:16 EDT(-0400)] <Justin_o> there may be more changes with the build component, and fixing up those bugs with the url head re-writing so not sure if we should start this after that or before
[11:04:28 EDT(-0400)] * alisonbenjamin (n=alisonbe@142.150.154.101) has joined #fluid-work
[11:04:34 EDT(-0400)] <michelled> and link it to this page http://wiki.fluidproject.org/display/fluid/Custom+Build
[11:04:44 EDT(-0400)] <Justin_o> ah yes...
[11:04:47 EDT(-0400)] <Justin_o> that too
[11:05:11 EDT(-0400)] <Justin_o> maybe i'll just start by putting up a warning that the page is out of date and provide the link to the custom build page
[11:05:45 EDT(-0400)] <michelled> that makes sense. it's quite out of date
[11:06:08 EDT(-0400)] <michelled> at the bottom it mentions that the war is not automatically created which of course it is and has been for quite a while
[11:06:29 EDT(-0400)] <Justin_o> i think it's been a year or more since this page was updated...
[11:08:04 EDT(-0400)] <Justin_o> michelled: i've placed a warning at the top of the page
[11:08:18 EDT(-0400)] <michelled> thanks Justin_o
[11:30:43 EDT(-0400)] * elicochran (n=elicochr@dhcp-169-229-212-34.LIPS.Berkeley.EDU) has joined #fluid-work
[11:38:19 EDT(-0400)] <athena> i had a question about the fluid renderer
[11:38:41 EDT(-0400)] <athena> right now i'm iterating through my collection of items to manually build some hydrated component tree
[11:39:07 EDT(-0400)] <athena> we weren't sure if this was the right approach - namely, if that caused a loop both to build the component tree, and then a loop during the fluid rendering process
[11:39:20 EDT(-0400)] <athena> and we weren't sure if there was some more efficient way to be accomplishing this
[11:40:55 EDT(-0400)] <anastasiac> athena, I'm not sure I understand what you're already doing
[11:41:08 EDT(-0400)] <anastasiac> when you say "iterating through my collection of items"
[11:41:23 EDT(-0400)] <anastasiac> do you mean that your component tree has entries for all of your data??
[11:41:46 EDT(-0400)] <athena> well, basically i took a look at the rendering documentation i found in the wiki
[11:42:11 EDT(-0400)] <athena> and looped through the collection of the things i want displayed on the screen to build hydrated component trees like were in those examples
[11:42:23 EDT(-0400)] <athena> we weren't sure if that was what we were actually supposed to be doing
[11:43:09 EDT(-0400)] <anastasiac> if your data consists of something analogous to rows in a table, then the component tree not include all of the rows
[11:43:32 EDT(-0400)] <anastasiac> it would identify the markup in the template to replicate for each row
[11:43:49 EDT(-0400)] * anastasiac is not sure if she's making any sense
[11:43:57 EDT(-0400)] <athena> i'm sure you are, but i'm not sure i'm following 
[11:44:01 EDT(-0400)] <anastasiac>
[11:44:02 EDT(-0400)] <athena> is there an example somewhere i can look at?
[11:44:20 EDT(-0400)] <anastasiac> http://build.fluidproject.org/infusion/standalone-demos/pager/html/pager-render.html
[11:44:37 EDT(-0400)] <athena> ok, that's using the pager though, right?
[11:44:51 EDT(-0400)] <athena> we're just using the renderer itself
[11:44:53 EDT(-0400)] <anastasiac> yes, but also the renderer
[11:44:59 EDT(-0400)] <anastasiac> let me get a simpler example
[11:45:13 EDT(-0400)] <anastasiac> http://build.fluidproject.org/infusion/standalone-demos/renderer/html/programmatic-tree-menu.html
[11:45:37 EDT(-0400)] <anastasiac> http://source.fluidproject.org/svn/fluid/infusion/trunk/src/webapp/standalone-demos/renderer/ for the source
[11:46:03 EDT(-0400)] <anastasiac> note that the example doesn't actually render until you click the "render" button
[11:46:09 EDT(-0400)] <athena> right
[11:46:26 EDT(-0400)] <athena> so it does look like there's some code to build a component tree from the model?
[11:46:36 EDT(-0400)] <anastasiac> that particular version programmatically generates the component tree, which sounds like what you want to do
[11:46:42 EDT(-0400)] <athena> yeah
[11:46:54 EDT(-0400)] <athena> i think we just wanted to make sure that we did want to be programmatically generating the component tree
[11:47:03 EDT(-0400)] <athena> dan was concerned that we're looping through our data once to build the tree
[11:47:08 EDT(-0400)] <anastasiac> it's the better way
[11:47:17 EDT(-0400)] <athena> then the renderer is looping through the tree again to render the HTML
[11:47:27 EDT(-0400)] <athena> and wanted to make sure that we're not missing something
[11:47:54 EDT(-0400)] <anastasiac> eventually, Infusion will have utility functions to build trees for you, but we don't have that yet 
[11:48:16 EDT(-0400)] <anastasiac> but it sounds like you're not doing it wrong
[11:50:02 EDT(-0400)] <athena> ok
[11:50:03 EDT(-0400)] <athena> thanks!
[11:50:12 EDT(-0400)] <athena> we just wanted to make sure we were on the right track
[11:50:23 EDT(-0400)] <athena> so far though it's been working well and i've liked it
[11:50:36 EDT(-0400)] <anastasiac> good!
[11:51:24 EDT(-0400)] * athena doesn't really enjoy manually building HTML via javascript, so is quite happy
[11:52:25 EDT(-0400)] * michelled (n=michelle@CPE001310472ade-CM0011aefd3ca8.cpe.net.cable.rogers.com) has joined #fluid-work
[11:58:33 EDT(-0400)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[12:29:33 EDT(-0400)] * apetro (n=apetro@71.0.0.232) has joined #fluid-work
[12:30:34 EDT(-0400)] * dogle (n=daphne@dhcp-169-229-212-37.LIPS.Berkeley.EDU) has joined #fluid-work
[12:52:50 EDT(-0400)] * heidi_ (n=thesumme@142.150.154.101) has joined #fluid-work
[13:40:25 EDT(-0400)] * Bosmon (n=Antranig@ginger.caret.cam.ac.uk) has joined #fluid-work
[13:46:24 EDT(-0400)] * laurel (n=Laurel@142.150.154.178) has joined #fluid-work
[13:59:33 EDT(-0400)] <Bosmon> I found this interesting post on accessibility of HTML Canvas, stuck in Google's cache.. http://209.85.229.132/search?q=cache:JQ0H-RzhjaEJ:www.paciellogroup.com/blog/%3Fp%3D257+html+5+canvas+examples&cd=11&hl=en&ct=clnk&client=opera
[13:59:47 EDT(-0400)] <Bosmon> Oddly despite being only a few days old, the original post seems to have disappeared completely
[14:03:16 EDT(-0400)] * michelled (n=michelle@CPE001310472ade-CM0011aefd3ca8.cpe.net.cable.rogers.com) has joined #fluid-work
[14:22:08 EDT(-0400)] <yura> michelled: ping
[14:22:21 EDT(-0400)] <michelled> hi yura
[14:23:20 EDT(-0400)] <yura> hi Michelle, I have a patch with some python code for parser and couch db wrapper, I was wondering if I should post is somewhere?
[14:23:53 EDT(-0400)] <michelled> yes, attach it to the JIRA that you're working on
[14:24:50 EDT(-0400)] <michelled> http://issues.fluidproject.org/browse/FLUID-2816
[14:25:42 EDT(-0400)] <yura> michelled: great, i just did
[14:26:06 EDT(-0400)] <michelled> thanks, I'll take a look at it soon
[14:26:30 EDT(-0400)] <yura> it's pretty simple, but the parser looks better now
[14:28:57 EDT(-0400)] <michelled> so did you manage to import the data into couchdb then?
[14:30:16 EDT(-0400)] <yura> yes its pretty neat
[14:30:48 EDT(-0400)] <yura> you can try connecting to my test db : http://142.150.82.64:5984
[14:31:02 EDT(-0400)] <yura> list dbs: http://142.150.82.64:5984/_all_dbs
[14:31:25 EDT(-0400)] <Bosmon> Cool
[14:31:57 EDT(-0400)] <yura> and that's the document instance of the test artefact document : http://142.150.82.64:5984/test/04e73be73df871981191879c1f322e1e
[14:33:07 EDT(-0400)] <yura> by the way, i tested the json returned by parser and its good
[14:33:45 EDT(-0400)] <michelled> great!
[14:34:15 EDT(-0400)] <michelled> this is going to be really useful for Armin's experimentation
[14:35:39 EDT(-0400)] <yura> ya, ill look into views and all that right now , the wrapper that i submitted is a simple one with basic comands
[14:52:57 EDT(-0400)] <Bosmon> athena: I noticed you were discussing component trees ealier
[14:53:04 EDT(-0400)] <Bosmon> I am around atm in case you have any further questions
[14:53:11 EDT(-0400)] <athena> thanks!
[14:53:16 EDT(-0400)] <athena> i think everything's working well
[14:54:07 EDT(-0400)] <athena> i think my coworker's exact comment was "rock on, renderer"
[14:55:59 EDT(-0400)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[15:40:09 EDT(-0400)] <Bosmon> Ah, that's awesome
[15:40:11 EDT(-0400)] <Bosmon> Regards to Dan 
[15:41:12 EDT(-0400)] <athena>
[15:46:20 EDT(-0400)] <Bosmon> Btw, have you been having any luck with wacky things like "2 rendered columns per column" or "2 columns in one column"?
[15:49:27 EDT(-0400)] <athena> hm, i haven't tried that
[15:49:41 EDT(-0400)] <athena> and i haven't yet re-tried the 2 rows per pageable item
[16:54:22 EDT(-0400)] * alisonbenjamin (n=alisonbe@142.150.154.101) has joined #fluid-work
Page Comparison
Manage space
Manage content
Integrations