On Tue, 05 Feb 2008 09:25:33 -0800, Daniel Pitts
Well, the L&F off the JFileChooser is very specific to the OS,
including which "features" it offers. So, from the API point of view,
the JFileChooser returns a set of files. From the user point of view,
the functional appearance depends greatly on the OS, as each OS has a
standard approach to the task.
Well, that's what I thought would be the case. But the JFileChooser on
the Mac is definitely _not_ dependent on the OS. It's not using any
existing OS implementation (or at least, not one I've ever seen). In
fact, one strong motivation for me going back to the AWT FileDialog
class is that the JFileChooser is so non-compliant with the Mac OS UI.
How much does the look-and-feel control? I was under the impression
that it was mainly a question of how individual controls looked, and in
some cases operated (i.e. buttons, toggle controls, etc. should all
_work_ the same on any OS, but more complex controls might vary in
subtle ways, like a combo box, list box, etc.). But it's not clear to
me whether this variability can extend all the way up to the entire
Is there some other look-and-feel that I might be able to choose that
would work more like the built-in Mac OS dialog? Or perhaps even just
use it directly?
code? That should make it act more like a Mac GUI. I usually call this