Re: Changing JFrame components at runtime
- From: "Andrew Thompson" <andrewthommo@xxxxxxxxx>
- Date: 24 Sep 2006 21:01:55 -0700
Lionel wrote:
Andrew Thompson wrote:
lego_lax wrote:
Which IDE are you (mis)using?Netbeans, but I'm not using GUI designer.
Avoiding the GUI designer is probably best,
until you get a good working knowledge of
Java layouts and general GUI techniques.
Isn't it always?
I don't *think* so, but have never had an opportunity to
prove that theory.
The thing is, if for example, you need to churn out
...dozens of GUI elements according to relatively
simple principles, for a single system, and assuming
you can lock in Java version and font sizes (probably
forgotten a couple of things).. the GUI designers
can be more productive.
I have never had much luck with GUI designers myself,
but feel they are gradually getting better, occasionally
check in them to see if I can make them work for me,
and do wish there were some way to design rugged
X-Plat GUI's by 'Drag & Drop'.
...Every time I get the idea that maybe I can do something
faster in a gui designer I end up kicking myself and going back and
writing it by hand.
I feel as though Gui designers hide information from me, and they all
seem to store information in some other file which I assume probably
won't port to well . . . just my thoughts.
NetBeans uses an XML description. I have also
worked with the SaverBeans screensaver project,
where our saver config. files are the same definition
of XML used by XScreenSaver.
A couple of notes about the XSS UI description files
and why I *like* them.
1) They are rendered by both CPP and Java
components, but the developer and end user
of a screensaver can view/edit them in a
plain text editor.
2) They are generally more terse (pre java
compilation - at least) than the equivalent Java.
1 general class (of around 20Kb) to render the GUI's
and hundreds of XML descirptions (around 2-3Kb each)
is ultimately smaller in bytes than the equivalent pure
Java classes.
3) Being XML, they are easily open to analysis/verification
by XSD (which can check UI layout) and XSLT (for
creating deployment web pages, webstart JNLP files..)
I am not inherently against using some way outside
core Java to store UI descriptions, it can have its
advantages, but I think it comes back to whether
the XML is 'portable' as you mentioned, and *rugged*
(to different system settings and user preferences).
Hopefully one of the NetBeans GUI designer gurus
will pop by and clarify where NB stands in relation
to portability of the XML descriptons ( and if so, at
what cost in bytes to the end user ;)
Andrew T.
.
- References:
- Changing JFrame components at runtime
- From: lego_lax
- Re: Changing JFrame components at runtime
- From: Andrew Thompson
- Re: Changing JFrame components at runtime
- From: lego_lax
- Re: Changing JFrame components at runtime
- From: Andrew Thompson
- Re: Changing JFrame components at runtime
- From: Lionel
- Changing JFrame components at runtime
- Prev by Date: Re: Changing JFrame components at runtime
- Next by Date: A Simple jTextPane Problem
- Previous by thread: Re: Changing JFrame components at runtime
- Next by thread: Re: Changing JFrame components at runtime
- Index(es):
Relevant Pages
|
|
