Tapestry 4.0 includes a new mechanism whereby it searches a list of packages for your page or component classes. This is used if you omit the page specification, or omit the class attribute from the page specification. So you can go a bit further without a page specification, but it's still quite recommended!
On 4/25/05, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > You're going to want the .page file. > > Unless you have such a simplistic website that you don't really need > Tapestry in the first place, you will need properties on your pages, > either to hold information that people enter in forms or to hold > information that you've passed in to the page from elsewhere to > display. You declare these in the .page file. > > Todd > > On Apr 25, 2005, at 10:18 AM, Hao Chen wrote: > > > Hi, all > > > > I am new to Tapestry and just started playing with Tapestry 3.1. I > > like defining all component attributes inside the .html file. But > > because the page class is defined inside the .page file using > > <page-specification class="...">, I cannot get rid of the .page file > > completely. So I have provide a one-line .page file for every page. > > This is really cumbersome. > > > > I wonder if there is anyway to eliminate the .page file? Can we define > > some HTML directive and put the page class information inside the > > .html file? > > > > Thanks, > > - Hao > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
