RouteConverter and Mac OS X

[hvdwolf]

The Maven Plugin I use generates this structure:
<snip>
Let's see if I can come closer to your structure.

As far as I can judge from the "jar tf jarfile" command your mac jar contains already everything. That's why my application is so much simpler.
The Maven plugin assumes that you did not yet pack everything in the jar and checks automatically which dependencies are needed to also put in the bundle (the bundle concepts makes it possible to put "everything" in the bundle). On the other hand, the Maven plugin is not so smart that it detects that every dependency is already inside the Routeconverter jar and therefore it adds it again redundantly.

The Platypus option I used is based on the fact (my understanding) that everything was already in the jar. Once the Platypus structure has been built it is also very simple to maintain it by hand on a Linux or windows system. It only requires you to pack a new jar inside the folder structure and update two ASCII xml files for version numbers/dates and so on. I will send you the instructions once we have a good working version.

So all of the mentioned __MACOSX can be removed. It's waste on all other platforms.

But it would make sense on Mac OS X?

No, not really. OSX only uses this as some quick preview AFAIK, but it can handle every zip file. For smaller zip files, the quick view has no added value as a small zip can be interpreted fast enough.
I "normally" always use the command-line zip as I hate to put all these extra stuff into a zip. I also work on linux and at my work on windows. I don't want this rubbish inside my zips.

I didn't expect that - finally, we're doing remote debugging here with one Mac-OS-X-but-not-Java-expert at the one end and one Java-but-not-Mac-OS-X-owner at the other end. Please be patient I think we still can make progress.

I have no problem in bug-fixing and troubleshooting any further. I have been in this kind of processes many times on the other projects where I'm a real contributor for the OSX part. I'm new to RouteConverter as my pda first with TomTom and in the past 2 years with IGO8 using .kml's finally crashed after 6 years and I had to buy a new one: a Navigon 1410 using ".freshroute" as route format.

Cool. So -XstartOnFirstThread is needed.

Yes, apparently. I must have been all wrong when concluding that it had to do with X11.

Opening the firewall is generally a bad thing. But maybe you could allow that the Mac OS X browser connects to the RouteConverter process on the local loopback device (i.e. it calls http://localhost:<some port number above 1024>/...)

I don't like to open the firewall either, but I was troubleshooting. I have already closed everything again.
With regard to the localhost "thing": I need some guidance here: how do I do that, add something in my service file or so?
Also: it "auto chooses" another port at every new startup. Can you set a fixed port for this? Otherwise it will remain a moving target I'm affraid.

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.

Do you see errors on the console or inside the log?

No, it does not. Once it's hanging no new entries are added to the RouteConverter.log and neither to the systemlog nor to the OSXes "CrashReporter" logs.

- 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.

But a map is displayed? That would mean you've managed to get where noone has been before since I switched the map to Eclipse SWT.

Yes, and I'm very happy with it.

- Right-clicking works apart from Insert/Remove

There for example I need the backchannel from the browser to the Java process

- 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?

That's the new design I'm working on.

- I do miss the handy on-screen "open" and "Save" buttons for conversion. On purpose as a design decision?

I'm not sure if I use menu- and toolbar or switch to Ribbons. I had only on-screen buttons but for switching to menu- and toolbar plus context menu I have to restructure the complete action handling of the application... so I'm focusing on that since it enables me to have not just one but as many user controls for one action.

What do you think about Ribbons from the Mac OS X standpoint?

With ribbons I assume you mean the Office 2007 like feature for swt as described here?
I still have to get used to the Office 2007 ribbons menu in my daughter's and son's pcs. It's not logical to me and I keep searching for commands and options, but it can be me just being too dumm to understand it. I prefer a simple menu structure like you have now, especially as I don't foresee RouteConverter getting as many commands and options as Office 2007.
But my first wish is to get a nice working application and I will manage to adapt to every menu you throw at me.

Thanks so far your work in trying to help us.

Thank you for helping me. (You say us?)

With "us" I mean the OSX users. For delivering such a nice tool to "us", which seems to get even better in the near future for which "we" are all very grateful.

Vielen Dank.

ps: If necessary I can also participate in the german forums. I do read and understand (almost) everything. My writing is not good but that requires some flexibility from the german users.