no probs - that’s still cool!

__________________

-> put this banner into your own signature! <-
--
Erst im Spiel lebt der Mensch.
Nur ludantaj homoj vivas.
GnuFU.net - Gnutella For Users
Draketo.de - Shortstories, Poems, Music and strange Ideas.

I've returned the Launch function at end of installation.

With help of Yvan at Mac Scripters who put a script together for icon adding which works in Mavericks, I'm over half way there. It works with the user selecting source and destination files of the icon. I've reduced it down to user select source. With any luck I can get it to do it automatically. (I can achieve it if I know the location of the the source as this has worked in testing. If I can't script it to find its present position then I may install a temporary dummy file with the icon & remove it at the end. A sloppy approach I know.) If I can get it working all the way I'll try adding it to the installer script or alternatively calling the script from the main script (the call part works.)

cool!

__________________

-> put this banner into your own signature! <-
--
Erst im Spiel lebt der Mensch.
Nur ludantaj homoj vivas.
GnuFU.net - Gnutella For Users
Draketo.de - Shortstories, Poems, Music and strange Ideas.

It's done. The icon installs correctly. Should I upload this installer any place? It's really only needed for Mavericks (or later). Example: the Phex site as an alternative OSX download?
I can host it independently myself of course.

Phex connected fine on Mavericks. A touch slow for grabbing 5 peers but eventually 7 after about 5 mins. A couple of Phexs from the connect file.

Arne it did cross my mind to iconize the java executable but that might conflict with anybody who uses Java for other things. Also, I presume Java updates would remove that icon. Not to mention there might be multiple java versions on someone's system which would give me fun trying to script to find the right one.

7-8 months since my last scripting so I was a touch rusty.

Again, a huge thanks to Yvan of MS for the icon scripting.

Thanks for analyzing this and trying to find a way to make it work again.
I'm not sure what you did and I'm far from understanding how it works. But what I would really like to see is to use the "Apple recommended" way to build the installer. I would also make it easier to me to rebuild and distribute when there are changes.
https://developer.apple.com/library/...8447-TPXREF120

From what I read I would think the problem is the JavaApplicationStub distributed with Phex. I would be really happy if you could try to just replace the JavaApplicationStub with a updated one from Maverick.
This file should be located on your Maverick system here:
/System/Library/Frameworks/JavaVM.framework/Versions/Current/Resources/MacOS/

Basically I would like to know if Phex starts with the new Maverick JavaApplicationStub on Maverick and maybe also on older Mac OS X versions. Otherwise it may be necessary to provide two OS X builds.

Would be great if you could find this our for me. Thanks.

Gregor

__________________

Even with phex_3.4.2.116, opening via accessing the jar file from the resource folder opens fine on Mavericks. And this is same process as the one I worked with in previous posts.

I did your test and works fine in Mavericks OSX 10.9 but not for Snow Leopard OSX 10.6 (nothing happens.)
I suspect this is because of the limitation Apple puts on Java versions for each OSX, and the system java for OSX 10.7 & above were designed specifically for the later OSX's.

I don't have OSX 10.7 so cannot test on it. And upgraded 10.8 to 10.9 a month ago to see if I liked it or not (I don't.) But I could always set up other guest OS's for testing if necessary.

Likewise all my connection, etc. installers are app bundles so all I need to do is replace with updated contents & rename the app's date.

It just occurred to me, you could use a Phex installer which alternates between installing one stub or another depending on OSX version of user's system. That would save from needing two separate installers. The older stub works in OSX 10.8 (for now at least) so I guess the Mavericks stub would only be needed for OSX 10.9 or later (for now at least.) Not sure any system updates on 10.8 or even 10.7 might affect the useability of the older stub.

However the Phex snapshots archive would probably need two separate versions if they are simply zipped folders.

So what should I do to make things work again? I still don't understand... ;-)

__________________

Include the new Maverick JavaApplicationStub in the installer. Have installer do a system check condition. If OSX 10.9 or later, install the Phex app package and replace the JavaAppStub with the new Maverick JavaApplicationStub within the app package on disk.

The problem is definitely the JavaApplicationStub file not being compatible with Mavericks.

Would probably also be good to include upgraded settings such as I have in the connection installers. ie: port blocks and host file size.
My connection installers insert the text into the settings file if the properties file exists. Otherwise a fresh properties file is installed.

My Linux connection installer script includes the upgraded settings which should be readable on Windows or Linux. The following link also includes the Mavericks JavaappStub https://www.mediafire.com/folder/xbqablpc3sttu/Phex
Just discovered one of my hosting sites has recently closed down (Hotfile.) In several hours later when I get time I will shift some items to Mediafire instead. (Some items were only hosted at Hotfile, such as the LW Clone connection installer.)

* Edit: After having woken up a little more. A better approach would be for installer check system, if OSX 10.7 or later, install phex app package, then replace the JavaApplicationStub with a copy-replace of the one on that person's system. Does that sound messy to you?
Alternatively just install the application package without the stub file and duplicate the specific system's stub file & copy to the app package MacOS folder. In that way there's no replacing & no system checks.
Destination of the JavaApplicationStub would be the user's chosen location for the phex app package. Phex/Phex.app/Contents/MacOS or Phex.app/Contents/MacOS

The snapshots folder is a different kettle of fish. You might need to include two separate phex's for OSX (one with Mavericks stub file.)

An applescript app bundle installer for Phex could do this quite easily. At least for installing into the applications folder. If user choice is given for location, then that would test my skills but could be done, you probably know how. ie: save the chosen directory for using in the stub duplication process.

What I don't know however is if this stub file is a part of the OSX system or installed after Java is installed. The later OSX versions do not have java installed by default (starting from OSX 10.7 or 8, I can't remember which.) In any case, if the stub file is not found, an error message saying please install Java first before installing Phex could be added to the installer.

If my suggestions are silly, then I apologise, since I'm not educated in developing complex apps. You are the ones in the know.


Off-topic: from what I've read, the security issues with Java are with the Java browser plug-in, not apps that are programmed in Java per se. Two separate things.