roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] [Commented] (ROL-2015) Add a description element to theme descriptor file (theme.xml)
Date Fri, 27 Jun 2014 10:43:25 GMT


Glen Mazza commented on ROL-2015:

Spacing is OK, it looks very good.  I prefer going without default descriptions as some themes
are just (hopefully) pretty and don't need explanation, it's gets tiring on the eyes to scan
unnecessary boilerplate.  I think we're done here, thanks.

I'm unsure why using Ajax would be "cheating" (because it's easy?), but post-5.1, I'd like
us to reduce the number of <servlet/>s we have defined in our web.xml, we're using 23
right now.  If there is a way to use Ajax while consolidating the number of servlets needed
to support it that would good, if not, to see if there are non-Ajax ways of accomplishing
the same thing for certain tasks, reducing the servlet count that way.  Too many servlets
for a web app might be code smell and a source of additional security holes.

> Add a description element to theme descriptor file (theme.xml)
> --------------------------------------------------------------
>                 Key: ROL-2015
>                 URL:
>             Project: Apache Roller
>          Issue Type: Improvement
>          Components: Themes and Macros
>    Affects Versions: 5.1
>            Reporter: Glen Mazza
>            Assignee: Greg Huber
>             Fix For: 5.1
> The theme.xml packaged with each theme already has a <preview-image/> element allowing
the user to see what the theme looks like.  Add a text description field as well, allowing
for an explanation of the theme, which will appear on the theme selection page.  This will
allow for explanations that a theme is intended for front-page aggregation, includes a planet
page, features a wide text column helpful for blogging code or narrow columns for blogging
prose, mentions the technologies (jQuery, bootstrap, etc.) that the theme uses, etc.

This message was sent by Atlassian JIRA

View raw message