Re: JGoodies Forms

Hi Steven,

> I'm new to the forum, so please excuse me for being potentially 
> redundant or just plain old ignorant.

Welcome ;-)!

> As others have mentioned, if possible, I'd also like access to code that 
> would let JGoodies Forms be used as the layout manager. We have to make 
> Java apps pretty and easy to develop! And that's where JGoodies Forms 
> comes into play. 
 > [...jgoodies ad...]

At the moment it isn't possible to extend the swixml api so that it can
handle other layout managers. But in the next few days there (hopefully)
will come out a patch that makes this possible.

> Also (let me apologize in advance if it's easy for SwiXML can do this) - 
> we need the ability to add extend the controls to do validation. For 
> example, a text field should only be numeric, and the values range from 
> 1-9999. This does not belong in your code. Java 1.5 makes this easier to 
> do, but even in 1.4 this is clearly doable with PlainDocument. I rolled 
> my own for integers, double, dates, times.

- You have full access to all defined components.
   (define <textarea id="myTextArea"/> in xml,
    define public JTextArea myTextArea; in your java code
    and manipulate myTextArea the way you want (change document, add
    listeners etc.))
   => your problem isn't a problem with SwixML

- I hope that SwixML will deliver "extensions" in the future for
   additional layout managers like TableLayout and JGoodies forms.

> Lastly - am I the only person who needs this? - I don't think the actual 
> text for a control should be inside the XML file as done now. I am not 
> an authority on XML, but my problem is that I need to support multiple 
> languages and having to create identical XML files for each language is 
> unacceptable. Why can't instead of Text="abcd" you using Text=$xxx (or 

- SwixML has full i18n-Support with java resource bundles
   see the bundle-Tag and the examples on the web page!

> whatever) and variable xxx is read from a Properties file? Not being 
> able to do something like this is a deal breaker for me - it would be so 
> painful to support. And even if one only has to support a single 
> language, let's say you have to develop an application that uses "foo" 
> for a control in 50 places, and your boss say "I want to to say 
> "foobar"", what do you do? Wouldn't it be oh so nice to change just a 
> single line in a Properties file?


regards,
Marcel Gleis
http://www.netz-profis.de