Instantly share code, notes, and snippets.

Embed
What would you like to do?
PFQueryTableViewController Template
//
// This is the template PFQueryTableViewController subclass file. Use it to customize your own subclass.
//
#import <UIKit/UIKit.h>
#import "Parse/Parse.h"
@interface MyPFQueryTableViewController : PFQueryTableViewController
@end
@implementation MyPFQueryTableViewController
- (id)initWithStyle:(UITableViewStyle)style {
self = [super initWithStyle:style];
if (self) {
// Custom the table
// The className to query on
self.className = @"Foo";
// The key of the PFObject to display in the label of the default cell style
self.textKey = @"text";
// Uncomment the following line to specify the key of a PFFile on the PFObject to display in the imageView of the default cell style
// self.imageKey = @"image";
// Whether the built-in pull-to-refresh is enabled
self.pullToRefreshEnabled = YES;
// Whether the built-in pagination is enabled
self.paginationEnabled = YES;
// The number of objects to show per page
self.objectsPerPage = 25;
}
return self;
}
- (void)didReceiveMemoryWarning {
// Releases the view if it doesn't have a superview.
[super didReceiveMemoryWarning];
// Release any cached data, images, etc that aren't in use.
}
#pragma mark - UIViewController
- (void)viewDidLoad {
[super viewDidLoad];
// Uncomment the following line to preserve selection between presentations.
// self.clearsSelectionOnViewWillAppear = NO;
// Uncomment the following line to display an Edit button in the navigation bar for this view controller.
// self.navigationItem.rightBarButtonItem = self.editButtonItem;
}
- (void)viewDidUnload {
[super viewDidUnload];
// Release any retained subviews of the main view.
// e.g. self.myOutlet = nil;
}
- (void)viewWillAppear:(BOOL)animated {
[super viewWillAppear:animated];
}
- (void)viewDidAppear:(BOOL)animated {
[super viewDidAppear:animated];
}
- (void)viewWillDisappear:(BOOL)animated {
[super viewWillDisappear:animated];
}
- (void)viewDidDisappear:(BOOL)animated {
[super viewDidDisappear:animated];
}
- (BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation {
// Return YES for supported orientations
return (interfaceOrientation == UIInterfaceOrientationPortrait);
}
#pragma mark - PFQueryTableViewController
- (void)objectsWillLoad {
[super objectsWillLoad];
// This method is called before a PFQuery is fired to get more objects
}
- (void)objectsDidLoad:(NSError *)error {
[super objectsDidLoad:error];
// This method is called every time objects are loaded from Parse via the PFQuery
}
/*
// Override to customize what kind of query to perform on the class. The default is to query for
// all objects ordered by createdAt descending.
- (PFQuery *)queryForTable {
PFQuery *query = [PFQuery queryWithClassName:self.className];
// If Pull To Refresh is enabled, query against the network by default.
if (self.pullToRefreshEnabled) {
query.cachePolicy = kPFCachePolicyNetworkOnly;
}
// If no objects are loaded in memory, we look to the cache first to fill the table
// and then subsequently do a query against the network.
if (self.objects.count == 0) {
query.cachePolicy = kPFCachePolicyCacheThenNetwork;
}
[query orderByDescending:@"createdAt"];
return query;
}
*/
/*
// Override to customize the look of a cell representing an object. The default is to display
// a UITableViewCellStyleDefault style cell with the label being the textKey in the object,
// and the imageView being the imageKey in the object.
- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath object:(PFObject *)object {
static NSString *CellIdentifier = @"Cell";
PFTableViewCell *cell = (PFTableViewCell *)[tableView dequeueReusableCellWithIdentifier:CellIdentifier];
if (cell == nil) {
cell = [[PFTableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier];
}
// Configure the cell
cell.textLabel.text = [object objectForKey:self.textKey];
cell.imageView.file = [object objectForKey:self.imageKey];
return cell;
}
*/
/*
// Override if you need to change the ordering of objects in the table.
- (PFObject *)objectAtIndex:(NSIndexPath *)indexPath {
return [self.objects objectAtIndex:indexPath.row];
}
*/
/*
// Override to customize the look of the cell that allows the user to load the next page of objects.
// The default implementation is a UITableViewCellStyleDefault cell with simple labels.
- (UITableViewCell *)tableView:(UITableView *)tableView cellForNextPageAtIndexPath:(NSIndexPath *)indexPath {
static NSString *CellIdentifier = @"NextPage";
UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];
if (cell == nil) {
cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier];
}
cell.selectionStyle = UITableViewCellSelectionStyleNone;
cell.textLabel.text = @"Load more...";
return cell;
}
*/
#pragma mark - UITableViewDataSource
/*
// Override to support conditional editing of the table view.
- (BOOL)tableView:(UITableView *)tableView canEditRowAtIndexPath:(NSIndexPath *)indexPath {
// Return NO if you do not want the specified item to be editable.
return YES;
}
*/
/*
// Override to support editing the table view.
- (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath {
if (editingStyle == UITableViewCellEditingStyleDelete) {
// Delete the object from Parse and reload the table view
} else if (editingStyle == UITableViewCellEditingStyleInsert) {
// Create a new instance of the appropriate class, and save it to Parse
}
}
*/
/*
// Override to support rearranging the table view.
- (void)tableView:(UITableView *)tableView moveRowAtIndexPath:(NSIndexPath *)fromIndexPath toIndexPath:(NSIndexPath *)toIndexPath {
}
*/
/*
// Override to support conditional rearranging of the table view.
- (BOOL)tableView:(UITableView *)tableView canMoveRowAtIndexPath:(NSIndexPath *)indexPath {
// Return NO if you do not want the item to be re-orderable.
return YES;
}
*/
#pragma mark - UITableViewDelegate
- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath {
[super tableView:tableView didSelectRowAtIndexPath:indexPath];
}
@end
@jroes

This comment has been minimized.

Show comment
Hide comment
@jroes

jroes Jan 9, 2012

This may be a little crazy, but I'm overriding initWithCoder in this way to support Storyboard / Interface Builder as opposed to overriding initWithStyle above.

- (id)initWithCoder:(NSCoder *)aDecoder
{
    self = [super initWithClassName:@"Foo"];
    self = [super initWithCoder:aDecoder];
    if (self) {        
        // The className to query on
        self.className = @"Foo";

        // The key of the PFObject to display in the label of the default cell style
        self.keyToDisplay = @"text";

        // Whether the built-in pull-to-refresh is enabled
        self.pullToRefreshEnabled = YES;

        // Whether the built-in pagination is enabled
        self.paginationEnabled = YES;

        // The number of objects to show per page
        self.objectsPerPage = 25;
    }
    return self;
}

jroes commented Jan 9, 2012

This may be a little crazy, but I'm overriding initWithCoder in this way to support Storyboard / Interface Builder as opposed to overriding initWithStyle above.

- (id)initWithCoder:(NSCoder *)aDecoder
{
    self = [super initWithClassName:@"Foo"];
    self = [super initWithCoder:aDecoder];
    if (self) {        
        // The className to query on
        self.className = @"Foo";

        // The key of the PFObject to display in the label of the default cell style
        self.keyToDisplay = @"text";

        // Whether the built-in pull-to-refresh is enabled
        self.pullToRefreshEnabled = YES;

        // Whether the built-in pagination is enabled
        self.paginationEnabled = YES;

        // The number of objects to show per page
        self.objectsPerPage = 25;
    }
    return self;
}
@jamesyu

This comment has been minimized.

Show comment
Hide comment
@jamesyu

jamesyu Jan 9, 2012

Thanks Jonathan! I'll check it out and then add it to the template if it makes sense. We definitely want to support storyboards.

Owner

jamesyu commented Jan 9, 2012

Thanks Jonathan! I'll check it out and then add it to the template if it makes sense. We definitely want to support storyboards.

@joelcloralt

This comment has been minimized.

Show comment
Hide comment
@joelcloralt

joelcloralt Jan 20, 2012

Jonathan's code worked just fine for me with storyboards so thanks again.

What I would like to share for anyone interested is how to pass the selected object from the PFQueryTableViewController to a DetailViewController since it took me a bit to figure it out. It might not be the greatest way ever but it worked.

First create a property list of type id in the detail controller.

@property (strong, nonatomic) id detailItems; 

Then connect the TableViewCell to the DetailViewController and (assuming you are using a NavigationController) select Push. Select the segue and set the identifier to "whateverYouWant."

In your PFQueryTableViewController you need to implement the prepareForSegue method. Check if the segue being executed is the one with the same identifier. Get the row that was selected and set the detailItems object as follow :


- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { 
    if ([segue.identifier isEqualToString:@"whateverYouWant"]) {
        DetailViewController *detailViewController = [segue destinationViewController];
        NSInteger row = [[self tableView].indexPathForSelectedRow row];
        detailViewController.detailItems = [self.objects objectAtIndex:row];  
    }
}

This will pass the selected PFObject to the DetailViewController where you can show what you want.

Object keys will be the same column names you defined in your Parse Class. You can print it out to see them in the console if you put the following in the viewDidLoad method in your DetailViewController

NSLog(@"my object contains: %@", self.detailItems);

Hope this helps!

joelcloralt commented Jan 20, 2012

Jonathan's code worked just fine for me with storyboards so thanks again.

What I would like to share for anyone interested is how to pass the selected object from the PFQueryTableViewController to a DetailViewController since it took me a bit to figure it out. It might not be the greatest way ever but it worked.

First create a property list of type id in the detail controller.

@property (strong, nonatomic) id detailItems; 

Then connect the TableViewCell to the DetailViewController and (assuming you are using a NavigationController) select Push. Select the segue and set the identifier to "whateverYouWant."

In your PFQueryTableViewController you need to implement the prepareForSegue method. Check if the segue being executed is the one with the same identifier. Get the row that was selected and set the detailItems object as follow :


- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { 
    if ([segue.identifier isEqualToString:@"whateverYouWant"]) {
        DetailViewController *detailViewController = [segue destinationViewController];
        NSInteger row = [[self tableView].indexPathForSelectedRow row];
        detailViewController.detailItems = [self.objects objectAtIndex:row];  
    }
}

This will pass the selected PFObject to the DetailViewController where you can show what you want.

Object keys will be the same column names you defined in your Parse Class. You can print it out to see them in the console if you put the following in the viewDidLoad method in your DetailViewController

NSLog(@"my object contains: %@", self.detailItems);

Hope this helps!

@cbowns

This comment has been minimized.

Show comment
Hide comment
@cbowns

cbowns Feb 6, 2012

If you change the #pragma marks for the UITableView protocols to what I've got in https://gist.github.com/fe2283fa933d134ce4bd, namely:

#pragma mark - UITableViewDelegate protocol methods

and

#pragma mark - UITableViewDataSource protocol methods

the words UITableViewDataSource and UITableViewDelegate become option-clickable and will take you where those protocols are defined. (Quite handy when you've removed the helper comments but can't remember what other methods will help you customize your tableview.)

cbowns commented Feb 6, 2012

If you change the #pragma marks for the UITableView protocols to what I've got in https://gist.github.com/fe2283fa933d134ce4bd, namely:

#pragma mark - UITableViewDelegate protocol methods

and

#pragma mark - UITableViewDataSource protocol methods

the words UITableViewDataSource and UITableViewDelegate become option-clickable and will take you where those protocols are defined. (Quite handy when you've removed the helper comments but can't remember what other methods will help you customize your tableview.)

@michael-garland

This comment has been minimized.

Show comment
Hide comment
@michael-garland

michael-garland Feb 14, 2012

Here is one-line way to send the selected object to the detail view controller in your segue:

[[segue destinationViewController] setSelectedObject:[self objectAtIndex:[self.tableView indexPathForCell:sender]]];

You will need to replace the "setSelectedObject" with the name of your actual setter on the detail view controller.

michael-garland commented Feb 14, 2012

Here is one-line way to send the selected object to the detail view controller in your segue:

[[segue destinationViewController] setSelectedObject:[self objectAtIndex:[self.tableView indexPathForCell:sender]]];

You will need to replace the "setSelectedObject" with the name of your actual setter on the detail view controller.

@jamiechapman

This comment has been minimized.

Show comment
Hide comment
@jamiechapman

jamiechapman Feb 28, 2012

I'm having issues running PFQueryTableViewController on iOS 4.3, unfortunately I'm getting the following crash:

dyld: lazy symbol binding failed: Symbol not found: _objc_retainAutoreleasedReturnValue Referenced from: /Users/jamiechapman/Library/Application Support/iPhone Simulator/4.3.2/Applications/655CBFAD-E084-4ADB-853C-5B38F3409DDB/X.app/X Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Foundation dyld: Symbol not found: _objc_retainAutoreleasedReturnValue Referenced from: /Users/jamiechapman/Library/Application Support/iPhone Simulator/4.3.2/Applications/655CBFAD-E084-4ADB-853C-5B38F3409DDB/X.app/X Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Foundation

I'm assuming this is something to do with ARC (which we're not using)? Any ideas guys?

jamiechapman commented Feb 28, 2012

I'm having issues running PFQueryTableViewController on iOS 4.3, unfortunately I'm getting the following crash:

dyld: lazy symbol binding failed: Symbol not found: _objc_retainAutoreleasedReturnValue Referenced from: /Users/jamiechapman/Library/Application Support/iPhone Simulator/4.3.2/Applications/655CBFAD-E084-4ADB-853C-5B38F3409DDB/X.app/X Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Foundation dyld: Symbol not found: _objc_retainAutoreleasedReturnValue Referenced from: /Users/jamiechapman/Library/Application Support/iPhone Simulator/4.3.2/Applications/655CBFAD-E084-4ADB-853C-5B38F3409DDB/X.app/X Expected in: /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Foundation

I'm assuming this is something to do with ARC (which we're not using)? Any ideas guys?

@jamesyu

This comment has been minimized.

Show comment
Hide comment
@jamesyu

jamesyu Mar 1, 2012

Hey Jamie, you'll need to make sure you're running Xcode 4.2+, and if you're targeting iOS 4.3, then make sure to look at step #8 here: https://www.parse.com/apps/quickstart

Owner

jamesyu commented Mar 1, 2012

Hey Jamie, you'll need to make sure you're running Xcode 4.2+, and if you're targeting iOS 4.3, then make sure to look at step #8 here: https://www.parse.com/apps/quickstart

@kent

This comment has been minimized.

Show comment
Hide comment
@kent

kent Mar 23, 2012

Any word on when Parse will natively support Storyboards? Wondering if I should hack it out, or wait a bit ;)

kent commented Mar 23, 2012

Any word on when Parse will natively support Storyboards? Wondering if I should hack it out, or wait a bit ;)

@michael-crabtree

This comment has been minimized.

Show comment
Hide comment
@michael-crabtree

michael-crabtree Mar 25, 2012

I am using this current workaround template in my application, and nothing bad has become of it as far as I can tell. The only part that really bothers me is that I like doing things the proper way and sometimes I find myself waking up from dreams where I was trying to figure out a better PFQueryTableViewController Storyboard implementation. It might also be worth pointing out that I didn't have any problem making this work within a UISplitViewController in a Storyboard as well. If you start bringing things like UINavigationControllers into the detail views you will certainly have some fun with Segues but really everything works great regardless. Still, I am eagerly awaiting official Storyboard support and I'm positive I'll at least sleep a little better after that. Good Luck :)

michael-crabtree commented Mar 25, 2012

I am using this current workaround template in my application, and nothing bad has become of it as far as I can tell. The only part that really bothers me is that I like doing things the proper way and sometimes I find myself waking up from dreams where I was trying to figure out a better PFQueryTableViewController Storyboard implementation. It might also be worth pointing out that I didn't have any problem making this work within a UISplitViewController in a Storyboard as well. If you start bringing things like UINavigationControllers into the detail views you will certainly have some fun with Segues but really everything works great regardless. Still, I am eagerly awaiting official Storyboard support and I'm positive I'll at least sleep a little better after that. Good Luck :)

@kent

This comment has been minimized.

Show comment
Hide comment
@kent

kent Mar 25, 2012

I was having some problems getting yours to compile but I will give it another go. Thank you for the comment!

kent commented Mar 25, 2012

I was having some problems getting yours to compile but I will give it another go. Thank you for the comment!

@dazcox

This comment has been minimized.

Show comment
Hide comment
@dazcox

dazcox Apr 10, 2012

I'm having issues with deleting records - the template throws up errors if i just uncomment that section so I have this at present

