fluid-tech IRC Logs-2013-05-03

[13:33:59 CDT(-0500)] <yzen> Bosmon: !

[13:39:54 CDT(-0500)] <Bosmon> ZENE'EVICH!!

[13:41:02 CDT(-0500)] <yzen> hi

[13:41:15 CDT(-0500)] <yzen> so how do i take advantage of source semantics in applier?

[13:48:49 CDT(-0500)] <Bosmon> yzen - you can look in the Video player for examples of use of this API

[13:48:55 CDT(-0500)] <Bosmon> e.g. "fireSourcedChange" etc.

[14:00:51 CDT(-0500)] <colinclark> Bosmon: What's new and interesting in our world of the framework?

[14:02:40 CDT(-0500)] <Bosmon> colinclark - thanks to michelled's recent merge we now have http://issues.fluidproject.org/browse/FLUID-4986

[14:02:50 CDT(-0500)] <Bosmon> Which should allow us to simplify the trees in UIO substantially now

[14:04:29 CDT(-0500)] <colinclark> michelled: If you're not totally distracted with something else, can you describe how you think this new code is awesome?

[14:07:17 CDT(-0500)] <colinclark> Justin_o: Will you be using this to refactor the protoTrees in UIO?

[14:09:52 CDT(-0500)] <Justin_o> colinclark: it should help with some changes we had made to our panels for sure..

[14:11:09 CDT(-0500)] <colinclark> What kinds of things will it help with?

[14:11:24 CDT(-0500)] <colinclark> I don't want to be a distraction if everyone is busily coding and I'm just trying to get caught up

[14:11:37 CDT(-0500)] <colinclark> so feel free to send me a link to something in Github if that's easier

[14:11:38 CDT(-0500)] <colinclark>

[14:14:36 CDT(-0500)] <michelled> colinclark: I think this change will make it more intuitive when we are working with renderer components. it's become natural to use names in the way we use them with IoC

[14:17:28 CDT(-0500)] <Justin_o> colinclark: i was trying to find you something, but it looks like it was refactored out already

[14:19:40 CDT(-0500)] <colinclark> Will it make for fewer produceTree functions, michelled?

[14:20:06 CDT(-0500)] <colinclark> I have this dream that we're starting to send a few sparks in the Renderer's direction

[14:20:13 CDT(-0500)] <colinclark> don't tell Bosmon I said that

[14:21:17 CDT(-0500)] <michelled> good question - I don't know. my impression is that it will lead to the same number of trees, but they will be more understandable since they are using the same language

[14:22:12 CDT(-0500)]

[14:22:25 CDT(-0500)] <colinclark> but will it make for more declarative renderer trees?

[14:23:00 CDT(-0500)] <colinclark> I believe my original comment, several years ago, was originally motivated by the fact that there were certain things one just couldn't do without still writing a lot of code in a produceTree function

[14:23:26 CDT(-0500)] <colinclark> and I was under the impression that this was part of the discussion yzen and Bosmon were having, but I'm all so fuzzy--it's been a long couple of weeks

[14:32:57 CDT(-0500)] <colinclark> Bosmon: Can you give me a quick overview

[14:33:06 CDT(-0500)] <colinclark> ?

[14:33:11 CDT(-0500)] <colinclark> I think these dudes must be pretty busy with more important work

[14:33:24 CDT(-0500)] <colinclark>

[14:36:24 CDT(-0500)] <yzen> Bosmon: since you opened http://issues.fluidproject.org/browse/FLUID-4686 i have a couple of questions for you

[14:37:10 CDT(-0500)] <yzen> Bosmon: if there's nothing in the store initially, we do not want to wipe defaultModel defaults from enactors

[14:38:01 CDT(-0500)] <yzen> Bosmon: at what point do we need to monitor the source ?

[14:39:04 CDT(-0500)] <yzen> and should we make a decision about how enactor model gets updated if there was nothing set for a particular path in the settings store ?