• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode workflow
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode workflow


  • Subject: Re: Xcode workflow
  • From: Christiaan Hofman <email@hidden>
  • Date: Fri, 01 Apr 2011 17:18:06 +0200


On Apr 1, 2011, at 17:02, Jean-Denis Muys wrote:


On 1 avr. 2011, at 16:45, Stephen Hershey wrote:

Xcode 3.1 supports my standard workflow:
(1) create / edit source files
(2) compile
(3) link
(4) execute / debug
(5) repeat 1..4 until satisfied

Does Xcode 4 radically depart from this model? If so, how?

Well, I don't know of any development environment which would not allow for such a high level description. From 30,000 feet, all clouds look the same. Even the terminal with TextEdit.app would fit that description.

Xcode 4 brings many improvements in a lot of areas, including project settings management. In that respect, it is very good, much better than Xcode 3.

However, it also adopts a style of window management that many of us (mainly those of us who don't come from other platforms) find a severe regression from Xcode 3: the single-window-as-the-kitchen-sink window management style. It was clearly copied from IDEs on other platforms, for example Eclipse or Visual Studio.

If you are used to matching your windows to your screen (for example maximizing your word processing window to the whole screen, as encouraged by Windows), then you probably not find that a problem.

If on the other hand, you are used to taking advantage of overlapping windows in your work, especially when developing software, then you will feel handcuffed in Xcode 4.

For details, see recent threads.

Jean-Denis

Apart from that, I would say that Xcode 4 at least encourages a modification of the above. Instead of building, it encourages you to analyze instead, and part of that process is (or can be) live. So it's now more something like:

(1) create / edit source file
(2) (live) analyze
(3) repeat 1 & 2 until satisfied
(4) compile & link
(5) execute and debug
(6) repeat 1..5 until satisfied

The obvious advantage is that you can spend more time on editing and less time on building.

Christiaan

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Xcode workflow (From: Stephen Hershey <email@hidden>)
 >Re: Xcode workflow (From: Jean-Denis Muys <email@hidden>)

  • Prev by Date: Re: Xcode workflow
  • Next by Date: Re: Xc4 memory sanity
  • Previous by thread: Re: Xcode workflow
  • Next by thread: Re: Xcode workflow
  • Index(es):
    • Date
    • Thread