16:18 <e_dub> elia, started working on a wrapper for the Atom api over the weekend. Have all of the global `atom` object wrapped pretty nicely: https://gist.github.com/edubkendo/9602432#file-atom-rb . Have not yet figured out the best way to distribute it. Putting it in a gem means it gets used like other opal libraries do, which is good. I guess I could compile it and put it in npm and it could be used that way. Best would be we get

16:18 <e_dub> rubygems running on opal-node I think, but that's probably a huge undertaking .

16:24 <elia> e_dub, great!

16:24 <elia> e_dub, brb, with considerations about opal-gems

16:24 <e_dub> thanks

16:26 <meh`> e_dub, #initialize could be completely removed

16:27 <meh`> e_dub, alias_native :clipboard

16:27 <meh`> e_dub, alias_native :clipboard=

16:27 <e_dub> Ok, but then where do I set @native to make all the sweet native magic work?

16:28 <meh`> e_dub, `include Native` already does it for you

16:28 <meh`> just

16:28 <meh`> initialize becomes super(`atom`)

16:29 <e_dub> oh... /me smacks forehead

16:29 <e_dub> I'm sure there's plenty of really naive code in there. appreciate the reccomendations.

16:30 <meh`> e_dub, most of the code can be replaced with alias_native

16:30 <meh`> focus for instance

16:30 <meh`> alias_native :focus

16:30 <meh`> current_window

16:30 <meh`> alias_native :current_window, :getCurrentWindow

16:30 <meh`> etc

16:31 <meh`> also there are a bunch of inconsistencies if you haven't noticed

16:31 <meh`> sometimes you use atom.

16:31 <meh`> sometimes you use #@native

16:35 <e_dub> yeah, sorry can't remember exactly why but for some reason I thought I needed to do them that way.

16:37 <e_dub> really helpful, I'll clean this up before packaging it

16:46 <meh`> e_dub, I'm going to add #native_reader #native_writer and #native_accessor later

16:46 <meh`> so you don't have to add a thousand alias_native for accessors

16:47 <e_dub> that will be really awesome

16:56 <elia> e_dub, hackish way to get gems in opal-node could be to downlaod and unzip them and search for a lib/opal dir and add it to the load_path

16:57 <elia> e_dub, what's your current editor btw?

16:57 <e_dub> mostly sublime and vim in the terminal

16:58 <elia> k, bc I was working on a port of textmate stuff to atom

16:58 <e_dub> i saw, I was wondering where you were going with that. hard to tell from the description of "makes your life hard" ;P

16:58 <e_dub> but textmate has a lot of cool stuff

16:59 <e_dub> rmate, for instance

16:59 <elia> lol, yes, atom makes my life hard when I dare to use it

16:59 <e_dub> lol

16:59 <elia> the first missing feat for me is favorites

17:00 <elia> tm has this open faves that allows you to point to a dir and it considers all of the subdirs as projects

17:00 <e_dub> yeah, I have rsense working pretty well in sublime and now I can't live without it so I can't switch until I get it hooked up in atom

17:00 <elia> so I'm working on that

17:00 <e_dub> oh thats a cool idea

17:00 <e_dub> i have basically three dirs you could treat exactly like that

17:01 <elia> yeah, me too (2 dirs in my case)

17:02 <elia> (besides after reading about your addiction to rsense I'm wondering if there's a tmbundle for it)

17:03 <e_dub> dunno. I've made massive updates to it in this branch though https://github.com/edubkendo/rsense/tree/parser_port

17:03 <e_dub> it had been sitting untouched for a very long time

17:05 <e_dub> but with my changes, its currently even more of a bitch to get installed . Next step on it is turning it into something you can just say, "gem install rsense"

17:08 <elia> e_dub, that would be helpfu

17:08 <elia> *l

17:09 <elia> e_dub, found an rsense tmbundle: https://github.com/eandrejko/RSense.tmbundle/blob/master/Support/lib/rsense_completions.rb

17:10 <e_dub> because it has a dependency on java and jruby, it takes a bit of slick work with Spoon to make it work like that, but redcar and processing have both done something very similar to what I have in mind so its definitely doable

17:11 <elia> e_dub, so it needs to be started in bg, to have bearable perf, because jruby, right?

17:12 <e_dub> exactly, and has to use the jruby jars gem so you can install it with mri or whatever

17:12 <meh`> I still would have called it enola-mate

