[Solar-talk] Partials/Tiles/Elements/Components/Something

[Rodrigo Moraes]

On 11/5/06, Andreas Ravnestad wrote:
> Yes, from what I have been able to tell, the common opinion is that
> "fat" components are bad, and I completely agree with that. However, for
> lightweight bits and pieces I use often and at several places, it's
> perfect :-)

I like this idea, but let me tell you my only concern: If the
"component" controller extends Solar_Controller_Page, you may end with
a series of instances of this class for one single request.
Solar_Controller_Page is big, and perhaps this is a stupid performance
concern, but I would like to see the page controller as a property for
the app classes, so we can pass it along to "components" instead of
creating it over and over.

This is whole mechanism to think about, because the page controller
would require some adaptations and flags. In short words, I think it
would be a nice idea to have it set as a property for app classes,
while they extend a common class (Solar_App?) that serves as a proxy
to talk with the page controller. I know this will make no sense for
you, but at least I have tried to explain. :-P

> And thanks to Rodrigo for his hack, good stuff :)

But it was not me! :-)
I'm more and more surprised to see that many times you don't have to
hack Solar to achieve something: you only need to use the right tool
or trick (Yesterday I was surprised to discover that I can use a url
mapper without changing Solar_Controller_Front :-O).

rodrigo