Re: Side effect of OSX on Intel announcement
Giulio Cesare Solaroli <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Pierce, On 6/9/05, Pierce T. Wetter III <[email protected]> wrote: > > On Jun 9, 2005, at 5:45 AM, Giulio Cesare Solaroli wrote: > > > Hi Pierce, > > > > we are still using WebObjects 4.5.1 (objective-C), and we are stuck > > with Jaguar (MacOS 10.2.x). > > > > Have you been able to run any WebObjects-ObjC applications on > > Panther/Tiger too? > > Yes. Doing it right now on Tiger! You are making me an happy man!!! :-] Are you just deploying on Tiger, or also develop? > > I would be very interested in knowing how did you achieve that, as we > > are worried abount the current Apple hardware not beeing able to run > > MacOS 10.2. > > Well, we buy G5 XServes all the time, so here goes. > > At this point, we have this all in a giant tgz file we just > extract, so this is off the top of my head. > > Basically, starting from a working 10.x install of WO4.5.1P4, tar > up the following files/directories: > > Developer/Applications/EOModeler.app/ > Developer/Applications/WebObjects Builder.app/ > System/Library/Frameworks/EOAccess.framework/ > System/Library/Frameworks/EOControl.framework/ > System/Library/Frameworks/EOInterface.framework/ > System/Library/Frameworks/EOModeler.framework/ > System/Library/Frameworks/Plot.framework/ > System/Library/Frameworks/WebObjects.framework/ > System/Library/Frameworks/WOExtensions.framework/ > System/Library/PrivateFrameworks/MultiScript.framework/ > System/Library/PrivateFrameworks/XML.framework/ > System/Library/StartupItems/WebObjects/ > System/Library/StartupItems/WebObjects/StartupParameters.plist > System/Library/StartupItems/WebObjects/WebObjects > System/Library/WebObjects/Adaptors/ > System/Library/WebObjects/Applications/ > System/Library/WebObjects/Executables/ > > Basically, you need to get the two PrivateFrameworks above, and there > are a couple of .plist files in WebObjects that were missing a > trailing ';'. The 10.0 .plist parser was more flexible, the 10.1+ > complains. You can fix it by just opening it in a text editor and > adding a ; to the end of the file. > > Though if you're running on 10.2, you've probably fixed all that > already. Yes, I have got the whole list (still available if you need it). But we have not being able to run it on Panther anyway. :-( Did you eventually use the Oracle adaptor? This is the only adaptor we use. > Repeat for a deployment install instead of a developer install, > though in that case you don't need some of the above stuff. > > That's pretty much it. WO is basically a command line process, so > it doesn't depend on stuff. > > Then in your xcode projects (after upgrading them): Are you also able to use XCode!!! This is too much to bear for my soul all at once!!! :-D Don't tell me that you can still use a debugger, because I will get crazy. > The new KVC stuff ends up overriding the old WO KVC stuff, so you > have to include Foundation.framework LAST, after all the WO EOF stuff > so that WO uses the old KVC stuff instead of the new KVC stuff. I > think that happened in Panther? so that may be your problem. We will try this very soon. > The newer operating systems are also more fussy about if > "application"includes framework1, but not framework2, but framework1 > included framework2, it used to be ok. Now "application" has to > include framework2 as well if it uses it. Ok. > > For the definitive "exit" strategy we are closely looking at SOPE > > (http://sope.opengroupware.org/en/), that seems to be able to easily > > replace the WebObject.framework. For the EOF stuff things are more > > complex, but it looks like GDL2 is still under active (but not > > astonishing fast) development. > > Yeah, that's about where I was at too, its just that sope uses > GDL1... We have asked Mirko Viviani, the original author of GDL2 to integrate GDL2 with SOPE. We have and XCode project for it, but there are fuzzy problems with EOFaults that have blocked our development on MacOSX. Mirko's analysis was that the Apple's implementation of NSObject is not fully compatible with the current implementation of GLD2's EOFault class. As GDL2 still miss the Oracle adaptor, we have gave up further testing it. Thank you very much for you valuable information!! Best regards, Giulio Cesare Solaroli