Saving work with Three20! And write almost no code.

09/06/2010 § 42 Comments

I know, I know…RSS tutorials are all over the internet, but this one is not about it at all, really.

Yesterday I posted 5 reasons to use Three20 and perhaps one to do not do it. And then I thought that if the problem is documentation and documentation is really important, especially in the beginning, why not write a hands-on tutorial for the very basic stuff?

But every app needs an idea, therefore I had to come up with one too…and the idea is, of course, a RSS Feed Reader!

« Read the rest of this entry »


320: Did you ever heard about Three20?

09/05/2010 § 2 Comments

Hey there!

Did you ever heard about 320? It is an iPhone library that can save you a lot of work (and is easy to make it work on the iPad!).

Let me introduce you to this awesome library presenting 5 reasons to use it.

« Read the rest of this entry »

Understanding memory management

09/04/2010 § 3 Comments

It is well known that iOS developers deal with memory management everyday, although a lot of them didn’t really get the “reference counting” idea.  That is why it is better to talk about ownership instead of counting.

In fact, the memory management concept in iOS is all about an object ownership schema, that is implemented through reference counting. Basically when no one owns an object, that object reference counting reaches 0 and therefore it is deallocated.

As you probably are an iOS developer, you already know that Objective-C provides some methods like alloc, new, retain, copy, release and autorelease to deal with that counting. But the real question here is when to use them.

« Read the rest of this entry »

Presenting PDF files by yourself

09/04/2010 § 43 Comments

When it comes to present a PDF file, the first solution that comes to mind is to use the UIWebView.

And as everybody already knows, there are many ways to get weird results when displaying PDF files using the UIWebView on iPhone SDK 3.2 both in the iPad Simulator and the actual device.

There are basically three ways to avoid these results:

  1. To present the PDF file inside a HTML content
  2. To reload the web view when the app change it’s orientation
  3. To write your own PDF presenter

The first approach does not present the PDF file nicely. It does not scale the content accordingly to the screen size or orientation so that it fits perfectly, and we have to agree that it doesn’t feel like a native app.

« Read the rest of this entry »