On Sunday 01 April 2007 01:30:11 Michael Hall wrote:
If you're not current you might want to look at more recent releases.
I think I've noticed a fair amount of SWT compatibility work has been
going on.
I presume you mean a newer SWT? I'm using the latest stable. For
whatever
reason, I never thought to try the latest snapshot. I'll give that
a go.
You might just browse the release notes before changing to the
latest. They may make specific mention of SWT related changes.
Testing with it to see if there are any differences might be an idea
though. If it isn't a problem at that release it may be less of a
current issue for you.
How about in it's own task? A little bit involved but you could
'java' Runtime exec part of the code maybe. Somewhat recent
discussion of that could be found in the archives.
Hmm. It's a thought. So, one JVM launches and have it handle the
events from
OSX, and launches the real app using Runtime.exec() and pass
messages using
an RPC system? It sounds quite plausible. 99% of the infrastructure
to do
this is already in place (to get this kind of support on other
platforms), so
I'd just need to write the loader. This is definitely worth trying.
If you can remember some keywords or subject lines about the
discussions that
I can search for, please let me know.
http://lists.apple.com/archives/java-dev/2007/Mar/msg00335.html
Is I guess the one I was thinking of where we were (I was?) just
talking about Runtime'ing java.
But yes what I was thinking was roughly as you indicate. Normal
threading on the initial launch. That handles the OS X events and
then starts a jvm with the SWT required thread options running the
actual application code, also passing it the OS X event information
as parameters.
This would be via AppleEvent's. Ditto above 'recent discussion'
comments. Examples on my own web page that at least do this much I
would almost describe as "numerous" by now.
I'll check this out, thanks.
Or just check the com.apple.eawt documentation. It may be the same
'Application' related you were already talking about using.
Basically you have to provide a front-end before your launch that
changes the usual start up process and then turns around and launches
your 'normal' application code the way you want it.
This would work with the loader thing I describe above, I think.
You could also take a look at Steve Roy's application adapter
package. I think it has some launch time compatibility related
functionality.
I had a look at that to start with, and it didn't work. However, I
switched
pretty quickly to using the Apple classes, and it may have been
some other
issue causing it not to work. I'll have another go with it.
Thanks a lot for the suggestions (any more are quite welcome
though!), they
give me some hope that I'll be able to make this work :)
Maybe with a bit of a current work-around but I am again pretty sure
Apple has indicated on list that they have putting effort into SWT
issues so the need for the work-around may disappear at some point.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
