Roland said:
If you can use IB, use it. If you can't use it, try one last time to use it,
>then do it another way. That's what I think at least.
Ken said:
>I would say that you should use IB until you hit a case where you
>can't achieve what you want, or at least can't achieve it
>"comfortably". Of course, build a UI in code is "acceptable", it just
>usually unnecessary.
Good enough for me. I would use the equivalent [to IB] for MFC dialogs,
VB forms and now .NET forms, so I'll use it for Mac / iOS apps.
Admittedly I never use a visual builder for Java, but I never really got
on with the ones available (NetBeans was one I tried, as I recall).
I did struggle with connectors & outlets with IB - seemed an awful lot
of work to go to just to add a handler for a button click (I miss the
days where I could right-click the control and say 'Add Handler' or
simply double-click it), and every single tutorial I found on the net
failed to work - but after a bit of perseverance I finally got a handler
in there (it seems I have to manually add the IBOutlet declaration to
the controller's .h file before IB will let me drag the connector to it
- is that normal? I kind of expected to at least be able to get IB to
create an outlet for me that I could then drag to).
Onward and upward, as they say...
Regards,
--
Jason Teagle
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
