Dov Wasserman wrote: > It's a valid question in general, but since you're designing this > functionality from the ground up (and not retro-fitting it in to > existing code), wouldn't the better approach be to create a non-GUI > HList class, and a GUI subclass that adds the indicator methods? Or > even better, less tightly coupled and in line with the MVC pattern, an > HListModel class and a HListWidget class that composes an HListModel > within it.
Well, yes. But I wasn't mentioning this as "the best way" to handle this particular case; rather, I was using this particular case to illustrate the more general question. How do I remove functionality from a class or role that someone else put together? ===== Jonathan "Dataweaver" Lang __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash