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

Robert Lemke robert at typo3.org
Wed Apr 22 11:07:42 CEST 2009


Hi Karsten,

On 21.04.2009, at 08:42, Karsten Dambekalns wrote:

> Now, looking up what "default" really means made me think we should  
> have
> used "standard" to begin with, but that would probably confuse IT
> people. So,
> * either we ban "Default" only for this case and make it
> "StandardController"
> * tell people to always use some descriptive name instead and adjust  
> routing
> * change the naming scheme for view so the full controller name used  
> in
> it, so that the above example ends up being "namespace
> F3\TYPO3CR\Admin\View\DefaultController;"
> * do the above for PHP and HTML to keep things consistent.
>
> Those are sorted by (IMHO) awkwardness from top to bottom, most  
> awkward
> coming first. I had other ideas as well, they were very weird and I
> forgot them again quickly.
>
> What do you think? Better ideas (hopefully) or at least an opinion on
> the above (better than nothing)?

I wouldn't like to have "controller" in the view namespace so we'll  
have to find
a replacement for "Default".

In general we should really try hard to avoid a default controller at  
all and therefore
the future kickstarter shouldn't create one (but rather create a  
controller based on
an important model such as the Blog).

"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.
Therefore I think that "StandardController" is more logical.

However, if other frameworks have chosen "IndexController" already and  
it turns out
to be more intuitive for most of you, that would be a reason to choose  
it as well.

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/c0d9eb22/attachment.pgp 


More information about the TYPO3-team-core-v5 mailing list