Sounds good to me. Just one thing, get rid of that System.exit() in the dispose method! Let the implementer decide what to do when the window containing the panel is closed.
Jim > -----Original Message----- > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 21, 2002 8:07 AM > To: [EMAIL PROTECTED] > Subject: Re: AWT Window > > > > ----- Original Message ----- > From: "IvanLatysh" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, February 21, 2002 2:53 PM > Subject: AWT Window > > > > Hello, Alistair! > > You wrote to <[EMAIL PROTECTED]> on Thu, 21 Feb 2002 > 09:26:32 -0000: > > > > AH> Now that a few more people are interested in this: > > > > AH> I think that it would be more useful if the basic AWT API > returned a > > AH> JPanel rather than a JFrame. > ... > > From my practice the best way to make this flexible is just give JPanel > without any controls. > > Just a report. And implement into this "pane" methods to switch pages, > zoom, import .... > > And, If I need preview window I will do preview by myself with > my buttons > and my style. > > I think this is right way to do it. > > Better still... give the JPanel like you propose and Actions that (if > needed) can be easily put in a toolbar. > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
