> The same way I'm saying this (well, typing it) now. ECS, by your own
> statement and my prior investigation at the apache website, takes the approach
> of making you write code to generate HTML. In my opinion this approach has
> fundamental flaws in the majority of applications, e.g. when most of the page
> is static.
I never once said to use ECS in those environments. I spent a lot of time
all last week sending 2+ page emails where I was saying that it was a bad
idea to use things like ECS and Dash in those environments. It is possible,
but it isn't the best use of the technology. I'm not trying to solve all
problems, I'm simply trying to solve the web application development
problem. Maybe you don't create web applications...so, maybe this isn't the
right tool for you.
> It may have been what you were trying to say, but it's not what
> you said:
Huh? All I said is that you don't need to use it in ALL of your content. I
have never once suggested that you replace all of your content with ECS.
> You guess wrong. I looked at dash, read through your skimpy
> documentation of it, downloaded the classes and looked at them. At
> the time, I suggested you provide some documentation of what it
> actually does. You referred me to the same vague pages on your
> website. I think it's cool you're offering Dash as open source, and
> certainly I understand why you're promoting it here and in other
> forumns, but if you want to promote it, try providing better
> documentation.
The beauty of Dash is that it really isn't that complicated. It isn't some
huge application server framework. It is a simple small lightweight
framework that encapsulates things that you normally have to do by hand.
You say that it is skimpy, but what exactly is it lacking? Just because
there isn't 100 pages of documentation doesn't mean that it isn't
documented. There is definately more than enough documentation there to give
you a good overview of the entire system and how it works. The source code
is also filled with comments that describe things.
So, tell me exactly what you feel it is missing and I will be more than
willing to fill in the bits. Just telling me (after the fact) that it is
skimpy or that a page is vague is useless for the both of us. Be part of the
solution, not part of the problem.
> So you have no concept of how an HTML generation library could be
> awkward to use in combination with an HTML templating system? Life
> must be blissful for you.
Yes. I have no concept of how it would be awkward to use. I gave you an
excellent example of how it would work very very well to produce a table
from data in a database.
In the least, you can just say:
P p = new P("this is stupid")
p.toString();
instead of:
out.println ("<p>this is stupid</p>");
I'm not quite sure how that could be "awkward" in any shape or form.
Instead of spending all this time arguing with me over this stuff, why don't
you just try using it in a small hello world application for yourself? The
worst that happens is that you waste a couple hours of your time really
checking out something new and different. The best is that you might find
something that you actually like and actually saves you time and energy in
the future.
-jon
<http://www.working-dogs.com/dash/>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
