Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes, custom container view is the way to go (iOS 5 and greater). You basically write your own custom container, using the built-in <code>childViewControllers</code> property to keep track of all of the child view controllers. You may want your own property, say <code>currentChildIndex</code>, to keep track of which child controller you're currently on:</p> <pre><code>@property (nonatomic) NSInteger currentChildIndex; </code></pre> <p>Your parent controller should probably have some push and pop methods for non-swipe related navigation, such as:</p> <pre><code>- (void)pushChildViewController:(UIViewController *)newChildController { // remove any other children that we've popped off, but are still lingering about for (NSInteger index = [self.childViewControllers count] - 1; index &gt; self.currentChildIndex; index--) { UIViewController *childController = self.childViewControllers[index]; [childController willMoveToParentViewController:nil]; [childController.view removeFromSuperview]; [childController removeFromParentViewController]; } // get reference to the current child controller UIViewController *currentChildController = self.childViewControllers[self.currentChildIndex]; // set new child to be off to the right CGRect frame = self.containerView.bounds; frame.origin.x += frame.size.width; newChildController.view.frame = frame; // add the new child [self addChildViewController:newChildController]; [self.containerView addSubview:newChildController.view]; [newChildController didMoveToParentViewController:self]; [UIView animateWithDuration:0.5 animations:^{ CGRect frame = self.containerView.bounds; newChildController.view.frame = frame; frame.origin.x -= frame.size.width; currentChildController.view.frame = frame; }]; self.currentChildIndex++; } - (void)popChildViewController { if (self.currentChildIndex == 0) return; UIViewController *currentChildController = self.childViewControllers[self.currentChildIndex]; self.currentChildIndex--; UIViewController *previousChildController = self.childViewControllers[self.currentChildIndex]; CGRect onScreenFrame = self.containerView.bounds; CGRect offToTheRightFrame = self.containerView.bounds; offToTheRightFrame.origin.x += offToTheRightFrame.size.width; [UIView animateWithDuration:0.5 animations:^{ currentChildController.view.frame = offToTheRightFrame; previousChildController.view.frame = onScreenFrame; }]; } </code></pre> <p>Personally, I have a protocol defined for these two methods, and make sure that my parent controller is configured to conform to that protocol:</p> <pre><code>@protocol ParentControllerDelegate &lt;NSObject&gt; - (void)pushChildViewController:(UIViewController *)newChildController; - (void)popChildViewController; @end @interface ParentViewController : UIViewController &lt;ParentControllerDelegate&gt; ... @end </code></pre> <p>Then, when a child wants to push a new child on, it can do it like so:</p> <pre><code>ChildViewController *controller = ... // instantiate and configure your next controller however you want to do that id&lt;ParentControllerDelegate&gt; parent = (id)self.parentViewController; NSAssert([parent conformsToProtocol:@protocol(ParentControllerDelegate)], @"Parent must conform to ParentControllerDelegate"); [parent pushChildViewController:controller]; </code></pre> <p>When a child wants to pop itself off, it can do it like so:</p> <pre><code>id&lt;ParentControllerDelegate&gt; parent = (id)self.parentViewController; NSAssert([parent conformsToProtocol:@protocol(ParentControllerDelegate)], @"Parent must conform to ParentControllerDelegate"); [parent popChildViewController]; </code></pre> <p>And then the parent view controller has a pan gesture set up, to handle the user panning from one child to another:</p> <pre><code>- (void)handlePan:(UIPanGestureRecognizer *)gesture { static UIView *currentView; static UIView *previousView; static UIView *nextView; if (gesture.state == UIGestureRecognizerStateBegan) { // identify previous view (if any) if (self.currentChildIndex &gt; 0) { UIViewController *previous = self.childViewControllers[self.currentChildIndex - 1]; previousView = previous.view; } else { previousView = nil; } // identify next view (if any) if (self.currentChildIndex &lt; ([self.childViewControllers count] - 1)) { UIViewController *next = self.childViewControllers[self.currentChildIndex + 1]; nextView = next.view; } else { nextView = nil; } // identify current view UIViewController *current = self.childViewControllers[self.currentChildIndex]; currentView = current.view; } // if we're in the middle of a pan, let's adjust the center of the views accordingly CGPoint translation = [gesture translationInView:gesture.view.superview]; previousView.transform = CGAffineTransformMakeTranslation(translation.x, 0.0); currentView.transform = CGAffineTransformMakeTranslation(translation.x, 0.0); nextView.transform = CGAffineTransformMakeTranslation(translation.x, 0.0); // if we're all done, let's animate the completion (or if we didn't move far enough, // the reversal) of the pan gesture if (gesture.state == UIGestureRecognizerStateEnded || gesture.state == UIGestureRecognizerStateCancelled || gesture.state == UIGestureRecognizerStateFailed) { CGPoint center = currentView.center; CGPoint currentCenter = CGPointMake(center.x + translation.x, center.y); CGPoint offRight = CGPointMake(center.x + currentView.frame.size.width, center.y); CGPoint offLeft = CGPointMake(center.x - currentView.frame.size.width, center.y); CGPoint velocity = [gesture velocityInView:gesture.view.superview]; if ((translation.x + velocity.x * 0.5) &lt; (-self.containerView.frame.size.width / 2.0) &amp;&amp; nextView) { // if we finished pan to left, reset transforms previousView.transform = CGAffineTransformIdentity; currentView.transform = CGAffineTransformIdentity; nextView.transform = CGAffineTransformIdentity; // set the starting point of the animation to pick up from where // we had previously transformed the views CGPoint nextCenter = CGPointMake(nextView.center.x + translation.x, nextView.center.y); currentView.center = currentCenter; nextView.center = nextCenter; // and animate the moving of the views to their final resting points, // adjusting the currentChildIndex appropriately [UIView animateWithDuration:0.25 delay:0.0 options:UIViewAnimationOptionCurveEaseOut animations:^{ currentView.center = offLeft; nextView.center = center; self.currentChildIndex++; } completion:NULL]; } else if ((translation.x + velocity.x * 0.5) &gt; (self.containerView.frame.size.width / 2.0) &amp;&amp; previousView) { // if we finished pan to right, reset transforms previousView.transform = CGAffineTransformIdentity; currentView.transform = CGAffineTransformIdentity; nextView.transform = CGAffineTransformIdentity; // set the starting point of the animation to pick up from where // we had previously transformed the views CGPoint previousCenter = CGPointMake(previousView.center.x + translation.x, previousView.center.y); currentView.center = currentCenter; previousView.center = previousCenter; // and animate the moving of the views to their final resting points, // adjusting the currentChildIndex appropriately [UIView animateWithDuration:0.25 delay:0.0 options:UIViewAnimationOptionCurveEaseOut animations:^{ currentView.center = offRight; previousView.center = center; self.currentChildIndex--; } completion:NULL]; } else { [UIView animateWithDuration:0.25 delay:0.0 options:UIViewAnimationOptionCurveEaseInOut animations:^{ previousView.transform = CGAffineTransformIdentity; currentView.transform = CGAffineTransformIdentity; nextView.transform = CGAffineTransformIdentity; } completion:NULL]; } } } </code></pre> <p>It looks like you're doing up and down panning, rather than the left-right panning that I used above, but hopefully you get the basic idea.</p> <hr> <p>By the way, in iOS 6, the user interface you're asking about (the sliding between views using gestures), could probably be done more efficiently using a built-in container controller, <a href="http://developer.apple.com/library/ios/#documentation/uikit/reference/UIPageViewControllerClassReferenceClassRef/UIPageViewControllerClassReference.html" rel="noreferrer"><code>UIPageViewController</code></a>. Just use a transition style of <code>UIPageViewControllerTransitionStyleScroll</code> and a navigation orientation of <code>UIPageViewControllerNavigationOrientationHorizontal</code>. Unfortunately, iOS 5 only allows page curl transitions, and Apple only introduced the scrolling transitions that you want in iOS 6, but if that's all you need, <code>UIPageViewController</code> gets the job done even more efficiently than what I've laid out above (you don't have to do any custom container calls, no writing of gesture recognizers, etc).</p> <p>For example, you can drag a "page view controller" onto your storyboard, create a <code>UIPageViewController</code> subclass and then in <code>viewDidLoad</code>, you need to configure the first page:</p> <pre><code>UIViewController *firstPage = [self.storyboard instantiateViewControllerWithIdentifier:@"1"]; // use whatever storyboard id your left page uses self.viewControllerStack = [NSMutableArray arrayWithObject:firstPage]; [self setViewControllers:@[firstPage] direction:UIPageViewControllerNavigationDirectionForward animated:NO completion:NULL]; self.dataSource = self; </code></pre> <p>Then you need to define the following <a href="http://developer.apple.com/library/ios/#documentation/uikit/reference/UIPageViewControllerDataSourceProtocolRef/UIPageViewControllerDataSource.html" rel="noreferrer"><code>UIPageViewControllerDataSource</code></a> methods:</p> <pre><code>- (UIViewController *)pageViewController:(UIPageViewController *)pageViewController viewControllerAfterViewController:(UIViewController *)viewController { if ([viewController isKindOfClass:[LeftViewController class]]) return [self.storyboard instantiateViewControllerWithIdentifier:@"2"]; return nil; } - (UIViewController *)pageViewController:(UIPageViewController *)pageViewController viewControllerBeforeViewController:(UIViewController *)viewController { if ([viewController isKindOfClass:[RightViewController class]]) return [self.storyboard instantiateViewControllerWithIdentifier:@"1"]; return nil; } </code></pre> <p>Your implementation will vary (at the very least different class names and different storyboard identifiers; I'm also letting the page view controller instantiate the next page's controller when the user asks for it and because I'm not retaining any strong reference to them, the'll be released when I'm done transitioning to the other page ... you could alternatively just instantiate both at startup and then these <code>before</code> and <code>after</code> routines would obviously not instantiate, but rather look them up in an array), but hopefully you get the idea. </p> <p>But the key issue is that I don't have any gesture code, no custom container view controller code, etc. Much simpler.</p>
    singulars
    1. This table or related slice is empty.
    1. PONavigating UIViewControllers with gestures in iOS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRob
    1. USRob
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONavigating UIViewControllers with gestures in iOS
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTook me awhile to get the chance to look through this, but it looks like a great starting point. Makes sense, Thanks!
      singulars
      1. PO
      1. USf.perdition
    2. CO@f.perdition By the way, the approach I laid out achieves the UX you asked about in iOS 5 and above. If targeting iOS 6 and above, you can use `UIPageViewController`, which provides the scrolling transition between views, and you don't have to write any gesture code, and it is much simpler. If you're interested in seeing that implementation, let me know.
      singulars
      1. PO
      1. USRob
    3. COThat would be massively handy if you could. I was actually working on something that just supports iOS 6 and above, I should have mentioned it, thanks again.
      singulars
      1. PO
      1. USf.perdition
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload