🚀 go-pugleaf

Matt Krevs wrote:

> A basic rule of thumb might be that you should definitely use the swing menu
> stuff if your are using JFrames or JDialogs as the Swing menu components are
> lightweight. If you use the AWT menus with Swing containers then you may run
> into lightweight/heavyweight problems.
>
> I'm not sure about DecoratedFrame as I have never used it.

When I use "File | New | Frame" in JBuilder it uses a DecoratedFrame

public class DecoratedFrame extends Frame implements Serializable .....

which extends

public class Frame extends Window implements MenuContainer......

This does not look like a Swing container. Does this then imply I should NOT be
placing Swing components into this container (or suffer the
heavyweight/lightweight problems)??? Am I ok if I place ONLY Swing components
into the Decorated Frame??? If I should NOT put Swing components in, what
"frame" should I be adding so that I can safely use Swing components???

Any guidance, pointing to references, etc. would be greatly appreciated.

I am trying to prototype for a fairly large application and want to get clear
what goes with what before I go generating a very big mess.

>
> I think the Swing menu components have better functionality and can be
> integrated with toolbars better.
>
> Randall J. Parr wrote in message <3677B88C.3892424B@temporal.com>...
> >I'm building a Java application using JBuilder 2.01; the application
> >can/will be "installed" on the clients with whatever JVM, etc. required
> >(IE download time not a concern).
> >
> >Should I be using ...swing.JMenuBar or java.awt.MenuBar ???
> >
> >Strong reasons for / against?
> >
> >Fully useable, debuggable, etc. within JBuilder?
> >
> >Thanks
> >R.Parr
> >
> >P.S. I have similar, general, question about using dbSwing, Swing vs
> >JBCL?
> >
> >