[TYPO3-ect] Controller for Typo3

[Elmar Hinz]

Michael Scharkow schrieb:
>> Read my post about "Inversion of control" for the BE from yesterday
>> specially for you. I think we need a container first.
> 
> 
> I read your post and also thought about that: Either make the BE one
> controller that calls the modules or leave all modules as standalone
> scripts that inherit form a BE controller that provides the necessary
> infrastructure as auth, rendering the modules frame and the page tree...
> 
> Both seem like a hell of a lot of work but need to be done anyway if we
> want to get rid of the frames in BE.
> 


As long as Autoloading isn't fully available one big problem is the
different behaviour of pathes for FE and BE plugins. (What a
superfluous problem!) The starting directory is the same for all FE
plugins while BE have to deal with this problematic backpathes.

Already this makes common handling of FE and BE difficult. One BE
controller that calls the modules would lead to the same kind of path
behaviour for FE and BE.

Now let the frameset be there for a while and do a smaller controller
first:

a) The dispatching to the different modules will be very similar to
the FE plugin dispatch controller. So you can wait for that solution.

b) The additional setup of "the environment": For this the scripts are
available. You currently include them into each BE modul:

30 	{
31 	  unset($MCONF);
32 	  require ("conf.php");
33 	  require ($BACK_PATH."init.php");
34 	  require ($BACK_PATH."template.php");
35 	  $LANG->includeLLFile("EXT:myext/mod1/locallang.php");
36 	  require_once (PATH_t3lib."class.t3lib_scbase.php");
37 	  $BE_USER->modAccess($MCONF,1);    // This checks permissions and
exits if the users has no permission for entry.
38 	}

c) What does t3lib_SCbase? We need to merge that into the strategy to
replace pi_base.

Is it that difficult then?

Regards

Elmar