4 ms·
Actually three20 is a great option to go with for many apps. This is the only bit of advice in your post that I completely disagree with. Three20 may have some
by Zev 16y ago
Actually three20 is a great option to go with for many apps.
This is the only bit of advice in your post that I completely disagree with. Three20 may have some nice UI bits, but it is a very poorly designed framework. I say this having looked at it before and after Facebook made a big redesign of it (breaking backwards compatibility and minimally documenting the changes.)
You can't add one view without adding a dozen other classes. Its not very well documented. It adds a large amount of bloat to the binary and drastically increases compile time.. I can go on, if you like.
- pshapiro 16y agoWe agree on those points, however. It's a big pain in the backside that they don't document their API better. And many of the classes, like TTPhotoViewController and TTScrollView, have some big problems that require modification to overcome. But besides being a free library, I used three20 in many of my recent apps because I have been working with publishers to build navigation-based apps that require things like image caching and URL navigation. A number of other features of three20 are quite welcome, despite their quirks. I usually try to do a quick test of the framework before I integrate it into a project and guarantee that it will work, because, you're right, some of them don't behave as advertised. This is even the case with some of Apple's libraries, but I daresay their documentation is better than three20's.