danieltiger / pilot Goto Github PK

Transition animation isn't supported yet. Maybe one day we can have custom animation support, but for now, support for the stock transitions will do.

No longer needed?

It would be cool to have a method that doesn't add on top of the navigation stack, like:

[Pilot showModel:myModel replaceCurrentView:YES animated:whatever];

These should call showObject:withSelector:animation but be simpler for people to use.

We need a test app where we can run this through the paces.

This is on my laptop, I don't know if I have the same problem at work but I get the following error when I try and run either test app:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Cannot create an NSPersistentStoreCoordinator with a nil model'

I traced it back to:

NSURL *modelURL = [[NSBundle mainBundle] URLForResource:@"PilotTestApp" withExtension:@"momd"];
__managedObjectModel = [[NSManagedObjectModel alloc] initWithContentsOfURL:modelURL];

modelURL is nil for some reason. I tried changing that code to the more accepted:

[NSManagedObjectModel mergedModelFromBundles:nil];

Which solved the nil problem but then it crashed because it couldn't find an entity named redObject.

We need to make sure our coverage is a lot better, and that we have helpful NSAsserts sprinkled around

We now have the models and the VCs, we just need to create model instances in the app delegate, then try pushing them on.

Currently animation is shown, even if UIAnimationOptionTransitionNone is used. Probably need to use our own enum for Pilot animations. Maybe we can add our own style animations, if that is useful.

Before Posterous posts about this open source project, we need to make sure our README is bomber.

We need an NSObject subclass that handles the pushing/popping of UIViewControllers

This should be optional. If the protocol is implemented then use it otherwise use [object objectID] instead. Will remove the need to have PTObject.

We need an app delegate superclass that has the UINavigationController on it.

We need a few simple models and view controllers to build a mock app to navigate around with. I suggest something like:

RootViewController.h/.m

Red.h/m
RedViewController.h/.m

Blue.h/m
BlueViewController.h/.m

Green.h/.m
GreenViewController.h/.m

Tapping on the RootViewController loads Red. Tapping on Red loads Blue, etc. Then maybe you could put a label in the middle of the view that shows how deep you are in the stack. Or maybe we could load an image in each VC view and test how deep in the VC stack we can go with properly view unloading.

For pushing views it should use the visible navigation controller.

An admin needs to do this.

http://pages.github.com/

We need a way for Pilot to access the UINavigationController

We need support to show a modal VC

We should integrate Appledocs into Pilot.

https://github.com/tomaz/appledoc

The finest grain method we have it lets you convert a model to a viewController and the run it with a specific selector and animation style.

for testing initWithTabBarController

Make sure to fail with useful error when the RootViewController class can't be found.

We need a way to not only call a custom init on a VC, but also a way to pass in an object, to use in the init.

Post -> PostViewController