I have Xcode running all the time. I personally don't care about
memory - when you have 4GB, it is not much concern. The only problem
I have is that if you quit EOModeller or WO Builder while Xcode is
running, it goes into an infinite loop (cpu to 100%) and the only way
is to force quit it. I have filed a feature enhancement to get java
as a native Xcode target so that we can do away with eclipse. The
code completion in Xcode is so much quicker than eclipse, but because
of the way WO apps get built during development makes it so slow that
it still is not worth using.
If you can put up with the above problems, then come across to tiger.
The OS is much faster than panther, but if the majority of work is in
eclipse, it may not be worth it for you. Best bet would be to get a
firewire hd and run it off that to test.
Greg
On 09/05/2005, at 2:42 PM, Brendan Duddridge wrote:
> Hi,
>
> I'm a little reluctant right now to upgrade to Tiger because the
> way I'm
> developing WebObjects with Eclipse and WOLips right now is awesome.
> I'm
> using the framework hack to get WOBuilder to see my code. I don't
> even think
> about it anymore.
>
> Now, with the move to Tiger, is the WOLips team working on some way of
> getting that functionality back? Or will we forever have to have
> Xcode 2.0
> running at all times if we want to use WOBuilder with Eclipse?
>
> I'd really like to move to Tiger, but I'm not too crazy about
> having to have
> Xcode 2.0 running all the time needlessly taking up memory.
>
>
> Thanks,
>
> ______________________________________________________________________
> ___
> Brendan Duddridge | CTO | 403-277-5591 x24 |
> brenda..lickspace.com
>
> ClickSpace Interactive Inc.
> Suite L100, 239 - 10th Ave. SE
> Calgary, AB T2G 0V9
>
> http://www.clickspace.com
>
>
>
>
This archive was generated by hypermail 2.0.0 : Mon May 09 2005 - 00:51:05 EDT