Hi Christian, you wrote: > > Lot of other APIs use css.graphic.XGraphic. Since XSimpleCanvas is > > going > > to be a convenience interface, there should be either an easy way to > > obtain an XBitmap from an XGraphic, or a method taking an XGraphic. > > XBitmap is an interface with limited use cases. But since it is used > at our current API at some places, I suggest we can still keep it to > transport bitmaps over the API. I think adding the XBitmap interface to > each XGraphic objekt makes working with this a lot easier. > Yikes - you're not confusing awt::XBitmap with rendering::XBitmap here, no? I was referring to the latter... > > Also, I think having access to the state of the simple canvas might be > > necessary (sorry I previously thought and told you otherwise :), in case > > people really want to use more complex functionality at the XCanvas. > > They need the current state of the simple XCanvas then, don't they? > Please not only the current state, but something like push() and pop() > for the state? > Please use XCanvas then - there, you can even store as many instances of your graphics state directly at your objects. I'd rather not bloat the XSimpleCanvas interface with this...
Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
