[Solar-talk] Composite views

Rodrigo Moraes rodrigo.moraes at gmail.com
Fri Nov 2 19:58:50 CDT 2007


On Nov 2, 2007 10:13 PM, Paul M Jones wrote:
> Having said that, I think the overhead of another page-controller
> would be too heavy for our purposes here (don't really need another
> whole dispatch cycle with the hooks and layouts and everything).  So
> a separate widget series, where the methods do the business logic and
> then return the results of a widget view script without any layout,
> would seem like a decent approach.  (But call them from the
> controller, not the view.)
>
> Hope I'm not missing the point, and that I made sense.  :-)

No, no, you're not, that's exactly what the called "widgets" are:
lightweight controllers that fetch some data and returns a rendered
view.

Maybe this matches the idea of a composite view: the main controller
reads which widgets are set for the current page "slots", and fetches
the output from lightweight controllers to fill the slots.

So, each of these small controllers would use their own view instance?
It would be interesting to have a mechanism to send messages up to the
main controller when needed, etc. Hm, this is very interesting, thanks
very much for the feedback. I'll play with the idea.

-- rodrigo


More information about the Solar-talk mailing list