>
> > 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 can't determine what in the above paragraph you're replying to
with this line. Which makes the next paragraph nonsensical as well.
> 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 seem to bounce around a lot. I'm no longer sure what you're
claiming to have said or not said. I'm not sure I care, either. I
certainly don't care enough to dig up the messages in this thread and
recount, yet again, a point-by-point summary of the discussion.
Besides, it would probably bore the list, which we're probably already
doing. Next thread, please.
> > 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. [...]
> [...]
> You say that it is skimpy, but what exactly is it lacking? [...]
>
> 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.
Too late. I contacted you at the time, you were unresponsive, I
gave up and moved on. Life is too short to waste my time convincing
you to document your own code.
This is a good object lesson in *why* you should document your
own code; people aren't going to fight an uphill battle to figure out
code of unknown and unproven utility (unless, of course, you're a
major corporation with a large marketing & sales budget).
> > 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.
> [...irrelevant example deleted...]
> I'm not quite sure how that could be "awkward" in any shape or form.
As I said, blissful.
Steven J. Owens
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___________________________________________________________________________
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
