[TYPO3-core] RFC: Feature Request #5610: Extend TCEFORM_confObj on Page TSconfig by property filterItems

[Oliver Hader]

Hi Ernesto,

Ernesto Baschny [cron IT] schrieb:
> Hi,
> 
> Oliver Hader wrote: on 15.01.2008 16:57:
> 
>> Problem:
>> In Page TSconfig there are currently these possibilities to manipulate 
>> the items of a select field:
>> TCEFORM.<table>.<field> {
>>   addItems.123 = new item
>>   removeItems = 234,456
>> }
>>
>> This works only relatively to a given set of items. It is not possible 
>> with these both methods to set/filter the items exactly to a 
>> predefined set.
>>
>> Solution:
>> The solution is a new feature "filterItems" - all other (available!) 
>> values which are not defined in the "filterItems" are cut off.
>>
>> Example:
>> TCEFORM.<table>.<field>.filterItems = 110,101,111
>>
>> Documentation changes:
>> See attached text file.
>>
>> Bugtracker references:
>> http://bugs.typo3.org/view.php?id=5610
>>
>> Branch: Trunk
> 
> Haven't reviewed the patch, but the naming is a bit misleading in my 
> eyes. For me "filtering" means excluding something (to filter "out"), 
> while the new property seems to leave only the entries defined here. So 
> maybe the property should be called "onlyItems" or "removeAllButItems" 
> or something.

The word "filter" could mean both: "pass/sieve" or "cut off"
But I'm fine with renaming it to something else, like keepOnlyItems or 
passOnlyItems...

> And in the bugtracker there is a mention to ".ignore", how is this 
> difference from listing the property in the "filterItems" list itself? 
> e.g. why is this:
> 
> TCEFORM.pages.doktype {
>   filterItems = 1,2,255
>   filterItems.ignore = --div--
> }
> 
> different from this:
> 
> TCEFORM.pages.doktype {
>   filterItems = 1,2,255,--div--
> }

Oh, correct, there's no difference between the variants you showed. 
Thus, the "ignore" property is obsoltete and can be removed.

olly
-- 
Oliver Hader
http://inpublica.de/