Kevin Connor:
> $.02 or so.
>
> I checked out Maypole exactly because it used TT and CDBI. I don't want
> to move away from those technologies or even abstract away from them.
> Frameworks are often unnecessarily abstract such that it's hard to
> figure out where the rubber hits the road. It's difficult enough to
> figure out how a column gets rendered as html or which columns get
> displayed or why no data is retrieved in a query.
TT2 and CDBI are still the default.
But now it's simple to use alternatives.
For example imagine you want a REST interface.
Just add this to your maypole.yaml
views:
- name: REST
base: REST::YAML
and this to your controller or additional_data
$r->view('rest') if $r->params->{rest};
And you have a working REST service using a YAML serializer.
(Maypole::View::REST::YAML does not yet exist, but would just serialize
$r->objects and/or $r->trunk to $r->output)
>
> As far as the default templates go, I found them immensely useful as a
> reference implementation. I don't think I would've gotten anywhere
> without them. Shipping without them would have been a bad idea IMHO.
> They're great for testing, demos, and learning.
>
Wouldn't it be great to have multiple of those demos, and be able to
remove those demos once you're used to Maypole?
> I'm not sold on the YAML configuration idea. I'd rather work with perl
> modules and templates.
>
Thats the best thing, if you don't like it you don't have to use it.
The YAML configuration is just a Plugin.
$r->config->views([{ name => 'REST', base => 'REST::YAML' }]);
sebastian
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT