RouteConverter and Mac OS X

[hvdwolf]

How do you build your .app's? Is it possible to minimize the files?

Yes it is. Sorry I wasn't more specific. The zip contains the application and the icons package. The application is only the file structure shown below:

./RouteConverter.app
./RouteConverter.app/Contents
./RouteConverter.app/Contents/Info.plist
./RouteConverter.app/Contents/MacOS
./RouteConverter.app/Contents/MacOS/RouteConverter
./RouteConverter.app/Contents/Resources
./RouteConverter.app/Contents/Resources/appIcon.icns
./RouteConverter.app/Contents/Resources/AppSettings.plist
./RouteConverter.app/Contents/Resources/English.lproj
./RouteConverter.app/Contents/Resources/English.lproj/InfoPlist.strings
./RouteConverter.app/Contents/Resources/English.lproj/MainMenu.nib
./RouteConverter.app/Contents/Resources/English.lproj/MainMenu.nib/keyedobjects.nib
./RouteConverter.app/Contents/Resources/RouteConverter.jar
./RouteConverter.app/Contents/Resources/script

The icons "package" is the file RouteConverter.icns (which you already used for the new prerelease)

OSX puts some zip indexing "garbage" in a zip file as "semi-hidden" 0byte files. It allows OSX to view big, complicated zip files very fast in the file manager. I had not thought of that and it looks really weird on Linux or Windows. I should have used the command line zip. Sorry.
So all of the mentioned __MACOSX can be removed. It's waste on all other platforms.

Good hint. I think I found the bug.

I'm not sure where RouteConverter stores it's preferences and so on. I found ~/.java/.userPrefs/slash which I removed. I started the "old" Routeconverter and it generated the error and then builds(?) or indexes(?) it's conversion options. The new RouteConverter64 does not generate the error.
Did I check this correctly?

Have a look a the prereleases page :-)

Nice one.
Unfortunately the Application still doesn't start, but it does contain a nice icon

The .jar starts correctly.
I first used "java -jar RouteConverterPrereleaseMac64.jar" and it opens correctly showing the following messages (only relevant ones):

Code:

java -jar RouteConverterPrereleaseMac64.jar
***WARNING: Display must be created on main thread due to Cocoa restrictions.
java.lang.reflect.InvocationTargetException

and

Code:

slash.navigation.converter.gui.RouteConverter6.main(RouteConverter6.java:48)
Caused by: java.lang.IllegalStateException: An error occurred while creating the SWT Display! On a Mac, the Native Interface can only be initialized from the main thread and the Java process needs to be started with the "-XstartOnFirstThread" VM parameter.

As you can see it mentions the "-XstartOnFirstThread". So it starts correct but doesn't show the map.

Then I started the .jar with "java -XstartOnFirstThread -jar RouteConverterPrereleaseMac64.jar".
Now it starts correct and it does show the map.
It does show an error message: "Unable to call RouteConverter from Webbrowser via port 53465. Please check your firewall."
So I opened my firewall for that port. On restart it throws another port error. After about 6 errors in the same range I decided to open a port range in my router firewall from 53400-53999 and completely opened my Apple macbooks firewall, but this still doesn't stop the error. It keeps on generating port errors in the same 53xxx range which I already completely opened. What is this?

Other observations:
- without the map loaded I can resize the screen, which is necessary as some buttons are obscured behind the window borders. With the map loaded the application hangs when trying to resize the screen. I can resize the map/text panes inside the application using the center spacer.
- The map never fills the entire left map pane. Zooming in/out on the map does work correctly. Dragging of the map sometimes results in only half a map, or 75% map or little more, but the entire map pane is never filled.
- Right-clicking works apart from Insert/Remove
- The application now has a menu (file, Edit, View, Tools, Extra and Help). Is this new design or is it due to the now working swt?
- I do miss the handy on-screen "open" and "Save" buttons for conversion. On purpose as a design decision?

Thanks so far your work in trying to help us.