[09:07:26 CST(-0600)] <michelled> Justin_o, colinclark: this looks interesting: http://www.sitepoint.com/jquip-lightweight-jquery/
[09:07:37 CST(-0600)] <michelled> I didn't look to see if it has most of what we use in jQuery
[09:09:44 CST(-0600)] <Justin_o> michelled: interesting.. that might work well if we have an improved and more modular build system
[09:13:01 CST(-0600)] <colinclark> Such a strange world
[09:13:07 CST(-0600)] <colinclark> where jQuery is forked because it's too big
[09:13:36 CST(-0600)] <colinclark> Seems to me one of the benefits of shipping with jQuery is that we can ensure compatibility with, well, jQuery 
[09:13:41 CST(-0600)] <colinclark> Meaning, people have other code
[09:13:44 CST(-0600)] <colinclark> and it's probably in jQuery
[09:29:39 CST(-0600)] <Justin_o> colinclark: if we ourselves only actually use what's in the subset we could give our users the option to take the smaller build of jquery rather than have to pull it all in
[09:29:51 CST(-0600)] <Justin_o> or they could just not take jquery and use their own i guess
[09:44:23 CST(-0600)] <Justin_o> colinclark, anastasiac: is there a way to reset the uploader?
[09:44:34 CST(-0600)] <colinclark> Reset it how, Justin_o?
[09:44:44 CST(-0600)] <Justin_o> colinclark: clear the queue for example
[09:44:49 CST(-0600)] <Justin_o> and any error messages
[09:44:54 CST(-0600)] <colinclark> oh
[09:45:00 CST(-0600)] <colinclark> is that specifically what you want to do?
[09:45:00 CST(-0600)] <anastasiac> good question
[09:45:02 CST(-0600)] <colinclark> clear the queue
[09:45:05 CST(-0600)] <colinclark> and the error messages?
[09:45:07 CST(-0600)] <colinclark> anything else/
[09:45:49 CST(-0600)] <Justin_o> um not sure.. basically i want to get it back to the initial state
[09:46:31 CST(-0600)] <Justin_o> i could just trigger a refresh of the page if there isn't a straightforward way to do it in the component
[09:46:44 CST(-0600)] <colinclark> Well, I'm trying to get a better sense of what that actually means
[09:46:56 CST(-0600)] <colinclark> The most heavy-handed approach is to, as you say, zap the page
[09:47:03 CST(-0600)] <colinclark> you can zap the Uploader itself, too, if you'd rather
[09:47:08 CST(-0600)] <colinclark> like the Gallery demo does
[09:47:21 CST(-0600)] <colinclark> But the question really is, what are you trying to do, specifically?
[09:47:27 CST(-0600)] <Justin_o> colinclark: hmm.. how would that work with it being a subcomponent though
[09:47:37 CST(-0600)] <colinclark> There are undoubtedly methods to do things like remove files from the queue
[09:47:43 CST(-0600)] <colinclark> and clear error messages
[09:48:03 CST(-0600)] <colinclark> but that doesn't really sound like what you want, exactly
[09:48:08 CST(-0600)] <colinclark> Do you have a wireframe or something?
[09:48:20 CST(-0600)] <Justin_o> colinclark: maybe it is.. yes i was just fetching them http://wiki.fluidproject.org/display/fluid/Decapod+0.5+Wireframes
[09:48:45 CST(-0600)] <Justin_o> so you see #7 there is a "Start Over" button/link
[09:49:08 CST(-0600)] <Justin_o> which should revert everything back to the original state
[09:49:59 CST(-0600)] <colinclark> Easiest is probably to reload the page
[09:50:11 CST(-0600)] <colinclark> but there should be methods for you to remove items from the queue and clear errors
[09:50:17 CST(-0600)] <colinclark> I'll have a look at the API real quick
[09:51:49 CST(-0600)] <colinclark> Justin_o: So FileQueueView offers the sort of method you'd expect: removeFile(file)
[09:52:11 CST(-0600)] <colinclark> but it's sort of at the wrong level of abstraction for you
[09:52:31 CST(-0600)] <colinclark> You could write something very easily on FileQueueView
[09:52:35 CST(-0600)] <colinclark> a clearAllFiles() method
[09:52:57 CST(-0600)] <colinclark> file queue view has a reference to a model of some kind which contains files
[09:53:01 CST(-0600)] <colinclark> and then you'd just remove 'em
[09:53:21 CST(-0600)] <colinclark> the ErrorPanel does contain a clear() method
[09:53:44 CST(-0600)] <colinclark> you'd probably fine with those two solutions if you didn't want to refresh the page
[09:54:22 CST(-0600)] <Justin_o> colinclark: thanks.. i might start with the refresh page and then change to those methods if i have time
[09:54:32 CST(-0600)] <colinclark> that's what i'd do, too
[09:59:33 CST(-0600)] <Justin_o> colinclark, yura: do you guys know if there is a way to force listeners to happen in a certain order
[09:59:40 CST(-0600)] <Justin_o> or at least to have one fire first
[10:00:05 CST(-0600)] <colinclark> hmm, Justin_o
[10:00:07 CST(-0600)] <colinclark> what do you mean?
[10:00:10 CST(-0600)] <yura> Justin_o: use priority
[10:00:11 CST(-0600)] <colinclark> ah listeners
[10:00:14 CST(-0600)] <colinclark> yes
[10:00:26 CST(-0600)] <yura> "first", "last" and/or index
[10:02:09 CST(-0600)] <Justin_o> yura: do you have a an example of the structure for that or will it look something like
[10:02:47 CST(-0600)] <yura> listeners:
[10:06:51 CST(-0600)] <Justin_o> yura: thanks
[10:07:03 CST(-0600)] <yura> np
[13:19:33 CST(-0600)] <michelled> fluid-everyone: would anyone like to be skyped into the community meeting?
[13:19:54 CST(-0600)] <jessm> michelled: me
[13:19:57 CST(-0600)] <michelled> fluid-everyone: jvass is going to give a workshop on photoshop