Unity and Baker Framework – Tutorial 1 of 2. This post is designed to help anyone using the Baker Framework (iOS eBook development) add 2D or 3D interactivity through Unity (popular game engine). By the end of this tutorial you will be able to add a simple 3D scene from Unity as a page into your Baker book, share information between the two tools and have a method of switching between the two as needed. Some long run potential uses for this: Integrating 2D/3D games into educational booksDevelop complex interactive learning experiences in Unity then dynamically feed book content based on performanceAdd models of high resolution digitized historical artifacts Obviously I am not teaching you to do all this, but having Unity as a tool inside your book will put those capabilities within your grasp.
I am biased towards educational uses, but I am sure there are plenty of recreational ideas out there! The battle plan Here is a summary of our major steps with the first one being the focus of this tutorial portion: Get started with Unity. Laker compendium – Designing digital publications in HTML5. Bakerframework/baker. How to package an HPub · bakerframework/baker Wiki. Preparing the Publication First of all, a HPub publication is like a HTML5 microsite.
You should be able to see it in a standard browser and test it in Mobile Safari (it will miss the pagination and Baker features of course, but it should work). This is important because it means that if your application shows and works correctly in Mobile Safari, then it's almost sure it will work in Baker. To prepare a publication just write it like a microsite, having a HTML file for each page inside Baker and have them ordered sequentially. Prepare also an index.html file, that will be visualized inside Baker when you double-tap the screen. Package When your publication is ready and tested in Mobile Safari, you have to wrap it up into a nice package to include it in Baker. Create a folder (e.g. a-study-in-scarlet) and copy all your publication files into that. After these simple steps are completed, your publication folder will contain an upacked HPub. Newsstand App Standalone App ... and one more thing. Book.json Baker extension parameters · Simbul/baker Wiki.
Book protocol · Simbul/baker Wiki. NOTE: Baker 4.1 support only a subset of the book protocol features (see below), while Baker 4.0 does not support the book protocol.
If you want to take advantege of the full book protocol use version 3.2.x instead. The HPub specification defines a protocol to identify books. Here is an example of the syntax for a book URL: Two great advantages: We are able to uniquely identify a book: being a URL the path is unique and it can be used to identify: a uniquely owned domain (i.e. example.org)a specific path (i.e. whatever/whenever)a specific publication (i.e. publication)format (i.e. hpub)Once we have identified a book, we can add further elements to the URL, to refer to specific items inside it: filename (i.e. filename.html)anchor (i.e. Notes: The specific extension can be omitted: in that scenario, the reading software might try to download the extension that is best suited. JSONLint - The JSON Validator. Brackets Extension Registry. Hpub specification · bakerframework/baker Wiki.
Tutorial for Standalone App · bakerframework/baker Wiki. Using Baker is simple and even if there are some technicalities involved, it's doable with just basic technical knowledge.
This tutorial assumes that you choose the Standalone publication support in Baker. If you're not sure, read here. A Mac with XcodeAn Apple iOS Developer account (required to publish to the store). Create your issues using the HPub tutorial. Add your Hpub publications in the books folder in Xcode (unzipped, one publication per sub-folder) and build the application. Within Xcode, open file UIConstants.h inside the BakerShelf folder. Test your publication, subscriptions and downloadsIf you have problems check the Problems and Debugging page.When you're ready, submit to the App Store. Baker Framework. Baker 4.2.1 Release. In5 v1.2 now supports Liquid Layout and Baker Framework.
In5 v1.2 now supports Liquid Layout and Baker Framework We’ve got some big new additions to in5 (InDesign to HTML5).
These updates, like all version 1.x updates, are available at no charge to existing in5 users. Take a gander. Liquid Layout InDesign CS6 added the Liquid Layout functionality that allows you to controls how and when your page items scale and re-position themselves. In5 even allows older versions of InDesign to use Liquid Layout (it simply defaults to scale mode). For more on using Liquid Layout in InDesign, check out: