Steve,
Please check the samples.
This xml fragment (taken from one of the samples)
<internalframe Title="Horizontal Box" Bounds="180,170,200,180"
Visible="true" Resizable="true">
<hbox border="TitledBorder(A Titled Border)">
<button text="1"/>
<button text="2"/>
<button text="3"/>
<glue/>
<button text="4"/>
</hbox>
</internalframe>
would draw a titled border, like shown in the screenshot:
http://www.swixml.org/samples/img/layout.png
Moreover, HBox and VBox are tag names. The implementation is in XHBox
and XVBox and these already extend javax.swing.Box ...
On Dec 3, 2003, at 11:25 AM, <[EMAIL PROTECTED]> wrote:
Can you change the next version's HBox and VBox to extend JPanel
rather then Box (and use a BoxLayout), Boxes can't have Borders, but
if they were panels with a Box layout (the same thing really) then
they could. Why the Box extends Container instead of JPanel I'll
never know. It's not like the Box is that much more lightweight and
it creates another schism in the API.
-----Original Message-----
From: Wolf Paulus [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 10:36 AM
To: Forum
Subject: [Forum] Swixml 1.0.1 and new sample code
Since I don't expect everyone on this list reading my blog, here is a
short heads-up ...
Swixml 1.0.1 has been released last week. It contains a couple smaller
fixes but maybe more importantly, more sample code has been added to
the distribution and the Web site as well.
I finally got to implementing Robinson and Vorobiev's CommonLayouts
example in Swixml, which contains all commonly used LayoutManagers in a
single InternalFrame.
Wolf
_______________________________________________
Forum mailing list
Forum@carlsbadcubes.com
http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
_______________________________________________
Forum mailing list
Forum@carlsbadcubes.com
http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
