Re: playing swf file
Re: playing swf file
- Subject: Re: playing swf file
- From: "Gurmit Teotia" <email@hidden>
- Date: Fri, 17 Mar 2006 20:15:28 +0530
Thank you for your reply Scott.
I'm thinking to implement WebView in Cocoa using Objective C and server
application in pure java (Without Cocoa framework object). Wherever OS
specific service is required I'll use Objective C for it.
While researching for above approach I came across Cocoa-Java bridge. But
most of the developers were complaining about it. Few of drawbacks of
Cocoa-Java Bridge pointed out were:
1. It is buggy, it crashes the application mysteriously
2. Performance penalty on application
3. Apple will not upgrade the Bridge in future.
Some other people were suggesting JNI as best option to Bridge.
Please suggest me which approach I should use:- JNI or Cocoa-Java Bridge?
As GUI is already developed in flash so I'm not concerned with look and
feel. I've analyzed my application and I'm of view that most of background
work can be done using pure java except 3-4 features, which I've outlined in
previous mail.
So I'm considering implementing system specific service in Objective C and
get called them in java using JNI. Is this approach correct?
For more information I request you to check the previous mail in same
thread. Please also look at window specific features:- Message Hooking ,API
Hooking. What can be the suggested approach for these techniques on MAC
platform?
Please help me to come to conclusion.
Thanks,
Gurmit
On 3/16/06, Scott Ellsworth <email@hidden> wrote:
>
>
> On Mar 16, 2006, at 12:25 AM, Gurmit Teotia wrote:
>
> > In other words flash is used for GUI task while C++ for background
> > job.
> >
> > Now If I consider the portability to Linux and above situations as
> > well
> > which language:- java or Objective C should be used for
> > development. I agree
> > that Cocoa related code would not be portable. Does Objective C
> > have better
> > interface with MAC OS just like C have with Windows?
>
> Cocoa is one of the two native languages of the MacOS. You can get
> at it easily from ObjC, Python, and Perl. Thus, you can get at all
> the underlying MacOS system services from Objective C.
>
> Java is well supported on the platform, so if what you want to do is
> covered by the Java API, it can work quite well. You can embed a
> Cocoa component, like a WebKit view, in a Java Swing window as well,
> so you can get at native platform features.
>
> I would thus look carefully at the Java API, and use it if it can do
> what you need. If you need substantial platform features not in Java
> or Apple's extensions, then Cocoa is the obvious choice.
>
> Really, it depends on your goals and how well they match what Java
> and Cocoa offer for the platform. Java will be cross platform, but
> if you need to drop down to the native level, that does not buy you
> much. ObjC/Cocoa is platform specific, but that makes sense for a
> single platform's implementation.
>
> Scott
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden