StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12151527
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-28T01:06:38.960
FavoriteCount
0
LastActivityDate
2012-08-28T01:06:38.960
LastEditDate
LastEditorUserId
0
OwnerUserId
1318452
ParentId
11515799
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p>The existing leaves view is hard-coded to be left-to-right. You can create a hard-coded top-to-bottom version easily enough, but there may well be more robust generic solutions.</p> <p>However, if you definitely must use leaves, you can rewrite its source to suit. The solution below hard-codes for vertical motion. If you need horizontal and vertical options, you will have more work do do.</p> <hr> <h1>Display</h1> <h2>setUpLayers</h2> <p>Reverse the axes in every call to <code>CGPointMake</code>. This fixes up the gradients that display the shadows.</p> <p>Also change <code>topPage.contentsGravity = kCAGravityLeft;</code> to <code>topPage.contentsGravity = kCAGravityBottom;</code> and <code>topPageReverseImage.contentsGravity = kCAGravityRight;</code> to <code>topPageReverseImage.contentsGravity = kCAGravityTop;</code>. This is a subtle change that makes sure incoming pages are displayed with the correct edges.</p> <h2>setLayerFrames</h2> <p>Most of the geometry changes happen here. The original code oddly uses view bounds in some places and layer bounds in others. I duplicated those, but it would be good to understand if the distinction is meaningful before using this code in production. </p> <pre><code>- (void) setLayerFrames { topPage.frame = CGRectMake(self.layer.bounds.origin.x, self.layer.bounds.origin.y, self.bounds.size.width, leafEdge * self.layer.bounds.size.height); topPageReverse.frame = CGRectMake(self.layer.bounds.origin.x, self.layer.bounds.origin.y + (2*leafEdge-1) * self.layer.bounds.size.height, self.bounds.size.width, (1-leafEdge) * self.layer.bounds.size.height); bottomPage.frame = self.layer.bounds; topPageShadow.frame = CGRectMake(0, topPageReverse.frame.origin.y - 40, bottomPage.bounds.size.width, 40); topPageReverseImage.frame = topPageReverse.bounds; topPageReverseImage.transform = CATransform3DMakeScale(1, -1, 1); topPageReverseOverlay.frame = topPageReverse.bounds; topPageReverseShading.frame = CGRectMake(0, topPageReverse.bounds.size.height - 50, topPageReverse.bounds.size.width, 50 + 1); bottomPageShadow.frame = CGRectMake(0, leafEdge * self.bounds.size.height, bottomPage.bounds.size.width, 40); topPageOverlay.frame = topPage.bounds; } </code></pre> <hr> <h1>Interaction</h1> <h2>updateTargetRects</h2> <p>Where this calculates <code>nextPageRect</code> and <code>prevPageRect</code>, put them on the bottom and top instead of the right and left.</p> <h2>touchesMoved:withEvent:</h2> <p>Change <code>self.leafEdge = touchPoint.x / self.bounds.size.width;</code> to <code>self.leafEdge = touchPoint.y / self.bounds.size.height;</code>.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPage rendering using leaves view
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDondragmer
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPage rendering using leaves view
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.