// Override to support editing the table view.

  • (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath
    {
    [tableView beginUpdates];
    NSInteger row = [[self tableView].indexPathForSelectedRow row];
    [[self.objects objectAtIndex:row] deleteInBackground];

    [tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:UITableViewRowAnimationFade];

    [tableView endUpdates];
    [tableView reloadData];
    }

but still get errors Invalid update: invalid number of rows in section 0. The number of rows contained in an existing section after the update (2) must be equal to the number of rows contained in that section before the update (2), plus or minus the number of rows inserted or deleted from that section (0 inserted, 1 deleted) and plus or minus the number of rows moved into or out of that section (0 moved in, 0 moved out).'

Totally stuck hope someone can help!

dazcox commented Apr 10, 2012

I'm having issues with deleting records - the template throws up errors if i just uncomment that section so I have this at present

// Override to support editing the table view.

  • (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath
    {
    [tableView beginUpdates];
    NSInteger row = [[self tableView].indexPathForSelectedRow row];
    [[self.objects objectAtIndex:row] deleteInBackground];

    [tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:UITableViewRowAnimationFade];

    [tableView endUpdates];
    [tableView reloadData];
    }

but still get errors Invalid update: invalid number of rows in section 0. The number of rows contained in an existing section after the update (2) must be equal to the number of rows contained in that section before the update (2), plus or minus the number of rows inserted or deleted from that section (0 inserted, 1 deleted) and plus or minus the number of rows moved into or out of that section (0 moved in, 0 moved out).'

Totally stuck hope someone can help!

@ashchan

This comment has been minimized.

Show comment
Hide comment
@ashchan

ashchan May 4, 2012

@jroes, @jamesyu, @kent: I found another way to support Storylboard without overriding initWithCoder. From the storyboard select the view controller, go to the Identifier inspector, add a User Defined Runtime Attribute: Key Path: 'className', Type: String, Value: your query model class name.

ashchan commented May 4, 2012

@jroes, @jamesyu, @kent: I found another way to support Storylboard without overriding initWithCoder. From the storyboard select the view controller, go to the Identifier inspector, add a User Defined Runtime Attribute: Key Path: 'className', Type: String, Value: your query model class name.

@jamesyu

This comment has been minimized.

Show comment
Hide comment
@jamesyu

jamesyu May 4, 2012

Hey guys, the latest version of our SDK should support storyboard and nibs out of the box! Get it at https://parse.com/docs/downloads

Owner

jamesyu commented May 4, 2012

Hey guys, the latest version of our SDK should support storyboard and nibs out of the box! Get it at https://parse.com/docs/downloads

@michael-crabtree

This comment has been minimized.

Show comment
Hide comment
@michael-crabtree

michael-crabtree May 6, 2012

michael-crabtree commented May 6, 2012

@ashchan

This comment has been minimized.

Show comment
Hide comment
@ashchan

ashchan May 6, 2012

@crabacus I don't know how the SDK changed for storyboarding, but I'm able to make PFQueryTableViewController work with storyboard as this:

  • from storyboard, add a UITableViewController
  • change the view controller's class to PFQueryTableViewController
  • on Identifier inspector, add a User Defined Runtime Attribute, the key path should be 'className', and the value is the PFObject class you will use (for example, 'Post')
  • now pushing this view controller from navigation controller or other view controller should work.

The problem with PFQueryTableViewController, or many other view controllers from 3rd party libs is they have a init method that requires special parameter. Storyboard seems to only call initWithNibName:bundle: or init. For PFQueryTableViewController, writing our own init or initWithStyle is not helpful, as for some reasons these are not called at all. As @jroes has described, initWithCode: is called, but overriding initWithCode is very strange.

ashchan commented May 6, 2012

@crabacus I don't know how the SDK changed for storyboarding, but I'm able to make PFQueryTableViewController work with storyboard as this:

  • from storyboard, add a UITableViewController
  • change the view controller's class to PFQueryTableViewController
  • on Identifier inspector, add a User Defined Runtime Attribute, the key path should be 'className', and the value is the PFObject class you will use (for example, 'Post')
  • now pushing this view controller from navigation controller or other view controller should work.

The problem with PFQueryTableViewController, or many other view controllers from 3rd party libs is they have a init method that requires special parameter. Storyboard seems to only call initWithNibName:bundle: or init. For PFQueryTableViewController, writing our own init or initWithStyle is not helpful, as for some reasons these are not called at all. As @jroes has described, initWithCode: is called, but overriding initWithCode is very strange.

@andwang

This comment has been minimized.

Show comment
Hide comment
@andwang

andwang May 7, 2012

@crabacus, what is the problem you are seeing with using PFQueryTableViewController in storyboard?

andwang commented May 7, 2012

@crabacus, what is the problem you are seeing with using PFQueryTableViewController in storyboard?

@andwang

This comment has been minimized.

Show comment
Hide comment
@andwang

andwang May 7, 2012

@crabacus, send me an email at andrew ( at parse )

andwang commented May 7, 2012

@crabacus, send me an email at andrew ( at parse )

@michael-crabtree

This comment has been minimized.

Show comment
Hide comment
@michael-crabtree

michael-crabtree May 7, 2012

michael-crabtree commented May 7, 2012

@andwang

This comment has been minimized.

Show comment
Hide comment
@andwang

andwang May 7, 2012

@crabacus, thanks for the positive feedback you gave us. Correct me if I am wrong, you are saying PFQueryTableViewController is now working with storyboard fine. That is definitely part of our latest changes to PFQueryTableViewController.

I entirely agree with what you said about PFQueryTableViewController's inheritance from UITableViewController. Your reasoning is also in complete agreement with mine. I have already planned making this change; stay tuned.

I am a fan of Core Data. Right now to use Core Data with Parse leads to a lot of boilerplate code. It is also on my plate to make this simple and straightforward. Again, stay tuned for the upcoming changes.

Cheers!
-Andrew

andwang commented May 7, 2012

@crabacus, thanks for the positive feedback you gave us. Correct me if I am wrong, you are saying PFQueryTableViewController is now working with storyboard fine. That is definitely part of our latest changes to PFQueryTableViewController.

I entirely agree with what you said about PFQueryTableViewController's inheritance from UITableViewController. Your reasoning is also in complete agreement with mine. I have already planned making this change; stay tuned.

I am a fan of Core Data. Right now to use Core Data with Parse leads to a lot of boilerplate code. It is also on my plate to make this simple and straightforward. Again, stay tuned for the upcoming changes.

Cheers!
-Andrew

@ilTofa

This comment has been minimized.

Show comment
Hide comment
@ilTofa

ilTofa Jun 21, 2012

I have a bunch of problems with this code. I upgraded Parse SDK to 1.0.47. Using XCode 4.4.3 (stable). Project uses Storyboards.

  1. @jamesyu I'm sorry but my derived class crashes if I use initWithStyle inizialization. Error is:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: classname)'

I still use the initWithCoder as in comment 1 (and it still works)

  1. self.keyToDisplay is not on class definition anymore (or at least Xcode complains that property is not found).

  2. I use to get back to a delegate for processing (I think this is a typical pattern) as in

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
    [super tableView:tableView didSelectRowAtIndexPath:indexPath];
    [self.delegate radioChooserViewControllerDidSelect:self withObject:[self objectAtIndex:indexPath]];
}

This crashes when user clicks on the "load more" cell. This is understandable, I know, but I have no way to know if I'm on a "pagination cell" without doing pagination myself...
Crash is

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 25 beyond bounds [0 .. 24]

This is for a 25 rows pagination, of course.

Any hint? (3) makes the class unusable for me.

ilTofa commented Jun 21, 2012

I have a bunch of problems with this code. I upgraded Parse SDK to 1.0.47. Using XCode 4.4.3 (stable). Project uses Storyboards.

  1. @jamesyu I'm sorry but my derived class crashes if I use initWithStyle inizialization. Error is:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: classname)'

I still use the initWithCoder as in comment 1 (and it still works)

  1. self.keyToDisplay is not on class definition anymore (or at least Xcode complains that property is not found).

  2. I use to get back to a delegate for processing (I think this is a typical pattern) as in

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
    [super tableView:tableView didSelectRowAtIndexPath:indexPath];
    [self.delegate radioChooserViewControllerDidSelect:self withObject:[self objectAtIndex:indexPath]];
}

