From: Joao Pedrosa <joaopedrosa@...>
Date: 2005-02-17T00:13:32+09:00
Subject: Re: Wee web-framework. It's great!

Hi,

I think it's important to say that the dynamic nature of Ruby
contributes to a nice development environment for Wee, that is,
whenever we are editing one of the components, and we save it, Wee
tries to reload it. If it had to be compiled it would slow this cycle
a little bit. And worse, because the compiler would complain at the
first sign of incorrectness, making errors appear when we surely new
that the component was not ready yet for compilation. Behind the
scenes, Wee remaps methods and creates components only when it's
necessary (time saving feature!)

It makes it appear that I'm editing an HTML and not a Ruby file.
That's it! Lovely.

Actually, it has less to do with editing an HTML and more with
creating the business logic of our application. The HTML is generated
automagically for us.

Look at this:

r.text_input.callback{|v| do_something_with v}.value(@original_value)

That's all that's needed to create the INPUT TYPE=TEXT object and at
the same time fill it with the default value and save its returning
value.

Add a submit button to it and you have your FORM.

r.submit_button.callback{save_edition}.value('Save Edition')

That's how everything is created, generally. There is more to it,
because it needs to support the simple and the complex, so it
"scales."

I hope you will give Wee a try. No, not many web-frameworks that work like this.

Cheers,
Joao