Re: Views on WOLips vs Xcode

WOLips is the way to go.  Nothing annoys me more than when I switch  
over to do something in Xcode.  There are so many sweet features of  
Eclipse that just don't exist in Xcode.  The first thing I did when I  
started with WO was switch over to WOLips and haven't looked back.   
The only catch is if you have other people on your team that DO use  
Xcode -- interoperability is kind of a pain.  But my solution for  
that is to have them switch to WOLips ;)

As far as WO moving forward, it may become the case that EOModeler  
goes away as a standalone app and exists only in Xcode.  If that is  
true, then you'll just have to fire up Xcode to edit your EOModel,  
and if that happens we'll just make WOLips integrate better for that  
to work smoothly.

One caveat in my statements is that I do not use WOBuilder, which  
apparently still requires some hoop-jumping with respect to Xcode.   
However, we're also actively working on making woo/wod/api/html/wo  
editing nicer in WOLips, too.

ms

On Jul 15, 2005, at 9:15 AM, Cedarstone wrote:

> Hi
>
> I am just at the early stages of learning and using WO.  I have  
> started down the WO route not least because it now comes with XCode  
> 2.1
>
> However my experience is with Eclipse and would prefer to use  
> Eclipse where possible.  As a WO newbie I would be grateful for  
> your views as to whether I should abandon Eclipse in favor of XCode  
> or should I go with WOLips and Eclipse.  In particular I am worried  
> that further integration of WO into XCode may force Eclipse  
> developers to make the switch.  Does WOLips have a future?
>
> Advice at this early stage would be much appreciated.
>
> Giles
> _______________________________________________
> WebObjects-talk mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>