This crashes when user clicks on the "load more" cell. This is understandable, I know, but I have no way to know if I'm on a "pagination cell" without doing pagination myself...
Crash is

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 25 beyond bounds [0 .. 24]

This is for a 25 rows pagination, of course.

Any hint? (3) makes the class unusable for me.

@michael-crabtree

This comment has been minimized.

Show comment
Hide comment
@michael-crabtree

michael-crabtree Jun 22, 2012

If you are using the PFQueryTableViewController and have pagination enabled then you need to take the pagination cell into account when overriding the tableview didSelectRowAtIndexPath method. Essentially, if you are not on the pagination row handle the touch with your own method, otherwise pass touch to the parent implementation. Something like this should work:

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
    if (indexPath.row < [self.objects count])
    {
        // Your custom row select code here
        [self.delegate radioChooserViewControllerDidSelect:self withObject:[self objectAtIndex:indexPath]];
    } else {
        // This is the pagination cell so let the parent handle it
        [super tableView:tableView didSelectRowAtIndexPath:indexPath];
    }
}

As far as using initWithStyle or initWithCoder, neither of those are really necessary with a Storyboard implementation and in fact initWithStyle will probably lead to problems. In your Storyboard with the PFQueryTableViewController scene selected, look at the Identity Inspector tab and there should be an area for User Defined Runtime Attributes. You can configure the className, objectsPerPage, pullToRefreshEnabled, and paginationEnabled right there (as well as any other needed properties). You can see a screenshot of what I mean right here:

http://crabtree.net/userDefinedRuntimeAttributes.jpg

As for the keyToDisplay property I have never used it but it may not exist anymore as I don't see it in the API. You might try using the textKey property instead. That could also be configured in the user defined runtime attributes in the Storyboard, although I usually just override tableView:cellForRowAtIndexPath:object: and create custom cell views.

Anyway, hopefully some of that will help you out.

michael-crabtree commented Jun 22, 2012

If you are using the PFQueryTableViewController and have pagination enabled then you need to take the pagination cell into account when overriding the tableview didSelectRowAtIndexPath method. Essentially, if you are not on the pagination row handle the touch with your own method, otherwise pass touch to the parent implementation. Something like this should work:

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
    if (indexPath.row < [self.objects count])
    {
        // Your custom row select code here
        [self.delegate radioChooserViewControllerDidSelect:self withObject:[self objectAtIndex:indexPath]];
    } else {
        // This is the pagination cell so let the parent handle it
        [super tableView:tableView didSelectRowAtIndexPath:indexPath];
    }
}

As far as using initWithStyle or initWithCoder, neither of those are really necessary with a Storyboard implementation and in fact initWithStyle will probably lead to problems. In your Storyboard with the PFQueryTableViewController scene selected, look at the Identity Inspector tab and there should be an area for User Defined Runtime Attributes. You can configure the className, objectsPerPage, pullToRefreshEnabled, and paginationEnabled right there (as well as any other needed properties). You can see a screenshot of what I mean right here:

http://crabtree.net/userDefinedRuntimeAttributes.jpg

As for the keyToDisplay property I have never used it but it may not exist anymore as I don't see it in the API. You might try using the textKey property instead. That could also be configured in the user defined runtime attributes in the Storyboard, although I usually just override tableView:cellForRowAtIndexPath:object: and create custom cell views.

Anyway, hopefully some of that will help you out.

@ilTofa

This comment has been minimized.

Show comment
Hide comment
@ilTofa

ilTofa Jun 22, 2012

OK. Thank you... You should edit this gist, btw... for all 3 things. This sample is linked from iOS guide. ;)

ilTofa commented Jun 22, 2012

OK. Thank you... You should edit this gist, btw... for all 3 things. This sample is linked from iOS guide. ;)

@jamesyu

This comment has been minimized.

Show comment
Hide comment
@jamesyu

jamesyu Jun 22, 2012

We've updated the gist to fix the issues! Thanks guys!

Owner

jamesyu commented Jun 22, 2012

We've updated the gist to fix the issues! Thanks guys!

@esteluk

This comment has been minimized.

Show comment
Hide comment
@esteluk

esteluk Jul 10, 2012

There are some really helpful comments here, but does anyone have any pointers on getting PFQueryTableViewController working well with sections? I can produce the sections and count the rows, but haven't yet been able to put them together.

esteluk commented Jul 10, 2012

There are some really helpful comments here, but does anyone have any pointers on getting PFQueryTableViewController working well with sections? I can produce the sections and count the rows, but haven't yet been able to put them together.

@davidhlee

This comment has been minimized.

Show comment
Hide comment
@davidhlee

