Re: 3 csets were pushed to core/commerce: Merge [email protected]:/var/bk/xaraya/c...

I saw 2 problems:

1. disabled an item id dont work together, and item id is mostly not 
wanted in display
2. disabled implies "non functional"

having the distinction between disabled (as in, visible but not 
enabled) and hidden (invisible, but functional) is useful to me 
without having to do it in templates.

whether the current implementation in dd supports this distinction i 
dont recall by head.

marcel

mikespub wrote:
> Marc Lutolf wrote:
> 
>> ...
>>       html/modules/dynamicdata/class/objects.php
>>         1.56 05/06/10 19:52:48 marc@marclaptop. +22 -10
>>         add a "hidden" property status value
>> ...     
> 
> What's the difference between hidden and disabled in your
> eyes ?
> 
> Up to now either the property is disabled and won't appear
> anywhere, or it's there - and you could always choose to treat
> it as hidden or not in the templates afterwards, but that
> didn't affect the DD code.
> 
> Here you seem to be mixing up both cases though, filtering
> out "hidden" properties here and there in the code as well.
> 
> Are you sure you really need this ?
> 
> Mike.