On 12/10/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I'm thinking about a custom JavaDoc doclet to generate component
documentation, since most of what you need to document is private.
Alternately, perhaps Tapestry code JavaDoc should just include privates as
well as everything else?
I wo
Hey, if it works for you.
description vs. alt : Early Tapestry 1.0 established the precendent of
giving "Java-ish" aliases to common HTML attributes. A mistake, in my
opinion, since it gained little, obscured some, and requires that much more
documentation.
In other words, I wouldn't inlcude a
Well, didn't end writer. Also "public'ed" methods --
@BeginRender
void renderImageTag (MarkupWriter writer)
{
writer.element ("img",
"src",
_imageAsset.getResource().getPath(),
"alt", _description
I needed one, so I took a shot at it. Flame away! :) Package
declaration deliberately left out:
import java.io.IOException;
import org.apache.tapestry.Asset;
import org.apache.tapestry.MarkupWriter;
import org.apache.tapestry.annotations.BeginRender;
import org.apache.tapestry.annotations.Compo
