• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Good news: Cocoa/EOF on Tiger...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Good news: Cocoa/EOF on Tiger...


  • Subject: Re: Good news: Cocoa/EOF on Tiger...
  • From: Florijan Stamenkovic <email@hidden>
  • Date: Mon, 6 Jun 2005 19:00:36 +0200


On Jun 06, 2005, at 18:14, Ricardo Strausz wrote:

I am not sure, of course, but what I think is that Core Data will support other kinds of persistence; in particular, I think that it is just a mater of time to Core Data to support RDB via some kind of adaptor... may be Oracle or Sybase are already working in one.

I was thinking in those lines as well as I was reading CoreData info (as it clearly states that additional adapters will become available), but at that point there was NO indication of CoreData getting into web data distribution. So, even if it does, I think it will be a painful experience at the least during the first period.



So, EOF will be part of Cocoa, but with other name and in Objective-C. If you noticed, Cocoa+Bindings works like EOInterface, Core Data like EOControl (+ EOModel and 3 adaptors) and Xcode 2 now incorporates a kind of EOModeler; we only need now to complete the EOAccess layer... if they have two fingers on top of their eyes, they should be working on that by now.

Yup, that just could be the case. I was also coming up with the idea that just maybe CoreData is a start of integrating (translating) the EOF into the system itself (because of all the similarities). But that is probably far fetched.



If your CEO app is well designed (uses MVC correctly) it should be VERY ease to incorporate such technology by the time it comes out.

What app? :)

One of our problems is that we need to have a multi-platform app, which could also have an OSX interface (CEO). So, CoreData is all good and nice, but even if it goes into distributing data online (10.5 ???), it would still mean that we (well, me actually) would have to write the same app in two APIs. In two programing languages. And to be honest, it was only a year ago that I first picked up Ivor Horton's Beginning C and learned about brackets and memory addresses.


With this approach in door, I do not think that Apple will officially support CEO... they had not since, in WO 5.0 many years ago, they decided to go "pure Java"; it is hard to think that they will change this policy unless in the very short, or the very long, term. Any how, supported or not, it is still the best approach these days to build Client/Server apps.


On the other hand, if they plan to keep around WO on OSX ---which I think they do--- they need to keep the Java Bridge in order to connect EOModeler with the DB; so, I do not see any reason to disappear CEO.

Yeah... Well, I suppose it is still an option then.

HIH Dino

All I see is more work there, and things getting complicated... :) But at least I see a bit more.


Cheers
F

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Good news: Cocoa/EOF on Tiger... (From: Ricardo Strausz <email@hidden>)

  • Prev by Date: Re: Good news: Cocoa/EOF on Tiger...
  • Next by Date: XCode 2.1 with WO 5.3
  • Previous by thread: Re: Good news: Cocoa/EOF on Tiger...
  • Next by thread: Error page displayed for one specific page.
  • Index(es):
    • Date
    • Thread