Thank you all very much, it is much clearer to me now. I'm diving into
documentation now...
___
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-a
I feel that there should be a long blog +video post that new devs
should be pointed to everytime this question(view/bad choice) crops up
that keeps all of the details of the many emails points that could be
like an Apple best of doc.
I know for sure that I have gone that route as well and still ne
On May 2, 2012, at 6:19 AM, ecir hana wrote:
> - I saw that Xcode named the Info.plist differently (it prepends my project
> name to it) - is it ok just to call it Info.plist? Is there any convention?
Xcode is actually prepending the target name, not the project name: A project
can have multipl
On May 2, 2012, at 6:19 AM, ecir hana wrote:
> As I said above, I don't want the question to be whether I should better
> use NIBs, or whether Cocoa is more suitable than assembler. I somewhat know
> already what the role of NIB is, that it can save time and so on. What I
> would like to know is
On May 2, 2012, at 7:19 AM, ecir hana wrote:
> - I saw that Xcode named the Info.plist differently (it prepends my project
> name to it) - is it ok just to call it Info.plist? Is there any convention?
https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPRuntimeConfig/Article
Thank you all for the replies!
As I said above, I don't want the question to be whether I should better
use NIBs, or whether Cocoa is more suitable than assembler. I somewhat know
already what the role of NIB is, that it can save time and so on. What I
would like to know is what to do if I was not
On 1 May 2012, at 20:46, Wade Tregaskis wrote:
>
> Actually, there are a lot of commercial developers who hard-code their entire
> UIs. I'm at something of a loss to see why myself, but they do it, and they
> swear it's the best way. Ironically, one of the reasons often given is
> "easier int
On May 1, 2012, at 12:46 PM, Wade Tregaskis wrote:
> Actually, there are a lot of commercial developers who hard-code their entire
> UIs. I'm at something of a loss to see why myself, but they do it, and they
> swear it's the best way. Ironically, one of the reasons often given is
> "easier
> Unlike other graphical UI layout tools, Interface Builder is central to Cocoa
> development, not simply a shortcut for newbies or a way to get started
> quickly. Anyone who thinks developing without Interface Builder is a purer
> path to understanding Cocoa has already missed the point.
Actua
On May 1, 2012, at 8:50 AM, Fritz Anderson wrote:
> NIBs _are_ how it works. They don't contain or generate code. They don't
> contain or generate scripts. They don't exercise much of the API you're
> trying to use. They contain archived objects and their connections.
True, but the beginner may
What Fritz said.
Unlike other graphical UI layout tools, Interface Builder is central to Cocoa
development, not simply a shortcut for newbies or a way to get started quickly.
Anyone who thinks developing without Interface Builder is a purer path to
understanding Cocoa has already missed the poi
On 1 May 2012, at 2:28 AM, ecir hana wrote:
> If nothing else, it would explain to me how things works, 20 lines of
> code would help me better than 20 documentation pages. There tutorials
> above certainly did the explaining very well.
Every few months, a beginner comes who wants to skip NIBs to
On May 1, 2012, at 12:28 AM, ecir hana wrote:
> If nothing else, it would explain to me how things works, 20 lines of
> code would help me better than 20 documentation pages. There tutorials
> above certainly did the explaining very well.
But it won't teach you how document-based Cocoa apps are a
On 29 Apr 2012, at 22:47, ecir hana wrote:
> Dear list,
>
> I'm trying to understand how the things in Cocoa works but I'm
> struggling with one thing. I saw
> http://cocoawithlove.com/2010/09/minimalist-cocoa-programming.html and
> http://casperbhansen.wordpress.com/2010/08/15/dev-tip-nibless-
If nothing else, it would explain to me how things works, 20 lines of
code would help me better than 20 documentation pages. There tutorials
above certainly did the explaining very well.
Also, I don't really want to argue whether there is merit or not - I
would be more thankful for the eventual tu
I see no merit in trying to make a "minimal" document based app, whatever that
is. It's usually misguided to try and build UI in code, it saves you nothing
and makes it much harder to get anywhere.
Just start a new Cocoa app and use the project template for a document based
app. It gives you th
16 matches
Mail list logo
