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

Marcel van der Boom wrote:
> 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

"Disabled" means disabled altogether in code here - it's not some
DD equivalent of the weird HTML disabled="disabled" attribute. So
it's really not visible and not functional anywhere :-)

How (enabled) properties are then shown in templates is another
issue - they could be visible and functional, visible but not
functional, invisible but functional, or invisible and not
functional - all depending on how you use the DD tags in the
templates :-)

I haven't dived into the exact use case for this "Hidden" status
yet, but somehow it feels in the wrong place there. After all
we already have a property type "Hidden" too, for those fields
you want to hide but keep functional - isn't that enough ?

Mike.