Hey, > I thought as much. Yes, using my own properties is an option as well but I > wanted to avoid that. > > What I need is to make use of multiple (comma-separated) rules for the CSS > background (http://caniuse.com/#feat=multibackgrounds) and box-shadow > (http://caniuse.com/#feat=css-boxshadow) properties as is allowed with CSS3. > > Layering multiple background images on top of each other is interesting if > one or more of them are partially transparent or they don’t cover the item’s > full size. > With box-shadows, the situation is even simpler as specifying multiple > shadows has always been part of the spec. > > To remain backwards-compatible, every property may be an array and if it is, > there will be multiple images/gradients/shadows. There is also a switch on > whether to put gradients atop images or the other way around. The only thing > that’s not possible is to interleave images and gradients, but so far I’ve > not been able to find a use case for that. > > I will try to merge my custom mixins into > qx.ui.decoration.MLinearBackgroundGradient, qx.ui.decoration.MBackgroundImage > and qx.ui.decoration.MBoxShadow and send you a pull request on GitHub and a > ticket on your bugzilla when I’m done.
Sounds great! Thanks. :) Best, Martin ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
