Re: Views on WOLips vs Xcode

Really depends on the development platform you are going to use.

For example if you are the sole developer developing on OS X then it 
makes sense to stick to Xcode - you might even have a better user 
experience on OS X using Xcode.

If you're working on a larger project where you have some developers 
working on Windows, maybe some using Linux then you really have no 
choice but to use eclipse with wolips.

We do WebObjects training and we've always trained using Xcode / OS X.  
For our last class we updated all of our training materials to work 
with Eclipse / WOLips (running on Windows) and it was very well 
received.

-shehryar

On Jul 15, 2005, at 7:21 AM, Mike Schrag wrote:

> As far as learning curve, I think a lot of it is just Eclipse learning 
> curve -- it definitely has a unique way of handling developer 
> workflow.  Once you're comfortable with Eclipse in general, though, I 
> think you'll find WOLips to make total sense.  I didn't have any 
> trouble (that I can remember) using WOLips coming from a background 
> where I used Eclipse for several years (well, save the occasional 
> WOLips bug -- but the latest cvs builds fix almost all the things I 
> used to run into).  From my perspective, Xcode has the steeper 
> learning curve ...  I can never find anything I'm looking for -- which 
> is pretty much what Eclipse newbies says, too, so I think it's just 
> what you're familiar with.
>
> If you do go the WOLips way, I would recommend getting on the WOLips 
> mailing list and definitely file bugs/complaints/requests.  And Ye 
> Newe WOLips Wiki -- http://objectstyle.org/confluence/display/WOL/Home 
> .
>
> ms
>
> On Jul 15, 2005, at 9:59 AM, Paul Lynch wrote:
>
>> I mainly use Xcode, not Eclipse, although I have both installed - my 
>> motivation being that I teach the Apple WO class every few weeks, and 
>> I want to stay very close to the standard used for the course. If you 
>> decide to use Xcode, it is currently better to use Xcode 2.0 rather 
>> than 2.1, because of the bugs related to WOBuilder, as Mike and Geoff 
>> have noted.  It is also conceivable that, at some point in the 
>> future, Apple will do something that gives Xcode a compelling 
>> advantage over Xcode - I am not suggesting that they will, just that 
>> it is prudent to consider that.  If so, it won't be for some time.
>>
>> If you are already familiar and comfortable with Eclipse, stick with 
>> it.  WOLips has its own, steeper, learning curve, compared to Xcode, 
>> but it has a lot of advantages to compensate for that.
>>
>> Good luck.
>>
>> Paul
>>
>>
>> On 15 Jul 2005, at 14:15, 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
>>>
>>>
>>>
>>
>> _______________________________________________
>> WebObjects-talk mailing list
>> [email protected]
>> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>>
>
> _______________________________________________
> WebObjects-talk mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>