What is the proper way to store an object with many attributes in Objective-C?
I have an object that I am downloading over HTTP, that has approximately 50 attributes. What is the proper way to store this information in Objective-C? Should I have an NSObject with a property for each attribute (if so, what would be a good way to initialize this object?)? Should I use an NSDictionary with 50 key-value pairs?
What is the proper way to store an object with many attributes in Objective-C?
I have an object that I am downloading over HTTP, that has approximately 50 attributes. What is the proper way to store this information in Objective-C? Should I have an NSObject with a property for each attribute (if so, what would be a good way to initialize this object?)? Should I use an NSDictionary with 50 key-value pairs?
Should accessible members of an internal class be internal too?
I’m designing a set of APIs for some applications I’m working on. I want to keep the code style consistent in all the classes I write but I’ve found that there are a few inconsistencies that I’m introducing and I don’t know what the best way to resolve them is.
Should accessible members of an internal class be internal too?
I’m designing a set of APIs for some applications I’m working on. I want to keep the code style consistent in all the classes I write but I’ve found that there are a few inconsistencies that I’m introducing and I don’t know what the best way to resolve them is.
Breaking up classes and methods into smaller units
During code reviews a couple devs have recommended I break up my methods into smaller methods.
Organizing solution / project structure and classes for Line of Business Application (LOB)
The question how-do-you-organize-your-projects already has a few good answers. I would like to get a better understanding about this suggested structure:
Organizing solution / project structure and classes for Line of Business Application (LOB)
The question how-do-you-organize-your-projects already has a few good answers. I would like to get a better understanding about this suggested structure:
Organizing solution / project structure and classes for Line of Business Application (LOB)
The question how-do-you-organize-your-projects already has a few good answers. I would like to get a better understanding about this suggested structure:
Practices for organizing JavaScript AMD imports
Our company has been using newer versions of the Dojo framework, which have progressed to an AMD-based loader format. I’m currently trying to find logical ways to separate layer files, taking a module and all its dependencies, and wrapping them all into single minified files. My goals are generally as follows:
Practices for organizing JavaScript AMD imports
Our company has been using newer versions of the Dojo framework, which have progressed to an AMD-based loader format. I’m currently trying to find logical ways to separate layer files, taking a module and all its dependencies, and wrapping them all into single minified files. My goals are generally as follows: