On 9/15/05, Peter Speltz <[EMAIL PROTECTED]> wrote:
> On 9/14/05, David Baird <[EMAIL PROTECTED]> wrote:
>
> > > ... and on text formatting:
> > > - readable text or HTML formatting should not be configured in Perl
> > > code, it should be in the templates, or at least overridable there. I
> > > need to correct that, automatic database introspection is OK but there
> > > needs to be a way for the template writer, not Perl programmer, to
> > > override it. So 'application_name' should be removed from the config,
> > > for example.
> >
> > I agree with your last point, config is not the place for that stuff.
> > But everything is already overridable in the templates, I'm not sure
> > what you mean by that.
> >
> > We've discussed before that it's handy, but feels theoretically wrong,
> > to put things like printable labels for columns in the model classes.
> > I've stopped thinking about Maypole's model classes as the Model in
> > MVC. I think Maypole provides the V and C of an MVC system, and that
> > Maypole's models are mostly V.
> >
>
> I think Maypole's stategy is that one person can get a quick app up
> and running. It would be easy to make a TT template to put variables
> in and have it processed in the header.
> http://www.template-toolkit.org/docs/default/FAQ/FAQ.html#How_can_I_configure_variables_on_a_per_request_basis_
>
> Also the view could pre process it :
> my $template = Template->new({
> PRE_PROCESS => [ 'config', 'header' ],
> POST_PROCESS => 'footer',
> };
>
> http://www.template-toolkit.org/docs/default/Manual/Config.html#Template_Processing_Options
>
> Then have a template "config" in the temlate root that defines the
> variables for human names and such:
>
> [% TABLES = {
> beer ={ singular = "Beer" , plural = "Beers" }
> ...
> }
> %]
>
An approach we could take to this is to distincly classify the types
of configuration variables. Heres a quick classification:
Application configuration
-- User Interface (column/table names,) Go in a template
-- Model and Maypole (required_cols, ignore_cols, all cols, base
model, uri_base, display_columns, list_columns ...) Go in $r->config
/ perl code
Model Configuration
-- ????
I can 't think of any Model configs off the bat. Anyone wondering why
display_columns is an App config rather than Model config? IMO, you
may have the same model used in different applications but different
requirements for display list columns. Really the way they are
implemented it could be either i guess.
cheers
--
pjs
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Maypole-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-devel
