FROM : Rémy Schumm
DATE : Tue Apr 05 10:13:16 2005
Hi Scott
finally somebody who answers, thank you!
seems that nobody does Java Cocoa...
Yes, that's usually what we can read if asking something about Cocoa
Java: "Do it in ObjC." And yes, you're right, ObjC is not as
complicated and a very beautiful language.
And yes, you're right: the documentation for Cocoa Java is bad,
Java-integration in XCode is "forthcoming", and it is often more easy
to do Cocoa in ObjC.
But the point is:
- my business logic is Java and I don't want to rewrite it in ObjC. So
are all my other skills like XML processing, WebService consumption,
Database Access, Threading etc. etc. and it would take _very_ long to
translate this all to ObjC.
- Apple does provide Cocoa Java: so why not use it?
- Cocoa Java does work well expect some limitations in functionality
and documentation, and, as said, in Cocoa binding.
- The ObjC-Java-Bridge (is it that what you mean? or how can I access
Java Object in ObjC) is "legacy". Why? Does it mean it will not work in
future?
greetings from switzerland
Rémy
Am 04.04.2005 um 21:48 schrieb Scott Stevenson:
> On Apr 4, 2005, at 2:32 AM, Rémy Schumm wrote:
>
>> combining a post of Scott Anguish and very lots of trying of myself
>> lead me to the conclusion:
>>
>> something as simple as [contentObject setTheString:@"Guten Tag"]; in
>> ObjC which will perfectly update the NSTextField which is bound to
>> the property "theString" will NOT work in Java, because KVO does not
>> work in Java, neither automatically nor manually.
>
> Java is always going to play second fiddle to Objective-C because
> Cocoa takes advantage of language features that Java doesn't have.
>
> Add to that:
>
> 1. Virtually all Cocoa code is in Objective-C
> 2. Objective-C is really easy to learn if you know Java
> 3. Objective-C provides access to Java code
>
> Java is a good language, but you're making things way too hard on
> yourself by using it for Cocoa apps. This is especially true if you're
> new to Cocoa.
>
> If you simply can't use Objective-C for some reason, you might
> consider PyObjC, which allows you to write Cocoa apps in Python.
>
>
> - Scott
--
Zürcher Hochschule Winterthur - ZHW
(Zurich University of Applied Science Winterthur, Switzerland)
Rémy Schumm, ZHW - T, E222, Postfach 805, 8401 Winterthur
dipl. Ing. FH, Assistent Softwareentwicklung, Dept. T,
tel. direkt +41 52 2677 490 gsm/mms/sms +41 79 21 1234 1
http://www.zhwin.ch/~smr - PGP ID 0x59BA4E81 - Mac OS X Panther on G5
Content Security by MailMarshal
DATE : Tue Apr 05 10:13:16 2005
Hi Scott
finally somebody who answers, thank you!
seems that nobody does Java Cocoa...
Yes, that's usually what we can read if asking something about Cocoa
Java: "Do it in ObjC." And yes, you're right, ObjC is not as
complicated and a very beautiful language.
And yes, you're right: the documentation for Cocoa Java is bad,
Java-integration in XCode is "forthcoming", and it is often more easy
to do Cocoa in ObjC.
But the point is:
- my business logic is Java and I don't want to rewrite it in ObjC. So
are all my other skills like XML processing, WebService consumption,
Database Access, Threading etc. etc. and it would take _very_ long to
translate this all to ObjC.
- Apple does provide Cocoa Java: so why not use it?
- Cocoa Java does work well expect some limitations in functionality
and documentation, and, as said, in Cocoa binding.
- The ObjC-Java-Bridge (is it that what you mean? or how can I access
Java Object in ObjC) is "legacy". Why? Does it mean it will not work in
future?
greetings from switzerland
Rémy
Am 04.04.2005 um 21:48 schrieb Scott Stevenson:
> On Apr 4, 2005, at 2:32 AM, Rémy Schumm wrote:
>
>> combining a post of Scott Anguish and very lots of trying of myself
>> lead me to the conclusion:
>>
>> something as simple as [contentObject setTheString:@"Guten Tag"]; in
>> ObjC which will perfectly update the NSTextField which is bound to
>> the property "theString" will NOT work in Java, because KVO does not
>> work in Java, neither automatically nor manually.
>
> Java is always going to play second fiddle to Objective-C because
> Cocoa takes advantage of language features that Java doesn't have.
>
> Add to that:
>
> 1. Virtually all Cocoa code is in Objective-C
> 2. Objective-C is really easy to learn if you know Java
> 3. Objective-C provides access to Java code
>
> Java is a good language, but you're making things way too hard on
> yourself by using it for Cocoa apps. This is especially true if you're
> new to Cocoa.
>
> If you simply can't use Objective-C for some reason, you might
> consider PyObjC, which allows you to write Cocoa apps in Python.
>
>
> - Scott
--
Zürcher Hochschule Winterthur - ZHW
(Zurich University of Applied Science Winterthur, Switzerland)
Rémy Schumm, ZHW - T, E222, Postfach 805, 8401 Winterthur
dipl. Ing. FH, Assistent Softwareentwicklung, Dept. T,
tel. direkt +41 52 2677 490 gsm/mms/sms +41 79 21 1234 1
http://www.zhwin.ch/~smr - PGP ID 0x59BA4E81 - Mac OS X Panther on G5
Content Security by MailMarshal
| Related mails | Author | Date |
|---|---|---|
| Rémy Schumm | Apr 4, 11:32 | |
| Scott Stevenson | Apr 4, 21:48 | |
| Rémy Schumm | Apr 5, 10:13 | |
| Jake Macmullin | Apr 6, 01:19 |






Cocoa mail archive

