 | |  |  | 

The primary reason to use Framemaker is the power that it offers in managing long and possibly technically complex documents. And while detailed control of the formatting of every paragraph and character is important, the overarching concern is overall structure and layout on a document- or book-wide basis.
As the product's name announces, at the heart of FrameMaker's structure and layout paradigm is the 'Frame'. Yet I found the user documentation on the actual subject of frames to be perplexingly opaque. Frames are mentioned here and there, and what is described is not incorrect. But nowhere in the user docs is there a concise and complete discussion of this central FrameMaker feature -- which tends to stall efforts to actually get started on using FrameMaker in a productively-planned manner. Indeed, it is tempting to speculate that the FM learning curve is infamously steep precisely because this conceptual core is so ill illuminated.
So, determined to dispell the fog (at least for me!), I resorted to studying the very helpful Programmers' Reference and Guide, and built a MIF-Browser tool to get to the bottom of the matter. Herewith is an effort to clarify what to me seem the essentials needed for productive use of FrameMaker, condensed in one place. View all five works by Wideman, Graham View all 5 works published by WidemanOne |
 Document Layout Concepts (Frames and All That) http://www.wideman-one.com/gw/tech/framemaker/fmdoclayout.htm
Wideman, Graham WidemanOne
Abstract: The primary reason to use Framemaker is the power that it offers in managing long and possibly technically complex documents. And while detailed control of the formatting of every paragraph and character is important, the overarching concern is overall structure and layout on a document- or book-wide basis.
As the product's name announces, at the heart of FrameMaker's structure and layout paradigm is the 'Frame'. Yet I found the user documentation on the actual subject of frames to be perplexingly opaque. Frames are mentioned here and there, and what is described is not incorrect. But nowhere in the user docs is there a concise and complete discussion of this central FrameMaker feature -- which tends to stall efforts to actually get started on using FrameMaker in a productively-planned manner. Indeed, it is tempting to speculate that the FM learning curve is infamously steep precisely because this conceptual core is so ill illuminated.
So, determined to dispell the fog (at least for me!), I resorted to studying the very helpful Programmers' Reference and Guide, and built a MIF-Browser tool to get to the bottom of the matter. Herewith is an effort to clarify what to me seem the essentials needed for productive use of FrameMaker, condensed in one place.
|
 |
 |  |