RE: [Sweet-swt-develop] Properties as Resources

[Dave O. <Da...@AS...>]

 

Whatever the solution, I think that rather than just solving Font with
FontManager, it should be generic and basically address the fact that
property values can come from other objects .... The problem here is that
you may be then getting into the issue of persistence, so right now I'm in
two minds.  Do you just reference things by value and allow static class
references, or do you allow anything more complex.  

This hits the nail on the head.  And I'll add another 2c: With SWT, aliasing
objects like this makes it hard to know if/when to generate dispose()
calls...  I don't have a good solution for this yet.  Maybe a
SWTResourceManager object that does reference counting for SWT objects and
calls dispose() at the right time...  But there are problems with this too.
 
 
Dave