[TYPO3-team-core-v5] Problem with handling of view classes due to naming/placement scheme

[Bastian Waidelich]

Robert Lemke wrote:

> the future kickstarter shouldn't create one (but rather create a 
> controller based on
> an important model such as the Blog).

But what if you don't have a model and a package which has only one 
purpose like the RouteTester?


> "IndexController" wouldn't really hit the nail because the controller is 
> not indexing
> something or displays (only) and index. There's also no "Index" model it 
> refers to.

I agree, "index" is not the best word for it. Although in web 
development it is used as a fallback (index.html => display it when 
nothing else is specified).
Additionally the indexAction does not index anything either (not by 
default at least).


> Therefore I think that "StandardController" is more logical.

I'm not sure but I think "standard" has the meaning of "prototype", 
"basic" or "average" rather than "default". Maybe some native speaker 
can confirm this?


> However, if other frameworks have chosen "IndexController" already

it seems like at least ZF did:
http://framework.zend.com/manual/en/zend.controller.html#zend.controller.quickstart.go

and
http://www.googlefight.com/index.php?word1=IndexController&word2=DefaultController 
;)

Bastian