**** BEGIN LOGGING AT Sun Dec 23 03:00:00 2012
Dec 23 16:41:08 <fxspec06> i feel like enyo is missing something regarding inheritance relationships between parent and child objects. i feel like i'm missing some basic interaction functionality here. this.parent.published._____ doesn't seem 'nice' to me
Dec 23 22:04:46 <Roy__> fxspec06_: What problem were you having with inheritance?
Dec 24 00:03:37 <fxspec06_> er, it's really a gripe with the way enyo passes variables through messages
Dec 24 00:04:57 <fxspec06_> like waterfall and bubbleup are supposed to send messages, but it's difficult to remember when to use what for what. and you have to create a 2nd object sometimes, and it feels kinda hackish
Dec 24 00:05:49 <fxspec06_> in my problem i think it is with signals thogh. i can not track down but somewhere in my code i am having an enyo.instance passed
Dec 24 00:06:03 <fxspec06_> to an object that i'm ultimately saving
Dec 24 00:06:49 <fxspec06_> the workaround is to remove the object before saving, but it doesn't fix anything, the fix is to find where the enyo.instance is being added to what i'm passing, probably through a waterfall() or bubbleup/down() call
Dec 24 00:07:22 <fxspec06_> a fix i guess would be to use signals, but that seems overkill
Dec 24 02:16:43 <Roy__> fxspec06_: Hmm, not sure I've ever run into that problem before.
**** ENDING LOGGING AT Mon Dec 24 02:59:58 2012