As long as we can fix the
package foo.pages.bar;
class Bar {
}
turning into /bar/ and not finding the html page bug ;)
Howard Lewis Ship wrote:
That may not make it into the initial release of Tapestry; there are
so many other concerns that are more critical!
On 6/12/07, David Peterson <[EMA
That may not make it into the initial release of Tapestry; there are
so many other concerns that are more critical!
On 6/12/07, David Peterson <[EMAIL PROTECTED]> wrote:
It's the word "view" that I'd like to get rid of because the more slashes in
your URL, the lower the page is ranked in certain
It's the word "view" that I'd like to get rid of because the more slashes in
your URL, the lower the page is ranked in certain search engines.
/article -> ArticleViewer
/admin/article/edit -> ArticleEditor
It would be nice to have the mapping strategy from URI to classname (and
back) be made plu
The current rules allow for this:
pages.view.ViewArticle is mapped to "view/article" (not "view/viewarticle").
This is very useful, since you'll likely add other options: "add/" or
"edit/" or "search/".
On 6/12/07, David Peterson <[EMAIL PROTECTED]> wrote:
I'm finding that I often want my page
I'm finding that I often want my pages to have the same names as classes in
my model.
For example, I have an Article class in my model and I want the article
viewer URL to be "/article" (with a context specifying the article
reference). Although this is possible by using fully-qualified class nam
