Hey,
> This IS something new in qx 2.0.
Yea, like every other bugfix as well.

> And I HAD used image decorators for shadows because I used the aristo theme 
> which did NOT used any css based shadow decorators. Aristo ALLWAYS used the 
> grid decorator for shadows.
This isn't about CSS decorators or not. The fix was in Widget and not in any 
decorator at all. And again, I did not change the behavior for nothing. I 
aligned the shadow behavior with the wider used decorator behavior. 
Additionally, I fixed a placement bug in case of a resize.

> So in the end what I'm complaining about is how the shadow (or 
> decorator) dimensions are defined. It should not be
> 
>     inset: [ -10 30 30 -10 ]
> 
> in order to get a shadow of 10px on every side of a widget. It should be
> 
>     inset: [ -10 10 10 -10 ]
> 
> if the new parameters for top inset and left inset have to be negative 
> number if the decorator should show up above or before the widget. In my 
> opinion the  definition in qx 1.6.1 having positive number top and left 
> insets was perfect.
> 
> Instead with the new implementation we have to do
> 
>     inset: [ -10 30 30 -10 ]
> 
> Why is that? Maybe I'm just not getting the point?
> 
> We should NOT need to make ourselves calculations like "how man px do I 
> have to add to the bottom inset to get a top of 10px IF i have a 10px 
> top decorator.

I agree with you that the other way would be nicer. But thats a separate topic 
and we should open up a report for that. But if the behavior is the same for 
decorators and shadows (as it should be), we need to change both and with that, 
need to check every inset we defined for decorator elements. Thats a lot of 
work and a huge change for all themes. Thats why I aligned the shadow behavior 
with the decorator behavior and not the other way around.

Regards,
Martin
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to