🚀 go-pugleaf

On 12/15/2003 at 9:42:35 PM, Jacklondon Chen wrote:

> In most case, we have to write a subclass of ComboBoxModel or just 
> use DefaultComboBoxModel.

I think you have the basic idea, but I have some problems with how you
describe interfaces.  You do not write a *subclass* of ComboBoxModel,
since it is an interface, not an abstract class.  You can *implement*
an interface, not *subclass* it.

> I think a good way is that sun give some tools good for simple
> application, others good for complex application.
> 
> for example, In most case, we use JComboBox for add string data and
> show and select. Sun can give a new class for this case:
> 
> 
> //--------------------------------------------------------------------
> ------ ------------------------------------>
> public class JSimpleComboBox extends JComboBox {
> 
>   public JSimpleComboBox() {
>     super(new DefaultComboBoxModel());
>   }
> 
>   public void addElement(Object obj) {
>     DefaultComboBoxModel dataModel = (DefaultComboBoxModel)
> getModel();     dataModel.addElement(obj);
>   }
> 
> }
> //<-------------------------------------------------------------------
> ------ -------------------------------------
> 
> I think in this way, programmer no need to write subclass of
> ComboBoxModel each time. It's good for simple application.

There is no need to write a subclass of ComboBoxModel (or of JComboBox)
each time.  I do not see any functionality provided by the above code
that is not provided by the JComboBox superclass.

-- 
Regards,

John McGrath [TeamB]

---------------------------------------------------
Before sending me e-mail, please read:
    http://www.JPMcGrath.net/newsgroups/e-mail.html