[01:09] czajkowski: it is on my todo for Monday morning. [06:14] nigelb: I'm using node.js to play around :) [06:15] It's pretty awesome [06:15] I just wrote a templating engine for it, with data stored in JSON. I should really update it to actually, you know, do something [08:11] duanedesign: great [08:11] paultag: go to sleep [10:12] paultag: neat [10:36] paultag: gah, now I'm installing node.js too. [15:56] czajkowski: I did :) [16:06] nigelb: I have a sever where it can be running on port 80 [16:07] nigelb: so I'm going to write something cool with nodejs, I think. I have it templating, so I need it to collaborate with something. Perhaps if I can work out the callbacks, I can make a pair-programming editor [16:07] have it auth'd, and then work off git or something. It'll clone it, filebrowse on the left, edit on the right, and let you commit and stuff [16:08] but only with local access :) [16:10] and a socket api, pretty please [17:18] paultag: something like web-based gobby? [17:18] nigelb: like google docs, but with like vi syntax or something [17:18] that's be sooooo cool ;) [17:19] paultag: node.js overall seems to be very cool [17:19] nigelb: yeah, it's a tad wonky, but I like the webserver having a state [17:19] heh [17:19] nigelb: so you can preload data, then start serving statc stuff, and re-work it on different events [17:19] nigelb: it's going to run a whole lot faster then php, imho [17:19] I've not tested it, but I have a feeling [17:19] its probably faster than most languages [17:20] Because particularly of its async loading [17:20] I've got to try client / server stuff. I think you have to vend out javascript in javascript [17:20] something about that seems dirty, I need to figure out how to do it right [17:21] What I like best about node.js is that now you only need 1 language for client and server side [17:21] which is like *awesome* [17:21] nigelb: i'm not convinced yet [17:22] nigelb: it's really awkward to do a lot of stuff [17:22] paultag: well, true. Callbacks and callbacks and more callbacks [17:22] nigelb: yeah, but if you can model it right, callbacks rock hard. [17:22] nigelb: what I don't like is that you have to smoosh it all into one file [17:22] nigelb: and that the js tree makes it hard to server actual things, like files [17:23] paultag: You'e using 2.5? [17:23] nigelb: so you can't put a css file in with the js files, and serve it on a request to that file, y'know [17:23] nigelb: I'm using git [17:23] There probably really active development [17:23] nigelb: yeah, I'm using the git head [17:23] nigelb: I have it installed to opt, and similinked in [17:23] paultag: http://transloadit.com/ [17:23] f [17:24] whops! [17:24] gnome-do's not working [17:24] I think I showed you before, its built with node.js and ffmeg and other open source stuff [17:24] nigelb: oh yes, you did [17:25] paultag: Well, if they can do something so awesome . . . [17:26] sky's the limit I'd reckon [17:27] nigelb: I'm worried about a few things. I think this is *great* as a secondary server, for tracking state ( you don't need a DB to hold "global" states ), but not great for doing the usual things [17:27] nigelb: I'm tempted to use the nodejs server as a json server, vend off php, and ajax state from node into the app [17:27] paultag: that would totally rock [17:28] nigelb: that or re-write the webserver [17:28] paultag: That makes sense from so many standpoints [17:28] nigelb: thanks :) [17:28] nigelb: I try and make sense :) [17:28] You can always fork and people might be running paultag.node.js :p [17:28] Nah, I'd be nice and send in patches [17:28] I don't have time to maintain something like that [17:28] heh [17:29] all I need to do is figure out to how barf json in javascript [17:29] it should be easy [17:30] dude, json is javascript object notation remember? [17:30] nigelb: that just means that you can take json and it's valid javascript [17:31] oh, well, use jquery then :p [17:31] nigelb: that does not mean javascript can make json, that'd be like saying that c can produce c code because it's written in c [17:31] nigelb: with nodejs ? [17:31] or at least look at jquery source to see how they barf json [17:31] true that [17:31] ah, json.org has a json.js script [17:32] damnit, I can't inline that [17:32] nodejs, you're cramping my style. Please be built in [17:32] Well, if you see jquery compressed, you'll know that anything is in-line-able [17:34] humm [17:34] nodejs has something called "JSON.stringify(" [17:34] I wonder if that'll do it [17:34] aha [17:34] g31 [17:43] nigelb: http://pastebin.com/EdrrVCrh [17:43] nigelb: that's what I just got off my netbook [17:44] nigelb: and I just got that json stuff to work. Now time to use it :) [17:48] paultag: I can't believe its just that much! [17:49] nigelb: I need to figure out how to make it smarter [17:49] that and debian needs a patch [17:50] nodejs is really out of date [17:50] to the point where that won't run [17:50] ew [17:50] ( and I knew my syntax was right ) [17:50] so I tried git and it worked flawlessly [17:50] heh [17:50] the only time i've blamed the compiler and won [17:50] I just compiled from source - the stable version [17:51] I wish there ws something like virtualenv [17:51] nigelb: I don't like running make install. I've just hacked it in [17:51] ah [17:51] nigelb: I just used bits of my old package manager to do it [19:30] wow [19:30] with autohide on unity is really starting to be awesome [19:33] jcastro, it needs an intellihide :) [20:06] Intellihide(¢∞§¶•ªºœ∑åß∂®ƒ†©\˙µΩ≈ç√∫˙∆¨^˚¬π…“æ‘« damnit! where's the TM symbol! [20:10] ™ === Pici` is now known as Pici [22:16] nisshh: yeah, some day [22:16] right now this will do the trick though [22:17] ironically, for all the drama, with autohid on it looks just like 10.10 except minus the bottom panel [22:32] jcastro, yeah, hehe