Re: Newbie question
Re: Newbie question
- Subject: Re: Newbie question
- From: Simon Wilson <email@hidden>
- Date: Wed, 11 Feb 2009 20:27:25 +0100
> I know C++ quite well, and for me it is more powerful, more
trustworthy and more universal.
I spent 15 years developing C++ apps for Windows so I guess I could
also claim to "know C++ quite well".
More portable it may be (providing you stick to lowest-common-
denominator GUI toolkits) but more powerful than Obj-C and IB it most
certainly isn't, assuming that your use of the term "powerful" is to
be understood as "productive" seeing as we're discussing a GUI design
tool here.
I've developed GUIs using Win32, MFC, .NET Windows Forms, VB, Swing,
AWT and SWT/Eclipse RCP and nothing comes even remotely close to IB in
terms of power and flexibility.
IB certainly isn't for everybody. If you want to develop cross-
platform apps using a single UI implementation then yes, you'll want
to steer clear of Obj-C and IB altogether.
But developers writing native Mac apps would be well advised to take
the time to get to grips both with Objective-C and Interface Builder
in order to profit from the significantly improved productivity these
tools offer over C++.
Simon
On Feb 11, 2009, at 20:08 PM, David Rowland wrote:
On Feb 11, 2009, at 10:51 AM, João Pavão wrote:
On 2009/02/11, at 18:43, David Rowland wrote:
IB is supposed to be an aid. I find it a hindrance. Its terminology
and operation amount to yet another language. You have to make that
language agree with your code. It is easier to define the things I
want in the code.
For example, I wanted a dozen buttons arranged in a circle and
responding to single and double taps. Without much trouble I was
able to write code that placed them where I wanted, made them work
as I wanted and allowed me to adjust the location and radius of the
circle. Perhaps IB could do this, but it was proving to be too much
work to learn it. My needs were simple, IB imposes a big threshold
to cross. This is only one example.
David
A very specific and somewhat contrived example, may I add. :) For
most UI development tasks IB makes your life a lot easier once you
are confortable with the basic concepts of how it works and how to
use it. Please don't put it aside as a waste of time.
All examples are specific (and contrived).
There is also a question of portability. Outside the Mac/iPhone world,
IB and Objective C are virtually useless. I use ObjC where I must, but
keep it to a minimum. I know C++ quite well, and for me it is more
powerful, more trustworthy and more universal. Using IB would entangle
me in another layer of incompatibility.
D
_______________________________________________
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
_______________________________________________
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