Re: Releasing widget collections

Steve Lidie wrote:

> I vote for CPAN as the master repository - that's where all other Tk 
> widgets are located.  As for bundling, I'm torn here.  Generally *I* 
> do not like having to install a bundle to get at a single widget.  
> Then again, it makes your life easier ;)

I can sympathize with having to download everything to get just one 
widget, but it sure makes it easier for me to manage! ;)

How about the following case: I noticed that some of my composites 
shared some code, so I created a base class, and had each of the 
composites inherit the common methods/options. By itself, the base class 
has very limited value, however the other composites need it to function 
correctly.

Maybe it would be better to get a namespace off of Tk? Tk::RSWidget or 
something, provided that Nick approved it
that I could use as a separate directory that would contain the 
additional widgets. There's about a half a dozen or so widgets that 
would go under this directory. My new version of JComboBox is one of the 
ones that extends the base class.

Rob
-++**==--++**==--++**==--++**==--++**==--++**==--++**==
This message was posted through the Stanford campus mailing list
server.  If you wish to unsubscribe from this mailing list, send the
message body of "unsubscribe ptk" to [email protected]