Dave wrote:
On 2/22/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
I'd like to continue down the road towards improving Roller's theme
support and I think the next step that needs to be taken is to create
and XML theme descriptor for themes. This will allow packaged themes to
do many more interesting things and ultimately make it possible for
themes to be more shared and imported/exported directly from weblogs.
Proposal is on this wiki ...
http://cwiki.apache.org/confluence/display/ROLLER/Proposal+Theme+XML+Descriptor
comments? this would be scheduled for addition in Roller 4.0.
I like it, but I'd like to propose that we add a contentType field to
the Template object. We need to know what content type is to be
generated by the template and we should have to rely on a a file
extension or web server setup to provide that info.
makes sense.
I would add that the only thing that kind of sucks about that is that
expecting most users to understand content types is a bit of a stretch
in my mind. So the benefit of the current solution where we just lookup
the content type based on the file extension used in the "link" value of
the template is that it keeps things simple for users.
Having to see a field marked "Content Type" with a value of "text/css"
on the template editing form for a css template may cause more problems
than it will solve. If people start to hack at it without knowing what
they are doing then they can break things.
So we may want to ask how often we think people need to create custom
templates where they need to set a custom content type which can't be
accomplished by using a file extension?
-- Allen
- Dave
