fluid-work IRC Logs-2011-08-08
- Fluid IRC Log Bot
[07:56:27 CDT(-0500)] <alison-benj> Justin_o: good morning <lahabana> cause obviously " " for eg doesn't exist <lahabana> Uncaught TypeError: Object Failed to resolve reference events.afterTimeChange - could not match context with name controllers from component root of type fluid.staticEnvironment has no method 'fail'
[07:57:08 CDT(-0500)] <Justin_o> alison-benj: hello, good morning
[07:58:29 CDT(-0500)] <alison-benj> Justin_o: I have a CSS question about mobile FSS. I think I'd like to make a header that uses .fl-table classes, similar to as shown here: http://build.fluidproject.org/infusion/demos/fss/mobile/html/mobile.html
[07:59:37 CDT(-0500)] <alison-benj> Justin_o: one of the containing elements though would be a div that appears or disappears - a link that the user activates to open or close a navigation menu.
[08:02:06 CDT(-0500)] <Justin_o> alison-benj: do you have a wire frame for that?
[08:02:18 CDT(-0500)] <alison-benj> Justin_o: I mocked that up and then realized that when the contained div appears it breaks increases the height of the table it is contained in. that visually messes up the whole look, if that makes sense.
[08:02:47 CDT(-0500)] <alison-benj> Justin_o: no but I can remake it & show you a a shot.
[08:03:18 CDT(-0500)] <Justin_o> I think so.. where would this div appear? in place of the radio type buttons on the page you sent me?
[08:06:11 CDT(-0500)] <Justin_o> alison-benj: thanks..
[08:07:27 CDT(-0500)] <alison-benj> Justin_o: I want to put a link that toggles a navigational menu in a .fl-table-cell. The menu will have a much greater height than the header, which should always be the same height. Sending an email!
[08:10:04 CDT(-0500)] <Justin_o> alison-benj: thanks.. i'll check out the e-mail
[08:21:00 CDT(-0500)] <huslage> morning
[08:37:24 CDT(-0500)] <Justin_o> alison-benj: have you sent the e-mail.. i don't think i've gotten it yet if you have
[08:37:44 CDT(-0500)] <alison-benj> Justin_o: nope just working on it. thx
[08:38:00 CDT(-0500)] <Justin_o> alison-benj: okay..
[08:56:20 CDT(-0500)] <alison-benj> Justin_o: sent.
[08:56:38 CDT(-0500)] <Justin_o> alison-benj: thanks.. i'll go take a look
[09:20:32 CDT(-0500)] <Justin_o> alison-benj: so i think with tables they tend to only go as small as the minimum size of their contents
[09:21:01 CDT(-0500)] <lahabana> hey anastasiac I'm wondering
[09:21:19 CDT(-0500)] <lahabana> is it better to put the style in the html templates?
[09:21:33 CDT(-0500)] <lahabana> or in an option.styles json object?
[09:21:48 CDT(-0500)] <alison-benj> Juston_o: yeah.
[09:22:24 CDT(-0500)] <anastasiac> lahabana, your styles should be defined in a CSS file, associated with class names. Those class names should be attached to the markup, and names in options.styles
[09:22:40 CDT(-0500)] <anastasiac> "named" in options.styles
[09:22:45 CDT(-0500)] <anastasiac> not "names"
[09:22:54 CDT(-0500)] <lahabana> ok thx 
[09:22:59 CDT(-0500)] <anastasiac> lahabana, does that make any sense? I'm not quite sure I understand your question
[09:23:16 CDT(-0500)] <lahabana> no no it answers perfectly
[09:23:23 CDT(-0500)] <anastasiac> oh, good
[09:23:38 CDT(-0500)] <lahabana> I was wondering whether my class names defined in the CSS
[09:23:49 CDT(-0500)] <lahabana> should be added to the template
[09:23:58 CDT(-0500)] <lahabana> or to the options.styles
[09:24:26 CDT(-0500)] <lahabana> cause for UIoptions it's done in the tempalte
[09:24:36 CDT(-0500)] <anastasiac> ah, I see. Well, generally, if they should be on the template by default, certainly put them there. options.styles is most useful for styles that you might be swapping programmatically
[09:24:42 CDT(-0500)] <Justin_o> alison-benj: but i'm not quite sure what you mean by "the fl-table seems to take on the height of this UL." or at least i'm not sure i see it
[09:25:08 CDT(-0500)] <anastasiac> for example, if you have a style that is only used while something is active, you put the class name in options.styles and the code can programmatically use that to know what class name to add to the mark-up
[09:25:12 CDT(-0500)] <anastasiac> make sense, lahabana?
[09:25:13 CDT(-0500)] <lahabana> anastasiac: ok that's what I thought 
[09:25:19 CDT(-0500)] <lahabana> yes perfect sens!
[09:25:23 CDT(-0500)] <anastasiac> good :_)
[09:25:29 CDT(-0500)] <lahabana> anastasiac: thx
[09:27:57 CDT(-0500)] <huslage> fluid-everyone, any objections to me taking down JIRA tonight to upgrade?
[09:28:56 CDT(-0500)] <Justin_o> huslage: i'm fine with that.. what time will it be down
[09:30:02 CDT(-0500)] <huslage> i'm thinking from 8-9ish
[09:31:25 CDT(-0500)] <alison-benj> Justin_o: oh, I mean, as you say, the table goes as small as the minimum size of what it holds. By the same token, it goes as large as the maximum size of its contents.
[09:32:22 CDT(-0500)] <alison-benj> Justin_o: One of the table's contents would be that UL, which is hidden or shown, ergo changing the height of the table – hope that makes sense.
[09:32:45 CDT(-0500)] <alison-benj> Justin_o: am talking to greggy1 today about the best way to implement my design goal :oS
[09:39:35 CDT(-0500)] <Justin_o> alison-benj: okay.. i wonder if the navigation actually needs to be in the table
[09:39:55 CDT(-0500)] <alison-benj> Justin_o: you mean the UL or the actual link that opens the UL?
[09:40:03 CDT(-0500)] <Justin_o> alison-benj: sorry.. the ul
[09:40:24 CDT(-0500)] <Justin_o> alison-benj: it's visually sort of a dialog
[09:40:51 CDT(-0500)] <alison-benj> Justin_o: yeah.
[09:52:17 CDT(-0500)] <alison-benj> Justin_o: Ok, I will do a search. If you know of an a11y example I could check out on my ipad as inspiration, feel free to send my way.
[09:54:13 CDT(-0500)] <Justin_o> alison-benj: i was looking at the jquery mobile site, but there dialogs don't really seem like dialogs for some reason
[09:54:14 CDT(-0500)] <Justin_o> http://jquerymobile.com/demos/1.0b2/#/demos/1.0b2/docs/pages/page-dialogs.html
[09:54:40 CDT(-0500)] <alison-benj> Justin_o: ah yes.. thx.
[10:14:25 CDT(-0500)] <Justin_o> alison-benj: just out of curiosity, would you have your code up anywhere live to try out
[10:40:33 CDT(-0500)] <alison-benj> Justin_o: I'm going to put an installation from my branch on my currently empty site benj.info when I am near done with my project but I'm a week or two away from that. I have a branch that is available to install in the meantime. But I should probably work a bit on the header before I point anyone to test it out.
[11:00:25 CDT(-0500)] <jhung> jameswy, justin_o: can someone start the decapod call?
[11:02:22 CDT(-0500)] <Justin_o> jhung: hello.. sorry was just having a quick meeting with colinclark and michelled
[11:03:17 CDT(-0500)] <jhung> justin_o: k. Can you or colin start the call?
[11:04:16 CDT(-0500)] <Justin_o> jhung: just going to be me today.. i'll try to start the skype call
[13:30:58 CDT(-0500)] <alison-benj> Justin_o: Thanks for the look at my screenshots today, but it seems like I've figured out a way to do what I need without an fl-table. Once again the jquery mobile stuff is cool, but I probably won't implement it in my summer of code project. hopefully later.
[13:56:27 CDT(-0500)] <jhung> jameswy, colinclark: I've sent over a PPT file for the Decapod chat for the 2-week intensive. Please take a look when you have a chance.
[14:01:02 CDT(-0500)] <colinclark> jhung: Thanks. I'll take a look and give you some feedback
[14:01:17 CDT(-0500)] <colinclark> I'll be there at the intensive to help you present
[14:01:37 CDT(-0500)] <jhung> Great! Feel free to add to it.
[14:17:29 CDT(-0500)] <colinclark> Hey jhung, one initial bit of feedback
[14:17:32 CDT(-0500)] <colinclark> about your preso
[14:17:34 CDT(-0500)] <colinclark> it looks good
[14:17:54 CDT(-0500)] <colinclark> I'm wondering if you can spend some time highlighting the opportunities in Decapod for our students
[14:18:06 CDT(-0500)] <jhung> ah. of course.
[14:18:13 CDT(-0500)] <colinclark> areas in which they can get involved
[14:18:24 CDT(-0500)] <colinclark> And also the kinds of interesting opportunities we discussed the other week
[14:18:32 CDT(-0500)] <colinclark> but that are probably out of scope for the Decapod project itself
[14:18:36 CDT(-0500)] <colinclark> Things like annotation
[14:18:38 CDT(-0500)] <colinclark> transcription
[14:18:44 CDT(-0500)] <colinclark> tagging, collaborative book capture and editing
[14:18:54 CDT(-0500)] <colinclark> the accessibility angle
[14:19:12 CDT(-0500)] <jhung> Sure.
[14:19:17 CDT(-0500)] <colinclark> perhaps an example of pulkit's work
[14:19:29 CDT(-0500)] <colinclark> where he's experimenting with fancy HTML5 image editing tools
[14:19:33 CDT(-0500)] <colinclark> and they'll make their way into Decapod
[14:19:38 CDT(-0500)] <colinclark> that sort of thing
[14:20:04 CDT(-0500)] <jhung> michelled: is pulkit's work hosted somewhere so I can take a screencap?
[14:20:09 CDT(-0500)] <colinclark> I think the other thing to keep in mind is that Jutta's goal has been to structure these sessions as conversational, informal
[14:20:26 CDT(-0500)] <colinclark> So think about some ways to, rather than just giving a presentation with slides, discuss with the students
[14:20:40 CDT(-0500)] <colinclark> these are grad students--smart, professional, and engaged in the field
[14:21:00 CDT(-0500)] <colinclark> so what are some of the research questions related to Decapod? What are the fascinating, tricky, rich problems...
[14:21:11 CDT(-0500)] <colinclark> some are, as you know first-hand, cultural
[14:21:14 CDT(-0500)] <colinclark> some are technology
[14:21:18 CDT(-0500)] <jhung> That's good to know. I'll massage the slides accordingly so it's less of one of us talking.
[14:21:25 CDT(-0500)] <michelled> jhung: no, pulkit's work isn't hosted. the source is on github
[14:21:25 CDT(-0500)] <colinclark> Cool
[14:21:37 CDT(-0500)] <colinclark> michelled: Is anything needed to try it out?
[14:21:44 CDT(-0500)] <colinclark> These look really good, jhung
[14:25:03 CDT(-0500)] <jhung> colinclark: looks like you need to deploy it to a server (https://github.com/pulkit110/ImageEditor/blob/master/README.txt)
[14:25:13 CDT(-0500)] <jhung> I'll see if I can get that running locally.
[14:26:59 CDT(-0500)] <michelled> sorry jhung - I was about to tell you that. I was distracted by the lack of styling when I loaded github
[14:27:12 CDT(-0500)] <michelled> jameswy: it sort of looks like github lineraized
[14:27:50 CDT(-0500)] <jhung> haha np michelled.
[14:29:46 CDT(-0500)] <Bosmon> "github linearized" I'm sure will be one of the most crucial capabilities in our refreshed UIOptions for the next release
[14:32:29 CDT(-0500)] <Justin_o_> alison-benj: yah makes sense.. let me know if i can be of any more help regarding mobileFSS stuff
[14:35:48 CDT(-0500)] <lahabana> michelled: Hi I need a little help
[14:36:22 CDT(-0500)] <lahabana> do you know if it's possible not to allow an option to be modified?
[14:36:38 CDT(-0500)] <lahabana> I mean I've got things set in the defaults
[14:36:44 CDT(-0500)] <michelled> lahabana: why would you want to do that?
[14:36:51 CDT(-0500)] <lahabana> and I don't want the user to be able to change it
[14:37:02 CDT(-0500)] <lahabana> cause they are part of the model
[14:37:21 CDT(-0500)] <lahabana> which are actually given by the video
[14:37:28 CDT(-0500)] <lahabana> for eg if the video is loaded
[14:37:34 CDT(-0500)] <lahabana> or its length
[14:37:42 CDT(-0500)] <michelled> what would happen if the user changed it?
[14:37:55 CDT(-0500)] <lahabana> nothing really
[14:38:05 CDT(-0500)] <michelled> do you think users will try to change it?
[14:38:17 CDT(-0500)] <lahabana> hmm it could
[14:39:08 CDT(-0500)] <michelled> actually, can we step back even further so I get a better picture? why are these things in the defaults?
[14:39:35 CDT(-0500)] <lahabana> don't really know
[14:40:21 CDT(-0500)] <lahabana> cause when I created it
[14:40:36 CDT(-0500)] <lahabana> it enabled me to have the full model quickly
[14:41:21 CDT(-0500)] <michelled> can you point me to the code?
[14:41:49 CDT(-0500)] <lahabana> yes
[14:42:46 CDT(-0500)] <lahabana> https://github.com/lahabana/videoPlayer/blob/master/js/VideoPlayer.js#L91-192
[14:44:41 CDT(-0500)] <lahabana> well I guess if it's explained in the API doc
[14:44:49 CDT(-0500)] <lahabana> there won't be any issue
[14:44:58 CDT(-0500)] <lahabana> no? michelled
[14:45:48 CDT(-0500)] <michelled> lahabana: yes, that's true. we generally like to expose everything we can to the user and then give them examples and documentation on how we expect them to use it
[14:46:14 CDT(-0500)] <lahabana> yes
[14:46:26 CDT(-0500)] <michelled> if they want to meddle with the model then they get some strange results but on the other hand they might want to do something interesting we hadn't thought of or implemented
[14:46:48 CDT(-0500)] <lahabana> yes that's totally true
[14:47:29 CDT(-0500)] <lahabana> ok so I'll just go this way
[14:48:34 CDT(-0500)] <lahabana> also michelled
[14:48:39 CDT(-0500)] <lahabana> I've got another question
[14:49:15 CDT(-0500)] <lahabana> if you look there: https://github.com/lahabana/videoPlayer/blob/master/js/VideoPlayer.js#L395-414
[14:49:34 CDT(-0500)] <lahabana> I've done a eventBinder which works fine
[14:50:33 CDT(-0500)] <lahabana> the only issue is that I've got some subcomponent
[14:50:47 CDT(-0500)] <lahabana> that are instantiated by the renderer
[14:50:53 CDT(-0500)] <lahabana> so possibly not here
[14:51:16 CDT(-0500)] <lahabana> and when they are not here there is an error
[14:51:45 CDT(-0500)]
[14:51:57 CDT(-0500)] <lahabana> do you have any idea of how to avoid that michelled ?
[14:52:27 CDT(-0500)] <michelled> ah, there is a way to have a subcomponent wait until some particular time before being created. the eventBinder should wait until everything else has been created
[14:53:12 CDT(-0500)] <michelled> 'createOnEvent'
[14:53:20 CDT(-0500)] <michelled> lahabana: can you use that strategy?
[14:53:44 CDT(-0500)] <lahabana> yes I could
[14:54:02 CDT(-0500)] <lahabana> just found it a little more logical to use the renderer decorator
[14:54:27 CDT(-0500)] <lahabana> but anyway that's not really going to change anything is it?
[14:54:43 CDT(-0500)] <lahabana> cause the thing is that some don't exist
[14:54:50 CDT(-0500)] <lahabana> *subcomponent
[14:55:44 CDT(-0500)] <michelled> one way to do this is to have an event that fires when all the subcomponents are ready and specify the event binder to be created when that event fires
[14:56:07 CDT(-0500)] <michelled> would that work in your case?
[14:56:28 CDT(-0500)] <lahabana> yes it's already the case
[14:56:39 CDT(-0500)] <lahabana> no
[14:56:55 CDT(-0500)] <lahabana> cause the thing is that some components are not compulsory
[14:57:55 CDT(-0500)] <lahabana> so I would need an eventBinder
[14:58:07 CDT(-0500)] <lahabana> to change according to what exists or not
[14:58:17 CDT(-0500)] <lahabana> if that makes sens...
[14:58:36 CDT(-0500)] <michelled> or smaller event binders that exist when a particular subcomponent exists maybe?
[14:59:03 CDT(-0500)] <lahabana> hmm possible
[14:59:35 CDT(-0500)] <lahabana> Good idea actually
[14:59:41 CDT(-0500)] <lahabana> that should solved my problem
[14:59:47 CDT(-0500)] <michelled> cool
[14:59:53 CDT(-0500)] <lahabana> thx michelled
[14:59:56 CDT(-0500)] <michelled> np
[15:00:02 CDT(-0500)] <Bosmon> lahabana - remember that you can fall back on "event injection"
[15:00:14 CDT(-0500)] <lahabana> sorry?
[15:00:18 CDT(-0500)] <Bosmon> To make sure that events are defined in the right scope of things where they actually exist
[15:00:50 CDT(-0500)] <Bosmon> There is this page on the subject
[15:00:51 CDT(-0500)] <Bosmon> http://wiki.fluidproject.org/display/docs/Event+injection+and+boiling
[15:01:06 CDT(-0500)] <Bosmon> I'm not sure whether this will help you in this situation or not, it sounds like you have resolved your issue already
[15:01:08 CDT(-0500)] <lahabana> isn't it what I do there: https://github.com/lahabana/videoPlayer/blob/master/js/VideoPlayer.js#L395-414 ?
[15:01:10 CDT(-0500)] <Bosmon> But this might help you in other cases
[15:01:39 CDT(-0500)] <Bosmon> Oh yes, this is all good - looks like you are using it already
[15:01:49 CDT(-0500)] <lahabana> ok that's waht I thought
[15:02:01 CDT(-0500)] <lahabana> even though I do listeners instead of Events?
[15:02:06 CDT(-0500)] <Bosmon> Yes
[15:02:16 CDT(-0500)] <lahabana> ok just making sure
[15:02:27 CDT(-0500)] <Bosmon> But you can do the same for events too - as well as a few other things
[15:02:28 CDT(-0500)] <lahabana> thank you for helping me
[15:02:36 CDT(-0500)] <lahabana> ok great
[15:02:46 CDT(-0500)] <Bosmon> Your code there looks written in good style wrt. the current framework
[15:03:01 CDT(-0500)] <lahabana> thank you
[15:03:04 CDT(-0500)] <lahabana> I tried to
[15:03:47 CDT(-0500)] <lahabana> so that it won't be necessary to go back at some point...
[15:04:17 CDT(-0500)] <Bosmon> This "eventBinder" solution is one that we are using in a number of places now
[15:04:35 CDT(-0500)] <lahabana> I know colinclark suggested it to me
[15:05:39 CDT(-0500)] <lahabana> the thing I'm doubting more about it
[15:05:42 CDT(-0500)] <Bosmon> Here is an example of what code looks like without this idiom - https://github.com/ajaxorg/ace/blob/master/lib/ace/editor.js#L145-186
[15:05:51 CDT(-0500)] <Bosmon> I think you will consider that it looks pretty awful 
[15:06:13 CDT(-0500)] <lahabana> yes
[15:06:37 CDT(-0500)] <Bosmon> And, of course, it is impossible to configure, without altering the core source file
[15:06:43 CDT(-0500)] <lahabana> is the way I do my shared model
[15:07:30 CDT(-0500)] <lahabana> yes I found it really nice to just link stuffs really quickly
[15:07:58 CDT(-0500)] <lahabana> and u find things quickly
[15:10:10 CDT(-0500)] <lahabana> Bosmon: looking at my code I think I can find an easier way to make it work
[15:10:23 CDT(-0500)] <Bosmon> lahabana - what way do you see?
[15:10:38 CDT(-0500)] <lahabana> cause atm it makes an error
[15:10:48 CDT(-0500)] <lahabana> cause for eg captionner doesn't exists
[15:11:01 CDT(-0500)] <lahabana> so it doesn't find resyncCaptions
[15:11:18 CDT(-0500)] <Bosmon> Surely if the captioner doesn't exist, the demands block doesn't operate?
[15:11:35 CDT(-0500)] <lahabana> sorryN
[15:11:37 CDT(-0500)] <lahabana> ?
[15:12:22 CDT(-0500)] <Bosmon> fluid.demands("fluid.videoPlayer.eventBinder",
[15:12:23 CDT(-0500)] <Bosmon> ["fluid.videoPlayer.controllers",
[15:12:23 CDT(-0500)] <Bosmon> "fluid.videoPlayer.captionner",
[15:12:35 CDT(-0500)] <Bosmon> The demands block you have written is only active in the case there is a captionner in the component tree....
[15:13:27 CDT(-0500)]
[15:13:32 CDT(-0500)] <lahabana> that's the error
[15:13:50 CDT(-0500)] <lahabana> (when controllers is not on)
[15:14:29 CDT(-0500)] <lahabana> so it looks like the demands block actually exists no?
[15:14:37 CDT(-0500)] <Bosmon> Well, it shouldn't
[15:14:46 CDT(-0500)] <Bosmon> It is also conditional on the existence of the controllers
[15:15:22 CDT(-0500)] <Bosmon> Oh, this is interesting
[15:15:32 CDT(-0500)] <Bosmon> The controllers is constructed using a renderer decorator
[15:15:40 CDT(-0500)] <Bosmon> I haven't seen this possibility used before
[15:15:43 CDT(-0500)] <Bosmon> But still, it should work
[15:16:27 CDT(-0500)] <Bosmon> ah!!!
[15:16:27 CDT(-0500)] <lahabana> it does work really well
[15:16:31 CDT(-0500)] <Bosmon> horrors
[15:16:34 CDT(-0500)] <Bosmon> I think I know what is going wrong here
[15:16:34 CDT(-0500)] <lahabana> except that binding part
[15:16:38 CDT(-0500)] <lahabana> ho?
[15:16:40 CDT(-0500)] <lahabana> tell me
[15:16:58 CDT(-0500)] <Bosmon> Well... it is a kind of combination of framework bugs
[15:17:09 CDT(-0500)] <Bosmon> Your demands block "matches" but really it mismatches
[15:17:20 CDT(-0500)] <Bosmon> The "controllers" component is not actually recognised by the IoC system as context-forming
[15:17:27 CDT(-0500)] <Bosmon> Although it really should be
[15:17:48 CDT(-0500)] <lahabana> ok
[15:18:57 CDT(-0500)] <lahabana> so ...
[15:18:57 CDT(-0500)] <Bosmon> And although there was a plan to remove mismatched demands blocks from consideration, it wasn't thought through sufficiently before the framework freeze for 1.4
[15:19:09 CDT(-0500)] <lahabana> ok
[15:19:22 CDT(-0500)] <lahabana> so I'll have to leave with the bug no?
[15:19:33 CDT(-0500)] <Bosmon> So by virtue of matching on 4 contexts out of 5, your demands block is allowed to win
[15:19:35 CDT(-0500)] <lahabana> try to find a walkaround
[15:19:41 CDT(-0500)] <Bosmon> Well, it will be hard
[15:19:55 CDT(-0500)] <Bosmon> Probably the best thing would be for me to make you a small branch of the core framework with the bug fixed this evening
[15:20:23 CDT(-0500)] <jameswy> jhung: Just took a look at your slidedeck-looks good. I wonder if your slide on "design & development" could be more focused on what makes Decapod inclusive, or how we're building inclusivity into it, instead of general verbiage on what inclusive design and UCD are? (I imagine pretty much every discussion/seminar/conversation they'll have had up to that point and beyond that point will be around what ID/UCD/etc. are-they're probably more interested in
[15:20:23 CDT(-0500)] <jameswy> special relationship between Decapod and inclusion)
[15:20:38 CDT(-0500)] <Bosmon> We can't afford a change this fundamental this close to the 1.4 release - but github will make it easy for you to work from my branch for a while
[15:20:40 CDT(-0500)] <lahabana> Bosmon: could you do that
[15:20:45 CDT(-0500)] <Bosmon> Yes, I will
[15:21:14 CDT(-0500)] <lahabana> so that would be really nice from you
[15:21:22 CDT(-0500)] <jameswy> jhung: It might be obvious, but might be good to either highlight it-or, better yet, get a discussion with the students around it-what, why, how it serves inclusion.
[15:23:16 CDT(-0500)] <lahabana> Bosmon: I guess I won't be here when you'll be done with it so can you email the link to me?
[15:23:31 CDT(-0500)] <Bosmon> http://issues.fluidproject.org/browse/FLUID-4392
[15:23:37 CDT(-0500)] <Bosmon> lahabana - yes, I will
[15:23:40 CDT(-0500)] <lahabana> ok cheers
[15:23:47 CDT(-0500)] <Bosmon> But you will discover the branch in my repo named for this JIRA
[15:24:27 CDT(-0500)] <lahabana> yes
[15:24:40 CDT(-0500)] <lahabana> it's ok now that I've got the name of the JIRA issue
[15:25:12 CDT(-0500)] <lahabana> Bosmon: wait though
[15:25:24 CDT(-0500)] <Bosmon> Yes
[15:25:28 CDT(-0500)] <Bosmon> I think I know what you're going to say
[15:25:39 CDT(-0500)] <lahabana> cause the reference is resolved when the component is created
[15:26:10 CDT(-0500)] <Bosmon> Well, sure, but it is only created after rendering is done
[15:26:16 CDT(-0500)] <lahabana> it's just when I remove them
[15:26:48 CDT(-0500)] <Bosmon> When you remove what?
[15:27:07 CDT(-0500)] <lahabana> the captionArea from the HTML template
[15:27:21 CDT(-0500)] <Bosmon> Yes
[15:27:43 CDT(-0500)] <lahabana> so the component is not created at all
[15:27:47 CDT(-0500)] <lahabana> yes?
[15:27:52 CDT(-0500)] <Bosmon> Yes, that's right
[15:28:07 CDT(-0500)] <Bosmon> The renderer will fail to construct it if it doesn't match any markup
[15:29:00 CDT(-0500)] <lahabana> yes that's the point
[15:29:15 CDT(-0500)] <lahabana> so it's quite normal "controllers is not resolvable"
[15:29:37 CDT(-0500)] <Bosmon> Yes - but surely the problem is it is never resolvable....
[15:29:43 CDT(-0500)] <Bosmon> Or do you sometimes see it as being resolvable?
[15:30:23 CDT(-0500)] <lahabana> it is (well I think) when the component is created
[15:30:31 CDT(-0500)] <Bosmon> That's odd
[15:30:39 CDT(-0500)] <lahabana> there's not error
[15:30:40 CDT(-0500)] <Bosmon> By my reading of the framework code, it should never be resolvable
[15:30:47 CDT(-0500)] <Bosmon> Let me look again...
[15:30:50 CDT(-0500)] <lahabana> and the event is fired and listened perfectly
[15:31:31 CDT(-0500)] <Bosmon> ok
[15:31:37 CDT(-0500)] <Bosmon> You are right, I misremembered the code completely
[15:31:40 CDT(-0500)] <Bosmon> This bug is quite wrong
[15:31:45 CDT(-0500)] <Bosmon> What you need is a completely different feature
[15:32:12 CDT(-0500)] <lahabana> being?
[15:32:39 CDT(-0500)] <Bosmon> "additive demands blocks"
[15:32:45 CDT(-0500)] <Bosmon> I was just speaking about this with yura_
[15:32:49 CDT(-0500)] <jhung> jameswy: That's a good point. I've added a slide that gives context to some of the design complexities in Decapod (i.e. trying to make simple a rather complex system). I think that slide would be a good segue into ID / UCD discussion.
[15:32:50 CDT(-0500)] <Bosmon> Since he really needs it for CollectionSpace also
[15:32:58 CDT(-0500)] <Bosmon> You need to be able to split this demands block into two
[15:33:10 CDT(-0500)] <Bosmon> And have one part of it "mismatch completely" in the case controllers is not present
[15:33:38 CDT(-0500)] <lahabana> yes
[15:34:16 CDT(-0500)] <lahabana> and how can I do that?
[15:34:29 CDT(-0500)] <Bosmon> I'll implement that feature instead, instead of the one I just described
[15:35:02 CDT(-0500)] <lahabana> ho ok
[15:35:03 CDT(-0500)] <lahabana> thx
[18:57:56 CDT(-0500)] <colinclark> hey huslage
[18:58:00 CDT(-0500)] <colinclark> you on the clock?
[19:03:19 CDT(-0500)] <huslage> hi
[19:03:21 CDT(-0500)] <huslage> i am
[19:03:32 CDT(-0500)] <huslage> what's up colinclark
[19:03:43 CDT(-0500)] <colinclark> Couple of quick questions for you if you have a sec
[19:03:51 CDT(-0500)] <colinclark> No rush on either
[19:03:56 CDT(-0500)] <huslage> ok
[19:04:09 CDT(-0500)] <colinclark> 1. I'm wondering if there's anything we can do with the move of the IDRC everyone@ list
[19:04:24 CDT(-0500)] <colinclark> A few of have accidentally sent emails to the old address and not noticed
[19:04:28 CDT(-0500)] <colinclark> no bounce or anything
[19:04:37 CDT(-0500)] <colinclark> Is there anything easy that can be done about that?
[19:05:09 CDT(-0500)] <colinclark> 2. Is there any kind of "self help" provision for mailing lists?
[19:05:52 CDT(-0500)] <colinclark> I'm thinking about introducing a bit of new infrastructure under the rubric of "Fluid Labs"--a more informal place for experimenting with design, user experience, inclusion, and the web
[19:06:11 CDT(-0500)] <colinclark> And I guess this is one of those cases where you could just hand me a fish to munch on
[19:06:20 CDT(-0500)] <colinclark> for much less time than it would take to get me fishing myself
[19:08:01 CDT(-0500)] <huslage> 1. I'll look at it. I'm not sure why it's not bouncing
[19:08:11 CDT(-0500)] <colinclark> Cool
[19:08:21 CDT(-0500)] <colinclark> If you do find something for #2, I think it will be a worthy investment in the long run
[19:08:34 CDT(-0500)] <colinclark> Things going okay for you otherwise, huslage?
[19:08:37 CDT(-0500)] <huslage> as for fluid labs we'll be able to support that sort of self-service provisioning of machines and stuff with the new infrastructure
[19:08:46 CDT(-0500)] <colinclark> That'll be really cool
[19:08:56 CDT(-0500)] <huslage> yeah it's pretty chill. just doing this silly JIRA update
[19:09:04 CDT(-0500)] <huslage> they changed stuff again mid-release cycle
[19:09:04 CDT(-0500)] <colinclark> I've got it on my to do list to write a bit of a requirements page about daily builds, too
[19:09:08 CDT(-0500)] <colinclark> ah, yeah
[19:09:10 CDT(-0500)] <colinclark> they're like that
[19:09:13 CDT(-0500)] <huslage> yeah, that'd be helpful
[19:09:30 CDT(-0500)] <colinclark> Justin_o is doing some work with the jQuery community related to TestSwarm and Jenkins
[19:09:37 CDT(-0500)] <colinclark> he'll probably need your help with it
[19:09:50 CDT(-0500)] <colinclark> and so we might want to follow that direction a bit and see if it's promising
[19:10:03 CDT(-0500)] <colinclark> but I'll write something about a self-provisioning dream for builds
[19:10:15 CDT(-0500)] <colinclark> and I'm thinking we can actually build something sooner rather than later
[19:10:38 CDT(-0500)] <huslage> oh good. i was thinking about testswarm and jenkins being good options
[19:10:58 CDT(-0500)] <huslage> yeah we probably can get there faster than any hardware will join us
[19:11:15 CDT(-0500)] <colinclark> might as well just go for it
[19:11:20 CDT(-0500)] <colinclark> it'll be immediately useful
[19:11:31 CDT(-0500)] <colinclark> I anticipate a real influx of people experimenting with stuff and wanting to show it off
[19:11:31 CDT(-0500)] <colinclark> w
[19:11:37 CDT(-0500)] <colinclark> within this "Labs" effort
[19:11:43 CDT(-0500)] <colinclark> students, etc.
[19:11:47 CDT(-0500)] <colinclark> it'll be exciting
[19:12:14 CDT(-0500)] <huslage> that's awesome
[19:12:19 CDT(-0500)] <huslage> i'm happy about that
[19:12:24 CDT(-0500)] <huslage> experimenting is FUN
[19:12:25 CDT(-0500)] <huslage> lol
[19:12:43 CDT(-0500)] <colinclark>
[19:12:50 CDT(-0500)] <huslage> someone needs to teach me js
[19:12:58 CDT(-0500)] <colinclark> That would be awesome
[19:13:03 CDT(-0500)] <colinclark> we can help with that for sure
[19:13:08 CDT(-0500)] <huslage> i was hacking jQuery this weekend and it was awful
[19:13:29 CDT(-0500)] <colinclark> why so awful
[19:13:31 CDT(-0500)] <colinclark> ?
[19:14:14 CDT(-0500)] <huslage> i just got stuck trying to find entry points and crap
[19:14:24 CDT(-0500)] <huslage> hacking on ushahidi…which has admittedly odd code
[19:14:34 CDT(-0500)] <colinclark> ah
[19:14:43 CDT(-0500)] <colinclark> jQuery can sometimes be like that
[19:15:00 CDT(-0500)] <colinclark> Just send us a pastie or Github link or whatever if you have questions
[19:15:03 CDT(-0500)] <colinclark> we can help
[19:15:08 CDT(-0500)] <colinclark> and Ushahidi is awesome
[19:15:27 CDT(-0500)] <huslage> thanks
[19:15:43 CDT(-0500)] <huslage> my last big jump into javascript was really in like 1997
[19:15:49 CDT(-0500)] <huslage> so i'm a little rusty
[19:16:13 CDT(-0500)] <colinclark> Yeah, it's so much better than in 1997, thankfully
[19:16:18 CDT(-0500)] <colinclark> I mean, I guess the language isn't much different
[19:16:22 CDT(-0500)] <colinclark> but people are less insane with it
[19:16:51 CDT(-0500)] <huslage> totally
[19:16:59 CDT(-0500)] <huslage> i was using Netscape LiveWire back when
[19:17:04 CDT(-0500)] <huslage> with Informix db
[19:17:06 CDT(-0500)] <huslage> lol
[19:17:10 CDT(-0500)] <colinclark> wow great
[19:17:20 CDT(-0500)] <colinclark> way back
[19:17:25 CDT(-0500)] <huslage> ghost-wrote about half of a book on the thing
[19:17:27 CDT(-0500)] <colinclark> livewire was on the server, right?
[19:17:34 CDT(-0500)] <huslage> yes
[19:17:40 CDT(-0500)] <colinclark> you were way ahead of your time
[19:17:41 CDT(-0500)] <huslage> but i did a bunch of client-side stuff toot
[19:17:42 CDT(-0500)] <huslage> too
[19:17:45 CDT(-0500)] <huslage> i was.
[19:18:02 CDT(-0500)] <huslage> that's why node.js doesn't surprise me…it's "oh, we're doing that again?"
[19:18:15 CDT(-0500)] <huslage> admittedly much better this time
[19:18:22 CDT(-0500)] <colinclark> yep
[19:18:26 CDT(-0500)] <colinclark> that's the thing about code
[19:18:39 CDT(-0500)] <colinclark> They really should teach more rigorous history of computing courses
[19:18:45 CDT(-0500)] <huslage> sorta like how what we're doing on the systems side is going back to mainframe principles
[19:18:49 CDT(-0500)] <huslage> they should
[19:18:56 CDT(-0500)] <colinclark> Though then schmucks like me would come along and never bother to take the courses
[19:19:02 CDT(-0500)] <huslage> it would create more opportunities to remember that we've done this crap already
[19:19:09 CDT(-0500)] <colinclark> yes, exactly
[19:19:11 CDT(-0500)] <colinclark> over and over again
[19:19:19 CDT(-0500)] <colinclark> luckily Node is the real deal
[19:19:23 CDT(-0500)] <huslage> iterative profession
[19:19:27 CDT(-0500)] <huslage> yes it is
[19:19:33 CDT(-0500)] <huslage> i'm loving watching that community
[19:19:58 CDT(-0500)] <huslage> i know a lot about a lot of these communities, but i have no interest in coding. i'm such a computer anthropologist
[19:20:06 CDT(-0500)] <colinclark> yeah, I know how that goes, too
[19:20:12 CDT(-0500)] <colinclark> communities are interesting
[19:20:25 CDT(-0500)] <huslage> in my spare time i go lurk and watch and poke around on github
[19:20:28 CDT(-0500)] <colinclark> cool
[19:20:35 CDT(-0500)] <colinclark> me too
[19:20:35 CDT(-0500)] <huslage> it's terribly boring to outsiders. to me it's fascinating
[19:21:06 CDT(-0500)] <colinclark> yep
[19:22:15 CDT(-0500)] <colinclark> well, i should run
[19:22:19 CDT(-0500)] <colinclark> no dinner yet
[19:22:21 CDT(-0500)] <colinclark> getting pretty hungry
[19:22:31 CDT(-0500)] <colinclark> let's check in later this week about builds, huslage
[19:22:36 CDT(-0500)] <huslage> k
[19:22:38 CDT(-0500)] <huslage> go eat
[19:22:39 CDT(-0500)] <huslage> enjoy
[19:22:40 CDT(-0500)] <colinclark> see you soon