From robert at typo3.org  Fri Apr  3 22:19:11 2009
From: robert at typo3.org (Robert Lemke)
Date: Fri, 3 Apr 2009 22:19:11 +0200
Subject: [TYPO3-team-core-v5] FYI: New profiling tool by Facebook
Message-ID: <mailman.1883.1238789966.20378.typo3-team-core-v5@lists.netfielders.de>

http://mirror.facebook.com/facebook/xhprof/

Cheers,
robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: Signierter Teil der Nachricht
Url : http://lists.netfielders.de/pipermail/typo3-team-core-v5/attachments/20090403/15aadcf2/attachment.pgp 

From bastian at typo3.org  Sun Apr  5 19:02:07 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Sun, 05 Apr 2009 19:02:07 +0200
Subject: [TYPO3-team-core-v5]  RFC: TagBuilder
Message-ID: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>

Hi everybody,

Whenever we need to create HTML (or XML) tags from PHP (e.g. in the 
tag-based view helpers for Fluid) we end up concatenating long strings 
like this:

return '<a href="' . $uri . '" ' . $this->renderTagAttributes() . '>' . 
$this->renderChildren() . '</a>';

This is not very readable and very error-prone.
I think, it would be nice, to have some kind of Tag-builder, so that you 
could write s.th. like:*

$tag = new Tag('a');
$tag->addAttribute('href', $uri);
$tag->addAttributes($this->tagAttributes());
$tag->setContent($this->renderChildren());
return $tag->render();

I think that could be a neat little class for TYPO3 v4 _and_ FLOW3.
What do you think,
Useful?
Where to put this class and how to name it?

All the best and have a great week!
Bastian

* In the case of Fluids tag-based View helpers the base class could even 
create the tag and you'd only need to write:

$this->tag->addAttribute('href', $uri);

From bastian at typo3.org  Sun Apr  5 19:03:52 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Sun, 05 Apr 2009 19:03:52 +0200
Subject: [TYPO3-team-core-v5] RFC: TagBuilder
In-Reply-To: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1238951045.5339.typo3-team-core-v5@lists.netfielders.de>

oops, didn't mean to post this to the core list. But as it is a public 
list, it won't get lost I guess..

Bastian

From masi-no at spam-typo3.org  Sun Apr  5 20:50:39 2009
From: masi-no at spam-typo3.org (Martin Kutschker)
Date: Sun, 05 Apr 2009 20:50:39 +0200
Subject: [TYPO3-team-core-v5] RFC: TagBuilder
In-Reply-To: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1238957436.3271.typo3-team-core-v5@lists.netfielders.de>

Bastian Waidelich schrieb:
> Hi everybody,
> 
> Whenever we need to create HTML (or XML) tags from PHP (e.g. in the
> tag-based view helpers for Fluid) we end up concatenating long strings
> like this:
> 
> return '<a href="' . $uri . '" ' . $this->renderTagAttributes() . '>' .
> $this->renderChildren() . '</a>';
> 
> This is not very readable and very error-prone.
> I think, it would be nice, to have some kind of Tag-builder, so that you
> could write s.th. like:*
> 
> $tag = new Tag('a');
> $tag->addAttribute('href', $uri);
> $tag->addAttributes($this->tagAttributes());
> $tag->setContent($this->renderChildren());
> return $tag->render();
> 
> I think that could be a neat little class for TYPO3 v4 _and_ FLOW3.
> What do you think,
> Useful?

Cumbersome.

While I agree that long lists of tags with many attributes get tiresome
written in the way you mentioned, I don't think you solve the problem
with your solution. I cannot imagine that I would like to call 5
functions just to create a single tag.

I know that in the TYPO3 world the double quote is shunned but I started
to use double quotes strings and HEREDOC more frequently. If you you use
the {$var} syntax with an editor that is able to hilight the variable
parts of a string this is best in terms of readability.

I'm sorry to say, but also in this respect I see no improvement by your
suggestion.

Masi

From bastian at typo3.org  Sun Apr  5 22:09:51 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Sun, 05 Apr 2009 22:09:51 +0200
Subject: [TYPO3-team-core-v5] RFC: TagBuilder
In-Reply-To: <mailman.1.1238957436.3271.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1238957436.3271.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1238962205.31970.typo3-team-core-v5@lists.netfielders.de>

