Mailing-List: contact dev-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tapestry development" <dev@tapestry.apache.org>
Received-SPF: pass (herse.apache.org: domain of hlship@gmail.com designates
 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=sMEgq10shFhVLOMbui+2TB9oTTvw6cR7jeUV7IbUt+tCZFY89wDSnMPaD+ieZZT/waOl49ZbqGmdm1ukoEac4fk4cPC2kSHB3RkDQU4YhWcKfvjYMCRfpoQVkUO55+a0x4XgqJ0G/7w0GLDD45ntUa0G/8hrFgf/Tf7jii3BA4s=
Message-ID: <ecd0e3310701130923h22c1da58xd18eded0a23cb518@mail.gmail.com>
Date: Sat, 13 Jan 2007 09:23:40 -0800
From: "Howard Lewis Ship" <hlship@gmail.com>
To: "Tapestry development" <dev@tapestry.apache.org>
Subject: Re: New T5 Snapshots
In-Reply-To: <D4349A38-E573-4685-8136-E5A47AA48C69@euroconsumers.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <ecd0e3310701101458od901b7eq9e3c6f53c0f68b16@mail.gmail.com>
	 <D4349A38-E573-4685-8136-E5A47AA48C69@euroconsumers.com>

We're still experimenting with the best solution for templates and
what goes in the templates.

I'm beginning to lean towards Kents proposal that everything in the
template, even inside <t:comp> be a literal unless prefixed.

In terms of location; its somewhat problematic to have the files in
the context root.  It also gives a false sense of security w.r.t. to
previewing and relative asset paths, since many pages will have a
"context" associated with them, extending the path by one or more
steps, and breaking relative URLs.  If you are using absolute URLs,
and you have Dreamweaver set up correctly, then it doesn't matter if
the files are in the context root or inside WEB-INF.

Finally, several users have gotten push-back from their operations
groups about having templates in the root where they are "visible" to
clients.  Strangely, JSPs are allowable, but not Tapestry templates.


On 1/13/07, Numa Schmeder <numa@euroconsumers.com> wrote:
> I don't understand, you said in the previous post that templates can
> be placed in the root context (that's great!) But in this mail you
> say that tap4 style templates must be in WEB-INF! Why?  Tap 4
> templates are great (in my point) and they should be also working in
> the root context.  I think most of the people will use tap 4 style
> templates, and putting everything in the root context is cleaner for
> the web developer-designer that don't have to see all kind of other
> file.
>
> Anyway good work and nice Job waiting to test Tap 4 :D
>
>
> Le 10 janv. 07 =E0 23:58, Howard Lewis Ship a =E9crit :
>
> > I've put up a new set of Tapestry 5 snapshots.
> >
> > Nothing too significant changed in tapestry-ioc.
> >
> > tapestry-core is really beginning to cook!  I've been adding more form
> > element components: PasswordField and Select to go with Checkbox,
> > TextField
> > and TextArea.
> >
> > Form components now post a bunch of different events that event
> > handler
> > methods can hook into.
> >
> > Event handler methods for forms can now return strings, links, or
> > components
> > to abort the form handling and redirect to the named page or link.
> >
> > An annoying bug related to multiple expansions on a single line of the
> > template is now fixed.
> >
> > Tapestry 4 style templates are back, with a few differences. They
> > must live
> > in the WEB-INF folder.  The default binding prefix is always
> > "prop:" whether
> > you use <t:comp> or t:id within an existing tag.
> >
> > There's now basic decoration of fields and labels, keyed off the
> > default
> > Tapestry stylesheet (that's automatically included).
> >
> > A bunch of other stuff too involved to explain.
> >
> > We're still aways from the point where I would want to unleash this
> > on the
> > unsuspecting public. I have to put in a few more features before I
> > do the
> > next screencast and start the tutorials:
> > - Application state objects
> > - Loop state management within a Form
> > - BeanForm-style behavior
> > - Implying component type based on element and attributes.
> >
> > ... and hats off to Kent Tong for diving in a building a
> > sophisticated,
> > built-in unit test framework.  It's somewhat similar to using
> > Selenium for
> > testing, but without the need to start Jetty and Selenium servers,
> > so it's
> > blindingly fast.
> >
> > --
> > 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


--=20
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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org