Re: Containers and Insets-Building the Manual
Jing Torralba wrote: I use Richard's technique in creating insets in multiple flows within the same source document. The insets populate cells of many similar tables where one table uses 100% of the insets and the rest, only a subset of all insets in different combinations. The tables describe the options for adding an administrator, and there are three types of administrators with unique and common options. Once I nailed down the process, inset management worked like a charm. Judy, I want to add this, in case you are producing PDFs and there are cross-references from your inset files to external files, meaning, to the container file itself or to other chapters in the book. These xrefs will be broken in the PDF. For this you can use Rick Quatro's script to unlock the insets, generate the PDF, then lock them again. This preserves the links. HTH too! Jing ,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,! - Original Message - From: Richard Combs richard.co...@polycom.com To: Judy j...@hypack.com, framers@lists.frameusers.com Sent: Thursday, May 21, 2009 1:15:48 PM GMT -08:00 US/Canada Pacific Subject: RE: Containers and Insets-Building the Manual Judy wrote: I read several posts concerning text insets in container documents and that sounded like the perfect solution. After a few tests on a very small scale, I moved forward to breaking down and reassembling the first 3 chapters of our user manual. Ch.1: 63 pgs,61 insets Ch.2: 224 pgs, 168 insets Ch 3: 83 pgs, 71 insets Each chapter (individually) worked fine, so with that much done, I decided to build a test book and work out the issues around cross-references and hypertext before I continued on to the remaining 6 chapters. My problem is that, with all of the fm files and books open at once, my computer slowed *way* down! I built a book with the 3 container documents and added a TOC, but had trouble scrolling through the TOC. Nothing crashed, but it was so slow it's clear that I'm headed for trouble. That seems like a lot of text insets, but without knowing how/where you're going to reuse them, I can't say whether you've gone too far (there's not much point in all this modularization unless the insets are pieces that will be reused a lot, but in different combinations and configurations). Is each text inset an FM file? It doesn't have to be. A text inset needs to be a complete flow, but a single FM file can contain many separate flows (each with its own flow name). So you can put just about any number of text insets in one file. You can even use this as an organizing method, putting all text insets of a certain category, subject, purpose, etc., together in an appropriately-named file. Consolidating all those text insets into a handful of files may solve your problem. The process isn't difficult: 1) On the last page of one of the existing text inset source documents, select Special Add Disconnected Pages. Set Number of Pages to Add to the number of text insets you want to store in this file and click Add. When FM tries to discourage you from proceeding, tell it you're sure. 2) On each added, empty page, paste one of the text insets you want to store in this file. Don't worry if some of them are more than a page -- FM will create new pages as needed for each flow (each disconnected page you added is a separate flow; each has its own end-of-flow symbol). 3) Give each flow a unique, meaningful name: -- Select a text frame in the flow and select Graphics Object Properties. -- In the Customize Text Frame dialog, enter the name in the Flow Tag field and click Set. -- In the Rename Flow dialog, select Rename Current Flow Only and click Rename. When you want to import one of the text insets, select the file and then, in the Import Text Flow by Reference, select the flow by name. HTH! Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as jingtorra...@comcast.net. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/jingtorralba%40comcast.net Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. I've actually used Richard's technique for insets smaller than a topic, but hadn't thought about doing it for larger sections. It would certainly cut down on the number of files I have to organize *and* that FM has to open and close. I'll think about how to organize things and give it a try. I don't usually have the Character and Paragraph Designers open, but I'll keep it in mind
Containers and Insets-Building the Manual
Jing Torralba wrote: > > I use Richard's technique in creating insets in multiple flows within > the same source document. The insets populate cells of many similar > tables where one table uses 100% of the insets and the rest, only a > subset of all insets in different combinations. The tables describe > the options for adding an administrator, and there are three types of > administrators with unique and common options. > > Once I nailed down the process, inset management worked like a charm. > > Judy, I want to add this, in case you are producing PDFs and there are > cross-references from your inset files to external files, meaning, to > the container file itself or to other chapters in the book. These > xrefs will be broken in the PDF. For this you can use Rick Quatro's > script to unlock the insets, generate the PDF, then lock them again. > This preserves the links. > > > > HTH too! > > Jing > > ,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,! > > > - Original Message - > From: "Richard Combs" > To: "Judy" , framers at lists.frameusers.com > Sent: Thursday, May 21, 2009 1:15:48 PM GMT -08:00 US/Canada Pacific > Subject: RE: Containers and Insets-Building the Manual > > Judy wrote: > > > I read several posts concerning text insets in container documents and > > that sounded like the perfect solution. After a few tests on a very > > small scale, I moved forward to breaking down and reassembling the > > first 3 chapters of our user manual. > > Ch.1: 63 pgs,61 insets > > Ch.2: 224 pgs, 168 insets > > Ch 3: 83 pgs, 71 insets > > > > Each chapter (individually) worked fine, so with that much done, I > > decided to build a test book and work out the issues around > > cross-references and hypertext before I continued on to the remaining > 6 > > chapters. > > > > My problem is that, with all of the fm files and books open at once, > my > > computer slowed *way* down! I built a book with the 3 container > > documents and added a TOC, but had trouble scrolling through the TOC. > > Nothing "crashed", but it was so slow it's clear that I'm headed for > > trouble. > > That seems like a lot of text insets, but without knowing how/where > you're going to reuse them, I can't say whether you've gone too far > (there's not much point in all this modularization unless the insets are > pieces that will be reused a lot, but in different combinations and > configurations). > > Is each text inset an FM file? It doesn't have to be. A text inset needs > to be a complete flow, but a single FM file can contain many separate > flows (each with its own flow name). So you can put just about any > number of text insets in one file. You can even use this as an > organizing method, putting all text insets of a certain category, > subject, purpose, etc., together in an appropriately-named file. > Consolidating all those text insets into a handful of files may solve > your problem. > > The process isn't difficult: > > 1) On the last page of one of the existing text inset source documents, > select Special > Add Disconnected Pages. Set Number of Pages to Add to > the number of text insets you want to store in this file and click Add. > When FM tries to discourage you from proceeding, tell it you're sure. > > 2) On each added, empty page, paste one of the text insets you want to > store in this file. Don't worry if some of them are more than a page -- > FM will create new pages as needed for each flow (each disconnected page > you added is a separate flow; each has its own end-of-flow symbol). > > 3) Give each flow a unique, meaningful name: > > -- Select a text frame in the flow and select Graphics > Object > Properties. > -- In the Customize Text Frame dialog, enter the name in the Flow Tag > field and click Set. > -- In the Rename Flow dialog, select Rename Current Flow Only and click > Rename. > > When you want to import one of the text insets, select the file and > then, in the Import Text Flow by Reference, select the flow by name. > > HTH! > Richard > > > Richard G. Combs > Senior Technical Writer > Polycom, Inc. > richardDOTcombs AT polycomDOTcom > 303-223-5111 > -- > rgcombs AT gmailDOTcom > 303-777-0436 > -- > > > > > > > ___ > > > You are currently subscribed to Framers as jingtorralba at comcast.net. > > 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://l
Containers and Insets-Building the Manual
The item that I thought of that may cause a slow-down is not your local config as much as if all those files and insets are across the network on one or more servers. If they're all open, and you're performing a file-intensive operation, you're going to be using up a lot of bandwidth. I'd try an experiment and use Bruce Foster's Archive plug-in to collect a copy of all the insets and files into a local directory (this doesn't disturb the source files in any way). Then see if the local location changes anything. If, by chance, you have two local hard drives, I'd store the files (actually all local data) on the drive that doesn't contain the operating system, swap space, and applications, but that's a footnote. Cheers, Art Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358 On Thu, May 21, 2009 at 3:16 PM, Judy wrote: > Hello Fellow Framers! > > After spending quite a bit of time reading posts in the FrameUsers > archives, I thought I had some things figured out. ?It worked on a small > scale, but now that I've begun using larger documents I'm running into a > problem and I hope you folks can help. > > I've been working toward making my unstructured FM 8 doc. set more > modular to improve my single-sourcing capabilities. > > I read several posts concerning text insets in container documents and > that sounded like the perfect solution. ?After a few tests on a very > small scale, I moved forward to breaking down ?and reassembling the > first 3 chapters of our user manual. > Ch.1: ?63 pgs, ? ?61 insets > Ch.2: 224 pgs, 168 insets > Ch 3: ? 83 pgs, ? 71 insets > > Each chapter (individually) worked fine, so with that much done, I > decided to build a test book and work out the issues around > cross-references and hypertext before I continued on to the remaining 6 > chapters. > > My problem is that, with all of the fm files and books open at once, my > computer slowed *way* down! ?I built a book with the 3 container > documents and added a TOC, but had trouble scrolling through the TOC. > Nothing "crashed", but it was so slow it's clear that I'm headed for > trouble. > > I checked the performance in the Windows Task Manager and, with _only > FM8_ open, the CPU Usage was around 50% (give or take about 7%). > My Computer: > ?- Intel Core 2 Duo CPU > ?- 2 GHz Motherboard > ?- 2 GHz, 3.5 Gb RAM > ?- OS: XP SP3 > > I'm wondering if I've broken the files down too far and FM can't handle > that, or if there's something else I don't know about. ?I've read, > numerous times, about the power of FM and that people use it to handle > much larger documents than mine. I have to believe that there's an > answer somewhere. > > Can you FM gurus please help me? > > Thanks so much! > Judy > > > > ___ > > > You are currently subscribed to Framers as art.campbell at gmail.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/art.campbell%40gmail.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. >
Containers and Insets-Building the Manual
Hello Fellow Framers! After spending quite a bit of time reading posts in the FrameUsers archives, I thought I had some things figured out. It worked on a small scale, but now that I've begun using larger documents I'm running into a problem and I hope you folks can help. I've been working toward making my unstructured FM 8 doc. set more modular to improve my single-sourcing capabilities. I read several posts concerning text insets in container documents and that sounded like the perfect solution. After a few tests on a very small scale, I moved forward to breaking down and reassembling the first 3 chapters of our user manual. Ch.1: 63 pgs,61 insets Ch.2: 224 pgs, 168 insets Ch 3: 83 pgs, 71 insets Each chapter (individually) worked fine, so with that much done, I decided to build a test book and work out the issues around cross-references and hypertext before I continued on to the remaining 6 chapters. My problem is that, with all of the fm files and books open at once, my computer slowed *way* down! I built a book with the 3 container documents and added a TOC, but had trouble scrolling through the TOC. Nothing crashed, but it was so slow it's clear that I'm headed for trouble. I checked the performance in the Windows Task Manager and, with _only FM8_ open, the CPU Usage was around 50% (give or take about 7%). My Computer: - Intel Core 2 Duo CPU - 2 GHz Motherboard - 2 GHz, 3.5 Gb RAM - OS: XP SP3 I'm wondering if I've broken the files down too far and FM can't handle that, or if there's something else I don't know about. I've read, numerous times, about the power of FM and that people use it to handle much larger documents than mine. I have to believe that there's an answer somewhere. Can you FM gurus please help me? Thanks so much! Judy ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: Containers and Insets-Building the Manual
Judy wrote: I read several posts concerning text insets in container documents and that sounded like the perfect solution. After a few tests on a very small scale, I moved forward to breaking down and reassembling the first 3 chapters of our user manual. Ch.1: 63 pgs,61 insets Ch.2: 224 pgs, 168 insets Ch 3: 83 pgs, 71 insets Each chapter (individually) worked fine, so with that much done, I decided to build a test book and work out the issues around cross-references and hypertext before I continued on to the remaining 6 chapters. My problem is that, with all of the fm files and books open at once, my computer slowed *way* down! I built a book with the 3 container documents and added a TOC, but had trouble scrolling through the TOC. Nothing crashed, but it was so slow it's clear that I'm headed for trouble. That seems like a lot of text insets, but without knowing how/where you're going to reuse them, I can't say whether you've gone too far (there's not much point in all this modularization unless the insets are pieces that will be reused a lot, but in different combinations and configurations). Is each text inset an FM file? It doesn't have to be. A text inset needs to be a complete flow, but a single FM file can contain many separate flows (each with its own flow name). So you can put just about any number of text insets in one file. You can even use this as an organizing method, putting all text insets of a certain category, subject, purpose, etc., together in an appropriately-named file. Consolidating all those text insets into a handful of files may solve your problem. The process isn't difficult: 1) On the last page of one of the existing text inset source documents, select Special Add Disconnected Pages. Set Number of Pages to Add to the number of text insets you want to store in this file and click Add. When FM tries to discourage you from proceeding, tell it you're sure. 2) On each added, empty page, paste one of the text insets you want to store in this file. Don't worry if some of them are more than a page -- FM will create new pages as needed for each flow (each disconnected page you added is a separate flow; each has its own end-of-flow symbol). 3) Give each flow a unique, meaningful name: -- Select a text frame in the flow and select Graphics Object Properties. -- In the Customize Text Frame dialog, enter the name in the Flow Tag field and click Set. -- In the Rename Flow dialog, select Rename Current Flow Only and click Rename. When you want to import one of the text insets, select the file and then, in the Import Text Flow by Reference, select the flow by name. HTH! Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: Containers and Insets-Building the Manual
Re this step: 2) On each added, empty page, paste one of the text insets you want to store in this file. Don't worry if some of them are more than a page -- FM will create new pages as needed for each flow (each disconnected page you added is a separate flow; each has its own end-of-flow symbol). Just to be clear: Place the text cursor into the flow (click in the text frame) before you paste. Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Containers and Insets-Building the Manual
I use Richard's technique in creating insets in multiple flows within the same source document. The insets populate cells of many similar tables where one table uses 100% of the insets and the rest, only a subset of all insets in different combinations. The tables describe the options for adding an administrator, and there are three types of administrators with unique and common options. Once I nailed down the process, inset management worked like a charm. Judy, I want to add this, in case you are producing PDFs and there are cross-references from your inset files to external files, meaning, to the container file itself or to other chapters in the book. These xrefs will be broken in the PDF. For this you can use Rick Quatro's script to unlock the insets, generate the PDF, then lock them again. This preserves the links. HTH too! Jing ,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,! - Original Message - From: Richard Combs richard.co...@polycom.com To: Judy j...@hypack.com, framers@lists.frameusers.com Sent: Thursday, May 21, 2009 1:15:48 PM GMT -08:00 US/Canada Pacific Subject: RE: Containers and Insets-Building the Manual Judy wrote: I read several posts concerning text insets in container documents and that sounded like the perfect solution. After a few tests on a very small scale, I moved forward to breaking down and reassembling the first 3 chapters of our user manual. Ch.1: 63 pgs, 61 insets Ch.2: 224 pgs, 168 insets Ch 3: 83 pgs, 71 insets Each chapter (individually) worked fine, so with that much done, I decided to build a test book and work out the issues around cross-references and hypertext before I continued on to the remaining 6 chapters. My problem is that, with all of the fm files and books open at once, my computer slowed *way* down! I built a book with the 3 container documents and added a TOC, but had trouble scrolling through the TOC. Nothing crashed, but it was so slow it's clear that I'm headed for trouble. That seems like a lot of text insets, but without knowing how/where you're going to reuse them, I can't say whether you've gone too far (there's not much point in all this modularization unless the insets are pieces that will be reused a lot, but in different combinations and configurations). Is each text inset an FM file? It doesn't have to be. A text inset needs to be a complete flow, but a single FM file can contain many separate flows (each with its own flow name). So you can put just about any number of text insets in one file. You can even use this as an organizing method, putting all text insets of a certain category, subject, purpose, etc., together in an appropriately-named file. Consolidating all those text insets into a handful of files may solve your problem. The process isn't difficult: 1) On the last page of one of the existing text inset source documents, select Special Add Disconnected Pages. Set Number of Pages to Add to the number of text insets you want to store in this file and click Add. When FM tries to discourage you from proceeding, tell it you're sure. 2) On each added, empty page, paste one of the text insets you want to store in this file. Don't worry if some of them are more than a page -- FM will create new pages as needed for each flow (each disconnected page you added is a separate flow; each has its own end-of-flow symbol). 3) Give each flow a unique, meaningful name: -- Select a text frame in the flow and select Graphics Object Properties. -- In the Customize Text Frame dialog, enter the name in the Flow Tag field and click Set. -- In the Rename Flow dialog, select Rename Current Flow Only and click Rename. When you want to import one of the text insets, select the file and then, in the Import Text Flow by Reference, select the flow by name. HTH! Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as jingtorra...@comcast.net. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/jingtorralba%40comcast.net Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http
Containers and Insets-Building the Manual
Hello Fellow Framers! After spending quite a bit of time reading posts in the FrameUsers archives, I thought I had some things figured out. It worked on a small scale, but now that I've begun using larger documents I'm running into a problem and I hope you folks can help. I've been working toward making my unstructured FM 8 doc. set more modular to improve my single-sourcing capabilities. I read several posts concerning text insets in container documents and that sounded like the perfect solution. After a few tests on a very small scale, I moved forward to breaking down and reassembling the first 3 chapters of our user manual. Ch.1: 63 pgs,61 insets Ch.2: 224 pgs, 168 insets Ch 3: 83 pgs, 71 insets Each chapter (individually) worked fine, so with that much done, I decided to build a test book and work out the issues around cross-references and hypertext before I continued on to the remaining 6 chapters. My problem is that, with all of the fm files and books open at once, my computer slowed *way* down! I built a book with the 3 container documents and added a TOC, but had trouble scrolling through the TOC. Nothing "crashed", but it was so slow it's clear that I'm headed for trouble. I checked the performance in the Windows Task Manager and, with _only FM8_ open, the CPU Usage was around 50% (give or take about 7%). My Computer: - Intel Core 2 Duo CPU - 2 GHz Motherboard - 2 GHz, 3.5 Gb RAM - OS: XP SP3 I'm wondering if I've broken the files down too far and FM can't handle that, or if there's something else I don't know about. I've read, numerous times, about the power of FM and that people use it to handle much larger documents than mine. I have to believe that there's an answer somewhere. Can you FM gurus please help me? Thanks so much! Judy
Containers and Insets-Building the Manual
Judy wrote: > I read several posts concerning text insets in container documents and > that sounded like the perfect solution. After a few tests on a very > small scale, I moved forward to breaking down and reassembling the > first 3 chapters of our user manual. > Ch.1: 63 pgs,61 insets > Ch.2: 224 pgs, 168 insets > Ch 3: 83 pgs, 71 insets > > Each chapter (individually) worked fine, so with that much done, I > decided to build a test book and work out the issues around > cross-references and hypertext before I continued on to the remaining 6 > chapters. > > My problem is that, with all of the fm files and books open at once, my > computer slowed *way* down! I built a book with the 3 container > documents and added a TOC, but had trouble scrolling through the TOC. > Nothing "crashed", but it was so slow it's clear that I'm headed for > trouble. That seems like a lot of text insets, but without knowing how/where you're going to reuse them, I can't say whether you've gone too far (there's not much point in all this modularization unless the insets are pieces that will be reused a lot, but in different combinations and configurations). Is each text inset an FM file? It doesn't have to be. A text inset needs to be a complete flow, but a single FM file can contain many separate flows (each with its own flow name). So you can put just about any number of text insets in one file. You can even use this as an organizing method, putting all text insets of a certain category, subject, purpose, etc., together in an appropriately-named file. Consolidating all those text insets into a handful of files may solve your problem. The process isn't difficult: 1) On the last page of one of the existing text inset source documents, select Special > Add Disconnected Pages. Set Number of Pages to Add to the number of text insets you want to store in this file and click Add. When FM tries to discourage you from proceeding, tell it you're sure. 2) On each added, empty page, paste one of the text insets you want to store in this file. Don't worry if some of them are more than a page -- FM will create new pages as needed for each flow (each disconnected page you added is a separate flow; each has its own end-of-flow symbol). 3) Give each flow a unique, meaningful name: -- Select a text frame in the flow and select Graphics > Object Properties. -- In the Customize Text Frame dialog, enter the name in the Flow Tag field and click Set. -- In the Rename Flow dialog, select Rename Current Flow Only and click Rename. When you want to import one of the text insets, select the file and then, in the Import Text Flow by Reference, select the flow by name. HTH! Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
Containers and Insets-Building the Manual
Re this step: > 2) On each added, empty page, paste one of the text insets you want to > store in this file. Don't worry if some of them are more than a page -- > FM will create new pages as needed for each flow (each disconnected page > you added is a separate flow; each has its own end-of-flow symbol). Just to be clear: Place the text cursor into the flow (click in the text frame) before you paste. Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
Containers and Insets-Building the Manual
I use Richard's technique in creating insets in multiple flows within the same source document. The insets populate?cells of many similar tables where one table uses 100% of the insets and the rest,?only a subset of all insets in different combinations. The tables?describe the options for adding an administrator, and there are three types of administrators with unique and common options. Once I nailed down the process, inset management worked like a charm. Judy, I want to add this, in case you are producing PDFs and there are cross-references from your inset files to external files, meaning, to the container file itself or to other chapters in the book. These xrefs will be broken in the PDF. For this you can use Rick Quatro's script to unlock the insets, generate the PDF, then lock them again. This preserves the links. HTH too! Jing ,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,.-*+*-.,! - Original Message - From: "Richard Combs" <richard.co...@polycom.com> To: "Judy" , framers at lists.frameusers.com Sent: Thursday, May 21, 2009 1:15:48 PM GMT -08:00 US/Canada Pacific Subject: RE: Containers and Insets-Building the Manual Judy wrote: ? > I read several posts concerning text insets in container documents and > that sounded like the perfect solution. ?After a few tests on a very > small scale, I moved forward to breaking down ?and reassembling the > first 3 chapters of our user manual. > Ch.1: ?63 pgs, ? ?61 insets > Ch.2: 224 pgs, 168 insets > Ch 3: ? 83 pgs, ? 71 insets > > Each chapter (individually) worked fine, so with that much done, I > decided to build a test book and work out the issues around > cross-references and hypertext before I continued on to the remaining 6 > chapters. > > My problem is that, with all of the fm files and books open at once, my > computer slowed *way* down! ?I built a book with the 3 container > documents and added a TOC, but had trouble scrolling through the TOC. > Nothing "crashed", but it was so slow it's clear that I'm headed for > trouble. That seems like a lot of text insets, but without knowing how/where you're going to reuse them, I can't say whether you've gone too far (there's not much point in all this modularization unless the insets are pieces that will be reused a lot, but in different combinations and configurations). Is each text inset an FM file? It doesn't have to be. A text inset needs to be a complete flow, but a single FM file can contain many separate flows (each with its own flow name). So you can put just about any number of text insets in one file. You can even use this as an organizing method, putting all text insets of a certain category, subject, purpose, etc., together in an appropriately-named file. Consolidating all those text insets into a handful of files may solve your problem. The process isn't difficult: 1) On the last page of one of the existing text inset source documents, select Special > Add Disconnected Pages. Set Number of Pages to Add to the number of text insets you want to store in this file and click Add. When FM tries to discourage you from proceeding, tell it you're sure. 2) On each added, empty page, paste one of the text insets you want to store in this file. Don't worry if some of them are more than a page -- FM will create new pages as needed for each flow (each disconnected page you added is a separate flow; each has its own end-of-flow symbol). 3) Give each flow a unique, meaningful name: -- Select a text frame in the flow and select Graphics > Object Properties. -- In the Customize Text Frame dialog, enter the name in the Flow Tag field and click Set. -- In the Rename Flow dialog, select Rename Current Flow Only and click Rename. When you want to import one of the text insets, select the file and then, in the Import Text Flow by Reference, select the flow by name. HTH! Richard Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as jingtorralba at comcast.net. 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/jingtorralba%40comcast.net Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
