Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You really should look into the <a href="http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/Introduction/Introduction.html" rel="nofollow">View Controller Programming Guide</a> -- by switching around the contents of a single view controller, you're making a lot of extra work for yourself with little benefit. By using multiple view controllers when you want to have different "screens" in your app, you can take advantage of storyboarding for easier development, and you automatically get better memory management (read: less potential for crashes), too.</p> <p>However, to more directly answer your question... if you're putting the WebView into the view hierarchy with <code>[self.view addSubview:webView]</code>, you can remove it with <code>[webView removeFromSuperview]</code>. (This means you'll have to keep a reference to the WebView around so you can refer to it when you want to dismiss it.)</p> <hr> <p>I also noticed in the code you posted to cl.ly an unrelated method <code>-deviceModel</code> which uses <code>uname()</code> to get device information. This is a bad idea, for two reasons:</p> <ul> <li><code>uname()</code> isn't guaranteed to do something useful on an iOS device (even if it currently does). Use the <code>UIDevice</code> class instead if you need this kind of info, or...</li> <li>Generally, you <strong>don't</strong> want to test for the device name to enable functionality in your app; instead, you should test for the capabilities you need. (For example, if you look for a device name starting with "iPhone 4" to test for a Retina display, you'll miss the 4th-generation iPod touch, and the iPhone-5-or-whatever-they-call-what's-next. Instead, use the <code>UIScreen</code> class.)</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload