@Fet:
You are correct. Here, I’m assuming you’re using Javascripts for most of the actions you’re writing GUIs for, so the Javascrips would be different anyways. You could, for example, use the view.yml to compound different Javascripts to form the GUI, if the GUI itself is modular and can be assembled like that. That way, you could have files assembled by the view.yml file and not have to worry about it neither in the action nor the template itself.

public function executeSomeRichGuiAction() {
$response = $this->getResponse();
$response->addJavaScript(’some_rich_gui’);
}

Okay, so we’re not bloating the view template. Excellent. One problem though - the model shouldn’t contain display logic. Ouch. Back to square one.

that would be the controller not the model you’re adding that to, no?

even still, its ugly

About your javascript file organization — such convention would probably lead to duplication on the file level or (as a means of avoiding that) on the code level. Or did I get something wrong?