I am so excited CS6 is finally out
There's one big feature that should interest DPS folks: alternate layouts. In InDesign CS6 you can now have one InDesign file that contains layouts for multiple orientations and/or devices.
Here's one easy example of where that's helpful: no more "_H" and "_V" files littering your machine. Just one InDesign document that has both H and V inside. Here's another example: one file that has your iPad and your Kindle Fire layouts in it.
The best part about this is the text is linked between the layouts, so if you have to make a text change somewhere you can do it once, the links panel will indicate the other layouts are out-of-date, and you can update the link to make the change ripple across the other layouts in the file. Typo correction is now far less painful.
You can also use the new page rules feature to define ways for InDesign to automatically create layouts for you. For example, you can start with an iPad layout, apply some page rules, and generate the Kindle Fire layout.
One small feature to look forward to: you can directly paste HTML snippets into your file and automatically get a web overlay with that HTML.
Note that to actually produce folios using the above you'll need the next release of DPS. The current release (v19) does not support CS6.
@Neil – I understand all your excitement.
To make that alternate layout feature perfect one should be able to alter the baseline grid on a per page basis.
Is that possible now?
Or defining margins and gutters on a per percent basis relative to the width and/or height of the page.
Maybe I'm wrong, but I cannot see that there are changes in that field:
Maybe I should rethink all that and undertake a paradigm shift, never using the "global" baseline grid and instead working with text frame baseline grids? Will they be taken into account with "alternate" or "liquid" layouts?
will the introduction of liquid layout reduce overall folio size?
I've found that exporting a Vertical seperately to a Horizontal decreases the folio size dramatically, yet they are not linked so it's a moot point
but presumably with the addition of liquid layout, as both orientations will be in the source doc, the output will be smaller?
Is there anywhere to look up what's to come in future DPS updates? Like what features/fixes are coming up in v20? I'd be more excited about fixes to current problems than the addition of new buggy features.
We don't post the proposed features for upcoming releases on any site. When the new release comes out, new features are posted here:
Bug fixes are posted here:
History of new features are posted here:
The links are always available on our Developer Center page, which is a great resource. http://www.adobe.com/devnet/digitalpublishingsuite.html. Look in the What's New list.
Regarding what Neil said, any limitations using Cloud-based Single Edition with CS6's and the upcoming version of the Builder panel / DPS? I seem to recall reading somewhere here that Renditions (for example) were only available to Pro users. Am I mixing that up with something else?
Basically, Renditions are different versions (orientation or resolution or both) of a single folio file, right? IOW same content, different way to view it? Hoping all of the tools CS6 and DPS offer (via cloud) put no content restrictions on Single Edition users for customizing iPad content.
Renditions are targeted at devices so you'd have renditions for iPad 1/2, iPad3, XOOM, etc.
The renditions are downloaded by the viewer and that's the reason why single edtion doesn't support them. Single edition is a self contained app, no downloads, no in app purchases.
That's why they can only be used by Pro and Enterprise level customers.
Yes, you would build the app and distribute it either via sideloading, testflight, or your own mobile device management system. You would need to build it with an enterprise certificate if you didn't want to record devices UDIDs and bake them into the app (how they're allowed to install the app if you don't build with an enterprise cert.)
Without an enterprise cert, it's a painful process, initially. You will need to collect the UDIDs for every device the app is going to be loaded onto. (And you're limited to 100/year)
How you load the app is up to you (I would probably recommend testflight if you don't have anything in place.)
As far as building the single-issue app building process and certificate creation, this is outlined in the Publishing Companion Guide. You can download this by logging in with an account to http://digitalpublishing.acrobat.com and clicking on the link at the bottom-right of the dashboard.