🚀 go-pugleaf

William Yu wrote in message <35A51F85.7783B76E@Bigfoot.com>...
>Let's say you want to create AWT components that are reusable. You can't
>inherit directly from ObjectPool; otherwise, the components would no
>longer be usable.


You <could> have an AWTTextField object pool, a AWTTextArea pool, etc... why
not?  You do this my making specific pools for holding these object types by
inheriting directly from your abstract pool for each kind.

>I think I was going beyond the idea of simply inheriting reuse
>behaviors. Let's say you want to reuse a whole wide range of objects
>from AWT components to Date/Font/Color/etc. but you don't want to write
>a wrapper class for everything. Rather, have a static recycler class
>that anybody could use. (I've been looking this left and right and it
>may be unfeasible.)

I would have to say that pool reuse should be specific to types, not to
types&specific-properties.  I mean, it could be feasible if you had limited
values, but this would'nt be a very scaleable solution in my mind.  I would
reuse the types, then set the desired properties for the particular context
for which they will be used.  It's ok to get a TextField with a blue
background from the pool.... if you need it to have a red background in the
particular context, then change it to red after checking it out.


Gerry Mantha