Mostly driven by Jarmo's request, we have just uploaded a new Swixml release
(Version 0.6)

The following class definitions were added to the Swixml tag library:
        *JFormattedTextField
        *JSlider
        *JSpinner
        *JTableHeader
However, like you know, those object's setter methods will only become
available, if there are ConverterObjects registered that would allow to
convert Strings into the setter's parameter.
To give an example, to process an XML Tag like this:

        <formattedtextfield Formatter="myformatter" .../>

one needs to have a Converter class registered that takes a String and
produces an instance of the  JFormattedTextField.AbstractFormatter class,
so that at the end this method can be invoked:

        setFormatter(JFormattedTextField.AbstractFormatter format)

Most converters are not that hard to write, take a look at the Converter
Package:

        src\org\swixml\converters

In case you are going to write some converters for the aforementioned Swing
Classes, let me know and we have them added into one of the next releases.


Concerning the requests about pre-processing and custom tags, take a
look at the samples that have been recently published on the swixml.org
site. You may especially find the "merge" and the "newtag" samples
interesting.
        http://www.swixml.org/samples


A new method:
        public Iterator getDescendants( final Component c )
was added to the SwingEngine class, allowing to iterate through all
sub-components of a container (not well tested yet!)

The setLabelFor() support was added for the label tag, again check the
sample
code on the Web site.

<label>This text will be assigned to the "Text" attribute</label> is
implemented in release 0.6
The parser will simply assign the text content of a tag to the tag's text
attribute. This however, only happens, if the tag doesn't already have an
text
attribute. Moreover, the attribute will only be processed if the widget has
a
setText(String ...) method.

Wolf

--
Wolf Paulus
MSCS, SCJP, Sr. Software Engineer



Reply via email to