[TYPO3-hci] BE vs FE

[Tapio Markula]

Waldemar Kornewald wrote:

> Of course I could. But then you should better close this mailing list
> because it seems that nobody is really interested in improving TYPO3's
> usability.

not true

> And what results do you have? Could your new scheme possibly replace
> the old concept?
> 
> You sound like you're going to add yet another concept which is only
> used by expert-power-users. What about those poor every-day users who
> only have to create very simple content? Should we forget them and
> only concentrate on adding new featuers to make every power-user
> happy? If you are really trying this your primary interest is not
> usability.

the module, which you would like to add, is not simple to implement
and implemention must be some kind of compromise solution

> You don't understand. Setting up a template is not an every-day task
> and the average editor does not need to do this. I'd like to simplify
> the BE, so editors don't need hours of training.

Agreed. Simplify BE is important - but as important is not to allow
normal user to touch templates.

Because Typo3 is for creating *custom* templates, which are different 
for every customers, setting up templates should be let for developers 
of templates.

For normal user should left just possibilities to select templates 
and/or change the layout sheme of them.
Template and CSS selectors can easily give for avarage users.

I have now tried get working a new system of Berhard Kraft.
I have now tried to combine tm_contentaccess + kb_nescefe - failed.
It seems that Bernhard Kraft don't have time or he doesn't like to
help me solving existings problems.
see topic 'Re: [TYPO3] Nested Content Elements - help needed' in the 
English mailing list (starts from '[TYPO3] Nested Content Elements').

Using that model in most cases users select nested template just 
selecting instead normal content element content are template
(content container is a nested content area template).