davidhlee Jul 11, 2012

Hi, I'm trying to implement a PFQueryTableViewController with storyboards, and I keep getting this error:

2012-07-11 01:31:01.360 ParseStarterProject[35323:f803] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'The nib file did not specify a UITableView as its view of PFQueryTableViewController.'

I've tried to add the "User Defined Runtime Attributes" in Interface Builder, as suggested above. But that hasn't worked.

I'm using Xcode 4.3.2 and I have the latest Parse SDK: v1.0.56 (downloaded this past week).

I've tried creating both a UITableViewController and a UIViewController (as the latest PFQueryTableViewController no longer subclasses UITableViewController by UIViewController instead). But that doesn't work either.

davidhlee commented Jul 11, 2012

Hi, I'm trying to implement a PFQueryTableViewController with storyboards, and I keep getting this error:

2012-07-11 01:31:01.360 ParseStarterProject[35323:f803] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'The nib file did not specify a UITableView as its view of PFQueryTableViewController.'

I've tried to add the "User Defined Runtime Attributes" in Interface Builder, as suggested above. But that hasn't worked.

I'm using Xcode 4.3.2 and I have the latest Parse SDK: v1.0.56 (downloaded this past week).

I've tried creating both a UITableViewController and a UIViewController (as the latest PFQueryTableViewController no longer subclasses UITableViewController by UIViewController instead). But that doesn't work either.

@nachovz

This comment has been minimized.

Show comment
Hide comment
@nachovz

nachovz Aug 21, 2012

Hi! Is it possible to use this class to control a UITableView (not fullscreen table view dragged from Objects Library to an existing ViewController)?

nachovz commented Aug 21, 2012

Hi! Is it possible to use this class to control a UITableView (not fullscreen table view dragged from Objects Library to an existing ViewController)?

@Jimexist

This comment has been minimized.

Show comment
Hide comment
@Jimexist

Jimexist Aug 24, 2012

@davidhlee

I am using storyboard and I got a similar exception saying that the loaded viewcontroller get something that is not UITableViewController. I checked the storyboard and in the Interface Builder I deleted the view under the ViewController (the IB created it in the first time), and It works for me. Guessing it's that view masked the UITableView that comes along with PFQueryTableViewController. Maybe you might also want to check on that.

Jimexist commented Aug 24, 2012

@davidhlee

I am using storyboard and I got a similar exception saying that the loaded viewcontroller get something that is not UITableViewController. I checked the storyboard and in the Interface Builder I deleted the view under the ViewController (the IB created it in the first time), and It works for me. Guessing it's that view masked the UITableView that comes along with PFQueryTableViewController. Maybe you might also want to check on that.

@jesseXu

This comment has been minimized.

Show comment
Hide comment
@jesseXu

jesseXu Sep 25, 2012

I'm trying to set the tableviewcell's separate color

self.tableView.separatorStyle = UITableViewCellSeparatorStyleNone; 

but it didn't work.

jesseXu commented Sep 25, 2012

I'm trying to set the tableviewcell's separate color

self.tableView.separatorStyle = UITableViewCellSeparatorStyleNone; 

but it didn't work.

@Snwspeckle

This comment has been minimized.

Show comment
Hide comment
@Snwspeckle

Snwspeckle Oct 9, 2012

One thing that needs made easier is the ability to create DetailViewControllers using storyboards and Parse. Currently I have it working but I had to include a lot of extra code that shouldn't be required.

Snwspeckle commented Oct 9, 2012

One thing that needs made easier is the ability to create DetailViewControllers using storyboards and Parse. Currently I have it working but I had to include a lot of extra code that shouldn't be required.

@biganth

This comment has been minimized.

Show comment
Hide comment
@biganth

biganth Feb 4, 2013

Noob question here.

@crabacus mentioned, "As far as using initWithStyle or initWithCoder, neither of those are really necessary with a Storyboard implementation".

Everything is working fine with initWithCoder but when I remove the init method to use the Storyboard it crashes.

@crabacus also mentions to change the view controller's class to PFQueryTableViewController but in MasterViewController.h I have it sub-classed as so: @interface MasterViewController : PFQueryTableViewController and according to https://parse.com/tutorials/geolocations (section 2) they don't change the custom class in Identity Inspector when it's already set as a sub-class.

Any help much appreciated.

biganth commented Feb 4, 2013

Noob question here.

@crabacus mentioned, "As far as using initWithStyle or initWithCoder, neither of those are really necessary with a Storyboard implementation".

Everything is working fine with initWithCoder but when I remove the init method to use the Storyboard it crashes.

@crabacus also mentions to change the view controller's class to PFQueryTableViewController but in MasterViewController.h I have it sub-classed as so: @interface MasterViewController : PFQueryTableViewController and according to https://parse.com/tutorials/geolocations (section 2) they don't change the custom class in Identity Inspector when it's already set as a sub-class.

Any help much appreciated.

@bjackson

This comment has been minimized.

Show comment
Hide comment
@bjackson

bjackson Mar 22, 2013

The className property has been changed to parseClassName property.

bjackson commented Mar 22, 2013

The className property has been changed to parseClassName property.

@exalted

This comment has been minimized.

Show comment
Hide comment
@exalted

exalted Oct 22, 2013

👍 @bjackson true that.

exalted commented Oct 22, 2013

👍 @bjackson true that.

@davidolesch

This comment has been minimized.

Show comment
Hide comment
@davidolesch

davidolesch Jan 17, 2014

- (PFObject *)objectAtIndex:(NSIndexPath *)indexPath

should be

- (PFObject *)objectAtIndexPath:(NSIndexPath *)indexPath

davidolesch commented Jan 17, 2014

- (PFObject *)objectAtIndex:(NSIndexPath *)indexPath

should be

- (PFObject *)objectAtIndexPath:(NSIndexPath *)indexPath
@xVinicius

This comment has been minimized.

Show comment
Hide comment
@xVinicius

xVinicius May 6, 2014

