That's purrty ;)

I'll take a look at this document later today and get back if any immediate
thoughts come up wrt different rendering schemes / etc...

On 9/5/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:

Things are beginning to come together.  Just added an @Inject annotation
that allows injection directly into fields.  More to go on that front (in
many cases, Tapestry will be able to deduce what to invoke based on either
the field name or the field type).

Also, I've been writing as much documentation as I can, as I go.

Here's a very important overview on component rendering:

http://tapestry.apache.org/tapestry5/guide/rendering.html

I haven't documented my thoughts on mixins yet, but the idea is that
mixins
will contribute in additional render phase methods.  We may need even more
render phases to properly support this.

--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com




--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

Reply via email to