Re: Apple's Support of WebObjects
Re: Apple's Support of WebObjects
- Subject: Re: Apple's Support of WebObjects
- From: David Holt <email@hidden>
- Date: Fri, 04 May 2007 15:23:45 -0700
Hi Mike,
Good question. I think that the only thing I have found in making the
transition to Eclipse is that you get used to a certain workflow/
workaroundflow in Xcode and it is very different from Eclipse (hardly
worth trying to change to reflect Xcode).
I also remember spending many days/weeks getting used to weird stuff
about Xcode (who hasn't run into the "space in pathname" screwing up
their build the first few times out). The biggest hurdle that I face
(d) is the confidence to know how to fix things that go wrong ("oh,
you just take the space out of the pathname") and as more and more
people make the transition, the more obvious "things that go
wrong" (TM) are getting highlighted over and over. Everything is
pretty stable on the Eclipse side too. There was a time where
updating WOLips/Eclipse involved a pretty good chance of having to go
back to a previous combination. It is also pretty clear that Eclipse
is the path going forward and uncertainty about that is minimal. That
definitely helps in the motivation department too.
Thanks!
David
On 4 May 2007, at 2:12 PM, Mike Schrag wrote:
I like the apple tools. I know WOLips and project WOnder exist
for eclipse but I do not like these tools much.
I agree with Kieran completely, but for people who just don't like
Eclipse/WOLips (compared to Xcode, specifically), what /exactly/ is
it that you don't like?
Note #1: This is NOT a question about WOBuilder, it's specifically
an Xcode vs Eclipse question.
Note #2: This is NOT intended to start a religious war, rather I'm
asking because it's possible we can fix some of the things people
don't like.
Note #3: This is in no way a commitment to fix that which you hate,
but just an informal poll for my own curiosity.
Note #4: Seriously, this is NOT a question about WOBuilder.
The things I can think of offhand:
1. Not as snappy as Xcode -- yes, i agree, but it's doing WAY
more ... probably not easily fixable, unless you can point to
SPECIFIC things that are slow.
2. No support for logical model vs physical model of project files
-- Eclipse 3.2 DOES have a logical model API, but we're not
currently using it in WOLips (and I haven't looked at how to yet).
This is on the Perpetually Increasing List of Things To Do (TM).
3. User Interface doesn't "feel OS Xish" -- This is leveled a lot,
but I'm REALLY curious to find out SPECIFICS of what people mean by
it. One of the most noticeable ones is that tabs don't look like
aqua tabs -- this is also on my list, but potentially harder to
change because Eclipse tabs can do more than aqua tabs. What else
is wonky?
4. You do Cocoa also and you don't want two IDE's -- Not much we
can do here.
Are there other specific complaints?
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden