Community
Participate
Working Groups
Bug 236505 required a change to how images are stored and later disposed. It turns out that we can reuse ImageRegistry for this purpose and since that seems to be a more standard approach, we should use that instead.
Adding Uwe for any input that he might have. I think that this "depends on" bug 236505 rather than blocking it, because the code that we essentially want to clean up here has been added with bug 236505.
If it turns out that this can be done without adding API, I think this is a potential candidate for 3.0.2 since it can help saving resources. Therefore, when you address this, please add a patch here on bugzilla in order to simplify backporting, just in case.
bulk update of target milestone
Dave, I think this is yours because you fixed bug 236505. Please set the target milestone as appropriate.
Created attachment 130428 [details] experimental approach to using ImageRegistry Here's one way to use ImageRegistry. In this case, I'm just using descriptor.toString() for the key. I'm not sure whether this is the best way to deal with keys though. Any thoughts?
Martin, do you have any thoughts on whether descriptor.toString() is an appropriate key?
I've committed the change to cvs.