adambeynon

5 ms·

1.
by adambeynon 12y ago
(Opal developer here). When it comes to debugging, I just use the standard chrome dev tools with source maps. Variables and properties on objects all compile using their ruby names, so viewing local vars and ivars in the debugger is easy. I
2.
by adambeynon 12y ago
Various projects. Two recent ones are a POS system running on the iPad. The app is wrapped using Cordova for native scanner/receipt printer access, but the rest is built in Opal with a Sinatra backend. So lots of client models, lots of
3.
by adambeynon 12y ago
The example in this post is definitely a bad example of inline js in Opal. This is better handled by the `Native` bridge class, or writing a wrapper for it. On the other hand, being able to drop down to native javascript anytime you like is
4.
by adambeynon 12y ago
Opal creator here. Debugging in Opal is no problem at all with source maps. I only need to look at generated code when Im working on improving the compiler/fixing bugs. Developing end apps always results in using the chrome debugger st
5.
by adambeynon 13y ago
opal is very much still alive: http://opalrb.org Most of the work in the recent weeks has been improving the ruby <=> js bridge so that calling js methods/functions from ruby is possible.
6.
by adambeynon 14y ago
Opal does support method_missing, it's just off by default, i.e. opt-in.
7.
by adambeynon 15y ago
Docs are definitely being worked on, kinda the top priority now that the language and runtime are pretty stable.
8.
by adambeynon 15y ago
Im using it for an internal project. There is an associated `vienna` gem, that is for building rich web apps (think sproutcore, cappuccino). It is not open source yet, but will be once the project its been written for is finished.