Navigation

[segundoseis]

Was: Footer bar - Navigation

As a user I think it would be interesting to have a horizontal navigation to different contents.. pages or chapters. (Footer bar)

I think that a good solution to avoid the refresh from html to html and calling a js each time... would be contain the navigation in a separate html (nav.html) and keep a top layer of the other content pages.
The navigation could have an option next and previous.

nav.html could adapted the heigth assigned by developer / designer, and it can customize perfectly the layout. :-)

example: http://itunes.apple.com/es/app/ars-technica/id393859050?mt=8

[folletto]

Interesting concept. I'd personally avoid next and previous, but nonetheless it could be a good approach. I'll think about it. :)

[ilovemac]

i'm testing just now footer and topbar for navigation page by page, using baker and jqmobile. Seems to work great.

[folletto]

Wow! Do you think you are able to distribute a demo page for developers when you're done with the testing, for us to see? ;)

[ilovemac]

For sure Folletto. I hope to distribute somethings in this weekend. i'm just looking what we can do with jquery mobile integrated with Baker.

i have see the implementation of Svdgraaf too..and i would like to use it with a final demo project.

Hope to give my contribute!

[segundoseis]

Hello! that good news ..
Only one question, if you use a js+css navigation on each page, switching to a new page refresh occurs right?. That's what I wanted to avoid a separate html page.

It will be great to see your demo with jqmobile ^_^

[folletto]

I think that's the case since that's how the book structure is built, but I think you can as well manipulate it to fit your needs. It's something I think that we'll have a lot of surprises the more people will start experimenting with it. :)

[ilovemac]

i'm sorry that i'm totally a newbie about object-c, but i learn fast :)
and sorry for the poor english too :))

[segundoseis]

Exactly! That's the good thing about this ^_^

[ilovemac]

Ok guys...it's seems to work.
I use jquery mobile for the header toolbar and integrate other script to simulate navigation page.

Can somebody help me to upload an example on my github?

[svdgraaf]

You should fork the baker project (there is button on the top), make the changes in the fork, and add a 'pull request' (also on top over here). I think that's the way to go, it was my first too :)

[ilovemac]

mmmmm....
are u sure that nothing explode? :) lol

i try to clean my baker folder before :D

[folletto]

Wait, this isn't a code change, this is just a different book, or I got something wrong? :)

If that's a book as I think, you just have to put it somewhere to allow us to download it. No github or forking required. :)

[ilovemac]

Folletto do u mean that i must zip just the BOOK/ dir and allow to download it?

http://www.ilovemac.it/book.zip

I have include jquery, jqmobile, and slidemenu by cubiq.org.

Hope it work fine

[ilovemac]

i think Baker can be used to make wonderfull HTML5 Magazine. I have already test Video in the page..and it work very well.

[folletto]

In fact, yes. Baker would be wonderful for that.

I'll try your book tomorrow! ;)

[svdgraaf]

@ilovemac: I'm already building tests with some of our magazines which are reformatted for ipad usage, works very, very good :)

[segundoseis]

Hey @ilovemac, thanks for sharing your example!
Seem to be missing some files or directories such as:
book / css / handle.png
book / gfx / toolbar_bkg.png
book / js / images / ajax-loader.png
book/Js/images/icons-18-white.png

I think it's a great choice to work with jqtouch or jquerymobile, but basically limited to use css and js for each page separately.

I think it does not solve the global navigation for hpub.

[ilovemac]

@sdvgraag: i'm waiting for your Classes implementation to send to APPSTORE my Magazine :)

Your latest fork don't seems to work fine with my ipad...but perhaps it's becouse i don't know how to clean my SDK cache...

i always see your charapter even if there aren't in my book dir...

@sugundoseis: i'm sorry...do u need a repack ?? :)

[segundoseis]

Is not necessary for me @ilovemac, but it would be interesting for others to appreciate your full demo.

I simply commented that it is a good graphics solution for html, but that does not help to have an independent global navigation. ;-)

[svdgraaf]

@ilovemac yep, that's a bug in the main branch as well. Just clean your ~Library/App support/iphone simulator//Applications/ directory, and you should be fine.

But perhaps there is a better way of cleaning up old leftover bits :)

[folletto]

About the bug: Xcode doesn't update "static" files, so if you change the content of the book/ folder you have to:

1. Clean All Targets
2. Delete the app from inside the iPad or the Simulator (you don't have to delete manually the files in the Application folder, just delete it as a normal iOS app keeping pushed the finger/mouse on the icon).

[svdgraaf]

awesome, I fixed the bug in my fork already (checks for valid number, otherwise default to page 1).

[svdgraaf]

I created a quick branch for pointing to what I'm thinking of:
https://github.com/svdgraaf/baker/tree/navigation

(tap on the window to open up that navigation). The links don't work, and rotation is a bit weird, but it works somewhat ;)

It's extremely simple, and uses a separate navigation html file. The height and location could be set in the meta file, but I'm not so sure about that.

[folletto]

But is it just the book? Could you make the book downloadable without the Framework so I can test it quickly? :)

[svdgraaf]

Nope, it's actually a separate layer in the app :)

[svdgraaf]

Wait, I just got a brainwave ;)

The solution within the pages itself is better (with the javascript and all), what we could do, is send an event once the page get's tapped (or does the uiwebview already do that?), so that the html page can do stuff as showing a menubar etc.

[folletto]

I think that's already in the code, no? ;)

[svdgraaf]

I think so, not sure ;)

[folletto]

Uhm I seem to be unable to test this branch... a few orientation quirks (probably early bugs on the master you branched) and I can't open the layer...

Let's move back to this after we merge back orientation from you and zip from Marco. ;)

[javifr]

Waiting for this navigation thing :)

[paulhontz]

I am too. This sounds really great!

[snive]

I would love to have a fixed navigationbar that don't reload with every page so any progress here?

[folletto]

Unfortunately not, because it's blocked by issue #8 since we don't want to force everyone to have a fixed navigation that defines in a specific way how you interact and see the book.

Once the issue is solved, we can start working on a overlaying UI with the navigation.

[nin9creative]

Anybody progress on this?

[folletto]

We are working on the issue #8, follow that one. This comes later. :)

[javifr]

thanks folletto. I'm also waiting for this footer nav to come also.

Cheers! Great Great Great job!

[MacBoy]

Yahoo! issue #8 has been resolved and closed!

How were you thinking of doing a footer navigation?

• iOS code to read-display contents of an XML table of contents file?
• iOS code that shows our HTML table of contents file within a URLWebView?
• iOS code that displays the file listing from the book folder?

Thank you!

[folletto]

I don't have an answer yet to those questions, we are now in design phase! :)

At this point, we'll take feedbacks, suggestions, wireframes and mockups by anyone that wants to do that, and we'll build an integrated solution. :)

If someone wants to sugest something, I'd just remind that the objective is to be as chrome-less as possible without impairing usability (or, in other terms, to avoid as much as possible any predefined UI).

[Simbul]

Implementation of the navigation (a.k.a. Index bar) has been completed in commit c8b93d1 (with some additional fixes and improvements in later commits).
Since the suggested feature has been implemented, I'm closing this issue.

[ilovemac]

Wonderfull! I Will test it very soon and hope to give u good feedback

Inviato da iPhone

Il giorno 31/mag/2011, alle ore 23:20, Simbul reply@reply.github.com ha scritto:

Implementation of the navigation (a.k.a. Index bar) has been completed in commit c8b93d1 (with some additional fixes and improvements in later commits).
Since the suggested feature has been implemented, I'm closing this issue.

Reply to this email directly or view it on GitHub:
#17 (comment)