[Typo3-dev] TYPO3 hook for BE interface generation [was: scan code for hook]

[Sylvain Viart]

Hi,

I start with some context:

This topic is related to hook programming in the BE. It's imply some 
modification in the core source to allow hook entry point.

My goal is to extend the TYPO3 permission system, controlled by 
user:TSconfig in BEgroups or BEuser. This, to be able to disable some 
parts of the BE GUI interface.

It could be extended to disable many more part of the BE GUI. Which 
could be very nice, because, you can have a BE which really behave as 
the client request without too much feature he doesn't need.

So, I've started studying the TYPO3 code source, based on TYPO3 3.7.0 
from CVS, following Robert Lemke advise and his example about hook 
programming.

You fill find here a picture of the BE, where I've circled some GUI area 
I would like to control:

http://wiki.typo3.org/index.php/Image:Remove_red_cercled_item.png

I've found all the 3 first area on the left:
- the toolBar at the Top
- the column header
- and the element header

You can find my documentation about this work in progress here:

http://wiki.typo3.org/index.php/Sylvain:Full_Website_Setup/Extension_Programming

Now, my problem is as follow:

A need more than one hook, I need almost one hook entry point by area. 
Hopefully the items in the same area are created together. :-)

So, what about the current design of generating the GUI ?

It seems to me, that some big part of this code as some duplicate. What 
about having ONE permission entry point (function) for controlling the 
draw any BE element ?

It seems like a design pattern. ;-)

I mean for user available GUI.

But I'm sure, someone have already wish he could control how the admin 
interface should behave.

If I patch sysext/cms/layout/class.tx_cms_layout.php and 
sysext/cms/layout/db_layout.php, can I make a new extension with the 
patched file and tell TYPO3 to use mine instead of the default system 
extension ?

Some documentation about changing system extension ?

Robert Lemke wrote:
> Sylvain Viart wrote:
> Again, if you need a *new* hook which is not included in 3.6.2, you will
> have to work with 3.7.0dev anyways (or at least that's what I recommend).
> It's not as difficult as it seems, just go ahead!
> 
>>>[1] http://robertlemke.de/de/typo3/hooks/index.html
-- 
Regards,
Sylvain Viart (France)
TYPO3 DocTEAM.