[TYPO3-dev] Usability of the Columns view

[Erik Svendsen]

Hello Tapio,

> Erik Svendsen wrote:
> 
>> 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
>> 
> Basically the same, which I have done using kb_contenttable and
> fx_2cols (I don't remember the correct name of the plugin f +
> something + _2cols) entension give different laout for text using
> different HTML-layout for some content elements.

This tells my that you don't really know TemplaVoila, and the opportunities 
regarding to FCE. It's not a question about making two columns in one main 
column, or "table based" blocks with text, but a question about making userfriendly 
content element especcially suited to certain types of content (without making 
an extension). 

>>> IMO not a big advance because creating content erea templates is
>>> easy
>>> 
>> Not agree, I find the TV much faster than using MTB.
>> 
> depends certainly on situation - in most cases I have used the same
> content area templates for many customers.

I never use the exactly same HTML template. But I reuse much of the TS.
 
>>>> Third is larger flexibility in the number of content
>>>> 
>> I working on sites where I with my knowlegde couldn't implemented the
>> design without TV.
>> 
> maybe the fact that you can't but maybe not.

There is a reason that Dassault System's website made the develoment of TV 
possible. Read the casestory on TYPO3.com. I suppose Kaspers knowlegde of 
what was achiveable the traditional way should be consider as maybe the best 
one.

>> 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.
>> 
> I made some for TemplaVoila 0.4 - but I can't install newer for typo3
> 3.8.1 and I can't use in the same installation TemplaVoila and
> standard
> page module. Both limits my possibities to make TV better.
> Endeed in principle it is possible to solve with some trick the
> content element wizard. I have some ideas but I don't know how to
> implement.
> Look at my comment at time 10:00, where I express some ideas.

Have commented it.

And why not do development on the newest plattform. Doing development for 
3.8.1 isn't any good idea, it's like developing for Linux 2.4 core, when 
most of the newer distros is using 2.6. I have sites with 3.7, 3.8.1 and 
all developing and testing on 4.0rc2.

>> But I also think its possible to get the same usability with TV
>> 
> I don't doubt - but there is really much work - many things must think
> at the bottom level and made totally new functionalities for that.

But this is neccessary to get TYPO3 userfriendly at all levels. You need 
a userfriendly templating engine, userfriendly configuration, userfriendly 
backend og userfriendly frontend editing to make the competition with other 
CMS's. 

>> 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).
>> 
> I'm afraid that too

Why be afraid. When systems develop, it's normal that extensions and other 
stuff gets obsolete. Because new technology emerges, PHP changes and so on. 
And gives new opportunities, and mostly better solutions. If new, and better 
solutions make anything obsolete, no problem. I have a small database application 
I developed in 1995. It's more or less rewritten four times because the change 
of techology and new rules for public accounting.


WBR,
Erik Svendsen
www.linnearad.no