You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2007/01/25 01:18:28 UTC
Is the HTML extension right?
I've been thinking again about the extension for Tapestry templates.
Although T5 again finds the deepest rut in plain old HTML (or XHTML),
I'm sure that SVG or various other markup-related formats are
possible. Possibly a Tapestry page could even be a dynamic CSS file.
So I've been thinking that the template files should get away from a
".html" extension and settle on something Tapestry specific (rather
than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server
Page :-) ), ".tap", etc.
The other question concerns recognizing render requests in URLs.
Render requests look like:
http://...//folder/Page.html
or
http://..//folder/Page.html/context0/context1/context2
The folder/ part is optonal (and may be a number of folders).
The context values are related to the page's passivate and activate
requests (the thematic follow on to T4's external service).
Once I implement the case-insensitive class search feature, I may be
able to reduce the render URL to:
http://...//folder/page
http://..//folder/page/context0/context1/context2
Which I kind of like. In other words, the point where the page name
ends and the context begins will be determined based on the available
set of pages (in folders).
Meanwhile, action URLs are a lot easier. Currently they are:
http://../folder/Page.action/id-path/context
Note that the period becomes an easy way to recognize the end of the
page name and the start of the action name.
In the short term, I'm thinking of changing this to:
http://../folder/Page.id-path.action/context
... and of course, the coming case-insentivity will apply here as well
(at least to the page name portion).
Thoughts?
--
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
Re: Is the HTML extension right?
Posted by Cyrille37 <cy...@gmail.com>.
Kent Tong a écrit :
> Kent Tong <kent <at> cpttm.org.mo> writes:
>
>
>> Using some unknown extension will prevent some HTML editors from
>> listing the files in the Open File dialog and thus creates
>> inconvenience in editing or previewing. I'd suggest a service
>> configuration listing those extensions that are to be tried
>> when looking for the template. By default the list should
>> include: .html, .htm, .wml, .svg.
>>
>
> I think along with each extension, a content-type should be specified
> like:
>
> .html => text/html
> .htm => text/html
> .wml => text/vnd.wap.wml
> .svg => image/svg+xml
>
Nice.
Like that each one can choose its preferred extensions.
cyrille
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Is the HTML extension right?
Posted by Kent Tong <ke...@cpttm.org.mo>.
Kent Tong <kent <at> cpttm.org.mo> writes:
> Using some unknown extension will prevent some HTML editors from
> listing the files in the Open File dialog and thus creates
> inconvenience in editing or previewing. I'd suggest a service
> configuration listing those extensions that are to be tried
> when looking for the template. By default the list should
> include: .html, .htm, .wml, .svg.
I think along with each extension, a content-type should be specified
like:
.html => text/html
.htm => text/html
.wml => text/vnd.wap.wml
.svg => image/svg+xml
--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Is the HTML extension right?
Posted by Kent Tong <ke...@cpttm.org.mo>.
Howard Lewis Ship <hlship <at> gmail.com> writes:
> So I've been thinking that the template files should get away from a
> ".html" extension and settle on something Tapestry specific (rather
> than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server
> Page ), ".tap", etc.
Using some unknown extension will prevent some HTML editors from
listing the files in the Open File dialog and thus creates
inconvenience in editing or previewing. I'd suggest a service
configuration listing those extensions that are to be tried
when looking for the template. By default the list should
include: .html, .htm, .wml, .svg.
> http://...//folder/page
> http://..//folder/page/context0/context1/context2
>
> Which I kind of like. In other words, the point where the page name
> ends and the context begins will be determined based on the available
> set of pages (in folders).
Then we have to make sure if we have a page P1, then we are
prohibited from having a folder named P1, otherwise we won't
be able to tell
http://...//folder/P1/P2
is referring to P2 inside folder P1 or just page P1 with context=P2.
--
Kent Tong
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Is the HTML extension right?
Posted by Cyrille37 <cy...@gmail.com>.
Howard Lewis Ship a écrit :
> I've been thinking again about the extension for Tapestry templates.
>
> Although T5 again finds the deepest rut in plain old HTML (or XHTML),
> I'm sure that SVG or various other markup-related formats are
> possible. Possibly a Tapestry page could even be a dynamic CSS file.
>
> So I've been thinking that the template files should get away from a
> ".html" extension and settle on something Tapestry specific (rather
> than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server
> Page :-) ), ".tap", etc.
Hello,
I think we need differents extensions for differents template content
to help at design time.
For example *.htmlt for html and xhtml, *.xmlt for xml, *.svgt for svg ...
We often could tell to editors softwares and/or operating system to
recognize an unknown extension as a known extension.
I could not imagine to work with ONE extension for different contents.
If there is only one extension for different content, what is the
extension usage ?
Regards,
Cyrille
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
RE: Is the HTML extension right?
Posted by Mark Stang <ms...@pingidentity.com>.
THTML
The HTML doesn't necessarily reference a page. Whereas, a JSP is pretty often a whole page. How about something at the component level.
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Wed 1/24/2007 5:18 PM
To: Tapestry development
Subject: Is the HTML extension right?
I've been thinking again about the extension for Tapestry templates.
Although T5 again finds the deepest rut in plain old HTML (or XHTML),
I'm sure that SVG or various other markup-related formats are
possible. Possibly a Tapestry page could even be a dynamic CSS file.
So I've been thinking that the template files should get away from a
".html" extension and settle on something Tapestry specific (rather
than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server
Page :-) ), ".tap", etc.
The other question concerns recognizing render requests in URLs.
Render requests look like:
http://...//folder/Page.html
or
http://..//folder/Page.html/context0/context1/context2
The folder/ part is optonal (and may be a number of folders).
The context values are related to the page's passivate and activate
requests (the thematic follow on to T4's external service).
Once I implement the case-insensitive class search feature, I may be
able to reduce the render URL to:
http://...//folder/page
http://..//folder/page/context0/context1/context2
Which I kind of like. In other words, the point where the page name
ends and the context begins will be determined based on the available
set of pages (in folders).
Meanwhile, action URLs are a lot easier. Currently they are:
http://../folder/Page.action/id-path/context
Note that the period becomes an easy way to recognize the end of the
page name and the start of the action name.
In the short term, I'm thinking of changing this to:
http://../folder/Page.id-path.action/context
... and of course, the coming case-insentivity will apply here as well
(at least to the page name portion).
Thoughts?
--
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