|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
_______________________________________________So why bother with the Mac market at all, then?
We're in academia where OSX is a very large chunk of our user base. That and the fact that Windows is, of course, pure evil incarnate. ;-)
Is the firewire etc stuff currently in Java, or C++ through JNI? I'm confused about the architecture, so I hope my comments aren't too irrelevant.
We had been using javax.comm for serial port access, but so far USB is not similarly supported. We'd been using JNI for framegrabber (image digitization) stuff, but want to move to firewire. Since none of this stuff is REALLY written yet (in the form we want to use) it's just as well to write it in another language.
Are you saying you just want to convert the GUI to Cocoa, or the whole app?
The whole thing. Since the non-GUI portion is the part that's problematic, it'll be necessary. The Java GUI works great, and accessing hardware through JNI is one option, but with CW potentially jumping ship on Java and QT4Java still up in the air, PLUS the hassle of indirectly accessing hardware... it's a tough call. I've been in the Mac Java game for many years and it's been an uphill battle all the way.
since you're talking about going from one language to another, you're truthfully talking about a complete re-write of your application. Recognize your project as a complete rewrite and the end result will likely be better for it.
This kind of advice is useful, even if it's not what I wanted to hear.
Thanks to all who responded.
4D Software Engineer Laboratory for Optical and Computational Instrumentation (LOCI)
Univ. of Wisconsin-Madison
1675 Observatory Dr.
Madison, WI 53706
608-265-3083 Fax email@hidden
|>Re: Java to Cocoa? (From: Charles Thomas <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.