RE: Object-Oriented Documentation

[Goober Writer <gooberwriter -at- yahoo -dot- com>]

> The suggestion to use text insets is a good one.
> 
> One approach would be to create individual documents
> for each procedure or
> concept, then use FrameScript to assemble the final
> documents based on
> various criteria. Essentially database publishing
> without the database.
> 
> Not a trivial thing to set up, but no solution will
> be.

IMO, text insets are a great idea, but FM does not
handle them well enough to be of great use. They're
helpful in limited applications, but I'd never create
a workflow that used them as the main composition elements.

=====
Goober Writer
(because life is too short to be inept)

"As soon as you hear the phrase "studies show",
immediately put a hand on your wallet and cover your groin."
      -- Geoff Hart

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

NEED TO PUBLISH FRAMEMAKER CONTENT ONLINE? "Mustang" is a NEW single
sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required! http://www.ehelp.com/techwr-l3

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot- 

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.