iphone - How to use pattern to simplify the UIPopoverController management? -


UIVopController (parent) & gt; It is always uncomfortable to use UIPopoverController with the hierarchy of the view controller. UIPopoverController & gt; UINavigationControler & gt; UIViewController.

Alternatively, it is likely that many pop-ups need to keep a book and display at the same time. The same bundle of most time code is copied and pasted from this class to another. Patterns like variables declaration / @products / retaining / @syntheses / release can not be terminated.

What is the good OOP pattern to make management of UIPopoverController easier? You can create subclass for UIPopoverController (like ). MyPopover ) and add all the standard code you want. Then create the sub-category of MyPopover where you only add specific code.

However, I guess that this does not give you less amount like diarrhea. The reason is that the things you mention (qualities, preserves, synthesized, release etc.) actually There are standard code blocks which can seem to be literal but in reality they are quite early in any class. Yes, purpose-is "verbose", if you do, but OOP is not unnecessary in meaning.

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -