Alternatively, have static configuration determine the page model names and
class correspondence.
----- Original Message -----
From: "Allen Gilliland" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 05, 2006 12:04 PM
Subject: Re: Atlas frontpage: how to specify page models for a blog?
Dave Johnson wrote:
On 6/5/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
this seems like the best mix of flexible and reasonably easy to use. my
one big suggestion here is that we not allow the admins to choose the
names for the models. i think that will only confuse people and create
a support nightmare, lets just standardize the names like you have in #1
and #2. this way the list of models is easier because it's just a list
of classnames.
We've got to get the model names from somewhere, so what you're
suggesting is a new option. I'll call it option #5:
Option #5: Add a new field to the website table called page_models, which
is editable only by Global Admins. The new field will list the additional
page models to be available to a blog in a simple format. For each model,
we list classname to be instantiatedfor the model.
<model 1 class>
<model 2 class>
<model 3 class>
Each model must implement an PageModel interface with a getName()
method so we can detrermine what name to use in the Velocity context.
yep, that sounds good to me. maybe the method name should be
getModelName() to make sure we identify what the name is describing.
-- Allen
- Dave
