Shadows seem orthogonal to cilpping... shouldn't this just be a separate widget?

Shadows seem orthogonal to clipping... shouldn't this just be a separate widget?

I definitely thought about putting this into a new widget, but the options i came up with would either:

• have a widget that is basically a direct copy of ClipPath but with a few added properties / shadow support
• have a widget that can only accept ClipPath / ClipRect / ClipOval / ClipRRect as a child

I was also looking at adding 'shadow' to the other Clippers but wanted to discuss how to go about it first.
How do you suggest this should be placed as a new widget / implemented differently? I was thinking we could look at adding a ClipperDecoration : Decoration class and this as a property to the 4 different clippers? (this would also add support for clip shaped borders etc)

Why not just a widget that takes a Path and draws a shadow to match that Path?

Come to think of it, does PhysicalShape address your need?

Looks like PhysicalShape or PhysicalModel (for rect shapes) does exactly this? I am going to close this PR for now. Feel free to add additional details if this did not resolve your issue.

@coman3 Could you solve this issue by using PhysicalShape or PhysicalModel as suggested? Because I could not find enough documentation and examples on those 2 classes. maybe you can help

@aytunch I ended up just implmenting a wrapper widget locally. PhysicalShape or PhysicalModel did not have support for a custom shadow which was too limiting in my situation.

If you need a basic shadow, and maybe some colour use PhysicalShape, otherwise have a look at this implementation: https://gist.github.com/coman3/e631fd55cd9cdf9bd4efe8ecfdbb85a7