gimenete / ios-boilerplate Goto Github PK

I have more than 1000 friend list in a UITableView. So if I scroll down its flickering with previous image almost 20+ times.
How we can avoid this flickering issue ? It's very annoying.

Few guys have already noticed the same issue but still no reply.
#21

If you change the delegate on the ImageManager to tabbar (if it's a tabbar app), images don't appear in the tableView till that cell has either passed the top or botom of the screen. Images on a normal detail view don't show at all.

Hi Alberto,

I created a library for dynamic scroll views, which I something I need in all of my projects. It's still in its early days but I thought you may consider if it's worth adding it to iOS-boilerplate.

https://github.com/oscardelben/FRDynamicScrollView/

Great project, what do you think about supporting ARC version of it, maybe in a branch?

The demo runs perfectly on the simulator but gives weird errors when trying to run on device.

/Users/sarperdag/dev/iphone/iOS-boilerplate/IOSBoilerplate/SwipeableCell.m:28: error: 'backView' undeclared (first use in this function)

/Users/sarperdag/dev/iphone/iOS-boilerplate/IOSBoilerplate/SwipeableCell.m:92: error: 'contentView' undeclared (first use in this function)

Is it possible?

File: ImageManager.m
Line: 101,102,113,120

issue code:request.url because the URL property can change when a request is redirected, should use request.originalURL instead.

If you first tap the cell and then try to swipe it, the lay out breaks. I got this just from testing the SwipeableTableViewExample. Great project btw!

I couldn't identify which license applies to the iOS-boilerplate project, neither here in the repo nor in the project's homepage. Could you please add a LICENSE file and possibly a mention of the license to the README?

/Users/cullepm3/Desktop/iphone/iOS-boilerplate/IOSBoilerplate/SwipeableCell.m:28:0 /Users/cullepm3/Desktop/iphone/iOS-boilerplate/IOSBoilerplate/SwipeableCell.m:28: error: 'backView' undeclared (first use in this function)

/Users/cullepm3/Desktop/iphone/iOS-boilerplate/IOSBoilerplate/SwipeableCell.m:92:0 /Users/cullepm3/Desktop/iphone/iOS-boilerplate/IOSBoilerplate/SwipeableCell.m:92: error: 'contentView' undeclared (first use in this function)

First off I should say (again :-) ) that I really love this project, and although I knew most of the libraries you're including, it's really helpful that you're creating some handy methods and classes to achieve tasks that we have to do everywhere :)

I only wanted to comment my concern with some decisions and discuss what you (and other developers) think about it.
I looked through all the clases, and I mostly like how code is organized, except for one thing!

BaseViewController has some methods to do async HTTP requests. This is useful, as you can use this as a base class for a View Controller which has a table and gets the data to fill the table off the network; but this is completely against the MVC paradigm! This puts some Model responsabilites within the Controller (therefore this would be hard to test among other things).
What I suggest, is to take exactly the same code you have to do those requests, and put it in another class (say HTTPRequestHelper or something like that), and inject that class into the BaseViewController during initialization. You could have a default init method which instantiates an object of that class by default, and another init method to pass a different object (probably a subclass of the first, so you make sure it responds to the same methods). Perhaps omething like this:

- (id)init {
   return [self initWithHTTPRequestHelper:[[[HTTPRequestHelper alloc] init] autorelease]];
}

- (id)initWithHTTPRequestHelper:(HTTPRequestHelper *)rh {
     if ((self = [super init])) {
        self.requestHelper = rh;  
    }

    return self;
}

(please, take this as constructive criticism and not like I'm trying to say you did a bad job!)

Patched to non-version specific file.
https://gist.github.com/1292325

I have increased the size of the results coming from the Twitter search example in AsyncCellImagesExample.m by changing the code as below

NSArray *keys = [NSArray arrayWithObjects:@"q", @"rpp", nil];
NSArray *objects = [NSArray arrayWithObjects:@"iOS", @"100", nil];
NSDictionary *params = [NSDictionary dictionaryWithObjects:objects forKeys:keys];

And when I run the code on my iPhone, if you scroll directly to the bottom of the table view, very fast, the images start showing some previously fetched and rendered versions, and then they quickly go back to normal. It is like there is some flickering, showing incorrect images.

Hi There,

On select of a fast cell within a table view, the selection colour is blocked by the opaque white background colour. Is there away to configure a fast cell to still have the traditional selection behaviour?

When I run it
The file “IOSBoilerplate.app” couldn’t be opened because you don’t have permission to view it.

Why?
Thanks!

Ben Copsey has discontinued it. http://allseeing-i.com/[request_release];

(you'll need to copy and paste the url, at least in safari. make sure you grab the trailing semicolon, too)

Hi everyone, I want to limit down the parsed results to just cities, towns, villages, states but not addresses, suburbs, countries, continents, oceans etc.

In ASIAuthenticationDialog.m file, starting at line 482, wouldn't it be better to call the @synthesize on a single line?