Re: Views on WOLips vs Xcode

If you're developing on any platform other than Mac (Windows) you have 
to use WOLips, and then you have no WOBuilder or EOModeler. Will it even 
be possible/legal to develop and/or deploy on windows in the future?

I noticed that WOLips had some kind of revival the last couple of weeks. 
This strikes me as odd. At first I was very happy about WO5.3, but soon 
I realized WO is becoming a Mac only product. My development machine is 
a Mac, but I have no intention to build Java server applications that 
can only run on Mac, and I will never ever tell any client they have to 
buy a Mac (to run my apps).

I’ve begun looking at Hibernate, Tapestry and Spring. I have a strong 
feeling my next project will use some or all of these.

/Anders

Mike Schrag wrote:
> The downside being that once the kinks are worked out, the new  
> eomodeler in Xcode looks like it's going to be really cool :)
> 
> On Jul 15, 2005, at 9:46 AM, Geoff Hopson wrote:
> 
>> What would be super-kewl would be if CayenneModeler could be enticed
>> to save out eomodeld folders/files. It already reads them in, so there
>> must be a way if there is a motivation.
>>
>>
>> On 15/07/05, Mike Schrag <[email protected]> wrote:
>>
>>> 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
>>>>
>>>>
>>>
>>> _______________________________________________
>>> WebObjects-talk mailing list
>>> [email protected]
>>> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>>>
>>