[TYPO3-hci] A new approach to a less frightening start with TYPO3

JoH asenau info at cybercraft.de
Fri Mar 2 00:24:59 CET 2007


>> 1. We already got the possibility to choose between different
>> interfaces.
>  > Currently there are only "backend" or "frontend" available
>  although there > are comma separated lists for [BE][interfaces] and
> [BE][loginLabels] since
>  > only "alt_main.php" and "../" are hardcoded in index.php.
>
> Concering alt_main.php I looked Typo3 4.1, where alt_main_new.php is
> disabled.
> Enabling it needs changing file name, when it *repaces* entirely
> existing system.
>
> I made to an evaluation version of tm_shared_lib
> a new User > Setup option to select the new frameset 'Dropdownmenu on
> top frame', if 'topapps' plugin has been installed.
>
> User > Setup options could be for some issues reasonalbe.
>
> In TS config for users they could overwritten.
> Endeed setup.override is inconvenient. Changes don't take effect
> before saving. For critical values it might be better to user
> setup.override setting directly from TS config field and not from
> 'uc' field.

Sorry to say, Tapio, but I didn't understand anything.
And what has this to do with the original approach in this thread: Having
predefined usergroups for the _existing_ interface?

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
openBC/Xing: http://www.cybercraft.de
T3 cookbook: http://www.typo3experts.com




More information about the TYPO3-team-hci mailing list