Hi Steve, My apologies for being unclear. If I understand you correctly, my strategy and yours accomplish the same thing. Please let me try again.
Again, the folder structure is *MANUALS* PACKAGEFOLDER1 unique *.fm files and images for Package1 PACKAGEFOLDER2 same for Package2 PACKAGEFOLDER3 same for Package3 SUB-PACKAGE1 *.fm files for Sub-package1 with conditional text to fit each major package SUB-PACKAGE2 samesame PackageBook1 actual book file for package one PackageBook2 etc. PackageBook3 etc. Here is an example of a *.book: PACKAGE1.book -PACKAGE1TOC.fm -\PACKAGEFOLDER1\PACKAGE1.fm -\SUB-PACKAGE1\SUB-PACKAGE1.fm -\SUB-PACKAGE2\SUB-PACKAGE2.fm -INDEX.fm (with two indices in two separate text insets - I certainly see the benefit of that. The indices for the sub-packages would be contained in the appropriate subfolder but not explicitly included in the *.book.) When I print the book, the sub-package files should be printed in their current version. Is there a known problem with that? Many thanks, Lea > -----Original Message----- > From: Steve Johnson [mailto:[email protected]] > Sent: Thursday, May 20, 2010 9:32 AM > To: Lea Rush > Subject: Re: Advice on folder structure > > I can't parse what you just said. > > A text inset is a blob of text that you import into a Frame file just > like a graphic. Like a graphic, you can either import it by reference > or copy it into the file. If the text is going to change you want to > import it by reference. > > File > Import File. Select the Import by Reference option at the > bottom of the Import dialog box. > > From them on whenever you change the text inset it is updated > everywhere it is used. Generally you need to generate the book or open > the file for it to be updated if you change the text inset while the > destination file is open. > > On Thu, May 20, 2010 at 11:24 AM, Lea Rush <[email protected]> wrote: > > Hi Steve, > > > > For shared text, I had planned to place the shared-text *.fm in each > > PackageN.book, referring to the *.fm in each SUBPACKAGE folder. Would you > > mind explaining the benefits of using text insets instead? > > > > Thank you, > > Lea > > > > > >> -----Original Message----- > >> From: Steve Johnson [mailto:[email protected]] > >> Sent: Thursday, May 20, 2010 9:15 AM > >> To: Lea Rush > >> Cc: Frame Users > >> Subject: Re: Advice on folder structure > >> > >> The folder structure should be taken into consideration only WRT > >> source control. In other words, when you branch from version 2.0 to > >> version 3.0, you want all like files to move together so things like > >> cross-references, figure references, and text insets move together in > >> the same relative hierarchy. > >> > >> For shared text, you want to use text insets properly. If you have > >> boilerplate text (e.g., copyrights) that are used by multiple books, > >> you might consider placing those outside your proposed directory > >> structure. > >> > >> On Thu, May 20, 2010 at 11:04 AM, Lea Rush <[email protected]> > > wrote: > >> > Hello to the fonts of All Wisdom Framemaker, > >> > > >> > ;) > >> > > >> > Seriously, Id like some advice. My company has three different software > >> > packages, and the three share two common sub-packages. Up to this point, > > the > >> > common bits were part of the Details chapter of each individual manual. > > Id > >> > like to break out the common bits into their own individual manuals. > > Heres > >> > what I see as the eventual folder and file structure. Any advice > > welcomed in > >> > advance. > >> > > >> > MANUALS > >> > > >> > PACKAGEFOLDER1 unique *.fm files and images for Package1 > >> > > >> > PACKAGEFOLDER2 same for Package2 > >> > > >> > PACKAGEFOLDER3 same for Package3 > >> > > >> > SUB-PACKAGE1 *.fm files for Sub-package1 with conditional text to fit > > each > >> > major package > >> > > >> > SUB-PACKAGE2 samesame > >> > > >> > PackageBook1 actual book file for package one > >> > > >> > PackageBook2 etc. > >> > > >> > PackageBook3 etc. > >> > > >> > My perceived benefit is that all the files in a given book are at the > > same > >> > folder level, and I think I remember the consensus on this list being > > that > >> > that is a good thing. Thoughts? Advice? Completely different paradigm > > which > >> > is eluding me? > >> > > >> > Thanks in advance! > >> > > >> > Lea > >> -- > ============ > Steve Johnson, [email protected] _________________________________ Lea Rush Software and Documentation Specialist Astoria-Pacific International www.astoria-pacific.com ph: 800-536-3111 fax: 503-655-7367 [email protected] Please consider the environment before printing this email. `.¸¸.´¯`.¸.´¯`...¸ ><((((º>`.¸¸.´¯`.¸.´¯`...¸><((((º> NOTICE OF CONFIDENTIALITY This communication is from Astoria-Pacific International and is intended to be confidential and solely for the use of the persons or entities addressed above. If you are not an intended recipient, be aware that the information contained herein may be protected from unauthorized use by privilege or law, and any copying, distribution, disclosure, or other use of this information is prohibited. If you have received this communication in error, please contact the sender by return email or telephone (503) 657-3010 immediately, and delete or destroy all copies. Thank you for your cooperation. _______________________________________________ You are currently subscribed to framers as [email protected]. Send list messages to [email protected]. To unsubscribe send a blank email to [email protected] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [email protected]. Visit http://www.frameusers.com/ for more resources and info.
