I'm just learning Objective-C and Xcode I like interface building, but as far as coding goes, I'm a little I'm losing.
Actually, I am trying to understand when I want a new class. I am reading a book that really covers "how", but "why not".
I am creating an application and I have a very complete interface.
In other words, I have a lot of NSObjects, but unfortunately, these objects do not know how to communicate with each other or with the built-in program. Here's fantasy.
I have several text fields that will eventually convey my input to the tables within my interface and external PDF templates.
My basic understanding of obj and the xcode is that to transmit the contents of the text field to a PDF file or table, I want to specify the content of the text field as a variable Will need to create a new class, and that variable somewhere (pdf or table).
However, if I have a button which will ultimately be responsible for sending data from the textfield, then I will also need to make a connection between buttons and text fields like this. / P>
(button) --- fetches --- & gt; (Content of text field) --- Sends ---> (Table)
So, above this point, I will all join this one class, right? As a variable in the form of text field, which I declare in my header file, the method of the button / action that I include in the header file and execute in .m file and the table also both .h Will be announced in And M files?
Am I on the right track? In addition, this is just a connection from a text field. If I made the decision with more text areas in this application, would I have to make a separate class for each? Or can I use the same class and separate them on ID basis?
I am clearly a Noble
I think the puzzle you Remember that the design pattern is how provide the documents you read - how to create classes, add methods, etc. It's like learning preparation techniques in the cooking class. How to chop, mix, dice, marine, etc. Design patterns are high-level recipes that show you that using all of these techniques you have learned to gather the material in the finished material. To get started, take a look at the applet's own design patterns section.
Comments
Post a Comment