adambeynon changed the topic of #opal to: - Ruby runtime and library on top of Javascript | 1.0.0 is near | This channel is logged at
e_dub has joined #opal
meh` has quit [Read error: Operation timed out]
meh` has joined #opal
GitHub17 has joined #opal
<GitHub17> opal-jquery/master dfdeedc Elia Schito: Merge pull request #30 from Arcovion/master...
<GitHub17> opal-jquery/master 7119947 Arcovion: Add .get()...
GitHub17 has left #opal [#opal]
<GitHub17> opal-jquery/master b747085 Arcovion: Updated by simply exposing the methods
<GitHub17> [opal-jquery] elia pushed 3 new commits to master:
GitHub142 has joined #opal
GitHub142 has left #opal [#opal]
<GitHub142> [opal-jquery] elia closed pull request #30: .get(), .prop(), .attr() & more (master...master)
meh` has quit [Ping timeout: 246 seconds]
DouweM has quit [Ping timeout: 265 seconds]
adambeynon has joined #opal
DouweM has joined #opal
elia has joined #opal
elia has quit [Client Quit]
kludge` has quit [Ping timeout: 248 seconds]
kludge` has joined #opal
elia has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #opal
elia has quit [Ping timeout: 272 seconds]
elia has joined #opal
fkchang has joined #opal
meh` has joined #opal
adrocknaphobia has joined #opal
rapind_ has joined #opal
<rapind_> hola
rapind_ is now known as daverapin
<adambeynon> hi daverapin
<daverapin> really looking forward to using opal
<daverapin> no luck running specs or running a node server with it yet
<daverapin> couldn't find file 'core/array/allocate_spec'
<daverapin> I'll try it out again another day
<daverapin> looks awesome though. thanks for making this.
<fkchang> daverapin: specs you can run w/the right setup and rake task. I havent' tried rspec yet, but opal-spec is fairly straightforward
<fkchang> daverapin: opal-node support is broken at the moment
<adambeynon> daverapin: that looks like the rubyspecs are missing
<adambeynon> they are a git submodule
<adambeynon> try: git submodule update --init
<daverapin> that's an attempt to run the opal specs
<daverapin> form a fresh clone / bundle install
<daverapin> *from
<daverapin> there we go. my bad.
<adambeynon> :) hopefully they should all pass..
<daverapin> few failures, but no exceptions
<daverapin>, Time.hour, and Time.month if you're interested
<adambeynon> ah yeh - we're having some timezone issues in those specs :(
<daverapin> would you recommend against using opal for an angular app? seriously considering it
<adambeynon> daverapin: I havent used angular before, but, from what I can tell I think you're going to hit some big issues with it
<adambeynon> for one, all ruby methods have a `$` prefix in javascript, which means angular wont be able to use them
<adambeynon> so only instance variables can be used for properties
<daverapin> lol yeah that does seem like a big deal
DouweM has quit [Ping timeout: 240 seconds]
elia has quit [Ping timeout: 246 seconds]
<fkchang> meh`: any plans on adding bindings or observers to lissio?
nik has joined #opal
nik is now known as Guest11828
<meh`> fkchang, not really, what do you have in mind?
<fkchang> meh`: originally, I was thinking of something like ember's bindings, but looking at vienna's observable, that seems like something more flexible
<fkchang> but ultimately, I want to be able to hook up components w/something binding like and have
<fkchang> them update automatically when values change
<adambeynon> fkchang: I have some pretty useful stuff I want to merge out of one of my apps
<adambeynon> two way data bindings with formatters
<adambeynon> could be used with lissio, as well
<meh`> fkchang, I'm not familiar with them
<meh`> any examples'
<meh`> ?
<fkchang> adambeynon: sounds cool. Looking at the vienna specs for observable, it seems like it would easily be the basis for a simple bindings api in vienna
<fkchang> meh`: long story short, use bindings to hook up various components so whenever values in model objects change, things automatically get updated. It's essentially an easy way to setup observers that propagate value changes
<fkchang> this is how ember does it
<fkchang> vienna has an generic observeable module that could support this and much more
<meh`> fkchang, I see
<meh`> yeah, sounds good
<adambeynon> back later
adambeynon has quit [Quit: ["Textual IRC Client:"]]
<fkchang> meh`: yeah, so I figure if I add something like bindings and some kind of data retrieval (might be in lissio, didn't see it), then I'd pretty much have all the things I could think of off the top of my head. I might duplicate some ember tutorials to see if there's stuff I'd be missing
<meh`> fkchang, by data retrieval you mean like REST and the like?
<fkchang> yeah
<meh`> fkchang, there are two adapters
<meh`> REST and localStorage
<fkchang> ah, just need to figure out how to use it. The description for Ember Data (still beta), kind of describes what I'd be looking for ultimately "Ember Data is a library that integrates tightly with Ember.js to make it easy to retrieve records from a server, cache them for performance, save updates back to the server, and create new records on the client."
<fkchang> just need bindings then..
<meh`> fkchang, yeah, that's what the adapters do
<fkchang> meh`: so u think lissio is ready for me to mess around w/then? Is head updated?
<meh`> fkchang, yeah, it works
<meh`> you need master everything so, I think
<meh`> s/so/tho/
<fkchang> this seems like a decent next step - "Ember Data is also designed to work with streaming APIs like, Firebase, or WebSockets. You can open a socket to your server and push changes to records into the store whenever they occur."
<meh`> fkchang, that was the later plan :)
e_dub has quit [Quit: It's a hard knock life]
<fkchang> nice
Guest11828 has quit [Quit: Page closed]
daverapin has left #opal [#opal]
ryanstout has joined #opal
DouweM has joined #opal
elia has joined #opal
DrShoggoth has joined #opal
<elia> meh`, spec paths mangling is almost done…
<meh`> elia, cool
<elia> meh`, not sure if it's exactly what you asked for, but at least now's easy to move directories around
<meh`> elia, tell me how it is, so we can agree to something before you commit it
<elia> meh`, i'll do a PR anyway, but…
<elia> it's spec/cli for rspec stuff and spec/opal for the rest
<meh`> spec/cli for rspec?
<meh`> erm
<meh`> rspec or rubyspecs? or what
<meh`> ◕ ◡ ◔
<meh`> the current mri_spec is now spec/cli?
<meh`> if that's the case, fine by me
<meh`> but yeah, I'll check the PR
<elia> yep, the real difference is between what's ran with rspec (mri) and what is ran through mspc+phantom
adambeynon has joined #opal
GitHub116 has joined #opal
<GitHub116> opal/spec-paths-cleanup ec255fe Elia Schito: Cleanup rake tasks
GitHub116 has left #opal [#opal]
<GitHub116> [opal] elia created spec-paths-cleanup (+8 new commits):
<GitHub116> opal/spec-paths-cleanup 0080aeb Elia Schito: {=> spec/opal}/rubyspec
<GitHub116> opal/spec-paths-cleanup 7cc002c Elia Schito: spec/{=> opal}/corelib
travis-ci has joined #opal
<travis-ci> [travis-ci] opal/opal#1465 (spec-paths-cleanup - 284cd8b : Elia Schito): The build passed.
<travis-ci> [travis-ci] Build details :
<travis-ci> [travis-ci] Change view :^...284cd8b08b32
travis-ci has left #opal [#opal]
adambeynon has quit [Quit: Textual IRC Client:]
<elia> meh`, adam is gone :\
<elia> meh`, let me know if you have any consideration on the pr
<elia> meh`, the less it stays around the better
<meh`> elia, squash the commits in the meantime
<elia> meh`, did I left any fixup! stuff?
<meh`> still checking
<meh`> also I'd move the stuff in spec/opal just in spec/
<meh`> and put compiler, corelib and parser into spec/opal
<meh`> basically
<meh`> cd spec
<meh`> mv opal/* .
<elia> meh`, i think I know why you wanna do that, but it's no good to mix rspec and mspec stuff
<meh`> mix how?
<meh`> having spec/opal is unclear
<meh`> a lot of that stuff has nothing to do with opal itself
<elia> the two have different sets of helpers and they need to be separate "physically"
<meh`> why?
<meh`> they're already separate
<meh`> they're in different directories
<meh`> just add more paths
<elia> so that the first joe that comes around can understand what's goin on
<meh`> instead of globbing mercilessly
<elia> re-reading
<meh`> they're already different directories, if they use different spec runners it's fine
<elia> i don't like spec/opal neither
<meh`> spec/opal should have specs that are specific to opal
<meh`> so the compiler stuff
<meh`> the parser stuff
<meh`> and the corelib/stdlib stuff that is specific to opal
<elia> k, so where you would put the filters for example?
<meh`> spec/filters
<meh`> in spec/opal only compiler, corelib, parser
<meh`> then we can remove the corelib stuff that is already covered by rubyspecs
<meh`> spec/stdlib
<meh`> we'll submodule there the sl-* specs
<meh`> also rename corelib to core
<meh`> since it's opal/core now
<meh`> spec/opal/core
<elia> mumbling
GitHub133 has joined #opal
<GitHub133> opal/spec-paths-cleanup 8761188 Elia Schito: spec/opal/{corelib → core}
GitHub133 has left #opal [#opal]
<GitHub133> [opal] elia pushed 1 new commit to spec-paths-cleanup:
<meh`> everything but cli is already mspec
<meh`> and cli is in its own directory in the first place
<meh`> and when running specs it's clear it's being ran differently
<elia> the thing on which im not convinced is the bundle of rubyspec stuff
<meh`> elia, rubyspec should become spec/core
<elia> it includes: the submodule, the whitelist, the filters
<meh`> the filters will apply to library too
<elia> ok, sounds good
<elia> so spec/core/rubyspec?
<meh`> no, just spec/core
travis-ci has joined #opal
travis-ci has left #opal [#opal]
<travis-ci> [travis-ci] opal/opal#1467 (spec-paths-cleanup - 8761188 : Elia Schito): The build passed.
<travis-ci> [travis-ci] Build details :
<meh`> rubyspec now only has the core stuff
<elia> oh i see now
<meh`> spec/core is Ruby
<meh`> spec/stdlib/whatever is Ruby
<meh`> spec/opal/core is opal specific specs in the corelib
<meh`> like some break specs
<meh`> and stuff that we have to test that's implied in MRI
<elia> meh`, wait current rev of rubyspec still has stdlib
<elia> let's do this way
<meh`> elia, yes, we need to update it
<meh`> and checkout the library specs we currently run
<meh`> and it's better to do it all now
<elia> we leave the structure as it is
DrShoggoth has quit [Remote host closed the connection]
<elia> it's better to do small steps
<brixen> elia: you mean your copy of rubyspec or
<brixen> I rm'd the library specs on master
<elia> brixen, talking about the revision in the opal checkout
<brixen> ah ok
<elia> as a submodule
<brixen> nasty :)
<elia> :)
<brixen> considering releasing rubyspec as a gem
<brixen> updated about once a week
<elia> meh`, there's stuff that I'm quite sure adam uses that's not working now
<brixen> so you'd just gem update and run a command
<meh`> elia, what stuff?
<brixen> using a changing rubyspec has been a perennial pain
<elia> rake build_spec for example
ryanstout has quit [Quit: ryanstout]
ryanstout has joined #opal
<elia> meh`, let me fix that stuff first and then we'll update rubyspec and fix the structure
<meh`> ok
gest has joined #opal
gest has quit [Client Quit]
elia has quit [Quit: Computer has gone to sleep.]