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

[Karsten Dambekalns]

Hi.

On 22.04.2009 11:52 Uhr, Bastian Waidelich wrote:
> Robert Lemke wrote:
> But what if you don't have a model and a package which has only one
> purpose like the RouteTester?

Still it would be possible to name it RouteTesterController.

>> "IndexController" wouldn't really hit the nail because the controller
>> is not indexing

Exactly what I had thought when writing my original post. The 
indexAction is a different case as pointed out below - it really models 
the "index.html" part of web development.

>> 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?

Well, default can be a noun or a verb, strictly spoken, never an 
adjective. Thus the way we (at least the germans) often use it, is 
wrong. Thus I am not surprised by the differing google fight results for 
standard vs. index as well - it all depends on your cultural background :)

I just discussed this again with Robert and we will go for 
StandardController as the value FLOW3 defaults to when nothing is 
explicitly given and/or configured.

Regards,
Karsten