Hello, please update line 20 and 106 from:

    // The className to query on
    self.className = @"Foo";

to:

    // The className to query on
    self.parseClassName = @"Foo";

xVinicius commented May 6, 2014

Hello, please update line 20 and 106 from:

    // The className to query on
    self.className = @"Foo";

to:

    // The className to query on
    self.parseClassName = @"Foo";
@ericfr

This comment has been minimized.

Show comment
Hide comment
@ericfr

ericfr May 21, 2014

talking about efficient code. this is awesome template!

ericfr commented May 21, 2014

talking about efficient code. this is awesome template!

@fssherwani

This comment has been minimized.

Show comment
Hide comment
@fssherwani

fssherwani Jun 11, 2014

very good help

fssherwani commented Jun 11, 2014

very good help

@abs8090

This comment has been minimized.

Show comment
Hide comment
@abs8090

abs8090 Aug 14, 2014

Hi,
I'm new to Parse and have this request. I want to build tho simple app in which I used Navigation controller ( so that I can go forward and backward from the main view) and has two buttons in the first view that will appear for the user, and each button will take the user to a different view. I dragged and dropped two view controllers, created a class named "CommentsViewController" which is a subclass of PFQueryTableViewController and assigned it to one of the two view controllers. Finally, I press on one button in the main view ctrl+click and drag to that view controller that has the above class assigned to it and clicked on push. Unfortunalty my app crashes when I want to go this view.
Any idea why??

abs8090 commented Aug 14, 2014

Hi,
I'm new to Parse and have this request. I want to build tho simple app in which I used Navigation controller ( so that I can go forward and backward from the main view) and has two buttons in the first view that will appear for the user, and each button will take the user to a different view. I dragged and dropped two view controllers, created a class named "CommentsViewController" which is a subclass of PFQueryTableViewController and assigned it to one of the two view controllers. Finally, I press on one button in the main view ctrl+click and drag to that view controller that has the above class assigned to it and clicked on push. Unfortunalty my app crashes when I want to go this view.
Any idea why??

@ThinkNate

This comment has been minimized.

Show comment
Hide comment
@ThinkNate

ThinkNate Aug 23, 2014

please update line 20 and 106 from:

// The className to query on
self.className = @"Foo";

to:

// The className to query on
self.parseClassName = @"Foo";

ThinkNate commented Aug 23, 2014

please update line 20 and 106 from:

// The className to query on
self.className = @"Foo";

to:

// The className to query on
self.parseClassName = @"Foo";
@nebiros

This comment has been minimized.

Show comment
Hide comment
@nebiros

nebiros Sep 4, 2014

Also, about storyboards, try commonInit pattern.

- (void)commonInit
{
    self.parseClassName = @"Foo";
    self.pullToRefreshEnabled = YES;
    self.paginationEnabled = YES;
    self.objectsPerPage = 25;
    self.loadingViewEnabled = NO;
}

- (id)initWithStyle:(UITableViewStyle)style
{
    self = [super initWithStyle:style];
    if (!self) return nil;

    [self commonInit];

    return self;
}

- (id)initWithNibName:(NSString *)nibNameOrNil bundle:(NSBundle *)nibBundleOrNil
{
    self = [super initWithNibName:nibNameOrNil bundle:nibBundleOrNil];
    if (!self) return nil;

    [self commonInit];

    return self;
}

- (id)initWithCoder:(NSCoder *)aDecoder
{
    self = [super initWithCoder:aDecoder];
    if (!self) return nil;

    [self commonInit];

    return self;
}

nebiros commented Sep 4, 2014

Also, about storyboards, try commonInit pattern.

- (void)commonInit
{
    self.parseClassName = @"Foo";
    self.pullToRefreshEnabled = YES;
    self.paginationEnabled = YES;
    self.objectsPerPage = 25;
    self.loadingViewEnabled = NO;
}

- (id)initWithStyle:(UITableViewStyle)style
{
    self = [super initWithStyle:style];
    if (!self) return nil;

    [self commonInit];

    return self;
}

- (id)initWithNibName:(NSString *)nibNameOrNil bundle:(NSBundle *)nibBundleOrNil
{
    self = [super initWithNibName:nibNameOrNil bundle:nibBundleOrNil];
    if (!self) return nil;

    [self commonInit];

    return self;
}

- (id)initWithCoder:(NSCoder *)aDecoder
{
    self = [super initWithCoder:aDecoder];
    if (!self) return nil;

    [self commonInit];

    return self;
}
@simontaen

This comment has been minimized.

Show comment
Hide comment
@simontaen

simontaen Sep 6, 2014

When deleting in

