I read http://blogs.adobe.com/indesigndocs/2012/03/guidelines-for-creating-fo lios-for-ipad-3.html and have some questions:
1. Rule one says to "Use PDF image format if possible". This do NOT work on kindle fire and other non iPad devices
- Should we make a seperate rendition for other devices?
I am confused by the difference between document size and folio size.
2. How is it possible to have a document size of 1024x768 but then create a folio rendition of 2048x1536 from the same source files?
3. Would I just use the same set of source files and choose a folio rendition of 2048x1536?
1. Yes, create separate renditions for other devices. For the Fire, create 1024x600 folios.
2. Try it! Create a 2048x1536 folio. Add or import 1024x768 articles. The content is scaled up (and the folio size will most likely double).
3. Yes, but you might have some issues with certain "pass-through overlays" such as image pans. You should check the results and then go back and use the Layers feature to handle image pans and other overlays differently. Or you can copy your source files and take that approach, but I prefer keeping everything in the same file if possible.
- Do we need to create a new application using v19 of the viewer builder
- I am using v18 of the producer tools (with the updated folio builder panel) and it lets me choose 2048x1536, will these work in v19 when I upgrade? (if I need to)
Keeping all your source files in one file sounds like a great plan when creating renditions. Would you please explain what you mean by using the "layers feature to handle image pans and other overlays differently".
Are you suggesting we separate iPad 1 & 2 overlays into one layer, and iPad 3 overlays into another? If this is the case, when we disable a layer containing iPad 1 & 2 overlays (while publishing to an iPad 3 folio), do these hidden layers not get uploaded (which would inadvertantly add useless weight to our files?
Blasto - 2048x1536 folios work only with v19 viewers. You'll need to update your viewer. The v19 Viewer Builder still has a couple of bugs (hi-res app icons not showing up; both renditions appearing in viewer in some instances), so you might want to wait for awhile before you submit the viewer.
Paul - Yes, I'm suggesting that you create separate layers for certain overlays, such as Pan & Zoom, Image Sequence, and Video. In 1024x768 articles, apply 200% [sorry - 50%] scaling to the hi-res overlays -- especially pan & zoom -- so that they scale up to 100%. Content on hidden layers is excluded from the uploaded article. Obviously, it's important to show and hide the right layers when you import the articles.
When will we be able to make a real, working single-edition folio that supports all ipads?
That is, how and when do we get renditions (or anohter solution) for single-folio publications?
Right now it sounds like any single-folio publication is compromised, either too big & slow for an ipad 1/2, or pixelated on an ipad3.
You’re making very bad assumptions. The same ones I was afraid of BEFORE the new iPad was released but I’m happy to say that even those designed for 1024x768 look excellent on the device. In short, stop worrying.
I'm not making any assumptions, either bad or good. From Bob Bringhurst's blogs.adobe.com Guidelines for Creating Folios for ipad3:
"If a customer with an iPad 3 downloads the 1024×768 app, content is scaled up and pixelated. If a customer with an iPad 2 downloads the 2048×1536 folio, content is unnecessarily large and scaled down, which can cause performance problems."
If I’m not mistaken (and Bob can correct me if I’m wrong) I believe that document was written before the new iPad was released.
As I said, I was worried about it big time. My fears were totally unfounded but I will note that my folio is PDF.
So, this elaborate system of different renditions for multi-folio apps is unnecessary since everything looks great no matter what resolution the folio is?
Or that single-folio producers should be happy with the uprezzed 1024x768 content looks and ignore the new functionality?
Some 1024x768 content looks great on the iPad 3. Some content is pixelated. It all depends on the content. Creating renditions is an option for multi-folio publications. Renditions for single-issue folios are not available and I'm not aware of plans to enable them.
Viewers on older iPads don't display 2048x1536 folios with two exceptions -- Preview on Device and single-issue viewers. If you use either method to display 2048x1536 folios on an iPad 1 or 2, the content looks fuzzy, and performance is poor. It's not simply a matter of the viewer scaling down content -- it's more complicated than that. In my opinion, when creating a Single Edition viewer, you're much better off creating a 1024x768 folio than a 2048x1536 folio. The performance and appearance on all devices is more even, especially if you use hi-res non-interactive content and take care with text. With a 2048 folio, the content will look great on the iPad 3 but lousy on the older models. Again, the iPad 3 is brand new and we're still trying to sort out best practices.
Johannes might submit his HD version of DONE. Let's see how Apple handles duplicate apps.
... I am not sure if I am submitting an HD version as a separate app. i
don't like the approach, but if it is best, I will try. there are games
that used the "HD" very well from iPhone to iPad.
I am not sure what you mean by "content" — text only looks great if I set
it to PDF, images are still pixelated and not softened. I am still testing
for best results.
Can I just run this past you guys? I'm trying to implement a rendition workflow, what I'm getting from your comments and posts is that PDF is the way forward (we'll gloss over smooth scrolling at the moment) and that 1024 documents scale up just fine as long as it contains HDs assets (no need to re-create a tonne o templates). So my plan is to work with HD images throughout (scaled for 1024 pages effective pixels res to 144ppi) for the first rendition then run a script to go through each page and strip out the HD assets, resize by 50% and flow back in. Now I'm thrown slightly by Bob's comment about scaling up content to 200%. Correct me if I'm wrong but this is as I understand it… lets say I have a scrollable frame on the page. For the HD rendition am I to scale the contents of that frame (lets say a simple column of text) by 200%, origin top left, which will essentially severly crops what I see on the page but will be fine when the page gets upscaled. Anyone see any floors in this plan!
Don't use the 200% 50% approach on scrollable frames. I was thinking in particular of pan & zoom images. In my testing, when I scale up the 1024 document, the pan & zoom view area scales up but the underlying image doesn't scale up, so the initial view is different and the image pan is more restricted on the iPad 3. The bottom line is that you're going to want to test your overlays when you scale up a 1024 document. If you see behavior you don't want, you can use a number of different methods to fix it -- (1) use the same source files and show/hide separate layers for certain hi-res and lo-res overlays (2) create separate 1024 source docs, (3) create separate 1024 and 2048 source documents.
OK Bob, got the wrong end of the stick. Anyway we've just succesfully tested some upscaled PDF folio's with HD assets. Wow looks amazing and the text is so sharp! Real strain moving back to a lap top screen! One thing though, I usually have hyper links to PDF's that exsist in the HTMLResource.zip file. The in-app browser is launching when these links are actioned but give a URL error message and do not display. Any thoughts on that one?
OK so that didn't work either.
Just to break it down…
PDF folio set at 2058…
Document at 1024 x 768
HTMLResources.zip contains PDF's set at 768 wide (varying lengths)
Published to the distribution server as private and free
Imported the zip file from folio builder and from folio producer but keep getting this message on the new iPad…
I did this exact same thing -- 2048x1536 and 1024x768 folios, 1024x768 source files, upload HTMLResources.zip to both 2048 and 1024 folios, and links to PDF documents worked well in both folios. At one point, I got the same message you got, but that was because I hadn't uploaded the HTMLResources.zip file to the 2048 folio yet. When I did, it worked.
Europe, Middle East and Africa