FULL PRODUCT VERSION :
Not Applicable

ADDITIONAL OS VERSION INFORMATION :
All OS

A DESCRIPTION OF THE PROBLEM :
The GridBagLayout has the expanding effect on small components. This is because it calculates grid size starting with components with smallest grid count first. This means that these components wil keep getting bigger and bigger as other components sharing the same grid lines get calculated. This translates to less grid=>get more length. This makes the whole layout looks real bad and hard to adjust. The reason for the effect is that Gridbag layout put the remaining width/height to the last grid of a component after distributing the width out. When distributing the width 0 weights, there will be a large remain left, and that all goes to the last grid. Combine this and the order of calculated stated in the begining of this description, it causes the layout to be uncontrollable. Smaller grid count components get larger share. For the same grid count components, it's unknown because depending on which one get calculated first. A very flaw in the algorithm. This causes most of people view GridBagLayout as hard, because it's unhumanly hard to control all of these aspects.

Currently, the GridbagLayout calculates grid size using smallest grid size first. The problem with this algorithm is that it's hard for users to control the layout and also when 2 components with a same grid size, it's the order of the component added to the container is used. This is very award, and not even mention in the GridbagLayout. However, this order of calculation greatly impact the outcome of complex layout. My propose change is to calculate using the order of component from left to right with respect to the right most grid of each components. The same goes for vertical direction.

My suggestion is to change the GridBagLayout so that the order of calculation of gridsize is from left to right and top to bottom with respect to the right/bottom edge of the component (not left edge/top edge). I have done experiment with this extensively and know for sure that it works very well. I also suggest do a quick sort first on these component's right/bottom edge before calculation. The current method traverse with hits and miss algorithm is very primitive, and hard to read code (and O(n^2) slow).

Please look at a Netbeans issues here for more information:

http://www.netbeans.org/issues/show_bug.cgi?id=38971

Please note that regardless of the application in Netbeans, the change to GridbagLayout suggested would benefit greatly to any users using gridbaglayout because it gives them the control and predictability they need.

With recent JDK1.5, the layout pad on both sides. This causes alot of current application to be relayout. Please take this opportunity to also introduce this change so that they only need to do this once.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
In a grid bag layout with many many components, its hard to get small components to size correctly. Once they have the right size, they push each other apart because the reason above (pushing means they occupy larger area, just they visible size is small, but still takes a large area).

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -

Small components should not push other components around it away. The layout should give programmers complete control of how things get sized and position with relative to each other.

REPRODUCIBILITY :
This bug can be reproduced always.
###@###.### 10/18/04 23:16 GMT