**** BEGIN LOGGING AT Sat Mar 24 02:59:59 2012
Mar 24 16:17:47 <PuffTheMagic> halfhalo, ping
Mar 24 16:19:51 <halfhalo> hmmm?
Mar 24 16:20:57 <halfhalo> PuffTheMagic, pong
Mar 24 16:23:38 <PuffTheMagic> you have used websockets right?
Mar 24 16:23:45 <PuffTheMagic> non-node
Mar 24 16:25:09 <halfhalo> I have used them yes, but nothing low level.   Always tried to use a library to deal with them+add fallback support.  Why?
Mar 24 16:25:27 <PuffTheMagic> im trying to make an enyo2 control for it
Mar 24 16:25:38 <PuffTheMagic> and im having issues :/
Mar 24 16:26:27 <halfhalo> Are you dealing with websockets yourself or letting some other library talk to them?
Mar 24 16:27:07 <PuffTheMagic> myself
Mar 24 16:27:12 <PuffTheMagic> i dont want touse node
Mar 24 16:27:36 <PuffTheMagic> they seem simplke
Mar 24 16:27:45 <PuffTheMagic> and outside of enyo my test code works
Mar 24 16:27:50 <PuffTheMagic> but when i put it in a control its not
Mar 24 16:28:17 <halfhalo> node has nothing to do with it
Mar 24 16:30:18 <PuffTheMagic> im just saying, i dont want to use node/Socket.IO
Mar 24 16:33:42 <PuffTheMagic> wtf is enyo.instance
Mar 24 16:39:34 <PuffTheMagic> DOH
Mar 24 16:39:40 <PuffTheMagic> i think i see my issue
Mar 24 16:39:42 <PuffTheMagic> name collision
Mar 24 16:40:21 <PuffTheMagic> yay!
Mar 24 16:40:44 <stbuehler> i think enyo.instance is part of a hack that uses instances of a class as the base prototype for derived class
Mar 24 16:42:35 <PuffTheMagic> it works now
Mar 24 16:42:43 <PuffTheMagic> my kind was called WebSocket
Mar 24 16:42:55 <PuffTheMagic> which totally killed the real WebSocket
Mar 24 16:43:02 <PuffTheMagic> renamed my kind to enyo.WebSocket
Mar 24 16:43:04 <PuffTheMagic> all is good now
Mar 24 16:43:19 <stbuehler> :)
Mar 24 16:43:35 <stbuehler> perhaps you should go for a different name
Mar 24 16:44:11 <stbuehler> as many people ommit the "enyo." prefix, and they probably won't get what they expected
Mar 24 16:49:06 <PuffTheMagic> ya i suppose
**** ENDING LOGGING AT Sun Mar 25 02:59:58 2012