(26.08.2010, 21:50)hvdwolf Wrote: The structure of the Application now is (I removed unnecessary listing info):

Code:

ls -lR RouteConverter64.app RouteConverter64.app/Contents: Info.plist MacOS Resources RouteConverter64.app/Contents/MacOS: Java6Check.jar RouteConverterPrereleaseMac64.jar error_message.app routeconverter RouteConverter64.app/Contents/Resources: RouteConverter.icns

(26.08.2010, 21:50)hvdwolf Wrote: 1 - I wrote this simple applescript application (10 minutes work), but I don't know whether your application does shows a (graphical) error message of it's own as I can't test that right now. Does it?

(27.08.2010, 20:54)routeconverter Wrote: I've tried to reproduce this structure with the new http://www.routeconverter.de/download/RouteConverterPreleaseMac64.zip

Does that work for you?

• You spelled the routeconverter script as Routeconverter. OSX is case sensitive. As such it is not a problem, but the Info.plist file has the section
  <key>CFBundleExecutable</key>
  <string>routeconverter</string>
  If you prefer the script to be called Routeconverter or RouteConverter (or whatever), the CFBundleExecutable string in the Info.plist file should be the same.
  
• The script should have the executable bit set and it didn't. When committing from OSX/BSD/Linux and so on to svn/cvs/git/mercurial and so on, the file attributes are maintained. I don't know how this works from Windows for un*x like files.
  
• I assume you copy/pasted my posted shell script entries into some text editor and saved it. Windows adds it own line ends/line feeds. For text files that's no big deal but it corrupts the shell script which makes that it doesn't work even when the file attributes have been set correctly.
  

(27.08.2010, 20:54)routeconverter Wrote:

(26.08.2010, 21:50)hvdwolf Wrote: 1 - I wrote this simple applescript application (10 minutes work), but I don't know whether your application does shows a (graphical) error message of it's own as I can't test that right now. Does it?

Yes, it does.

(28.08.2010, 12:28)hvdwolf Wrote: The structure as such is correct, but:

• You spelled the routeconverter script as Routeconverter. OSX is case sensitive. As such it is not a problem, but the Info.plist file has the section
  <key>CFBundleExecutable</key>
  <string>routeconverter</string>
  If you prefer the script to be called Routeconverter or RouteConverter (or whatever), the CFBundleExecutable string in the Info.plist file should be the same.

(29.08.2010, 12:15)routeconverter Wrote: I wanted the script called "RouteConverter" and in the downloaded ZIP the

<key>CFBundleExecutable</key>
<string>RouteConverter</string>

matches the MacOS/RouteConverter script. What went wrong there?

(29.08.2010, 13:53)hvdwolf Wrote: I downloaded the zip again and you are right. Probably I made an error. Sorry.

(29.08.2010, 13:53)hvdwolf Wrote: Your Java6Check.jar works fine and so does my script.

(28.08.2010, 12:28)hvdwolf Wrote: The structure as such is correct, but:

• You spelled the routeconverter script as Routeconverter. OSX is case sensitive. As such it is not a problem, but the Info.plist file has the section
  <key>CFBundleExecutable</key>
  <string>routeconverter</string>
  If you prefer the script to be called Routeconverter or RouteConverter (or whatever), the CFBundleExecutable string in the Info.plist file should be the same.
  
• The script should have the executable bit set and it didn't. When committing from OSX/BSD/Linux and so on to svn/cvs/git/mercurial and so on, the file attributes are maintained. I don't know how this works from Windows for un*x like files.
  
• I assume you copy/pasted my posted shell script entries into some text editor and saved it. Windows adds it own line ends/line feeds. For text files that's no big deal but it corrupts the shell script which makes that it doesn't work even when the file attributes have been set correctly.
  

But we are almost there.

(29.08.2010, 20:26)routeconverter Wrote: Please try http://www.routeconverter.de/download/RouteConverterPreleaseMac64.zip again.

And btw, I've verified that Java6Check.jar works with Java 1.4.2 on Windows and that it shows a dialog if the version is not Java 1.6

(29.08.2010, 20:51)hvdwolf Wrote: I can't download from the post (just like the previous) but I downloaded from the PreReleases page.
It opens so your Application bundle now works. Congratulations.

(29.08.2010, 20:51)hvdwolf Wrote: One other remark: The last 2 prereleases don't contain a menu. Not the application and neither the jar.

(29.08.2010, 21:25)routeconverter Wrote: Will revert that.

Quote:com.apple.mrj.application.apple.menu.about.name
Sets the application name that is displayed in the application menu and in the Dock.

This property take a string of text as an argument. For example, java -Dcom.apple.mrj.application.apple.menu.about.name="Application Name" yourApplication.


apple.laf.useScreenMenuBar
If you are using the Aqua look and feel, this puts Swing menus in the Mac OS X menu bar. Note that JMenuBars in JDialogs are not moved to the Mac OS X menu bar.

The default value is false. Java applications created with Project Builder have this set to true.


apple.awt.showGrowBox
Most native Mac OS X windows have a resize control in the bottom right corner. By default, Java application windows that use the Aqua look and feel have the functionality of this control, but there is no user interface cue that it is there. This flag causes the resize control to be displayed.

The default value is false.


apple.awt.brushMetalLook
This flag allows you to display your main windows with the “textured” Aqua window appearance. This should only be applied to the primary application window, and should not affect supporting windows like dialogs or preference windows.

The default value is false.

(30.08.2010, 07:45)routeconverter Wrote: Although it looked pretty reasonable to set these flags
http://developer.apple.com/mac/library/releasenotes/Java/java141/system_properties/system_properties.html

Or do I miss something?