Martin Kutschker wrote:

Hi Masi,

> Cumbersome.

I agree
	'<em>' . $this->value . '</em>';
or
	"<em>{$this->value}</em>"
is nicer than
	$tag = new Tag('em', $this->value); // or rather some 
t3lib_div::makeInstanceClassName hassle
	$tag->render();

But I'm especially talking about more complex constructions that can't 
be put in one line. Like this one (taken from the select view helper):

$out = '<select name="' . $name . '" ' . $this->renderTagAttributes() . '>';
$selectedValue = $this->getValue();
if ($this->arguments['options']) {
	if ($this->arguments['optionKey']) {
		foreach ($this->arguments['options'] as $domainObject) {
			// [...]
			$selected = '';
			if ($domainObject == $selectedValue
			    || ($this->arguments['multiple'] && in_array($domainObject, 
$selectedValue))) {
				$selected = 'selected="selected"';
			}
			// [...]
			$out .= '<option ' . $selected . ' value="' . $key . '">' . $value . 
'</option>';
		}
	} else {
		foreach ($this->arguments['options'] as $key => $value) {
			$selected = '';
			if ($key == $selectedValue) {
				$selected = 'selected="selected"';
			}
			$out .= '<option ' . $selected . ' value="' . $key . '">' . $value . 
'</option>';
		}
	}
}

I think, this is quite hard to read, error-prone and difficult to test 
(apart from the fact that this code could be refactored anyways).

But it's not only about readability or stability but reusability:
Instead of copying all the tag-creation code from a view helper to 
create your custom version, you could extend the view helper and only 
modify or add some attributes of the underlying tag:

class LinkViewHelper extends TagBasedViewHelper {
	public function render($uri) {
		$this->tag->addAttribute('href', $uri);
	}
}

class SpeciallinkViewHelper extends LinkViewHelper {
	public function render() {
		$this->tag->addAttribute('rel', 'I\'m special');
	}
}


All the best
Bastian

From bastian at typo3.org  Tue Apr  7 09:59:00 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Tue, 07 Apr 2009 09:59:00 +0200
Subject: [TYPO3-team-core-v5] RFC: TagBuilder
In-Reply-To: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1239091136.15292.typo3-team-core-v5@lists.netfielders.de>

FYI:
Sebastian and me decided now to add this class to the Fluid 
package/extension first and see how practical it is.

Bastian

From masi-no at spam-typo3.org  Tue Apr  7 10:07:08 2009
From: masi-no at spam-typo3.org (Martin Kutschker)
Date: Tue, 07 Apr 2009 10:07:08 +0200
Subject: [TYPO3-team-core-v5] RFC: TagBuilder
In-Reply-To: <mailman.1.1238962205.31970.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238950940.5339.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1238957436.3271.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1238962205.31970.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1239091623.30028.typo3-team-core-v5@lists.netfielders.de>

Bastian Waidelich schrieb:
> Martin Kutschker wrote:
> 
> Hi Masi,
> 
>> Cumbersome.
> 
> I agree
>     '<em>' . $this->value . '</em>';
> or
>     "<em>{$this->value}</em>"
> is nicer than
>     $tag = new Tag('em', $this->value); // or rather some
> t3lib_div::makeInstanceClassName hassle
>     $tag->render();
> 
> But I'm especially talking about more complex constructions that can't
> be put in one line. Like this one (taken from the select view helper):

[example snipped]

Makes much more sense to me now.

> But it's not only about readability or stability but reusability:
> Instead of copying all the tag-creation code from a view helper to
> create your custom version, you could extend the view helper and only
> modify or add some attributes of the underlying tag:
> 
> class LinkViewHelper extends TagBasedViewHelper {
>     public function render($uri) {
>         $this->tag->addAttribute('href', $uri);
>     }
> }
> 
> class SpeciallinkViewHelper extends LinkViewHelper {
>     public function render() {
>         $this->tag->addAttribute('rel', 'I\'m special');
>     }
> }

Nice, idea.

I see now that there are uses cases for such a class.

Masi

