[TYPO3-hci] BE vs FE

Franz Holzinger franz at fholzinger.com
Sun Aug 6 07:44:38 CEST 2006


Waldemar Kornewald a écrit :


>> > FE editing is indeed a nice concept and it's totally sufficient to
>> > have one easy to use BE editing concept for complex tasks and a very
>> > simple FE editing mode for simple tasks. But why do we need even more?
>> > That's what plugins are for.
>>
>> I don't think you got the point. A plugin in TYPO3 terms is a just a
>> different way of handling the output to the frontend. For the backend you
>> can create so called modules, and if you don't like the way it is done in
>> the page or list view, feel free to create your own module to handle the
>> backend stuff the way you want it. Currently we are developing 
>> something for
>> an end user with some special tasks that can't be solved with either 
>> page or
>> list view, since they have to handle a lot of DB relations in just one 
>> view.
> 
> 
> 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.
> 
I think what you want is only a simple checkbox to hide about 70% of all 
menu entries. Only the code of one class needs to be adapted to make 
this possible.
And there exist already some extensions to make the usage of frontend 
users as backend users possible.

But there stands nothing against writing an additional backend module 
for a more simple page creation wizard.


- Franz




More information about the TYPO3-team-hci mailing list