[TYPO3-core] RFC: #7891: Docheader Class with Hook for dynamic change of docheaders

Steffen Kamper steffen at sk-typo3.de
Tue Mar 18 12:55:12 CET 2008


"Tapio Markula" <tapio.markula at xetpoint.fi> schrieb im Newsbeitrag 
news:mailman.1.1205840733.13021.typo3-team-core at lists.netfielders.de...
> Steffen Kamper kirjoitti:
> > "Tapio Markula" <tapio.markula at xetpoint.fi> schrieb im Newsbeitrag
> news:mailman.1.1205839174.25342.typo3-team-core at lists.netfielders.de...
> >> Steffen Kamper kirjoitti:
> >>> Hi
> >>>
> >>> This is an SVN patch request.
> >>>
> >>> Type: Bugfix
> >>>
> >>> Bugtracker references:
> >>> http://bugs.typo3.org/view.php?id=7891
> >>>
> >>> Branches: 4.2
> >>>
> >>> Problem:
> >>> atm the docheaders are static. With rendering template.php doesn't
> know which module is rendered. There is no hook to change/add something to 
> docheaders
> >> but reading the diff I don't figure how to define for desired page
> own button groups like your previous proposal.
> >> Every called page should have possibility to define buttons as desired.
> >> For example reload could be in nav frame on the right button group
> but generally on the left.
> >>
> >> BTW. There has bee discussion NOT to use private function but
> 'protected final' - private function is extremely harmfull for XCLASSing.
> >
> > there is no private method in the class.
> >
> > The hook delivers all you need:
> > * array of buttons
> > * templatefile (you can use your own)
> > so there is no problem to change anything or add something, no
> xclassing is needed.
>
> In the previous proposal was possiblity to define with an option the 
> buttons. Now any change needs hooks. I send you a proposal to set generic 
> or page level configuration. I don't like this solution.
> -1 for this proposal

sry, but i think you don't got the point.
To change something in userTS is more complex as i've done in former 
proposal because it differs from module to module, so i've postponed this to 
4.3.
To give developers the chance to add something i did this patch as last 
chance for 4.2.
If not, there is no dynamic way before 4.3.

vg  Steffen




More information about the TYPO3-team-core mailing list