Description Tim Buschtoens 2011-04-05 10:29:12 EDT

RoundedBorders are currently handled in a very awkward fashion: 

Normal borders are handled like other complex values (Fonts, Gradients), i.e. created as a QxBorder instance on the Server, send to the client as an json-object, there converted to an qooxdoo-border and then stored in the ThemeStore where its reused as often as needed.

With rounded-borders however, things are different. The radii are a separate css-property (BoxDimension) and handled as such. When AppearanceBase requests a border for a widget that has radii bigger than 0, an new RoundedBorder object is created (in *addition* to a potentially useless not-rounded border) and *not* stored anywhere. This means everytime a RoundedBorder is needed in AppearanceBase, a new instance is created, even if an identical one already exists.

So i propose two steps:

1. Merge the qooxdoo classes Border and RoundedBorder. There is no need to make a difference between them, it just makes everyting more complicated. (Its a leftover from before we freely editied qooxdoo code.) This step will require some changes in Border and GraphicsMixin.

2. Re-use rounded borders. This can be achieved by either combining border and radii on the server (which might be difficult), or by creating an additional storage for rounded borders in ThemeStore.js. As a result we will save a bit of time and memory, and will a more consistent behavior.