Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - Apple & non-Cocoa Java support?
Apple & non-Cocoa Java support?
 
   NeoOffice Forum Index -> NeoOffice Development
View previous topic :: View next topic  
Author Message
Waldo
Oracle


Joined: Dec 03, 2004
Posts: 239

PostPosted: Sun Jul 10, 2005 6:40 pm    Post subject: Apple & non-Cocoa Java support?

I may have missed it, but I didn't see discussion about the note at the top of this page, which reads:

Quote:
Important: Features added to Cocoa in Mac OS X versions later than 10.4 will not be added to the Cocoa-Java programming interface. Therefore, you should develop Cocoa applications using Objective-C to take advantage of existing and upcoming Cocoa features


What is this saying exactly, and will it affect Neo/J? I thought that Neo/J's Java carbon stuff needed to be rewritten as Java Cocoa stuff in the new versions of Java for future OS X Java versions > 1.3. But this note suggests that features may be missing anyway w/o Objective-C.

Thoughts? Maybe this is old news (?)

W
Back to top
OPENSTEP
The One
The One


Joined: May 25, 2003
Posts: 4752
Location: Santa Barbara, CA

PostPosted: Sun Jul 10, 2005 9:41 pm    Post subject:

CocoaJava is (well, was) a second language that could be used to interface with the Cocoa frameworks. Instead of Objective-C, it could be used with Java to write Cocoa applications using com.apple.* packages. Of course, this resulted in Java that ran only on OS X machines. CocoaJava never became really popular and suffered from a number of bugs since 10.3 even.

The Java that's used within NeoJ is "pure" Java, AWT and Java 2D at present, and perhaps some Swing in the future. Anything that's using OS X specific frameworks is written in either C++ or Obj-C. Since the majority of the application is already C++ based, we just call the frameworks directly. There's no need for us to add an extra layer with the CocoaJava language bridge and never will be.

So the impact is none since we never did nor ever planned on using it.

We're also not planning on using Cocoa, but that's another story too. Cocoa isn't suited for porting procedural widget libraries Smile

ed
Back to top
ovvldc
Captain Naiobi


Joined: Sep 13, 2004
Posts: 2352
Location: Zürich, CH

PostPosted: Sun Jul 10, 2005 11:24 pm    Post subject:

OPENSTEP wrote:
We're also not planning on using Cocoa, but that's another story too. Cocoa isn't suited for porting procedural widget libraries Smile


Waitaminute. I thought you had no choice but to go Cocoa with Java 1.4..

_________________
"What do you think of Western Civilization?"
"I think it would be a good idea!"
- Mohandas Karamchand Gandhi
Back to top
val1984
Oracle


Joined: May 30, 2005
Posts: 229
Location: France

PostPosted: Mon Jul 11, 2005 2:42 am    Post subject:

Well the 1.3.1 JVM is implemented in Carbon whereas the 1.4+ JVM is implemented in Cocoa.
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Development All times are GMT - 7 Hours
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.