🚀 go-pugleaf

Hi Max,
Yes, the BoxLayout has problems with overlapping etc. Sadly, the examples I
usually find in books are pretty
basic and useless like a button(s) which covers the whole client area or text
box being big enough than needed. Avoid XYLayout also, since it can give
funny appearances when the resolution changes.

I too feel GridBagLayout is much manouverable once u learn to use it.

In general, I dont understand why we still have to bang our heads with
absolute or even relative coordinates ? Why cant we use percentages of client
area to be allocated to components. Using that we can completely forget about
screen resolutions. Are these already available in Java or not ? IMK, I found
only one such method that uses percentage, in the JSplitPanel
setDivider(float) and that didnt work too coz of a bug in swing 1.0.1.

Vasu

Max Polk wrote:

> I see the BoxLayout2, which I previously learned was a bean to support
> the BoxLayout that Sun failed to turn into a bean.
>
> But where is Box?  The Box container uses a BoxLayout, but also does nice
> things (struts and glue), as well as be a good thing for laying certain
> things out.
>
> I could not place a Box on the component palette because Swing does not
> include it as a bean, and JBCL does not encapsulate it as a bean either!
>
> I'm trying to avoid GridLayout and GridBagLayout completely (which means
> I have to avoid XYLayout as well which you are supposed to convert to
> GridBagLayout prior to deployment according to the JBuilder's developer's
> guide), and things like BorderLayout and FlowLayout are essentials.
>
> With nested panels, I can do anything with BorderLayout and
> FlowLayout.  But due to resizing considerations, I cannot use FlowLayout
> (which would wrap things when I size larger) so I need Box.
>
> Any ideas?  Any Box wrappers, like Box2 or something?  Thanks!