[TYPO3-project-formidable] Enablefields in FORMidable?

[Luc Muller]

Lol Rego.

This seems to be a highly philosophical problem for the moment ;)
I think we're going to ask Jerome, The Guru, Schneider, for his point of 
view.

but I agree that having true as default can be good also :p (or not ;))

But, just to get a little more of discussion...

Do you agree that maybe in a lister and a search form, the better state for 
a "default" view should be the view with the maximum of informations ? if 
you put a filter, that makes a lack of information, may a novice user miss 
some informations isn't it.
I mean, that in my point of view a "default" view should be the one with the 
less lack of information.

Hmmmmm well, nevermind! Just wait for the guru's answer :p!

Have a nice WE!

Luc

"Manuel Rego Casasnovas" <mrego at igalia.com> a écrit dans le message de news: 
mailman.126.1186075782.14781.typo3-project-formidable at lists.netfielders.de...
>> I think that a <enable_field>false</enable_fields> by default can be 
>> good,
>> because you get more information with false than with true.
>> if you put it to true by default you get a lack of some information by
>> default.
>>
> Hi Luc,
> I think that the better is true by default, because it's the correct use
> for database tables in Typo3.
> For example if you want to list some from tt_news and you don't use
> enable fields, properties like publish a new in a future date doesn't
> work good, for me true by default is the correct. But I don't mind if
> the default is false.
>
> Best regards,
>    Rego
>
> -- 
> Manuel Rego Casasnovas
> Enxeñeiro en Informática
> mailto:mrego at igalia.com
> Tel: +34 986 10 76 10
> Fax: +34 981 91 39 49
> Igalia - http://www.igalia.com