These are chat archives for opal/opal
btw @JikkuJose I don't see anything wrong with that code... I suspect its because Element is just a thin wrapper on Jquery and hence does not work. But I'm not sure.
Folks: Is there any known problem with circular requires? I have several classes that end up with a circular dependency.
On another note, I'm at an interesting place where working on opal-playground reinforces 2 'not particularly known/understood ideas' I want to pitch for opal, namely
That being said, it's potentially a long rambling blog post I don't know I have time to write while it's fresh in my brain
@fkchange - I am coming rapidly to the same conclusion working with opal-react (react.rb)... Current state of react.rb that my team is using is the same idea. behavior and markup are in together in small simple classes (have not really pushed my team to bring the style in, but I think that's next.)
And like wise its pretty obvious you could have a great development environment where you developed these classes in a very interactive environment.
I am imaging typing things like:
and having that fire up a window with the Navbar code. When you save it fires up a react rerender of the component...
@fkchang the only thing I might change about how lissio does it is to change this
css do rule '.title' do font size: 32.px end rule '.subtitle' do font size: 18.px, style: :italic end end
rule '.title' do font size: 32.px end
as the css seems redundant.
include React::Componentand then all the generator methods are available within that class.
@fkchang - not sure, but she is coming from Seattle so I am guessing pretty late... let me see if I can get txt her now.
but I think we can assume anytime before 5:00 PM EDT
include PIXI::BaseI can get rid of the x-strings in all the classes. Then i can start to implement some metaprogramming stuff like method missing. I couldn't get the x-string to interpolate without doing it like that