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

[Robert Lemke]

Hi Bastian,

On 22.04.2009, at 11:52, Bastian Waidelich 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?

that's an exception - than the standard controller should be generated.
We'll have to distinguish between "resource controllers" and "service  
controllers".

>> "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).

The index action is the former "listAction" and therefore should -
most of the time - be used to list things. It should be possible
to configure the default action (if that's not already possible)
because then a controller could defined that the "displayStuffAction"
is default.

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

see:

http://www.googlefight.com/index.php?lang=en_GB&word1=IndexController&word2=StandardController

Cheers,
robert

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.netfielders.de/pipermail/typo3-team-core-v5/attachments/20090422/e4a03f7b/attachment.pgp