[TYPO3-dev] Usability of the Columns view

Erik Svendsen erik at linnearad.no
Mon Apr 3 10:00:48 CEST 2006


Hello Tapio,

First! I give you credit for your work with usability in front-end editing, 
and tm_contentaccess.

> Erik Svendsen wrote:
> 
>> The use of TemplaVoila versus MTB is not so much a customer choice as
>> a designer/developer choice. TV has some advantages, who I consider
>> important. One is the FCE, who make it fast and easy to make elements
>> specific for the customer without making a new extension.
>> 
> yes if you need different functionality, not if you just need
> different
> layout kb_conttable makes the latter possible and there are several
> plugins, which makes it possible for the content type 'text'.
> It is for user *much easier* to change content element type
> from 'Text' to some alternatives than change whole template using
> 'Edit
> page properties'

The users do not change templates, they are given new content element types. 
Appearing in the same list as Test, Text w/Image and so on. FCE isn't a page 
template. Try to find an extension to make a simple staff list on a page 
(a company with 10 - 15 employes). With TV and FCE i took about 30 minutes. 
And I don't use tables in layout and design. Haven't done so for many years. 
But it also gives customer who has more knowlegde the possibility to choose 
between different pagelayouts who are homogenous.


>> lot, instead of installing extensions who are "overkill". Another is
>> fast implemeting of design from third party designers who make
>> finished HTML-templates.
>> 
> IMO not a big advance because creating content erea templates is easy

Not agree, I find the TV much faster than using MTB.
 
>> Third is larger flexibility in the number of content
>> 
> not a big advantage

I working on sites where I with my knowlegde couldn't implemented the design 
without TV.
 
>> Also i find that most of my customers find the web>page TV module
>> easier to understand than the normal web>page module.
>> 
> Yes if you think the default Web > Page module. It is messy. I just
> made it clearer - and in fact easier to use thatn TV module because of
> copy,cut and paste icons + AJAX-based moving content elements from one
> content area to other. Changed Web > Page module is certainly better
> than default TV module but concernig default interfaces you are right.

Yes, your modification through tm_contentaccess makes the normal web>page 
better. And is somehow a step in right direction. But why don't use the same 
ideas to make TV better.

>> And it also possible to get a decent frontend editing with TV
>> 
> TV has very bad frontend editing - at least TV 0.4 work really awfull
> bad way - bad frontend was the main reason, why I rejected TV.
> Even using my modifications it far from the level of using Web > Page
> module. If I some day will use TV for my customers it must have
> remarkable better frontend editing.

Maybe you are correct. Maybe the way I restrict the different users make 
it work for my customers. And also because many of them prefer the backend 
when editing.

But I also think its possible to get the same usability with TV in the future. 
And I also think the next half year to a year will give large changes in 
how we are editing in TYPO3.

And I'm afraid the work on usability to version 4.5 and the core redesign 
on 5.0 will make part of your work somehow obsolete (but not the ideas behind 
it).

WBR,
Erik Svendsen
www.linnearad.no






More information about the TYPO3-dev mailing list