[TYPO3-dev] Usability of the Columns view

[Tapio Markula]

Erik Svendsen wrote:
> Hello Tapio,
> 
>>> When TV is installed, the only logical web>page to use is TV. It's
>>> not necessary to use two, confuses the users.
>>>
>> But I mean for test sites it would be reasonable - if the content
>> element wizard would work both for standard page module and
>> TemplavVoila
>> could test in the same installation. I would really need for that some
>> detection system, which makes possibe to use two different content
>> wizard inside the same installation.
>> Using some TS Config for page would work if on the base of that could
>> build some detection method.
> 
> 
> Even for testing, I think it's a to complicated way to do it. You need 
> to versions of Rootpage TS (or at least a TS with a lot of conditions), 
> because differences in the two methods.
> 
> The easy way is to make two identical (near identical) sites on the same 
> TYPO3 installation. On one using TV setup through TS, on the other MTB 
> method.

but I would need to the root page some detection mechanish + XCLASS
implementation, which could use that mechanisms to automatic change the 
used content element wizard

If for root page has been set

a) checkbox with recursive 'TemplaVoilaSite'
b) TS Config for pages some special config

either method a) or b) I could make an automatic detection but

1) I don't know how to build a detection, which detects if the root page 
has a field (lets presume tm_contentaccess_templavoilasite) checked

2) The root pages has some special TS config for pages

> On production enviroment it's not logical to use both on same website. 
> Using both opens for user errors.

I know
> 
> The main flaw in frontende editing with TV is making new content element 
> not giving the Content Element Wizard, but directly a Text Content 
> Element.

at least in TemplaVoila 0.4 that came into unused elements.
I was *really confused* the behavior. I really thought, what went wrong.
I didn't expect so totally confusing and that's why *extremely* bad 
behavior. Simple unforgivable - I can't tolerate that kind of behavior.
I can't sell anybody any solution, which has so bad behavior.
When I added 'toolbar' the content element wizard worked *more 
confusing*. I was really totally lost - really intolerable situation!

 >For experienced users this is the best choice, but maybe not for "newbies"

maybe this is the point. Remember that differencies in the BE interface 
are not important because you can build your own interface, if you want.
I build for standard page module TemplaVoila-style BE interface.
Because both the standard style and TemplaVoila-styles are available 
there are much conditions.