OTOH, after having looked at this:
http://java.sun.com/docs/books/tutorial/uiswing/layout/spring.html
I think that SpringPane may be a bit too complicated for Pivot:
"SpringLayout is...very low-level and as such you really should only
use it with a GUI builder, rather than attempting to code a spring
layout manager by hand."
Pivot may one day support a GUI builder, but you should still always
be able to code your UI by hand using WTKX (or Java). Since TablePane
already does what you describe, a SpringPane container may just be
superfluous.
G
On Aug 6, 2009, at 8:37 AM, Greg Brown wrote:
TablePane facilitates this behavior.
You guys are sooooo HTML oriented :-)
Yeah. That's intentional. :-) HTML is good for layout, and most
developers are familiar with it. Tables are great for a lot of
different layout requirements, and AWT/Swing has never provided one
that is really easy to use. We wanted to make sure that we brought
HTML's ease of tabular layout to Pivot.
Could I recommend you to take a stab at trying the GUI designer in
IDEA?? Springs are really neat.
I'm familiar with SpringLayout, though I have never actually used it
myself. We have lots of other container classes that parallel AWT
layout managers, so adding SpringPane would not be a stretch.
Feel free to enter a JIRA ticket for it (and assign it to yourself
as well, if desired). :-)
