On Nov 17, 2008, at 1:59 PM, Kyle Sluder wrote:
Why does everyone new to the platform want to immediately discard IB?
It is the correct (yes, "correct", not "preferred", not "easiest", but
*correct*) way to implement your interface.
I think a quote from Aaron Hillegass is appropriate here:
"E
On Mon, Nov 17, 2008 at 7:07 PM, j o a r <[EMAIL PROTECTED]> wrote:
> I know of one thing that's currently difficult to do in code: Setting up the
> main menu.
This would be what I'm referring to. But the main menu is very
important; it includes things like the Services menu, Recent Files
functio
Dear Cocoa-Dev,
// You should use IB whenever and wherever you can //
It's often the case that developers new to the platform think that
they have to write their UI in code. Perhaps because UI design tools
on other platforms doesn't work as well as they should? Please note
that Cocoa devel
On Nov 17, 2008, at 6:53 PM, Andy Lee wrote:
On Nov 17, 2008, at 6:23 PM, Kyle Sluder wrote:
I'm wondering if Apple's doing a good enough job explaining how IB is
different from UI code generators and why it is important that one
use
it.
I think this is a good question. Maybe it'd be wor
On Nov 17, 2008, at 6:19 PM, Kyle Sluder wrote:
On Mon, Nov 17, 2008 at 5:25 PM, Brian Stern
<[EMAIL PROTECTED]> wrote:
I can tell you that the majority of iPhone developers are refusing
to use
IB. The reasons I usually see are
I didn't get the implication that the OP was doing iPhone de
On Nov 17, 2008, at 4:02 PM, Kyle Sluder wrote:
My point is that this isn't the case. Avoiding IB has been shown to
introduce subtle bugs.
Like what?
I know of one thing that's currently difficult to do in code: Setting
up the main menu. Difficult yes, but not impossible. Should this be
On Mon, Nov 17, 2008 at 6:54 PM, j o a r <[EMAIL PROTECTED]> wrote:
> I don't agree that it's somehow more important for Cocoa developers to use
> an UI design tool, compared to developers using other development
> environments. Cocoa developers, much like developers on other platforms, can
> alway
On Mon, Nov 17, 2008 at 3:53 PM, Andy Lee <[EMAIL PROTECTED]> wrote:
> There's no way to generate a text dump that you can eyeball.
Can generate XML that you can eyeball or transform into something more
readable... (not ideal but better then nothing)
ibtool --connections /Developer/Examples/Quar
On Nov 17, 2008, at 3:23 PM, Kyle Sluder wrote:
I'm wondering if Apple's doing a good enough job explaining how IB is
different from UI code generators and why it is important that one use
it.
I don't agree that it's somehow more important for Cocoa developers to
use an UI design tool, com
On Nov 17, 2008, at 6:23 PM, Kyle Sluder wrote:
I'm wondering if Apple's doing a good enough job explaining how IB is
different from UI code generators and why it is important that one use
it.
I think this is a good question. Maybe it'd be worth having a WWDC
session dedicated to clearing th
On Mon, Nov 17, 2008 at 6:17 PM, macdev <[EMAIL PROTECTED]> wrote:
> I guess 10+ years of developing in one platform pretty much shapes the way
> one thinks about "how to build and write code". Learning to think like a Mac
> developer is the hardest part so far...
It very much does, and I don't me
On Mon, Nov 17, 2008 at 5:25 PM, Brian Stern <[EMAIL PROTECTED]> wrote:
> I can tell you that the majority of iPhone developers are refusing to use
> IB. The reasons I usually see are
I didn't get the implication that the OP was doing iPhone development.
In fact, I'd be very surprised if he were
> mistakes. So it's really not a recommended technique. I understand
> that what you're describing is what you're used to. You need to
> understand that what you're used to isn't even close to optimal for
> this platform.
I guess 10+ years of developing in one platform pretty much shapes the way
o
That's an interesting question. We use IB where we can on the iPhone
and frankly we can use it a lot. Most of Apple's samples were redone
to use IB when IB for iPhone became usable. Yes, there are many
reasons to do things in code, but there are many to use IB. Its a
balance. Using IB cuts
On Nov 17, 2008, at 4:59 PM, Kyle Sluder wrote:
Why does everyone new to the platform want to immediately discard IB?
It is the correct (yes, "correct", not "preferred", not "easiest", but
*correct*) way to implement your interface.
I can tell you that the majority of iPhone developers are re
On Mon, Nov 17, 2008 at 7:49 AM, macdev <[EMAIL PROTECTED]> wrote:
> I am migrating from PC/.NET development and I am very new to Xcode/IB/Cocoa.
> I was wondering if I could generate GUIs using code without the need to use
> the IB.
Why does everyone new to the platform want to immediately disca
Just create a NIB with a main menu that's mostly blank except for the
menu, and programmatically do the rest of the GUI. You can
create all windows, add menus, etc.. all programatically.
On Nov 17, 2008, at 6:49 AM, macdev wrote:
I am migrating from PC/.NET development and I am very new to X
17 matches
Mail list logo
