Re: Writing application without Interface Builder
Re: Writing application without Interface Builder
- Subject: Re: Writing application without Interface Builder
- From: Patrick Hartling <email@hidden>
- Date: Mon, 17 Jul 2006 21:52:12 -0500
Murat Konar wrote:
>
> On Jul 17, 2006, at 7:00 PM, Patrick Hartling wrote:
>
>> I am experimenting with writing a Cocoa application without using
>> Interface
>> Builder (for portability reasons and to educate myself)...
>
>
> I wonder if it would be churlish to ask, since you don't want to use
> Interface Builder, why bother using Objective-C/Cocoa at all? I mean
> you're going to be swimming upstream since much of Cocoa is not
> available cross-platform (presumably the other platform is GNUStep), and
> any portability advantage you get from bailing on Interface Builder will
> surely be dwarfed by the struggle to find and use the subset of Cocoa
> that is GNUStep compatible. There are cross-platform portability
> solutions available that will give you better cross-platform parity with
> less effort... even if the Mac version will not be as nice.
The other platforms are Windows and X11, so by "portability," I was
referring to a different sort of concept than reusing the Cocoa code on
other platforms. I have a very large C++ library that currently works on OS
X by leveraging X11. The end result is not up to par with other OS X
applications, IMHO, and I would like it to have a more native interface.
This software package has two layers of cross-platform portability: OS
services and windowing. The OS services have been in place for a long time;
implementing that wasn't a problem at all. What I am doing, then, is trying
to put together the windowing system-specific parts for OS X using Cocoa
through some experimentation.
> If you're real goal is the "educating" part, you're succumbing to the
> meme that graphical UI builders are somehow a crutch and a barrier to
> understanding. That might be the case for other environments, but
> Interface Builder is a integral part of Cocoa Application development,
> not a shortcut for newbies. Which is to say, if you think eschewing
> Interface Builder is a purer path to app development, you have already
> missed the point.
I would love to use Interface Builder, but I haven't been able to see how to
put it to use in this particular context. Since I am dealing with a library
that is used as the basis for applications, I might be able to make a
standard .nib file that all applications end up using. Doing so would make
sense for my purposes, I think, because end users do not add their own
interface components. Perhaps I need to keep tinkering with things from both
levels to see just which solution would work better.
-Patrick
--
Patrick L. Hartling | VP Engineering, Infiscape Corp.
PGP: http://tinyurl.com/2oum9 | http://www.infiscape.com/
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden