[Mortar Issues] Issue 106 in mortar: Distinct treatment of "directory-type" location models

[mor...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 106 by charlequin: Distinct treatment of "directory-type"
location models
http://code.google.com/p/mortar/issues/detail?id=106

Some location model types (like Site, Blog, Directory, etc.) function more
like containers than content -- they generally don't have a "content"
field (and therefore redirect to a "default" content model underneath
rather than display on their own), they have specific model types they can
contain as children, etc.

To better support treating these types as mechanically distinct, a static
flag along the lines of "$isContainer" should be added, so that several
distinct features can be added that, when enabled, will apply only to
container-type models:

* Automatic aliasing for display of the "default" model, if present, at
the container's URL rather than its own.
* Use of directory-style URLs rather than file-type URLs (so that you
don't have situations like site.com/blog/entry-1.html but site.com/
blog.html)
* A Location class static method that returns a Location's "container
head," i.e. the last container at or above its location (this could be
used as a parameter for templates so that both site.com/blog and site.com/
blog/entry-1.html would use blog/ as the base for dynamic navigation tags.)

--
You received this message because you are subscribed to the Google Groups "Mortar Issues" group.
To post to this group, send email to mortar...@googlegroups.com.
To unsubscribe from this group, send email to mortar-issue...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mortar-issues?hl=en.