http://www.alphero.com Sun, 27 Nov 2011 23:15:10 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.alphero.com/mobile-development/understanding-objective-c-autorelease-memory-management/#comment-276 Brendon Sun, 27 Nov 2011 23:15:10 +0000 http://www.alphero.com/?p=335#comment-276 When you add a UIImage to a UIImageView, the UIImageView increases the retain count on the UIImage object, stoping it from being released, until you release the containing UIImageView. So if you add this view onto the screen, it will be retained until the view is removed via removeFromSuperview, at which point the retain count will be decreased and the UIImage can finally be released. When you add a UIImage to a UIImageView, the UIImageView increases the retain count on the UIImage object, stoping it from being released, until you release the containing UIImageView. So if you add this view onto the screen, it will be retained until the view is removed via removeFromSuperview, at which point the retain count will be decreased and the UIImage can finally be released.

]]> http://www.alphero.com/mobile-development/understanding-objective-c-autorelease-memory-management/#comment-275 Lada Sun, 27 Nov 2011 22:56:58 +0000 http://www.alphero.com/?p=335#comment-275 Thanks for the article. I started self-learning Objective C more the year ago and I never understood this memory management. I made a couple of apps without taking care of releasing, it somehow worked. But now I have difficulties with [UIImage imageNamed:] as you mention. Is there a better way to show a jpeg from app´s bundle than this one? You say this method contains autorelease inside. It means that if I load this UIImage into UIImageView and then release that view then the image is released automatically, right? When I add it as subview to a view which is permanently shown on the screen then the autorelease cue is damaged? It must be because the image survives many system loops then, apparently is not autoreleased. But then when I removeFromSuperview the view, which should mean the superview releases my view with the image, then is it released or not? I'm completely lost :-( Thanks for the article. I started self-learning Objective C more the year ago and I never understood this memory management. I made a couple of apps without taking care of releasing, it somehow worked. But now I have difficulties with [UIImage imageNamed:] as you mention. Is there a better way to show a jpeg from app´s bundle than this one? You say this method contains autorelease inside. It means that if I load this UIImage into UIImageView and then release that view then the image is released automatically, right? When I add it as subview to a view which is permanently shown on the screen then the autorelease cue is damaged? It must be because the image survives many system loops then, apparently is not autoreleased. But then when I removeFromSuperview the view, which should mean the superview releases my view with the image, then is it released or not? I’m completely lost

]]> http://www.alphero.com/mobile-development/distributing-your-html5-app-via-the-app-store-or-marketplace/#comment-268 HTML 5 Vs. Native Applications : Ahmad Assaf`s Blog Fri, 25 Nov 2011 12:59:47 +0000 http://www.alphero.com/?p=311#comment-268 [...] App Store Services (discovery, updates, payments & trust) — Not only can HTML5 apps be sold through HTML5 or Chrome app stores, they can be sold directly through Apple’s App Store, Android Marketplace or Blackberry App World, after being placed in a simple “native” app shell such as Nimblekit or Phonegap (Distributing your HTML5 app via the App Store or Marketplace). [...] [...] App Store Services (discovery, updates, payments & trust) — Not only can HTML5 apps be sold through HTML5 or Chrome app stores, they can be sold directly through Apple’s App Store, Android Marketplace or Blackberry App World, after being placed in a simple “native” app shell such as Nimblekit or Phonegap (Distributing your HTML5 app via the App Store or Marketplace). [...]

]]> http://www.alphero.com/innovation/two-conferences-two-days-two-extremes/#comment-8 Two conferences, two days, two extremes | Today Headlines Mon, 11 Apr 2011 19:51:30 +0000 http://www.alphero.com/?p=294#comment-8 [...] the rest here:  Two conferences, two days, two extremes Share [...] [...] the rest here:  Two conferences, two days, two extremes Share [...]

]]>