fluid-work IRC Logs-2011-06-16

[08:26:55 CDT(-0500)] <Bosmon4> Justin_o - have you appeared?
[08:27:19 CDT(-0500)] <Justin_o> Boshello
[08:27:23 CDT(-0500)] <Justin_o> Bosmon4: hello
[08:27:29 CDT(-0500)] <Justin_o> that was a weird combination there
[08:27:40 CDT(-0500)] <Bosmon4>
[08:28:03 CDT(-0500)] <Bosmon4> Did my patch from yesterday help to get over the immediate roadblock?
[08:28:34 CDT(-0500)] <Justin_o> Bosmon4: yes.. it did.. however.. i think it may have caused another one...
[08:28:46 CDT(-0500)] <Justin_o> we need to pass in the iframe to the uiOptionsBridge
[08:29:05 CDT(-0500)]

[08:29:16 CDT(-0500)] <Justin_o> but it complains about a circular reference
[08:29:43 CDT(-0500)] <Bosmon4> Well, it probably is
[08:29:55 CDT(-0500)] <Bosmon4> Does the markupRenderer depend on the bridge somehow?
[08:29:59 CDT(-0500)] <Justin_o> Bosmon4: nope
[08:30:20 CDT(-0500)] <Bosmon4> Is that checked in now?
[08:30:25 CDT(-0500)] <Justin_o> the markupRenderer is what creates the iframe
[08:30:46 CDT(-0500)] <Justin_o> the checked in version doesn't have your patch merged in
[08:30:54 CDT(-0500)] <Justin_o> did you want me to do that?
[08:31:02 CDT(-0500)] <Bosmon4> If there's something I could test, sure
[08:31:06 CDT(-0500)] <Bosmon4> I have just a few minutes now
[08:31:15 CDT(-0500)] <Justin_o> Bosmon4: okay i'll do it quickly
[08:32:15 CDT(-0500)] <Justin_o> Bosmon4: okay it's in
[08:32:21 CDT(-0500)] <Bosmon4> Thanks
[08:34:43 CDT(-0500)] <Bosmon4> Justin_o - there is indeed a circular issue since the event which is referencing the renderIframe is fired from its own finalInit function
[08:35:53 CDT(-0500)] <Justin_o> Bosmon4: not sure i'm following
[08:36:17 CDT(-0500)] <Justin_o> Bosmon4: by the way, do you know when you'll be in toronto?
[08:37:04 CDT(-0500)] <Bosmon4> Justin_o - the event fires from finalInit, named "afterRender"
[08:37:11 CDT(-0500)] <Bosmon4> This triggers the creation of the bridge
[08:37:29 CDT(-0500)] <Bosmon4> The bridge then refers back to the component which fired the event, the renderIframe, which is still in the middle of its finalInit function
[08:37:34 CDT(-0500)] <Bosmon4> And so has not completed construction
[08:37:59 CDT(-0500)] <Bosmon4> But this is still a symptom of the bigger problem I mentioned yesterday
[08:38:04 CDT(-0500)] <Bosmon4> That this event is firing far too early
[08:38:12 CDT(-0500)] <Justin_o> Bosmon4: ah i get it now
[08:38:15 CDT(-0500)] <Bosmon4> It isn't enough to know that the iframe has RENDERED, it actually needs to have LOADED
[08:38:22 CDT(-0500)] <Bosmon4> So the use of "afterRender" is not appropriate here anyway
[08:38:34 CDT(-0500)] <Justin_o> Bosmon4: yes.. that's correct.. i need to wire up the iframe.load event
[08:38:35 CDT(-0500)] <Bosmon4> If it were appropriate, a way out of the problem might be to supply the iframe as an argument to the event
[08:38:41 CDT(-0500)] <Bosmon4> But it isn't
[08:38:55 CDT(-0500)] <Justin_o>
[08:39:09 CDT(-0500)] <Bosmon4> I haven't booked my travel for Toronto yet
[08:39:17 CDT(-0500)] <Bosmon4> Do you have an opinion one way or the other?
[08:39:27 CDT(-0500)] <Justin_o> okay.. thanks.. let me go to try to do this.. in our preliminary work we had used the load event so it should be quick work to figure it out again
[08:40:04 CDT(-0500)] <Justin_o> Bosmon4: we're thinking of organizing a meal during summerlicious http://www.toronto.ca/special_events/summerlicious/2011/index.htm
[08:40:14 CDT(-0500)] <Justin_o> we're hoping you'll be around to join us
[08:40:38 CDT(-0500)] <Justin_o> There is overlap with the hackathon week, but it might be too crazy around here then
[08:40:47 CDT(-0500)] <Bosmon4> Ok
[08:40:51 CDT(-0500)] <Bosmon4> Which day were you thinking of?
[08:41:24 CDT(-0500)] <Justin_o> Bosmon4: I hadn't thought of anything in particular yet.. was checking to see when you were available first
[08:41:30 CDT(-0500)] <Bosmon4> Ok
[08:41:40 CDT(-0500)] <Bosmon4> I think I will try to appear at least for the Thursday before
[08:41:48 CDT(-0500)] <Bosmon4> Although I am worried about the CATTTT
[08:42:27 CDT(-0500)] <Bosmon4> I guess Thursday 7th
[08:42:31 CDT(-0500)] <Bosmon4> Not quite settled yet
[08:42:34 CDT(-0500)] <Justin_o> Bosmon4: ah okay.. well we can't make reservations till June 23rd at the earliest anyways.. so yo have time to decide still if you need it
[08:42:46 CDT(-0500)] <Bosmon4> ok
[08:42:57 CDT(-0500)] <Bosmon4> I'll probably deal with my travel on Monday
[08:43:05 CDT(-0500)] <Justin_o> Bosmon4: does the number of T's at the end of CATTTT correlate with his age?
[08:43:09 CDT(-0500)] <Bosmon4> Hopefully I will have heard a bit more from GGREGG by then anyway
[08:43:15 CDT(-0500)] <Bosmon4> Justin_o - only very loosely
[08:43:31 CDT(-0500)] <Justin_o>
[08:47:50 CDT(-0500)] <Justin_o> Bosmon4: okay.. so moving the event firer seems to have solved that problem.. now the iframe is null in the uiOptionsBridge.. on to dig into this
[09:23:02 CDT(-0500)] <jameswy> jhung, heidi_: the latest fat panel is in jhung's repo, correct?
[09:23:17 CDT(-0500)] <jhung> jameswy: yes.
[09:23:17 CDT(-0500)] <heidi_> jameswy yep or mine has his stuff merged in as well
[09:23:32 CDT(-0500)] <jameswy> Cools. So, either works?
[09:23:47 CDT(-0500)] <heidi_> jameswy go with jhung's incase he's made changes since yest
[09:27:19 CDT(-0500)] <jhung> jameswy: see anastasiac's email re: "get involved" lacking in infusion tech docs design.
[09:28:06 CDT(-0500)] <jhung> jameswy: I don't remember if we made a decision on an "About" page. I recall it being in the top nav, and/or the footer at some point.
[09:43:23 CDT(-0500)] <lahabana> hi folks
[09:49:37 CDT(-0500)] <michelled> hi lahabana
[09:49:47 CDT(-0500)] <lahabana> hi
[09:50:17 CDT(-0500)] <lahabana> I'm currently working on a component inspired by that :https://github.com/fluid-project/image-gallery/blob/master/js/image-gallery.js#L188-206
[09:50:51 CDT(-0500)] <lahabana> the idea is to have a way to quickly create elements in a container
[09:51:31 CDT(-0500)] <lahabana> for eg for what I'll use create controllers for a video player without repeating always the same lines of codes
[09:51:50 CDT(-0500)] <lahabana> I was just wondering
[09:51:59 CDT(-0500)] <lahabana> the version here uses stringTemplates
[09:52:54 CDT(-0500)] <cindyli> michelled: heidi_, Justin_o, just sent a pull request for the fix on the ui options template prefix issue: https://github.com/fluid-project/infusion/pull/78. so is there anything in particular you guys want me to work on?
[09:52:57 CDT(-0500)] <lahabana> but maybe I should use a more complex object which will contain the name of the tag, the classes, the content, the attributes...
[09:53:18 CDT(-0500)] <michelled> lahabana: do you have the repetitive code up somewhere?
[09:53:40 CDT(-0500)] <cindyli> michelled: Justin_o, heidi_, if not, i'm going to work on is 4284 (http://issues.fluidproject.org/browse/FLUID-4284) that hide TOC throws js error in fat panel version
[09:53:51 CDT(-0500)] <lahabana> sorry left
[09:53:55 CDT(-0500)] <lahabana> back
[09:53:59 CDT(-0500)] <lahabana> yes let me find it
[09:54:10 CDT(-0500)] <michelled> cindyli: maybe help harriswong get the toc stuff ready for a push
[09:54:25 CDT(-0500)] <michelled> I think there will be conflicts if you also work on toc separately
[09:54:51 CDT(-0500)] <michelled> but anything Justin_o or mlam need should be done first
[09:54:52 CDT(-0500)] <cindyli> michelled: ok. harriswong, let's talk
[09:55:17 CDT(-0500)] <lahabana> it's 22 lines long shall I send it here anyway?
[09:55:24 CDT(-0500)] <cindyli> Justin_o: mlam, anything in ur hands need my help?
[09:55:45 CDT(-0500)] <michelled> lahabana: either push it up to github or use pastie
[09:55:57 CDT(-0500)] <Justin_o> cindyli: not sure just yet
[09:55:57 CDT(-0500)] <harriswong> michelled, cindyli: i think there is just one thing left on toc tests which is to rewrite some test case sugeested by justin_o yesterday
[09:56:02 CDT(-0500)] <michelled> lahabana: either push it up to github or use pastie
[09:56:14 CDT(-0500)] <lahabana> true
[09:56:59 CDT(-0500)] <cindyli> harriswong: ok. let me know if u need my help. otherwise, i will merge in ur toc branch and work on 4284
[09:58:17 CDT(-0500)] <lahabana> https://github.com/lahabana/videoPlayer/blob/master/js/VideoPlayer.js#L405-430
[09:58:26 CDT(-0500)] <lahabana> here it is
[09:59:01 CDT(-0500)] <lahabana> As u'll see it's pretty much always the same
[09:59:31 CDT(-0500)] <lahabana> except for the scrubber which is slightly more complex and calls a method
[10:00:06 CDT(-0500)] <lahabana> that's why colin Suggested to make a small component to do that kind of repetitive tasks
[10:01:08 CDT(-0500)] <heidi_> jhung how's it going?
[10:01:41 CDT(-0500)] <jhung> heidi_: good. Working on some IDI stuff this morning. How's it going?
[10:02:05 CDT(-0500)] <heidi_> jhung ah ok. how'd the browser testing go? good here - still doing clean up and linearizing
[10:02:08 CDT(-0500)] <lahabana> ho in fact just thought that I could integrate tags and things like that in my string Template no?
[10:03:18 CDT(-0500)] <lahabana> somethings like <%tag %attributes>%container</%tag> no?
[10:04:14 CDT(-0500)] <lahabana> and the attributes part could be formatted correctly before...
[10:04:39 CDT(-0500)] <michelled> lahabana: that should work, although I'm curious to see what your little component looks like
[10:05:03 CDT(-0500)] <michelled> lahabana: it might be worth pulling out the selectors and using add class to put them into your markup fragment
[10:05:14 CDT(-0500)] <michelled> but it will depend on what you are doing with the little component
[10:05:33 CDT(-0500)] <michelled> do you want to work on the component and then show it to us?
[10:06:10 CDT(-0500)] <lahabana> yes I'm going to do that
[10:06:14 CDT(-0500)] <jhung> heidi_: I didn't get to the testing yet. Hope to do that after stand-up / this afternoon.
[10:06:27 CDT(-0500)] <lahabana> I'll share a link on the mailing list to get feedback
[10:06:37 CDT(-0500)] <michelled> that will be great lahabana
[10:06:44 CDT(-0500)] <heidi_> jhung k great
[10:06:46 CDT(-0500)] <lahabana> thanks for the help
[10:07:17 CDT(-0500)] <michelled> np
[10:13:25 CDT(-0500)] <jhung> jessm, jameswy: Can you review this document to see if I captured the goal and functions of the IDI website well enough? http://wiki.fluidproject.org/display/fluid/IDI+Website+Goals+and+Features
[10:16:14 CDT(-0500)] <jameswy> jhung: Will do this afternoon.
[10:27:52 CDT(-0500)] <jessm> jhung: likewise
[10:28:08 CDT(-0500)] <jhung> jameswy, jessm: np. thanks!
[10:29:21 CDT(-0500)] <jessm> fluid-everyone ocad connect is still down
[10:29:28 CDT(-0500)] <jessm> so, we'll use york again
[10:29:34 CDT(-0500)] <jessm> anastasiac: can you remind everyone of the url?
[10:29:54 CDT(-0500)] <jessm> or here it is: connect.yorku.ca/fluidwork
[10:29:57 CDT(-0500)] <jessm> huslage: ^
[10:31:24 CDT(-0500)] <huslage> ok
[10:35:55 CDT(-0500)] <smriti> I'm having problems connecting to Adobe Connect at the moment for stand up My update is I'm continuing work with applying fss onto drupal's page template for the new snow site today..
[10:41:53 CDT(-0500)] <jessm> smriti: see above, the OCAD server seems down – we used york, but no problem
[10:42:07 CDT(-0500)] <jessm> fluid-everyone i sent a message to OCAD admins about connect
[10:42:57 CDT(-0500)] <smriti> k..i missed that.. thx!
[10:51:51 CDT(-0500)] <jessm> fluid-everyone: OCAD connect is back up
[10:51:56 CDT(-0500)] <jessm> we'll use it tomorrow
[11:56:44 CDT(-0500)] <jessm> jhung: the wiki IDI website goals page is good
[11:57:07 CDT(-0500)] <jessm> i think the 3rd use case in the audience and the goals is probably going to be the priority
[11:57:24 CDT(-0500)] <jhung> jessm: cool. okay, I'll push that to the top.
[11:57:34 CDT(-0500)] <jessm> jhung: and i'm wondering on the functions section
[11:57:52 CDT(-0500)] <jessm> do you think we'll have a number of active wikis where folks will collaborate? what do you think?
[11:59:55 CDT(-0500)] <jessm> jhung: i actually think the static content will be pretty static
[12:00:05 CDT(-0500)] <jhung> jessm: interesting. Not sure why we'd need more than one active wiki (especially if we can create unique spaces within that). Can you explain?
[12:00:21 CDT(-0500)] <jessm> jhung: yeah, i didn't mean to suggest multi-wiki
[12:00:26 CDT(-0500)] <jessm> but multi-spaces for sure
[12:00:44 CDT(-0500)] <jessm> i imagine most of the IDI traffic and activity being there – do you?
[12:01:02 CDT(-0500)] <jhung> jessm: yes. I definitely think the wiki will get bulk of the traffic.
[12:02:06 CDT(-0500)] <jessm> yeah
[12:02:32 CDT(-0500)] <jessm> jhung: are there things in particular that we can work through that will help round out what huslage was interested in? or do you think you've got most of it?
[12:03:05 CDT(-0500)] <jhung> jessm: I think that's most of it. The discussion will continue of course.
[12:03:30 CDT(-0500)] <jessm> jhung: is the list from james kick-off email in the wiki someplace?
[12:03:46 CDT(-0500)] <jhung> jessm: I'll put in some notes about priorities and where we foresee bulk of the attension. This way we'll be sure to get the right tools for the job.
[12:03:58 CDT(-0500)] <jessm> great
[12:04:58 CDT(-0500)] <jhung> jessm: not sure which email you're referring to...
[12:05:16 CDT(-0500)] <jessm> james' email that kicked off the thread about technologies
[12:05:20 CDT(-0500)] <jhung> ah
[12:05:31 CDT(-0500)] <jessm> Back-end needs for the IDI website
[12:05:50 CDT(-0500)] <jhung> jessm, not formally. Sort of scattered. I'll make sure to put that into the wiki page as possible technologies.
[12:06:03 CDT(-0500)] <jessm> great, thanks
[12:31:15 CDT(-0500)] <heidi_> jameswy thanks for your fat panel list - gonna work on that now! jhung maybe make a similar list for browser testing
[12:31:20 CDT(-0500)] <heidi_> when you get a chance
[12:31:21 CDT(-0500)] <heidi_> thanks dudes
[12:31:39 CDT(-0500)] <jhung> heidi_: kk
[13:09:59 CDT(-0500)] <jhung> heidi_: I'm finally getting around to testing UIO in browsers. Up first is IE8, and then IE6.
[13:10:33 CDT(-0500)] <heidi_> thanks jhung!
[13:18:53 CDT(-0500)] <jameswy> jhung: Good stuff on the IDI page. Made some edits here and there.
[13:19:03 CDT(-0500)] <jameswy> Thanks for writing that up.
[13:19:13 CDT(-0500)] <jhung> jameswy: okay cool.
[13:29:32 CDT(-0500)] <heidi_> hey Justin_o i'm playing with reorderers and linearizing. do you have a sec to look at http://build.fluidproject.org/infusion/demos/reorderer/layoutReorderer/html/layoutReorderer.html
[13:30:03 CDT(-0500)] <heidi_> it linearizes this in a way that the first tab-able element is in between two locked items
[13:30:23 CDT(-0500)] <heidi_> and it can't be moved. does that make sense?
[13:30:35 CDT(-0500)] <heidi_> (when using kboard)
[13:30:53 CDT(-0500)] <Justin_o> heidi_: hmm.. i don't think you can linearize this
[13:31:28 CDT(-0500)] <Justin_o> heidi_: there's a bug with the layout reorderer.. where if the columns become stacked.. the reordering doesn't work properly anymore
[13:31:35 CDT(-0500)] <heidi_> Justin_o using the mouse you can reorder ok
[13:31:53 CDT(-0500)] <Justin_o> heidi_: are you sure you can reorder between all of the columns if they are all lined up
[13:31:55 CDT(-0500)] <heidi_> tho the meaning of the locked items doesn't really transfer
[13:32:13 CDT(-0500)] <Justin_o> heidi_: that's true.. the locked ones should all move to the top of the page
[13:32:49 CDT(-0500)] <heidi_> Justin_o i think it's only letting me move items within a column around, not from one (old) col to another
[13:33:12 CDT(-0500)] <heidi_> but yeah i feel like it should: move locked items to the top, then behave like a list reorderer?
[13:33:42 CDT(-0500)] <Justin_o> heidi_: yes.. that would make sense
[13:34:20 CDT(-0500)] <heidi_> thanks Justin_o
[13:34:30 CDT(-0500)] <Justin_o> heidi_: i was just thinking a bit more about this...
[13:34:35 CDT(-0500)] <heidi_> i could actually see someone wanting a linear portal area
[13:34:46 CDT(-0500)] <Justin_o> why do you think someone might have these things arranged in columns?
[13:34:49 CDT(-0500)] <heidi_> and moving the most interesting stuff to the top
[13:35:34 CDT(-0500)] <heidi_> Justin_o like why is the layout reorderer demo the way it is? seems to be replicating a typical portal-y page
[13:36:30 CDT(-0500)] <Justin_o> heidi_: i was going to say that we might be breaking some sort of semantics if all the locked portlets were grouped together when linearized, but i guess then people wouldn't let the other porlets be reordered between columns
[13:37:02 CDT(-0500)] <heidi_> Justin_o it becomes one col so the 'between cols' thing is no longer an issue
[13:37:24 CDT(-0500)] <heidi_> and moving to the top makes sense cos locked stuff is likely important stuff that shouldn't be bumped down
[13:37:42 CDT(-0500)] <heidi_> wouldn't really make sense anywhere else... can you have locked items at the bottom of a col?
[13:39:56 CDT(-0500)] <heidi_> or in the middle?
[13:40:07 CDT(-0500)] <heidi_> i feel like no
[13:47:08 CDT(-0500)] <Justin_o> heidi_: we currently only support them at the top of a column.
[13:47:24 CDT(-0500)] <heidi_> Justin_o yes that makes sense
[13:47:34 CDT(-0500)] <Justin_o> it was confusing when things would move around them anywhere else
[13:47:51 CDT(-0500)] <heidi_> otherwise you could 'move' locked items by manipulating their surrounding
[13:48:18 CDT(-0500)] <Justin_o> heidi_: exactly
[14:00:02 CDT(-0500)] <cindyli> Justin_o: harriswong, michelled, i'm thinking what's the better approach to turn on/off toc with ui options. the old toc component has a show()/hide() func. so toc only gets created at the first turning on, afterwards, it was just to show/hide
[14:00:29 CDT(-0500)] <cindyli> Justin_o: harriswong, michelled, the new toc component doesn't have these functions, for now.
[14:01:15 CDT(-0500)] <cindyli> I'm thinking if this is a good approach to add back?
[14:01:30 CDT(-0500)] <michelled> I think lazy initialization is a good idea
[14:01:46 CDT(-0500)] <cindyli> agree
[14:02:01 CDT(-0500)] <michelled> if it doesn't make API sense for the toc component have show hide then we could wrap it in a little component
[14:02:18 CDT(-0500)] <michelled> Justin_o: why was show/hide removed?
[14:02:34 CDT(-0500)] <jhung> michelled: do we have image editor meeting now?
[14:02:51 CDT(-0500)] <Justin_o> michelled: don't recall.. i probably didn't notice them...
[14:03:03 CDT(-0500)] <michelled> yes, thanks jh
[14:03:05 CDT(-0500)] <michelled> jhung:
[14:03:32 CDT(-0500)] <Justin_o> michelled: it could have been because of the TODO: note in the old one
[14:03:45 CDT(-0500)] <Justin_o> but i can't quite recall
[14:06:17 CDT(-0500)] <michelled> fluid-everyone: is there anyone whom I haven't called who wants to be on this image editor call?
[14:25:05 CDT(-0500)] <Justin_o> cindyli: would you be able to tell me what classnameMap is?
[14:26:51 CDT(-0500)] <cindyli> Justin_o: that's the array of the mappings between the ui options setting and corresponding css class
[14:28:16 CDT(-0500)] <cindyli> meaning, when the setting is selected, the corresponding css class should be applied
[14:28:44 CDT(-0500)] <Justin_o> cindyli: okay.. and the only component that actually has information about it is uiEnhancer?
[14:29:16 CDT(-0500)] <michelled> huslage, jessm: pulkit has a good start on the gsoc image editor and I think it would be awesome to be able to see it up somewhere so we can all play with it
[14:29:26 CDT(-0500)] <huslage> ok
[14:29:27 CDT(-0500)] <michelled> thoughts on how we should do that?
[14:29:35 CDT(-0500)] <cindyli> Justin_o: yes
[14:29:36 CDT(-0500)] <huslage> what's it need?
[14:30:02 CDT(-0500)] <jessm> michelled: is it somewhere now that we can see it?
[14:30:03 CDT(-0500)] <michelled> pulkit ^
[14:30:14 CDT(-0500)] <michelled> jessm: the code is in github
[14:30:18 CDT(-0500)] <michelled> it isn't up anywhere yet
[14:30:34 CDT(-0500)] <jessm> michelled: so you're thinking a demo of sorts?
[14:30:41 CDT(-0500)] <huslage> but is it just an html thing or PHP or what?
[14:31:34 CDT(-0500)] <Justin_o> cindyli: thanks...
[14:31:44 CDT(-0500)] <cindyli> no. oh, Justin_o: it's also passed into ui options thru IoC and demands block
[14:31:54 CDT(-0500)] <michelled> pulkit: how do you use it now?
[14:31:57 CDT(-0500)] <pulkit> huslage: Its html+JavaScript
[14:32:15 CDT(-0500)] <pulkit> I have it on local apache server
[14:32:18 CDT(-0500)] <huslage> can't it just live on the demo site?
[14:32:52 CDT(-0500)] <michelled> huslage: good question - it's sort of in the category of fluid labs which we've talked about but not really sketched out yet
[14:33:03 CDT(-0500)] <huslage> ah
[14:33:11 CDT(-0500)] <huslage> interesting
[14:33:13 CDT(-0500)] <michelled> https://github.com/pulkit110/ImageEditor
[14:33:46 CDT(-0500)] <michelled> it probably wouldn't ship with Infusion for a while yet
[14:34:14 CDT(-0500)] <jessm> michelled: who is the intended audience for the "demo"
[14:34:46 CDT(-0500)] <michelled> well, right now joanna who is going to be doing some interaction design for it
[14:34:59 CDT(-0500)] <michelled> but I guess anyone in the community who's interested
[14:35:23 CDT(-0500)] <michelled> jessm: I suppose it's like a sneak peek component - something we're cooking but won't ship for a while
[14:35:48 CDT(-0500)] <jessm> michelled: we should probably fit it into some of the web thinking that jameswy and jhung have been doing
[14:39:00 CDT(-0500)] <pulkit> michelled, jhung, jameswy: Here's the pdf containing few screenshots of Image Editor: http://pulkitgoyal.files.wordpress.com/2011/06/imageeditor.pdf
[14:40:11 CDT(-0500)] <pulkit> michelled, jhung, jameswy: I haven't yet worked on the interface much. But cropping, resize and tag seem to work fine.
[14:42:50 CDT(-0500)] <michelled> thanks pulkit
[14:48:57 CDT(-0500)] <jameswy> pulkit, michelled: Is there a wiki space for the image editing project right now?
[14:49:31 CDT(-0500)] <pulkit> jameswy: yes. have a look here: http://wiki.fluidproject.org/display/fluid/Image+Editor
[14:49:46 CDT(-0500)] <jameswy> Super, thanks pulkit!
[14:54:41 CDT(-0500)] <jhung> pulkit, when you say "resize" are you referring to resizing of image dimensions, or resizing of bounding boxes?
[14:55:22 CDT(-0500)] <pulkit> jhung: I am referring to image dimensions. Is it okay?
[14:56:06 CDT(-0500)] <jhung> pulkit: yep that's fine. Just wanted to make sure I understood.
[14:56:17 CDT(-0500)] <EricDalquist> ping Bosmon2
[14:56:38 CDT(-0500)] <jhung> pulkit: although I think allowing the user to resize a bounding box is useful since people rarely get it right the first time.
[14:56:42 CDT(-0500)] <michelled> EricDalquist: Bosmon2 is on vacation for a week
[14:56:48 CDT(-0500)] <EricDalquist> ah thanks
[14:56:49 CDT(-0500)] <michelled> he might reply to e-mail on monday
[14:57:35 CDT(-0500)] <pulkit> jhung: It currently allows resizing of bounding box using mouse
[14:58:03 CDT(-0500)] <jhung> pulkit, nice!
[14:58:27 CDT(-0500)] <jhung> looking forward to see all of this come together.
[15:01:25 CDT(-0500)] <michelled> EricDalquist: was there something someone else could help with?
[15:02:02 CDT(-0500)] <EricDalquist> oh maybe . it's a question about multi-dimentional rendering with the pager
[15:02:09 CDT(-0500)] <EricDalquist> let me pastebin something
[15:03:06 CDT(-0500)] <cindyli> Justin_o: michelled, can we make a decision on toc show/hide so i can proceed? if we give up on the old show/hide functions and replace with a little component? where does this component fit, ui enhancer or toc? what does it do? still show/hide or create/destory toc completely?
[15:03:18 CDT(-0500)] <EricDalquist> http://pastebin.com/y4ztJu5a
[15:03:27 CDT(-0500)] <EricDalquist> so that is what I have
[15:03:52 CDT(-0500)] <EricDalquist> what I need is for the two cells that have the leaveFurloughReportLinks and missingReportLinks links
[15:04:00 CDT(-0500)] <EricDalquist> to have 0-N links be rendered
[15:05:25 CDT(-0500)] <Justin_o> cindyli: i'll go with whatever you and michelle decide, but i think it's a bit wierd that ToC is a subcomponent of uiEnhancer
[15:05:26 CDT(-0500)] <EricDalquist> essentially my data a json array of one has per row but within each row hash the data from those two cells is another array of hashes
[15:05:51 CDT(-0500)] <EricDalquist> and I'm not sure how to get the renderer to generate multiple links for me
[15:05:55 CDT(-0500)] <EricDalquist> for one cell
[15:06:46 CDT(-0500)] <yura_> EricDalquist: the problem with pager in renderer mode at the moment is that you can't change the structure of the renderer tree without rewriting the whole fluid.pager.selfRender
[15:07:32 CDT(-0500)] <EricDalquist> yeah so what I'm doing right now is actually defining those two cells as: <td class="hrs-data-text" rsf:id="leaveFurloughReportLinks"></td>
[15:07:57 CDT(-0500)]

<EricDalquist> and then pre-processing my json data before rendering it: leaveStatement.leaveFurloughReportLinks += "<a href=\"$

Unknown macro: {renderRequest.contextPath}

/statement/leave_furlough_report.pdf?docId=" + leaveFurloughReport.docId + "\" target=\"_blank\">" + leaveFurloughReport.title + "</a>";

[15:08:02 CDT(-0500)] <EricDalquist> which works
[15:08:08 CDT(-0500)] <EricDalquist> it just isn't all that pretty
[15:11:02 CDT(-0500)] <yura_> EricDalquist: this looks like the simplest way. The other alternative, as I mentioned above would be proving the pager a different selfRender, since that's the "subcomponent" that creates the tree for rendering
[15:11:13 CDT(-0500)] <yura_> providing*
[15:11:22 CDT(-0500)] <EricDalquist> hrm, ok
[15:12:08 CDT(-0500)] <anastasiac> EricDalquist, it sounds like we don't yet have a better way than what you've gotten working, so "not pretty" may just be in for now
[15:12:25 CDT(-0500)] <EricDalquist> yup, and I'm fine with that
[15:12:34 CDT(-0500)] <EricDalquist> I had just mentioned this issue to Bosmon2 at the jasig conference
[15:12:42 CDT(-0500)] <EricDalquist> and he asked me to show him the example
[15:13:00 CDT(-0500)] <EricDalquist> I just happened to be in that code right now so I figured I'd see if he was around
[15:13:17 CDT(-0500)] <jhung> heidi: wow. Linearizing goes boom in Chrome 12.
[15:13:51 CDT(-0500)] <michelled> cindyli: what do you think makes the most sense? keep in mind that toc is sneak peek so we still have the opportunity to so some API change in 1.5
[15:14:23 CDT(-0500)] <yura_> EricDalquist: you can also try post processing , after the pager is done rendering. You could then render the markup in the "second" dimension
[15:14:55 CDT(-0500)] <cindyli> michelled: i personally think the old show/hide API is quite handy and easy to use.
[15:15:05 CDT(-0500)] <michelled> go for it
[15:15:19 CDT(-0500)] <cindyli> haha, ok. thanks, michelled & Justin_o
[15:30:37 CDT(-0500)] <jhung> heidi_: new list of UIO issues sent to the list.
[15:30:47 CDT(-0500)] <heidi_> jhung how was it?
[15:31:00 CDT(-0500)] <jhung> heidi_ moderately painful.
[15:31:05 CDT(-0500)] <heidi_> dang
[15:31:17 CDT(-0500)] <jhung> heidi_: some should be easy I think.
[15:32:10 CDT(-0500)] <jhung> heidi_: Not sure how many of those issues I found are being worked on / documented already. So may not be too bad.
[15:32:35 CDT(-0500)] <heidi_> jhung okay cool... IE the worst i'm assuming
[15:33:00 CDT(-0500)] <jhung> heidi_: IE6 just plain doesn't work. Hopefully a simple fix?
[15:33:11 CDT(-0500)] <jhung> heidi_ IE8 actually was pretty good.
[15:33:28 CDT(-0500)] <heidi_> jhung ah, there was a fix for it awhile ago Justin_o found extra commas, but i think that would be in master right justin?
[15:33:57 CDT(-0500)] <heidi_> jhung thanks for doing this btw - now do you have time to fix stuff? hehe
[15:34:17 CDT(-0500)] <jhung> heidi_: hey! No fair!
[15:34:23 CDT(-0500)] <heidi_> haha
[15:34:25 CDT(-0500)] <heidi_> gotcha
[15:34:32 CDT(-0500)] <jhung> I'll leave you the IE6 bugs.
[15:34:55 CDT(-0500)] <heidi_> i don't have IE6... i'm hoping Justin_o 's fix is the issue. did you update from master recently
[15:35:10 CDT(-0500)] <jhung> heidi_: I have not. I'll do that now.
[15:35:16 CDT(-0500)] <heidi_> k
[15:35:44 CDT(-0500)] <heidi_> ah justin's off for the day so not sure if the fix is in yet
[15:35:48 CDT(-0500)] <heidi_> guessing so
[15:47:31 CDT(-0500)] <michelled> heidi_: I just had a thought on linearizing - I'm just thinking out loud here
[15:47:54 CDT(-0500)] <michelled> heidi_: what if we had different linerizing levels - let's call them A, B, and C for now
[15:48:04 CDT(-0500)] <heidi_> listening
[15:48:22 CDT(-0500)] <michelled> and we get integrators to put in markers for what level of linearizing their markup is ready for
[15:48:45 CDT(-0500)] <michelled> then we could add in the A, B, and C classes on the particular elements that have been markup up for it
[15:49:00 CDT(-0500)] <michelled> so the things we think are safe to do on everything we could still do on the body
[15:49:09 CDT(-0500)] <michelled> but other things we could do selectively
[15:49:19 CDT(-0500)] <michelled> do you think a scheme like this would be possible?
[15:49:37 CDT(-0500)] <heidi_> thinking...
[15:50:07 CDT(-0500)] <heidi_> the thing is the "safe to do on everything" stuff doesn't really exist i don't think
[15:50:50 CDT(-0500)] <heidi_> i'm not sure... will have to think more on it. it would make for really really nit-picky markup for the integrator
[15:51:06 CDT(-0500)] <heidi_> but options are always good
[15:52:15 CDT(-0500)] <heidi_> michelled how would you define A, B, C
[15:52:18 CDT(-0500)] <heidi_> roughtly
[15:53:48 CDT(-0500)] <michelled> heidi_: I'm not really sure and I'm also not sure how many levels to types there would be. I suppose it will take a lot more thought on what we actually do right now and how we could break that down into more usable bits
[15:55:41 CDT(-0500)] <heidi_> michelled the stuff it does to everything right now is resets all clears, floats, margins, alignment
[15:56:07 CDT(-0500)] <heidi_> and then some extra stuff depending on the element (like width)
[15:56:27 CDT(-0500)] <heidi_> not sure how we'd separate those things out, or if that would make sense to do/be effective
[15:56:56 CDT(-0500)] <heidi_> what would be awesome is a "don't linearize this part" class but because of the global-ness of the style, we can't do that
[15:57:30 CDT(-0500)] <heidi_> right now you can put fl-layout-linear on whatever part you want, but even still, if there are things within that you don't want linearized... no luck
[15:59:04 CDT(-0500)] <michelled> heidi_: maybe we should be so global then
[15:59:28 CDT(-0500)] <michelled> shouldn't
[15:59:35 CDT(-0500)] <heidi_> how so?
[15:59:55 CDT(-0500)] <michelled> can we write the class so it doesn't act on decendents?
[16:00:10 CDT(-0500)] <michelled> then we could put it on everything except for things that aren't supposed to linearize
[16:00:33 CDT(-0500)] <michelled> it feels messy because we'd be dropping this class in everywhere
[16:00:41 CDT(-0500)] <michelled> but it would allow the don't linearize use case
[16:00:52 CDT(-0500)] <michelled> which I think has been your biggest headache
[16:01:36 CDT(-0500)] <heidi_> michelled add a classname to every single thing i think would be more tricky than adding it to the body, and tweaking some things
[16:02:00 CDT(-0500)] <heidi_> but it would be good to have both options, sort of like how reset has both global and contextual classes
[16:02:20 CDT(-0500)] <heidi_> tho i think they work globally in that you put it on a container all its contents are affected
[16:03:13 CDT(-0500)] <heidi_> no, different. context reset is just put into a name space which is what linear already does
[16:03:47 CDT(-0500)] <michelled> heidi_: let me mull it over tonight and let's chat more tomorrow
[16:03:57 CDT(-0500)] <heidi_> michelled i'll mull too
[16:03:58 CDT(-0500)] <heidi_>
[16:04:01 CDT(-0500)] <michelled>
[16:54:07 CDT(-0500)] <lahabana> hey does anyone knows where is the the documentation of the fluid.stringTemplate ?
[16:54:22 CDT(-0500)] <lahabana> I've been looking on the old and new documentation without any success
[17:31:24 CDT(-0500)] <lahabana> is anyone here now?