From info at sk-typo3.de  Tue Apr  7 11:58:52 2009
From: info at sk-typo3.de (Steffen Kamper)
Date: Tue, 07 Apr 2009 11:58:52 +0200
Subject: [TYPO3-team-core-v5] Character problem in Cache Framework
In-Reply-To: <mailman.1.1238198236.6676.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238198236.6676.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1239098325.14702.typo3-team-core-v5@lists.netfielders.de>

Hi Robert,

any news here?

vg Steffen

From robert at typo3.org  Thu Apr  9 13:53:46 2009
From: robert at typo3.org (Robert Lemke)
Date: Thu, 9 Apr 2009 13:53:46 +0200
Subject: [TYPO3-team-core-v5] Character problem in Cache Framework
In-Reply-To: <mailman.1.1239098325.14702.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238198236.6676.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1239098325.14702.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.5104.1239278033.20378.typo3-team-core-v5@lists.netfielders.de>

Hi Steffen,

Am 07.04.2009 um 11:58 schrieb Steffen Kamper:

> any news here?

yes, I've updated the File Backend so it uses "^" as the separator.
Committed in r2148, see also http://typo3.org/go/issue/2982

Cheers,
robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: Signierter Teil der Nachricht
Url : http://lists.netfielders.de/pipermail/typo3-team-core-v5/attachments/20090409/75643da0/attachment.pgp 

From info at sk-typo3.de  Thu Apr  9 14:01:38 2009
From: info at sk-typo3.de (Steffen Kamper)
Date: Thu, 09 Apr 2009 14:01:38 +0200
Subject: [TYPO3-team-core-v5] Character problem in Cache Framework
In-Reply-To: <mailman.5104.1239278033.20378.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1238198236.6676.typo3-team-core-v5@lists.netfielders.de>	<mailman.1.1239098325.14702.typo3-team-core-v5@lists.netfielders.de>
	<mailman.5104.1239278033.20378.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1239278497.12826.typo3-team-core-v5@lists.netfielders.de>

Hi Robert,

Robert Lemke schrieb:
> Hi Steffen,
> 
> Am 07.04.2009 um 11:58 schrieb Steffen Kamper:
> 
>> any news here?
> 
> yes, I've updated the File Backend so it uses "^" as the separator.
> Committed in r2148, see also http://typo3.org/go/issue/2982
> 
> Cheers,
> robert

thx, i will update my patch so it does the same.

vg Steffen

From karsten at typo3.org  Tue Apr 21 08:42:44 2009
From: karsten at typo3.org (Karsten Dambekalns)
Date: Tue, 21 Apr 2009 08:42:44 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due to
	naming/placement scheme
Message-ID: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>

Hi.

While sitting at DFW airport waiting for the flight back home I set out 
to fix the current code of the TYPO3 package.

Most things were simply adjustments to new method names or "EBKAC" type 
of issues (e.g. the problem with aggregate roots being in the object 
tree to be persisted but not being added to their repositories).

One thing needs more consideration, though. The naming and placement 
scheme for view classes has changed since Fluid is around. The new 
scheme is rather intuitive and works well for the Fluid-based code being 
around, as there are only HTML files present as views.

The TYPO3 package uses PHP views in a few places (JSON services) and 
still used the old class name scheme. I this created the needed 
directories, moved/renamed the files and adjusted namespaces and class 
names. Didn't work. Ok, the ActionController in FLOW3 had the old view 
name pattern. Changed that. Now TYPO3CR didn't work any longer. Fixed 
that. Bang - this leads to code like this for the default view of the 
default controller in the TYPO3CR Admin subpackage (in 
TYPO3CR/Classes/Admin/View/Default/IndexHTML.php):

<?php
declare(ENCODING = 'utf-8');
namespace F3\TYPO3CR\Admin\View\Default;
  [...]
class IndexHTML extends \F3\FLOW3\MVC\View\AbstractView {
  [...]
}
?>

Who spots the error? Two words: "reserved words", in this case "default" 
cause syntax errors. This is why we decided on postfixing Controller to 
controller names, as to avoid "class Default ...".

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

Regards,
Karsten

From bastian at typo3.org  Wed Apr 22 10:38:20 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Wed, 22 Apr 2009 10:38:20 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
 to naming/placement scheme