- (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath

I always have to reload the complete data set using [self loadObjects]. This seems wasteful and I'd love to see support to delete/reload single rows such that it can be used in combination with

[tableView deleteRowsAtIndexPaths:@[indexPath] withRowAnimation:UITableViewRowAnimationFade]

simontaen commented Sep 6, 2014

When deleting in

- (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath

I always have to reload the complete data set using [self loadObjects]. This seems wasteful and I'd love to see support to delete/reload single rows such that it can be used in combination with

[tableView deleteRowsAtIndexPaths:@[indexPath] withRowAnimation:UITableViewRowAnimationFade]

@mortonimus

This comment has been minimized.

Show comment
Hide comment
@mortonimus

mortonimus Nov 13, 2014

Are there plans for (or is there already) a similar sample subclass template file in Swift?

mortonimus commented Nov 13, 2014

Are there plans for (or is there already) a similar sample subclass template file in Swift?

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 12, 2015

Any idea where I cold find this in SWIFT?

ghost commented Feb 12, 2015

Any idea where I cold find this in SWIFT?

@SharkyZg

This comment has been minimized.

Show comment
Hide comment
@SharkyZg

SharkyZg Mar 27, 2015

I agree with herveg, we would really appreciate the template written in Swift. Now its more pain than gain ...

SharkyZg commented Mar 27, 2015

I agree with herveg, we would really appreciate the template written in Swift. Now its more pain than gain ...

@zsll

This comment has been minimized.

Show comment
Hide comment
@zsll

zsll Apr 29, 2015

Really appreciate it if you can have a swift version of this.

zsll commented Apr 29, 2015

Really appreciate it if you can have a swift version of this.

@msamoylov

This comment has been minimized.

Show comment
Hide comment
@msamoylov

msamoylov May 2, 2015

+1 for a modern Swift implementation.

msamoylov commented May 2, 2015

+1 for a modern Swift implementation.

@Caraveo

This comment has been minimized.

Show comment
Hide comment
@Caraveo

Caraveo May 7, 2015

What's the best way to reload the TableView and re-run the query programmatically(not using an interface control or gesture)? I think [self.tableView reloadData]; reloads the table view with the original query data not the refreshed data. Please help, Thanks!

EDIT: [self loadObjects];
Seems to do the task. Thanks!

Caraveo commented May 7, 2015

What's the best way to reload the TableView and re-run the query programmatically(not using an interface control or gesture)? I think [self.tableView reloadData]; reloads the table view with the original query data not the refreshed data. Please help, Thanks!

EDIT: [self loadObjects];
Seems to do the task. Thanks!

@phalladar

This comment has been minimized.

Show comment
Hide comment
@phalladar

phalladar commented Jul 22, 2015

Swift++

@Vortec4800

This comment has been minimized.

Show comment
Hide comment
@Vortec4800

Vortec4800 Oct 9, 2015

Here's one that supports Storyboards, customizing the default cells, changes the row height and adds a sort to the generated query written in Swift. Doesn't include everything as listed above but should get some of you guys started.

import UIKit
import Parse
import ParseUI

class ShipmentListViewController: PFQueryTableViewController {

    required init?(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)

        // The className to query on
        self.parseClassName = "ClassName"

        // The key of the PFObject to display in the label of the default cell style
        self.textKey = "text"

        // Uncomment the following line to specify the key of a PFFile on the PFObject to display in the imageView of the default cell style
        self.imageKey = "image"

        // Whether the built-in pull-to-refresh is enabled
        self.pullToRefreshEnabled = true

        // Whether the built-in pagination is enabled
        self.paginationEnabled = true

        // The number of objects to show per page
        self.objectsPerPage = 25
    }

    override func viewDidLoad() {
        super.viewDidLoad()

        self.tableView.rowHeight = 54.0
    }

    override func didReceiveMemoryWarning() {
        super.didReceiveMemoryWarning()
        // Dispose of any resources that can be recreated.
    }

    override func queryForTable() -> PFQuery {
        let query = super.queryForTable()

        query.orderByAscending("createdAt")

        return query
    }

    override func tableView(tableView: UITableView, cellForRowAtIndexPath indexPath: NSIndexPath, object: PFObject?) -> PFTableViewCell? {
        let cell = super.tableView(tableView, cellForRowAtIndexPath: indexPath, object: object)

        // Configure the cell
        cell?.imageView?.contentMode = .ScaleAspectFill
        cell?.imageView?.clipsToBounds = true
        cell?.accessoryType = .DisclosureIndicator

        return cell
    }

    /*
    // MARK: - Navigation

    // In a storyboard-based application, you will often want to do a little preparation before navigation
    override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?) {
        // Get the new view controller using segue.destinationViewController.
        // Pass the selected object to the new view controller.
    }
    */

}

Vortec4800 commented Oct 9, 2015

Here's one that supports Storyboards, customizing the default cells, changes the row height and adds a sort to the generated query written in Swift. Doesn't include everything as listed above but should get some of you guys started.

import UIKit
import Parse
import ParseUI

class ShipmentListViewController: PFQueryTableViewController {

    required init?(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)

        // The className to query on
        self.parseClassName = "ClassName"

        // The key of the PFObject to display in the label of the default cell style
        self.textKey = "text"

        // Uncomment the following line to specify the key of a PFFile on the PFObject to display in the imageView of the default cell style
        self.imageKey = "image"

        // Whether the built-in pull-to-refresh is enabled
        self.pullToRefreshEnabled = true

        // Whether the built-in pagination is enabled
        self.paginationEnabled = true

        // The number of objects to show per page
        self.objectsPerPage = 25
    }

    override func viewDidLoad() {
        super.viewDidLoad()

        self.tableView.rowHeight = 54.0
    }

    override func didReceiveMemoryWarning() {
        super.didReceiveMemoryWarning()
        // Dispose of any resources that can be recreated.
    }

    override func queryForTable() -> PFQuery {
        let query = super.queryForTable()

        query.orderByAscending("createdAt")

        return query
    }

    override func tableView(tableView: UITableView, cellForRowAtIndexPath indexPath: NSIndexPath, object: PFObject?) -> PFTableViewCell? {
        let cell = super.tableView(tableView, cellForRowAtIndexPath: indexPath, object: object)

        // Configure the cell
        cell?.imageView?.contentMode = .ScaleAspectFill
        cell?.imageView?.clipsToBounds = true
        cell?.accessoryType = .DisclosureIndicator

        return cell
    }

    /*
    // MARK: - Navigation

    // In a storyboard-based application, you will often want to do a little preparation before navigation
    override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?) {
        // Get the new view controller using segue.destinationViewController.
        // Pass the selected object to the new view controller.
    }
    */

}
@stefanocoding

This comment has been minimized.

Show comment
Hide comment
@stefanocoding

stefanocoding Nov 21, 2015

For the ones that want to do the same in Swift, you can check the examples provided by Parse: https://github.com/ParsePlatform/ParseUI-iOS/tree/master/ParseUIDemo/Swift/CustomViewControllers/QueryTableViewController

stefanocoding commented Nov 21, 2015

For the ones that want to do the same in Swift, you can check the examples provided by Parse: https://github.com/ParsePlatform/ParseUI-iOS/tree/master/ParseUIDemo/Swift/CustomViewControllers/QueryTableViewController

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment