Well, I looked at ~/.cayenne/modeler.preferences, but it was 0 bytes in
size. I removed ~/.cayenne completely, but it still didn't use the Aqua
L&F (it did re-create the 0 byte file, though). Should I add the
Editor.lookAndFeel to the file manually? By the way, I'm using 1.1 for
this ...
Thanks!
/dev/mrg
-----Original Message-----
From: Andrus Adamchik [mailto:andru..bjectstyle.org]
Sent: Tuesday, February 17, 2004 9:31 PM
To: cayenne-use..bjectstyle.org
Subject: Re: Aqua look-and-feel?
On Feb 17, 2004, at 9:47 AM, Gentry, Michael wrote:
> Is there a way to get CayenneModeler to have the Aqua look-and-feel
> (like what is showing in the documentation). I spent over an hour
this
> past weekend trying to find the right karma for it (searching Google
> for
> command-line arguments that might affect it, etc), but failed. I was
> running on OS X 10.3 with all the latest updates (Java 1.4.2, etc).
File controlling this is "~/.cayenne/modeler.preferences". It is not
documented yet to avoid confusion, since at the moment there is plenty
of unorganized ad hoc info stored there.
The property in question is "Editor.lookAndFeel". It stores the value
defining "look and feel"
(http://java.sun.com/j2se/1.4.2/docs/api/javax/swing/LookAndFeel.html).
Its meaning changed between 1.0 and 1.1. In 1.0 it the "name" of
LookAndFeel (LookAndFeel.getName()), in 1.1 it is LookAndFeel fully
qualified Java class name. Examples:
- CayenneModeler 1.1 with default "plastic" LNF:
Editor.lookAndFeel=com.jgoodies.plaf.plastic.PlasticXPLookAndFeel
- CayenneModeler 1.0 with Windows LNF (I think, I don't have 1.0 on
Windows at the moment):
Editor.lookAndFeel=Windows
Since Aqua is default on Mac OS X, and if you are using 1.0, you should
stop the modeler, completely delete this property from
"modeler.preferences", and restart the modeler again.
> PS. I have to update modeler.bat on Windows every time I download a
new
> version of Cayenne. I'm not good with .bat files (pathetic,
actually),
> but it seems to be related to my having Java installed under "Program
> Files" and I think the space messes it up.
Somehow I am not surprised that spaces in the path can cause problems
on Windows. I am no .bat guru either, and would gladly apply patches if
anyone submits them.
Andrus
This archive was generated by hypermail 2.0.0 : Thu Feb 19 2004 - 12:48:07 EST