ios - Is there a better way for calling methods in a managing view controller from a managed view controller? -


in apps i've developed far, i've had uiviewcontroller in charge of presenting other uiviewcontrollers display transitions in ui. whenever i've had "managed" view controller call method in "managing" view controller, i've had ensure had reference managing controller inside of managed controller.

for example: if have uiviewcontroller called maincontroller in charge of managing other uiviewcontrollers in application's ui, , maincontroller creates 2 controllers presentation. called subcontroller1 , subcontroller2 respectively. if subcontroller1 finished , maincontroller needs display subcontroller2, i've set maincontroller reference variable inside of subcontroller1 communicate change maincontroller. means whenever maincontroller creates subcontroller1 has set subcontroller1's maincontroller reference variable self.

should worried memory usage method of communications? better off using notifications kind of behavior? major benefit i've found method i'm using makes incredibly easy share information between view controllers if necessary. thoughts appreciated.

handling changes, actions, or user interaction in other views essential use case of delegates. best practice have main controller delegate of first/second view controller, , events happen in child controllers, call methods on delegates, can take necessary action.

passing references way describe won't have noticeable memory impact, tightly couple code maincontroller, should avoided. should strive flexibility handle potential changes in future. happens if transition universal app , ipad ui has vastly different structure? delegates, need ensure contract between controllers intact, free change of underlying implementation details.

other options keeping values/state in sync between views are:


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more