one of the most notorious of the layout managers in Java
in fact for many developers it symbolizes the failure of the layout manager concept. That is the main reason why we never added it.
Last week I had a very interesting conversation with a very prominent Swing developer
and he asked me whether we had gridbag support. I answered that we do not and repeated the regular “no one likes it” line, turns out he does like it and has a lot of Swing code that uses GridBag!
Porting a Swing/AWT layout manager to Codename One is pretty close to trivial, there are very few things you need to actually change.
Codename One doesn’t have Insets, I added some support for them in order to port gridbag but components in Codename One have a Margin they need to consider instead of the insets (the padding is in the preferred size).
AWT layout managers also synchronize a lot on the AWT thread. This is no longer necessary since Codename One is single threaded like Swing.
Components are positioned relatively to container so the layout code can start at 0, 0 (otherwise it will be slightly offset).
Other than those things its mostly just fixing method signatures and import statements which are slightly different. Pretty trivial stuff and GridBagLayout from project Harmony is now working on Codename One.
So to show this off I
took this code from the Java tutorial
and ported it to Codename One, pretty easy stuff:
Now this stuff probably won’t make it into the GUI builder in the forseeable future, but if you are hellbent on GridBag or porting some Swing code this should be pretty convenient. Its also a great case study if you want to port some of your other favorite layout managers such as MiG or FormLayout.
Notice: This post was automatically converted using a script from an older blogging system. Some elements might not have come out as intended…. If that is the case please let us know via the comments section below.