[TYPO3-dev] TCA-Configuration

[Malte Jansen]

Steffen Kamper schrieb:
> "Malte Jansen" <mail at maltejansen.de> schrieb im Newsbeitrag 
> news:mailman.1.1194520020.28623.typo3-dev at lists.netfielders.de...
>> Steffen Kamper schrieb:
>>> "Malte Jansen" <mail at maltejansen.de> schrieb im Newsbeitrag 
>>> news:mailman.1.1194517955.8617.typo3-dev at lists.netfielders.de...
>>>> Steffen Kamper schrieb:
>>>>> "Malte Jansen" <mail at maltejansen.de> schrieb im Newsbeitrag 
>>>>> news:mailman.1.1194516366.21111.typo3-dev at lists.netfielders.de...
>>>>>> Steffen Kamper schrieb:
>>>>>>> "Malte Jansen" <mail at maltejansen.de> schrieb im Newsbeitrag 
>>>>>>> news:mailman.1.1194515567.22871.typo3-dev at lists.netfielders.de...
>>>>>>>> Hi Steffen,
>>>>>>>>
>>>>>>>> ok, upload size are very common, but you could change other 
>>>>>>>> properties too.
>>>>>>>>
>>>>>>>> But what I miss in the TCA is a option for using an other column for 
>>>>>>>> field or the other way round: define a other config if the type is 
>>>>>>>> changed. I have the problem with a inline-field in one case I need 2 
>>>>>>>> relations required in an other case I need at least 2 realtions. You 
>>>>>>>> could use the same column both... If the table gets bigger you have 
>>>>>>>> a needless column...
>>>>>>>>
>>>>>>> this is very specific :-) Can you think about how such manipulation 
>>>>>>> could be done?
>>>>>> Should be done somewhere in the t3lib_transferdata. But I have done 
>>>>>> something with this class. But there would be some tables which would 
>>>>>> have several columns less....
>>>>>>
>>>>>>> Shall we find the most common things first to get a list of values 
>>>>>>> obvious to configure ?
>>>>>>> tt_content
>>>>>>> * media sizes
>>>>>>> * max files
>>>>>>> * max image sizes
>>>>>>> * hide fields (e.g. hide password of FE_USER)
>>>>>> Normaly you could use nearly every option for this except removing a 
>>>>>> password field (see the other thread about md5-password ;) ). It would 
>>>>>> be something like the kickstarter, only overriding some special 
>>>>>> values...
>>>>> i meant hide password field in list view, or in this case also in page 
>>>>> module - not in the form.
>>>>> I only try to collect some useful settings to make a suggestion.
>>>>>
>>>>> vg  Steffen
>>>> Ok, I get it.
>>>> But than it nearly as the TCEFORM-part or mod.web_list via PageTS, which 
>>>> has a small wizard.
>>>>
>>>>
>>>> - hide fields belongs to the mod.web_list/mod.web_page
>>>>
>>>> - media size etc. belongs to the TCEFORM
>>>> The are already some config values implemented
>>>> TCEFORM.[tablename].[field].config.[key]
>>>> http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.1.0/view/1/3/#id3541144
>>>>
>>>> Have you already test it this way?
>>>>
>>>>
>>>> Malte
>>> yes, i know that way. As we are coders we also have the opportunity to 
>>> debug values and change them. but there are a lot of Admins / BE-User, 
>>> they don't have this ability. And they don't know which setting is in 
>>> which table/field, so they are often lost if they want to configure 
>>> special things, they google and try even wrong postings etc. So this 
>>> should be a bridge interface.
>>> Experts still know how to deal, but it's helpful too to click a config 
>>> form and quick change some values.
>>>
>>> vg  Steffen
>> What about a "real" wizard for the PageTS/UserTS. The Wizard could be a 
>> seperate Extension in the Web-Module.
>> Than you only need a title for TCEFORM (like "Form-Config" | 
>> "Formularkonfiguration").
>>
>> Perhaps you only need other translations for the TSconfig...
>>
>> Malte
>>
> 
> sounds good.
> A limitation would be, that pageTS is only valid for the tree branch. If you 
> have several trees it might be complicated. Thats why I thought about a 
> global one.
> 
> vg  Steffen 
> 
> 

What about something like the template module.
You could make a configuration for a table and add it to a special page.
Or displaying it like the right-management of the ext be_acl.

How is the information of the TSconfig etc saved? Sure somewhere in 
database. Perhaps it would fit to "[TYPO3-dev] Ideas backend 
documentation" (2007-11-06)

But perhaps it could be something else for my bachelor theses in 
april/may...


Malte