If you are using structured frame, you can use the Inset Plus plug-in from West Street Consulting. You don't have to use separate flows. Instead, you identify content chunks by element or attribute.
Mike -----Original Message----- From: framers-bounces+mike.feimster=acstechnologies.com at lists.frameusers.com [mailto:framers-bounces+mike.feimster=acstechnologies.com at lists.frameuse rs.com] On Behalf Of Robert.Werner at appsense.com Sent: Thursday, May 10, 2007 7:10 AM To: framers at lists.frameusers.com Subject: Text insets - best practices I have started using text insets to share content between different "container" files and I am concerned about the best practices for using these. Some of the content items are one or two paragraphs long but some are detailed procedures with tables, graphics, captions, notes, ordered and unordered lists. The same content appears in different files in separate books but at different levels in the heading sturcture of each document. Because of the formatting constraints imposed by the different levels of headings I use in each container file, I have placed the source content of each text inset in separate files with logical naming for each file. I was thinking however of placing related content in a single file but in separate flows with unique names. I had tried creating a sample such as this for importing the content for each separate item by referencing the unique flow name. I found however that depending on how I was to implement this, items with long tracts of text, graphic etc., would either not be in full view or would overlap as each separate flow and as more items were added with their own unique flow. Each one needing to be smaller. If, for example, an item contains a graphic that is larger than the flow in which it is placed, the graphic overlaps the next flow on the page and obscures the next flow from view. Is there a better way of doing this? Perhaps I could set up up a unique master page for each content item with a unique flow name on each master page? Alternatively, it may be less maintenance for me to simply place individual content items with clear file naming in separate files. I have only implemented this on a small scale at the moment but in the future I anticpate more complexity and the need to contain files together. I also might consider cross project sharing which presents other difficulties. All comments, ideas or suggestions welcome. If you can share your own experiences on this matter and how you resolved the issue I would be grateful Rob Robert Werner Technical Author AppSense(r) 3200 Daresbury Park Daresbury Warrington WA4 4BU UK Email: robert.werner at appsense.com Web: http://www.appsense.com/ Tel: +44 (0) 161 216 3200 Mob: +44 (0) 796 9829137 Fax: +44 (0) 161 216 3232 AppSense provides user environment management solutions that personalize and optimize virtual and physical user environments. Whether delivered via Citrix, Terminal Server, Virtual Desktops, Streaming, Blade PCs or physical desktops, AppSense solutions ensure consistent, contextual and responsive environments to all users all the time. Find out more by visiting us at www.appsense.com. CONFIDENTIAL: The contents of this email and any attachments may be confidential. It is intended for the named recipient(s) only. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to any other person or make any copies. AppSense monitors communications. AppSense Limited is Registered in the United Kingdom, Registration Number 3873980. Registered Address: 3200 Daresbury Park, Daresbury, Warrington, Cheshire, United Kingdom, WA4 4BU _______________________________________________ You are currently subscribed to Framers as mike.feimster at acstechnologies.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/mike.feimster%40acst echnologies.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.