Welcome, Guest
Username Password: Remember me

Sub Menu on the iPad Split View Example
(1 viewing) (1) Guest
  • Page:
  • 1

TOPIC: Sub Menu on the iPad Split View Example

Sub Menu on the iPad Split View Example 1 year, 5 months ago #1

Afternoon

Is it possible to have a submenu on the iPad Split View example.

For example, If I had a book with 2 Chapters, each with 40 pages, rather than showing 80 rows, I would show 2 - one called Chapter 1 and the other called Chapter 2, then when you click on the Chapter, it would take you there, then there would be 40 rows to review.

Iain
  • ihmunro
  • OFFLINE
  • Expert Boarder
  • Posts: 135
  • Karma: 0

Re: Sub Menu on the iPad Split View Example 1 year, 5 months ago #2

How are you implementing your books and chapters? (eg. Core Data entities or normal objects?) Also, I am not sure I completely understand what you mean by a "sub menu".
  • tarekskr
  • OFFLINE
  • Administrator
  • Posts: 2402
  • Karma: 72

Re: Sub Menu on the iPad Split View Example 1 year, 5 months ago #3

Hi Tarek

Still not sure about which way I am doing it - core data or normal objects as I still dont know which is the better or more advantageous.

What I mean by a sub menu is as follows:

At the moment, there is a rootviewcontroller that provide you with a row listing.

If I have 40 pages, the only way I can see listing them is all 40 together - but 20 belong to one chapter and the other 20 belong to the other chapter.

What I want is the first list or rows to show Chapter 1 and Chapter 2, then when I click on Chapter 1, it takes me to another rootviewcontroller that shows the pages.

I was also thinking could this be done with sections on the rootviewcontroller ? which have a click down option ?

Iain
  • ihmunro
  • OFFLINE
  • Expert Boarder
  • Posts: 135
  • Karma: 0

Re: Sub Menu on the iPad Split View Example 1 year, 5 months ago #4

Hi Iain,

The reason I am asking if you're using Core Data is that you'll be able have STV do what you want almost automatically by using a Core Data feature called "relationships", where there will be a one to many relationship between book & chapters, and between chapter and pages. I would almost certainly recommend that you use Core Data. Please check out the books from my previous post.
  • tarekskr
  • OFFLINE
  • Administrator
  • Posts: 2402
  • Karma: 72
  • Page:
  • 1
Time to create page: 0.75 seconds