17:14 <GitHub42> [opal] meh pushed 1 new commit to master: http://git.io/3cYRpQ

17:14 <GitHub42> opal/master d9989fc meh: Add #native_reader, #native_writer and #native_accessor

17:14 <e_dub> elia its extremely fast now, once you get it started but startup time would make it unusable crap if it was actually firing the process up cold each time you needed autocomplete or to find a method definition

17:19 <elia> meh`, lol, was hoping for some italian pearl, btw enola-mate is still the only candidate (excluding atom-mate)

17:23 <travis-ci> [travis-ci] Build details : http://travis-ci.org/opal/opal/builds/20953935

17:23 <travis-ci> [travis-ci] opal/opal#1755 (master - d9989fc : meh): The build passed.

17:23 <travis-ci> [travis-ci] Change view : https://github.com/opal/opal/compare/8ae7056a68df...d9989fcd4ae8

17:30 <travis-ci> [travis-ci] Build details : http://travis-ci.org/opal/opal/builds/20953935

17:30 <travis-ci> [travis-ci] Change view : https://github.com/opal/opal/compare/8ae7056a68df...d9989fcd4ae8

17:30 <travis-ci> [travis-ci] opal/opal#1755 (master - d9989fc : meh): The build passed.

17:55 <meh`> e_dub, you can now just s/attr(_accesssor)/native\1/

17:56 <e_dub> word

17:56 <meh`> and replace the initialize content with super(`atom`)

17:56 <meh`> and most methods with alias_native

17:56 <meh`> I really need to write some documentation on how to use native efficiently

18:19 <adambeynon> e_dub: does atom just use npm packages then?

18:22 <e_dub> adambeynon it has a packagemanager apm built on top of npm. every atom plugin is an npm package, and has a package.json for installing dependencies. I'm not sure what apm adds on top, but its got 1 up on most other editor package managers (ala sublime text) because you can use other people's plugins as dependencies in your own.

18:23 <e_dub> and easily require node packages as dependencies

18:24 <adambeynon> e_dub: interesting. still looking towards making opal work nicely with bower/npm for general use as well

18:27 <e_dub> adambeynon yeah, kind of liking the idea of opal packages all up in npm and on rubygems... rubyify all the things

23:16 <elia> e_dub, http://cl.ly/image/3V152M2Q2f34

23:17 <elia> my faves dir

23:17 <elia> http://cl.ly/image/1k2m1Q0b3y1h

23:40 <e_dub> nice elia, beat me to it ;P pretty awesome though.

23:40 <elia> still needs events management

23:40 <elia> lol btw

23:41 <elia> hope it helps also

23:41 <elia> e_dub, also checkout this embryo stuff

23:41 <e_dub> embryo?

23:41 <elia> https://github.com/opal/opal-node/blob/master/lib/opal_node_gem.rb

23:42 <e_dub> ah right

23:42 <elia> link-search-delay

23:42 <elia> just stubbing stuff out

23:42 <elia> but I think it could work

23:43 <e_dub> tried using it to install and use anything yet?

23:43 <elia> no, of course lol

23:43 <e_dub> lol

23:44 <elia> in theory it works for installing, still misses gem activation stuff, and dependency

23:44 <elia> management

23:44 <e_dub> that last one is the hard part

23:44 <elia> but could come really handy I think…

23:44 <e_dub> it might actually be easier to implement enough ruby to run the real rubygems than to implement dependency management

23:45 <elia> yeah, in fact I could leave it out altogether

23:45 <elia> e_dub, agree, only problem is that the File/Dir/HTTP stuff are totally under-developed

23:46 <elia> but once they're ready will probably be almost straightforward