If you don't have a lot of view only logic (the view is just a dumb 'take this
perl data structure, convert it to a display format using default serialization
rules and send it to the response) then a thin view adaptor with
Catalyst::Model::Adaptor might be the easiest thing. If you are using
looks to me like you'd want Catalyst::Model::Adaptor + Data::iCal + an
optional very thin view that did something like:
$c->res->content_type($ical_content_type);
$c->res->body($c->stash->{calendar});
in the process method, and not much else.
The reason you don't see views for stuff
Thanks for the reply - may I ask what the model would be doing, given that
presumably it would have to go through a view in the end anyway? Because
the data itself already exists in a model, all I'm wanting to do
effectively is extract that and display it in a slightly different format,
so I'm
A View is fine but because there is a format for files and it's
natural to show/deliver content with a view.
The view is going to be very THIN though. Basically nothing but a
wrapper around what iCalendar really is which is data and therefore
the Model domain. The view will essentially be
Hi
So as part of my sports league web site, I've been looking at adding the
ability to download matches into personal calendars. It strikes me the
most obvious way to do this is with a view, something like
Catalyst::View::ICal - there doesn't seem to be anything like that around
at the moment,
