[eluser]breaddes[/eluser]
I know a widget actually can't have a link to methods of itself because it's just a »slave« of a controller. I only can post it back to itself and process the input like the $_POST vars. The widget must then decide for itself what to do with the input.
The problem is that I have something that is very much widget-like from it's appearance and reusabilty. View-wise it is a DIV with a collection of links. Whenever a link is clicked the view should be replaced by a matching other view. This should be kind of a intelligent partial.
This partial is like a component. It can be used in different other views depending on whether it's needed or not.
Now it's clear that there must be something more than just the partial view. If a link get's clicked where do I process that link? I mean logically it must be in the current controller because globally I don't wanna go somewhere else unless there would be a redirect to my site back.
Are there any best practise example for a situation like that? I go round in circles and can't find a way out.