ios - For completely programmatically created UIView/UIViewController, what should be in loadView vs viewDidLoad? -


for experimentation purposes, trying in code.

i have custom root uiview/uiviewcontroller subclass pair called rootview , rootviewcontroller respectively.

i have glkview/glkviewcontroller subclass pair called renderview , renderviewcontroller.

both uiviewcontroller subclasses create managed views in loadview overrides.

setting main rootviewcontroller/rootview simple. in appdelegate subclass, create main window , assign rootviewcontroller proeprty so...

#import "appdelegate.h" #import "rootviewcontroller.h"  @implementation appdelegate    - (bool)application:(uiapplication *)application didfinishlaunchingwithoptions:(nsdictionary *)launchoptions     {         cgrect screenbounds = [[uiscreen mainscreen] bounds];       // set window         uiwindow* mainwindow = [[uiwindow alloc] initwithframe:screenbounds];         mainwindow.rootviewcontroller = [rootviewcontroller new];         self.window = mainwindow;          [mainwindow makekeyandvisible];          return yes;     }  @end

the rootview appears on screen 1 expect.

what i'm wondering view hierarchy initialization. rootviewcontroller has property hold instance of renderviewcontroller, , renderview (initially) placed in frame stored in second property of rootviewcontroller called renderviewframe.

my question proper place set hierarchy?

the documentation states that's uiviewcontroller's loadview i'm doing there...

- (void)loadview {     self.view = [[rootview alloc] initwithframe:[[uiscreen mainscreen] bounds]];   // set renderviewcontroller     renderviewcontroller* renderviewcontroller = [renderviewcontroller new];     [self addchildviewcontroller:renderviewcontroller];      renderviewcontroller.view.frame = self.renderviewframe;     [self.view addsubview:renderviewcontroller.view];      self.renderviewcontroller = renderviewcontroller; }

...and works, i've seen people no, should move relating creating renderview/renderviewcontroller rootviewcontroller's viewdidload , not loadview, no 1 can why. mean part of hierarchy , that's loadview for.

and if i'm right, why i/anyone need use viewdidload @ if we're doing initialization in loadview, or artifact when memory unload views way in ios6?

your solution fine programmatic solution. since need implement loadview can initialization here.

you can mixed loadview , viewdidload solution (only set view property in loadview, rest in viewdidload); might make easier go nib/story board solution later on. having initialization in 1 place (just loadview) might easier maintain having split in 2 (loadview , viewdidload). on other hand, people expect see viewdidload method. can see, it's matter of taste.

when using xibs or story boards, of course it's recommended avoid touching loadview @ , should implement viewdidload.


-

Popular posts from this blog

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

i working apache nifi 0.5.1 on groovy script replace incoming json values ones contained in mapping file. mapping file looks (it simple .txt): header1;header2;header3 a;some text;a2 i have started following: import groovy.json.jsonbuilder import groovy.json.jsonslurper import java.nio.charset.standardcharsets def flowfile = session.get(); if (flowfile == null) { return; } flowfile = session.write(flowfile, { inputstream, outputstream -> def content = """ { "field1": "a" "field2": "a", "field3": "a" }""" def slurped = new jsonslurper().parsetext(content) def builder = new jsonbuilder(slurped) builder.content.field1 = "a" builder.content.field2 = "some text" builder.content.field3 = "a2" outputstream.write(builder.toprettystring().ge...
Read more

node.js - How do I prevent MongoDB replica set from querying the primary? -

read-operations-only: is there way have mongodb replica set, make mongodb instance on box connected to, mongodb gets queried? i have 3 ec2 instances behind aws load balancer. on each ec2 instance runs mongodb, part of replica set. i have express endpoints on nodejs , connect replica set follows mongodb.mongoclient.connect('mongodb://1.1.1.1,2.2.2.2,3.3.3.3.', function (err, db) { if (err) { complete('{}'); } else { i distribute load of queries evenly across 3 instances of mongodb replica set instead of default having queries routed ec2 instance primary mongodb defined, because destroys point of load balancer (which balance load of queries across 3 instances evenly). my understanding when connecting mongodb replica set, primary instance selected unless primary instance down, , therefore purpose of every secondary instance serve backup. in example people call hot,cold,cold. because there 2...
Read more