[ajug-members] Can anyone recommend a book for learningRubyonRails?

[Rick]

On Wed, Jul 30, 2008 at 3:50 PM, Les Hazlewood <les at hazlewood.com> wrote:
>  t I think these frameworks and those like them totally miss the mark.
>
> Component oriented design is much more in line with Object-Orientation.
> Frameworks that cater to component-oriented design, re-use, OO, etc, etc.
> *That's* what people should be looking at.  Frameworks like Wicket, GWT,
> Tapestry 5, and my current favorite, Click.

To emphatically state (with asterisks) *that's* what people should be
looking it is completely wrong. I'd maybe concede that's what people
*should consider* looking at. I'm so tired of this haughty "My
framework is the killer OO framework and it allows for reuse, yada
yada."  I 'used' to think the way you did, then reality hit in after
coding a bazillion web applications. How often do you really reuse web
application components? Sure you might reuse a display widget but all
the latest "fast and easy" frameworks handle that already with out the
bloat of having to code a web app like a Swing app.  Sure enjoy it if
you want, but I want productivity these days. And yes I've used Wicket
-  been involved in the community even. It's a very nice framework if
you think component based frameworks are the pinnacle of coolness. I
still think it's typically 100% overkill solution for 95% of the web
applications developers will need to code.

I haven't used Click but took a quick look at some of the example
code. Whenever I see this in a Java web app, I'm turned off. If I'm
going to build my app with true event handlers and components I'd
rather spend the time with Flex, otherwise I'm happy with ajax events.

   public void onInit() {
        form = new Form("form");
        form.add(new HiddenField("id", Integer.class));
        form.add(new TextField("firstName"));
        form.add(new TextField("lastName"));
        Select stateSelect = new Select("state");
        populateStates(stateSelect);
        form.add(stateSelect);
        form.add(new DateTextField("birthDate"));
        form.add(new Submit("submit", this, "onSubmit"));
        addControl(form);
    }

The only place I see the true benefit of a component based web
framework is if you anticipate that your large company is going to
truly need some java based web components that you will need to use in
DIFFERENT web applications.  The amount of times this comes up in
reality I'm sure is extremely slim and I'd like some true real
examples of the "reuse" part that you mention above.  I've had to
expose services within companies, but never the actual web components
themselves. (I'm sure it comes up some, but it's certainly not common
enough for me to hinge my framework choice upon it.)