roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ROL-601) Better plugin architecture
Date Thu, 19 Dec 2013 00:46:07 GMT

    [ https://issues.apache.org/jira/browse/ROL-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852411#comment-13852411
] 

Glen Mazza commented on ROL-601:
--------------------------------

I guess what Dave is saying (or was saying, this is from 2005) is that if a user wants to
attach arbitrary meta-data to particular blog entries (any dynamic list of user-desired qualities
about the blog entry--such as where the person was while writing the blog entry, what the
person was eating when writing the blog entry, what music was playing in the background while
writing the blog entry, whether the blog entry was requested by a customer or the blogger's
boss, which product the company is trying to promote with the blog entry, etc., etc....) 
Roller should provide a database for storing the information.  I would say that's out-of-scope
today and wouldn't do much for Roller's market share -- an Excel spreadsheet or some CMS might
do the job for the relative few wanting this.  Back in 2005, Roller had several paid full-time
developers working on it, so luxuries such as these could have been looked into.

> Better plugin architecture
> --------------------------
>
>                 Key: ROL-601
>                 URL: https://issues.apache.org/jira/browse/ROL-601
>             Project: Roller
>          Issue Type: Improvement
>          Components: Page Rendering & Management, Weblog Editor
>            Reporter: David Johnson
>            Assignee: Roller Unassigned
>
> We need a better plugin interface to support assigning arbritary meta-data to entries
and to allow edit-time fix up on entries.
> We've discussed a proposal for this:
> http://www.rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_WeblogEntryPlugin



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message