<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.day, 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>
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 socket.io, 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