**** BEGIN LOGGING AT Tue Jan 08 02:59:59 2013
Jan 08 17:08:58 <swisstomcat_> ShiftyAxel?
Jan 08 18:52:30 <fxspec06_> enyo.mixin adds an .originator property to objects for me.
Jan 08 18:52:35 <fxspec06_> it's really bad
Jan 08 19:25:51 <fxspec06_> i've been doing it wrong. you CAN'T mixin like:
Jan 08 19:26:21 <fxspec06_> this.setMyObj({property: enyo.mixin(someobj, anotherobj)});
Jan 08 19:26:27 <fxspec06_> you HAVE to do like:
Jan 08 19:26:58 <fxspec06_> this.setMyObj(enyo.mixin({property: someobj}, {property: anotherobj}));
Jan 08 19:27:10 <fxspec06_> omg jesus that gave me headaches and back aches for AGES.
Jan 08 19:27:20 * fxspec06_ throws the towl at whomever did that
Jan 08 19:36:39 <fxspec06_> honestly that took me a very long time to find that bug, i would submit it but i'm taking abreak right now
Jan 08 19:41:17 <summatusmentis> \what does mixin do?
Jan 08 19:41:38 <fxspec06_> combines two objects into one, returning the original object
Jan 08 19:41:49 <summatusmentis> weird
Jan 08 19:41:50 <fxspec06_> but it also MODIFIES the original object as well
Jan 08 19:42:03 <fxspec06_> but, there's no way in any scenario should i see an originator
Jan 08 19:42:33 <fxspec06_> i changed all way i do it, and my problems from 6mos ago are now fixed without crap workarounds
Jan 08 19:42:52 <fxspec06_> i feel i'm right tho and enyo is wrong (for once)
Jan 08 19:44:24 <fxspec06_> mixin is great, actually.. it puts the 2nd obj into the 1st w/ priority, keeping the 1st
Jan 08 19:44:32 <fxspec06_> i use it everywhere
Jan 08 19:47:31 <_minego> I had never heard about it until I saw you complaining here. I found it in the docs, but I don't see any reason I'd start using it.
Jan 08 19:48:22 <fxspec06_> let's say you got a stock theme, and someone adds to it.. you got 2 objects w/ css properties and values
Jan 08 19:48:55 <_minego> Yeah I see it's use. I'd just probably write my own implementation so I could be sure it was behaving like I expect.
Jan 08 19:48:57 <fxspec06_> you need to have the base theme, but want to put the user's stuff over it neatly.. so you ahve to merge objects. instead of having your own fn enyo.mixin
Jan 08 19:49:44 <summatusmentis> why do you care about the originator?
Jan 08 19:50:01 <fxspec06_> because when i go to stringify it everything blows up
Jan 08 19:50:18 <_minego> So just remove the originator after calling it
Jan 08 19:50:21 <fxspec06_> and i didn't put it there, so it don't belong
Jan 08 19:50:48 <fxspec06_> that's not the right way though, it doesn't solve the problem, and it doesn't ensure it won't happen somewhere else
Jan 08 19:50:54 <fxspec06_> now i actually FOUND the problem
Jan 08 19:51:27 <_minego> Well report the bug, and then work around it until there is a proper fix.
Jan 08 19:51:49 <summatusmentis> or just assume enyo is actually right, and work-around anyway
Jan 08 19:52:10 <_minego> Well in this case you could at least make the argument that the behavior should be more clearly documented
Jan 08 19:52:25 <summatusmentis> pedantry >_>
Jan 08 19:52:42 <_minego> Naw, it may prevent someone else running into the problem.
Jan 08 19:53:22 <summatusmentis> I'm writing a parser for js objects that are saved in the DB on the server, so that I can pull out the data
Jan 08 19:53:25 <summatusmentis> it's hacky
Jan 08 19:53:56 <_minego> Stored how? As JSON?
Jan 08 19:54:13 <summatusmentis> well, so they're not strictly js objects
Jan 08 19:54:32 <summatusmentis> but one of the comma-separated fields (in a string) is a JS date string
Jan 08 19:54:54 <_minego> okay...
Jan 08 19:55:03 <summatusmentis> we expose the DB via json
Jan 08 19:55:06 <summatusmentis> so, yes, json
Jan 08 19:55:09 <summatusmentis> is the short answer
Jan 08 19:55:21 <summatusmentis> but the point is, it's hacky, and it's called PullOut.js
Jan 08 19:55:43 <summatusmentis> and, as everyone knows, the PullOut technique is mostly ineffective
Jan 08 19:56:36 <_minego> lol
Jan 08 19:57:04 <summatusmentis> _minego: basically the enyo app records a bunch of stuff, and concatenates the required data into a string, which then gets saved to the DB backend
Jan 08 19:57:33 <_minego> I don't see anything too painfully hacky about that
Jan 08 19:57:55 <summatusmentis> well, it's a one-off kind for this particular data I need right now
Jan 08 19:58:07 <summatusmentis> I really should be writing a report-generator framework
Jan 08 19:58:10 <summatusmentis> but that seems hard
Jan 08 19:59:38 <_minego> If you only have one use case, make a 1 off kind. If you have more and can make a clean generic kind do. If it is too complicated don't
Jan 08 19:59:44 <summatusmentis> we expose all our data in the DB as json objects via a REST API
Jan 08 19:59:57 <summatusmentis> right now, I don't have time for the 1-off
Jan 08 20:00:04 <summatusmentis> long-term, our users will want the generic thinger
Jan 08 20:00:17 <summatusmentis> err.. don't have time for anything but the 1-off
Jan 08 20:00:34 <summatusmentis> I kind of both love, and hate, that JS is so string based
Jan 08 20:01:05 <_minego> Well in that case the only advice I can give is to try to make the 1-off version a starting point for the generic one. Design it so it could be extended if you can, and add comments about where you'd like to extend it.
Jan 08 20:01:48 <_minego> Yeah, I agree with ya there.
Jan 08 20:01:50 <summatusmentis> it's taken me 30 mins, I'm not worried about needing to start over really
Jan 08 20:02:11 <_minego> If you won't need to start over then I'd call it a success.
Jan 08 20:03:04 <summatusmentis> success is a lie
Jan 08 20:03:22 <_minego> Ugg, I should be doing day job stuff, but my next task involves RDP'ing into a remote windows box to try to debug a bunch of code that will be thrown away in a few months. I just don't feel like it.
Jan 08 20:03:56 <summatusmentis> just leave the bug for a few months
Jan 08 20:03:59 <summatusmentis> no one will know
Jan 08 20:04:09 <summatusmentis> and if anything, you'll expedite the process of it being thrown away
Jan 08 20:04:11 <summatusmentis> >_>
Jan 08 20:04:12 <_minego> My boss will know
Jan 08 20:04:25 <_minego> It's the only thing he wants me to do today
Jan 08 20:04:44 <_minego> And there is a demo sometime in the next few weeks that will require that it works
Jan 08 20:04:56 <_minego> At least it's C
Jan 08 20:05:02 <summatusmentis> you're still demoing code that's being thrown away?
Jan 08 20:05:11 <summatusmentis> C is awful to debug, I think
Jan 08 20:05:11 <fxspec06_> so take a video of it working, and practice the timing of your fingers on the screen
Jan 08 20:05:28 <_minego> I love C
Jan 08 20:05:40 <summatusmentis> it's because you have a beard
Jan 08 20:05:48 <_minego> I can't argue with your logic
Jan 08 20:06:09 <_minego> Although, do I love C because I have a beard, or do I have a beard because I love C?
Jan 08 20:06:21 <summatusmentis> Segmentation fault.
Jan 08 20:06:23 <summatusmentis> no other error.
Jan 08 20:06:25 <_minego> haha
Jan 08 20:07:56 <summatusmentis> tangentially, I initially read that as "do I love C because I have a beard, or do I beard because I love C"
Jan 08 20:08:10 <summatusmentis> which, the idea of beard as a verb is intriguing
Jan 08 20:08:32 <_minego> Haha, I like it.
Jan 08 20:08:46 <_minego> I'm not a fan of debugging C on windows, but on most any other platform I am.
Jan 08 20:09:55 <summatusmentis> maybe it's just because gdb feels like a flaming dumpster of functionality
Jan 08 20:10:14 <_minego> I actually like gdb
Jan 08 20:10:25 <_minego> That may be just because I spend so much time in it
Jan 08 20:10:33 <_minego> I despise the visual studio debugger
Jan 08 20:10:51 <summatusmentis> some people actually like Honey Boo Boo
Jan 08 20:10:53 <summatusmentis> doesn't mean it's ok
Jan 08 20:11:11 <_minego> pfft
Jan 08 20:21:34 <_minego> Okay, a bit more coffee, then real work :/
Jan 08 20:30:16 <fxspec06_> oxymoron..
Jan 08 20:30:26 <fxspec06_> real work, LOL (jk) =P
Jan 08 20:30:42 <_minego> by "real work" I mean the kind I get paid for
Jan 08 20:36:43 <summatusmentis> is there a way to write to a file in JS?
Jan 08 20:37:10 <fxspec06_> not that i am aware of.
Jan 08 20:37:28 <_minego> Depends where it is running. In a browser or say a webOS app no. You'd need a service to do it for you.
Jan 08 20:38:02 <summatusmentis> ugh
Jan 08 20:38:03 <fxspec06_> you could use a php extention
Jan 08 20:38:05 <summatusmentis> in a browser
Jan 08 20:38:11 <summatusmentis> I just need to export this parsed stuff
Jan 08 20:39:35 <_minego> In a browser the answer is no. A (very hacky) solution I've used in the past is to have a simple module on the server that will save your data on the server, and then you can provide a link for the browser to allow it to be downloaded.
Jan 08 20:39:51 <_minego> I don't know of any way to convince the browser to save a file without sending it to the server and back.
Jan 08 20:40:23 <summatusmentis> I don't have a server really for this right now
Jan 08 20:40:44 <_minego> Then the best you can do is to display a textarea with instructions to copy/paste.
Jan 08 20:41:03 <_minego> There may be some other solution, but I don't know of any.
Jan 08 20:43:03 <summatusmentis> I'll just js console log what I need
Jan 08 20:43:22 <GodGinrai> hey, is anyone there?
Jan 08 20:43:57 <summatusmentis> yes
Jan 08 20:43:59 * fxspec06_ echo
Jan 08 20:44:26 <_minego> mostly
Jan 08 20:44:30 <GodGinrai> I'm having a problem w/ Enyo in IE8.  Even tho' I use setDisabled to disable my onyx.Button, it still fires events in IE8
Jan 08 20:44:40 <_minego> summatusmentis: If you do find a better solution for that please let me know.
Jan 08 20:44:42 <GodGinrai> it works as intended in Firefox
Jan 08 20:45:29 <summatusmentis> _minego: for right now I just copied out of the JS log
Jan 08 20:47:10 <fxspec06_> hrm
Jan 08 20:48:32 <fxspec06_> check in FF to see what changes when setDisabled is called, and check to see if IE is doing that
Jan 08 20:48:45 <_minego> GodGinrai: Does the button appear disabled like it should?
Jan 08 20:48:46 <fxspec06_> IE might not remove event or support a disabled property.. not sure
Jan 08 20:48:56 <_minego> GodGinrai: What event are you using? ontap?
Jan 08 20:50:50 <GodGinrai> Yes, it appears disabled
Jan 08 20:51:43 <GodGinrai> The IE8 on my computer has a bug where you can't pull up the dev tools, fxspec06_
Jan 08 20:51:59 <GodGinrai> So I can not check to see if IE does what it should
Jan 08 20:53:09 <_minego> GodGinrai: I just looked at the source for enyo.Button (onyx.Button is just a styled version of enyo.Button) and it looks like it checks this.disabled for the tap event, but not for any others
Jan 08 20:56:31 <GodGinrai> but shouldn't that mean that it should see that I set this.disabled to true and be aware of that?
Jan 08 20:56:59 <GodGinrai> (I use ontap for my click events)
Jan 08 20:57:29 <_minego> Well it sounds to me like you are using it correctly.
Jan 08 20:57:53 <fxspec06> button is a catch to me: i dislike it's seemingly lack of functionality and ties to the root of enyo.. but i admire it's incredible simplicity
Jan 08 20:57:57 <_minego> I would simply add this to the start of your callback: if (inSender.getDisabled()) return;
Jan 08 20:58:16 <fxspec06> what happen when you put a log for .getDisabled() in your ontap?
Jan 08 20:58:28 <GodGinrai> ooh, good idea.  I'll try that
Jan 08 20:58:46 <GodGinrai> fxspec06_: IE8 doesn't have console.log
Jan 08 20:59:42 <_minego> GodGinrai: If I recall correctly Firebug Lite should work in ie8. https://getfirebug.com/firebuglite
Jan 08 21:00:30 <GodGinrai> it does
Jan 08 21:00:42 <GodGinrai> but Firebug Lite doesn't have JS support
Jan 08 21:00:46 <GodGinrai> due to limitations
Jan 08 21:02:07 <GodGinrai> the if statement fixed it, thanks :)
Jan 08 21:02:22 <_minego> np, glad to help
Jan 08 21:02:30 <GodGinrai> Still bothers me that it didn't work normally, tho'
Jan 08 21:02:44 <GodGinrai> I should report that as a bug when I get home
Jan 08 21:03:03 <_minego> Sounds like it
Jan 09 01:52:14 * phil_bw wanders by
Jan 09 01:52:54 * ka6sox waves at phil_bw 
Jan 09 01:53:05 * phil_bw nods
Jan 09 01:57:55 * fxspec06_ waves at ka6sox and phil_bw
Jan 09 01:58:39 <ka6sox> heya fxspec06_
Jan 09 01:58:51 <phil_bw> Evenin' fxspec06_
Jan 09 02:00:41 <fxspec06_> what's happenin' gentlemen
Jan 09 02:01:04 <fxspec06_> i'm currently trying to write blackberry enyo2 backend file for neo and it's jibberish
Jan 09 02:01:49 <fxspec06_> esp coz i can't test because i think this stuff only work on BB10. but idk. meh
Jan 09 02:02:34 <phil_bw> I hate blackberry
Jan 09 02:02:54 <phil_bw> Had to port a bb app to palmos once. Nightmare
Jan 09 02:02:55 <fxspec06_> i get good sales. and webworks is super sweet for enyo.
Jan 09 02:03:12 <fxspec06_> setting up the dev environment couldn't be more back asswards
Jan 09 02:05:52 <phil_bw> Heh, try setting up a dev environment for old bb
Jan 09 02:06:22 <phil_bw> Had to install this elaborate second program just for Internet to work on the simulator
Jan 09 02:11:29 <fxspec06_> they make it so hard, i wonder if they COULD make it easier
Jan 09 02:15:51 <fxspec06_> i don't even want to do this but i have to.
Jan 09 02:16:04 <fxspec06_> the end is good, and this weekend if i submit i get $200
Jan 09 02:16:14 <fxspec06_> $100 for demo $100 for full
Jan 09 02:20:45 <phil_bw>  that's pretty good
Jan 09 02:23:28 <fxspec06_> ya, if i can get those things working
Jan 09 02:23:38 <fxspec06_> i need help but they are talking to each other over there. lol
Jan 09 02:25:05 <phil_bw> Well I need to run. Have fun with that
Jan 09 02:25:21 <fxspec06_> cool, have good one phil_bw
Jan 09 02:25:34 * phil_bw wanders off
**** ENDING LOGGING AT Wed Jan 09 02:59:59 2013