In-Reply-To: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1240389499.18211.typo3-team-core-v5@lists.netfielders.de>

Karsten Dambekalns wrote:

Karsten Dambekalns wrote:

Hi Karsten,

>  [...]
> class IndexHTML extends \F3\FLOW3\MVC\View\AbstractView {
>  [...]
> Who spots the error?

me me me! the square brackets...


> Two words: "reserved words"

uhm, yeah..
I still don't understand why namespace segments can't use reserved words.


> * either we ban "Default" only for this case and make it 
> "StandardController"

We could also rename it to "Index" as we did with actions..


> * tell people to always use some descriptive name instead and adjust 
> routing

thats a good plan anyways and we should set an example in the core classes.
OTOH, if there's only one controller in a package, it can be hard or 
even counterproductive to find a better name..


> * 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;"


I don't know.. IMHO it's a bit confusing to have "Controller" in views 
namespace and filepath.


> * do the above for PHP and HTML to keep things consistent.

yes, I definitely opt for a consistent solution!


> Better ideas (hopefully)

not really, sorry..


 > or at least an opinion

At the moment, I'd prefer to rename "default" to "index" - and I just 
found out, they did the same in ZF. Probably for the same reason.

all the best
Bastian

From robert at typo3.org  Wed Apr 22 11:07:42 2009
From: robert at typo3.org (Robert Lemke)
Date: Wed, 22 Apr 2009 11:07:42 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
	to naming/placement scheme
In-Reply-To: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>

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 

From bastian at typo3.org  Wed Apr 22 11:52:42 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Wed, 22 Apr 2009 11:52:42 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
 to naming/placement scheme
In-Reply-To: <mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
	<mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>

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

From robert at typo3.org  Wed Apr 22 13:16:35 2009
From: robert at typo3.org (Robert Lemke)
Date: Wed, 22 Apr 2009 13:16:35 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
	to naming/placement scheme
In-Reply-To: <mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
	<mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.7244.1240399001.9952.typo3-team-core-v5@lists.netfielders.de>

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 

From karsten at typo3.org  Wed Apr 22 14:21:19 2009
From: karsten at typo3.org (Karsten Dambekalns)
Date: Wed, 22 Apr 2009 14:21:19 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
 to naming/placement scheme
In-Reply-To: <mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
	<mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1240402879.1571.typo3-team-core-v5@lists.netfielders.de>

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

From bastian at typo3.org  Wed Apr 22 14:27:19 2009
From: bastian at typo3.org (Bastian Waidelich)
Date: Wed, 22 Apr 2009 14:27:19 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
 to naming/placement scheme
In-Reply-To: <mailman.7244.1240399001.9952.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>	<mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>	<mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>
	<mailman.7244.1240399001.9952.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1240403238.22888.typo3-team-core-v5@lists.netfielders.de>

Robert Lemke wrote:

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

damn, I give up ;)

From ingmar at typo3.org  Wed Apr 22 14:52:58 2009
From: ingmar at typo3.org (Ingmar Schlecht)
Date: Wed, 22 Apr 2009 14:52:58 +0200
Subject: [TYPO3-team-core-v5] Problem with handling of view classes due
 to naming/placement scheme
In-Reply-To: <mailman.1.1240402879.1571.typo3-team-core-v5@lists.netfielders.de>
References: <mailman.1.1240333201.18931.typo3-team-core-v5@lists.netfielders.de>
	<mailman.7074.1240391270.9952.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1240393960.16110.typo3-team-core-v5@lists.netfielders.de>
	<mailman.1.1240402879.1571.typo3-team-core-v5@lists.netfielders.de>
Message-ID: <mailman.1.1240404781.17430.typo3-team-core-v5@lists.netfielders.de>

Hi Karsten,

Karsten Dambekalns schrieb:
> 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 :)

Well, even if it's not an adjective but a noun, defaultController is
perfectly fine grammar-wise, just like monsterController. The German
word "Standard" is not an adjective either but still you can say
"Standardausstattung" or stuff like that...

Anyway, just my two cents, and as for the question at hand, I actually
don't care how you do it ;-)

cheers
Ingmar

-- 
Ingmar Schlecht
TYPO3 Core Developer