[TYPO3-mvc] Extension spread over several pages - best practice?

[Felix Oertel]

Hey,

Am 17.05.10 11:50, schrieb Bastian Waidelich:
> Felix Oertel wrote:
>> The task of the uri-builder is too build the uri and looking up the PID is one part of it.
> Looking up TS settings is not in the domain of the uri builder really.

yep, i was a little wishy-washy (funny, concearning google translator 
this is valid speech ;) ) on that ...

of course the uri-builder does not look anything up. i introduced a new 
subpart in config.tx_extabse called uri ...

config.tx_extbase.uri.mapping {
    default-index = 75
    default-show = 78
}

this is read in AbstractConfigurationManager and stored in 
pluginConfiguration['uri'] which get's merged into 
frameworkConfiguration via 
mergeConfigurationIntoFrameworkConfiguration() in the 
FrontendConfigurationManager.

the uri-builder then fetches this via 
Tx_Extbase_Dispatcher::getExtbaseFrameworkConfiguration(); and tries to 
map the specified controllerAction-pair to an appropriate pageID.

>>> Maybe it would be better to do that in the respective view helper(s)
>> Yeah, I did that before. But then you're unable to use the configured
>> PIDs in redirects, etc
> What do you mean?

$this->redirect() in your controller for example would not work if you 
configure PIDs in the viewHelper. f:form would not respect viewHelper's 
settings as well.
the uri-builder is the central place where the uri building happens ... 
it should take care of the PIDs.

>>> <f:link.action action="foo"
>>> pageUid="{settings.somePid}"></f:link.action>
>>> is not too bad after all, is it?
>> it's not bad, but far away from "nice" ... i want to configure the PIDs
>> once and then never care for them anymore ;)
>
> agree.. Lets see what Jochen & Sebastian think about your solution.

we are the state ... the wall must go !

*gg*

regards, foertel

ps: ya, propably it would have been better to skip the last (two) coffee ;)