On 9/22/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> And that ASP.NET component approach relies on massive IDE and backend
> support. I wonder how to encapsulate one component into another with
> JSF or ASP.NET. Visual tools help to drag the component on the screen

Hmmm, I wouldn't say "rely". Anders came up with a well designed
framework. Inspired, even. The marketing geeks do manage to hide the
best bits behind the IDE, but the framework works well for hand coders
too. Actually, I think it works better, since if you write your own
code, you can take advantage of OOP features the IDE doesn't expose.

I like to think of ASPX as a thoughtful framework with rudimentary
coding examples. Like Yin and Yan,  JSP is a rudimentary framework
with thoughtful coding examples. :)

Of course, JSF changes things for JSP, just as ASPX changed things for ASP.

> When AmiPro 3.0 allowed to put a table inside a table, this
> was considered a huge achievement ;-) On the other hand, how many
> people used it? Struts Classic is still "good enough" for me, but I
> would agree that writing Struts apps is kinda like coding HTML in a
> Notepad. The result can be good but takes quite some time.

Yes, Struts Classic is way good enough, and we're continuing to make
it better. We're trudging along with Struts 1.3.x, just as we have
trudged along with every other release these past five years.

The big question with either/or is "getting there from here". A
prudent Struts Classic product manager is not going to want to throw
away perfectly good applications that cost  thousands of work hours.
Struts Shale might be a better way to write new applications, but,
today, most of us are spending our time on the applications we're
already written.

Eventually, I'm sure we'll come with relatively painless ways to
migrate an application to newer technology. Or, better yet, ways to
refactor our application layer so that presentation layers are easier
to change. But until then, we trudge. :)

-- HTH, Ted.
http://www.husted.com/poe/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to