<adambeynon_>
elia: yo yo. Could do it tonight. There are enough docs ready on the website as well. All the library gems might need a bump too for versioning.
<adambeynon_>
Might make everything <1.0.0 as well
<elia>
adambeynon_, sounds good
dimaursu16 has joined #opal
<adambeynon_>
elia: do you think 0.6 should have the require fixes in it?
<elia>
adambeynon_, if you mean the "real requires" answer is no
<elia>
they're still early stage
<elia>
untested and can get out in 0.7 or 1.0 (whichever comes first)
<elia>
adambeynon_, side note: for real requires we'll need a custom sprockets-free lookup system (that can use sprockets itself as an adapter)
<elia>
this is what sass does
<elia>
and we have the same problem
<elia>
also a custom cache system could sneak in
elia has quit [Ping timeout: 268 seconds]
DrShoggoth has joined #opal
elia has joined #opal
e_dub is now known as hard_knock_dub
hard_knock_dub is now known as e_dub
<e_dub>
so, I want to write Atom plugins with opal, any recommendations for the best way to do that? opal-node? set up a compile step?
elia has quit [Quit: Computer has gone to sleep.]
<ryanstout>
e_dub: a compile step wouldn't be too hard to setup
<ryanstout>
you could do it with a rake file
<e_dub>
yeah, that's probably easiest way to go. thanks
<ryanstout>
you could include opal-parser and compile on the fly also
<ryanstout>
but I think a build step is probably simpler
<ryanstout>
just curious, what are you thinking of building?
<e_dub>
Been updating this since last summer (my GSoC project) : https://github.com/edubkendo/rsense/tree/parser_port and have pretty decent autocompletion in sublime, vim and emacs now . Want to get it running on atom. Planning to finally wrap it up and get an "initial" release out
<e_dub>
soonish
<ryanstout>
e_dub: very cool. I had heard @headius talk about sense, hadn't checked it out though
elia has joined #opal
<ryanstout>
I would use it if you did it. I'm hoping atom takes off
<ryanstout>
:-)
<e_dub>
yeah, I've got some recent bugfixes i need to push that get it work with Ruby2 syntax mostly. and then there's a handful of small wins to be made in terms of making install much easier than it currently is. After that, there's some big features I want to add, but figured I could get a release out for others to use before i move on to those
<e_dub>
Next plans are to add support for reaching into integrated languages like java for JRuby and maybe using something like Tern for Opal
<ryanstout>
that would be cool
<e_dub>
And Atom makes it possible to do lost of cool things that were not in Sublime, like adding a popup tooltip with docs beside the autocomplete box
<ryanstout>
yea
<ryanstout>
I think the fact that the plugins are just github repo's will help people get started with it too
<e_dub>
yeah, i really like that so much of the functionality is implemented as plugins. a lot like redcar
<ryanstout>
I never looked at redcar, was it very good?
<ryanstout>
for me, I didn't want an editor that ran on the JVM. I know the startup time shouldn't be a big deal, but for some reason it felt wrong to have a big startup time on an editor, hehe
<e_dub>
It was a good idea, and could have been amazing but the primary force behind it fizzled out really just as it was getting good
<ryanstout>
bummer
<e_dub>
yeah. startup time was a bummer
<e_dub>
rsense is built on jruby but it uses a daemon to keep it really responsive
elia has quit [Quit: Computer has gone to sleep.]
<e_dub>
30ms or so on my machine
<ryanstout>
its funny, I use jruby for most of my stuff, I guess maybe the slow boot made me think of my eclipse java programming days, hehe
<e_dub>
no, i don't blame you. redcar had a lot of cool ideas, but the slow boot and staring at the splash screen was annoying
<ryanstout>
e_dub: just curious, what's your day job?