Re: WebObjects 5.2.4 and XCode

Hi there,

On 01/04/2006, at 7:13 PM, Denis Stanton wrote:

> On 1/04/2006, at 8:12 AM, Ricardo Saito wrote:
>
>> I tried to install the WO 5.2.4 and XCode 2.2 but had some problems
>> then  I have been told that the best combination is 5.24 and 2.0.

The best development environment (on the Xcode side of the fence)  
where the aim is to deploy to a WO5.2.4 based server imho is with  
Xcode 2.2/WO5.3.

There's no need to install WO5.2.4 on your development machine if  
you'd still like to deploy to that setup. Simply develop with Java  
1.4.2 and only refer to Java 1.4.2 & WO5.2.4 apis and everything will  
be fine. I've found the updated tools to be more stable and therefore  
more enjoyable to use.

> There is some truth in that advice. Xcode 2.1 introduced some new  
> features and was quite buggy. There is a new EOModeler plugin that  
> has been heavily criticized and most of us have chosen to avoid it  
> and keep using the older EOModeler app

There's no need to use the old EOModeler either. In fact, if you  
install WO5.3 you can't use it, period (due to framework  
dependencies). But that's fine as the WO5.3 EOModeler is better and  
its output files are still fine deploying to WO5.2.4.

> with XCode 2.1 or 2.2 which is a little tricky to do at first  
> because just clicking the model file in Xcode 2.1 and above tries  
> to open the new EOModeler module instead of the old EOModeler app.  
> I have to find my model file and drop it onto the dock icon for  
> EOModeler.app 5.3

No (as Jerry mentioned), all you need to do is change your Xcode  
"File Types" preferences to associate your preferred editor for  
*.eomodeld files. Then [double-]click as per normal.

> In my opinion Xcode 2.1 wasn't usable, but Xcode 2.2.1 is. Perhaps  
> foolishly, I prefer to move forward with the latest versions rather  
> than stick with an 'out dated' one.

I was certainly cautious about upgrading as I have projects that must  
deploy to WO5.2.4. The trick is not using the old tools ;-)

> There is another point I didn't mention. I'm using an intel iMac. I  
> can't use Xcode 2.0 on that. So my preference for Xcode 2.2.1 is  
> heavily influenced by necessity. I'm hoping they improve Xcode  
> soon, and make the good ideas introduced with 2.1 actually work  
> smoothly.

It'd certainly be nice to see reported bug fixes come down the  
pipeline a little sooner than waiting for a major update to be released.

> To sum up. you might get an easier start with Xcode 2.0, but sooner  
> or later you will move to the latest, and currently that means  
> 2.2.1.  I'm using that and I'm (mostly) happy with it.

Go directly to 2.2.1. 2.0 was buggy (e.g., crashing/stalling when  
saving from WOBuilder). I'm pretty happy with the new release. It's  
definitely better than previous releases but I must admit that there  
is some green lookin' grass

> PS. the above comments on XCode 2.1 and 2.2 problems only apply to  
> WebObjects development.  Developers working with other languages  
> may not encounter these issues.

with regards,
--

Lachlan Deck