data reuse in structured FM...
Hi Elisa, First of all, Lynne's answer is good and I have only one thing to add: Inset Plus (http://www.weststreetconsulting.com/WSC_InsetPlus.htm) It's been a great plug in. That and the Sourcerer (www.advantica.biz/sourcerer), to filter attributes are great and get away from Frame's conditional text limitations, have been wonder tools. If there are enough frameusers in France who would like Russ to come over and speak or do a workshop, I bet we could twist his arm - answer me off-list. (secretary at stcfrance.org ) Russ, if you are reading this, tell me how much twisting it would take ;-) Regards, Ellen Lebelle KDS -- Forwarded message -- From: "Elisabeth SABOT" < esa...@talend.com> To: Date: Thu, 7 Sep 2006 16:14:26 +0200 Subject: data reuse in structured FM... Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). --- I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa -- Forwarded message -- From: "Lynne A. Price" < lpr...@txstruct.com> To: "Elisabeth SABOT" ,< framers at lists.frameusers.com> Date: Thu, 07 Sep 2006 09:40:48 -0700 Subject: Re: data reuse in structured FM... At 07:14 AM 9/7/2006, Elisabeth SABOT wrote: >But I am unable to import a >specific part of a data flow from one section to another in the same FM >file. Elisa, A text inset cannot consist of part of a flow. Instead, create a new flow containing only the reusable portion and import it into both sections. This flow can be the main flow of a new document, a body flow of a new document, or a reference flow in the document you are editing or another one. Since you can create multiple body flows or reference flows in one document, you have the option of storing all text insets in one document. Just remember that if you use reference flows of the containing document, you'll need to save it before importing the text insets. A structured text inset must have a root element. You might therefore want your EDD to define an element that can contain part of a section. For example, suppose you want a Section to contain a Title and then four Paragraph elements of which the three last ones are to be in a text inset. You might define an element called TextInset that can contain all of the children of a Section (except possibly the Title). You would then create a flow containing a TextInset element with the three reusable Paragraphs, and the section with the text inset would consist of the Title, the first Paragraph, and the imported TextInset. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training lprice at txstruct.com http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284
data reuse in structured FM...
Hi Elisa, First of all, Lynne's answer is good and I have only one thing to add: Inset Plus (http://www.weststreetconsulting.com/WSC_InsetPlus.htm) It's been a great plug in. That and the Sourcerer (www.advantica.biz/sourcerer), to filter attributes are great and get away from Frame's conditional text limitations, have been wonder tools. If there are enough frameusers in France who would like Russ to come over and speak or do a workshop, I bet we could twist his arm - answer me off-list. (secretary at stcfrance.org) Russ, if you are reading this, tell me how much twisting it would take ;-) Regards, Ellen Lebelle KDS -- Forwarded message -- From: "Elisabeth SABOT" < esa...@talend.com> To: Date: Thu, 7 Sep 2006 16:14:26 +0200 Subject: data reuse in structured FM... Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). --- I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa -- Forwarded message -- From: "Lynne A. Price" < lpr...@txstruct.com> To: "Elisabeth SABOT" , Date: Thu, 07 Sep 2006 09:40:48 -0700 Subject: Re: data reuse in structured FM... At 07:14 AM 9/7/2006, Elisabeth SABOT wrote: >But I am unable to import a >specific part of a data flow from one section to another in the same FM >file. Elisa, A text inset cannot consist of part of a flow. Instead, create a new flow containing only the reusable portion and import it into both sections. This flow can be the main flow of a new document, a body flow of a new document, or a reference flow in the document you are editing or another one. Since you can create multiple body flows or reference flows in one document, you have the option of storing all text insets in one document. Just remember that if you use reference flows of the containing document, you'll need to save it before importing the text insets. A structured text inset must have a root element. You might therefore want your EDD to define an element that can contain part of a section. For example, suppose you want a Section to contain a Title and then four Paragraph elements of which the three last ones are to be in a text inset. You might define an element called TextInset that can contain all of the children of a Section (except possibly the Title). You would then create a flow containing a TextInset element with the three reusable Paragraphs, and the section with the text inset would consist of the Title, the first Paragraph, and the imported TextInset. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training lprice at txstruct.com http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284
RE: data reuse in structured FM...
You may want to check into the tools at http://www.weststreetconsulting.com, specifically InsetPlus to see if they help. Try the tutorial and then start to develop based on ideas that Russ explains. Bernard Bernard Aschwanden Publishing Technologies Expert Publishing Smarter [EMAIL PROTECTED] www.publishingsmarter.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Elisabeth SABOT Sent: Thursday, September 07, 2006 10:14 AM To: framers@lists.frameusers.com Subject: data reuse in structured FM... Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). In brief, I'm currently writing a user guide for an OpenSource ETL process designer. This designer allows me to use components to compose ETL process flowcharts. In one chapter of this guide, I detailed each component and in particular the component's specific property parameters. This chapter is divided into section per component and subsections for properties and use case scenario. Then within the properties subsection, the actual properties are organised in a table which differs more or less from one component to the other. I want to be able to reuse the content of part of the component properties table for another component which has almost the same properties although some differ... The idea behind this, being obviously to ease the maintenance and update of the component properties chapter... I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. Talend shall not therefore be liable for the message if modified. ___ 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/bernard%40publishingsmarter.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ 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.
data reuse in structured FM...
Hi Elisa, First of all, Lynne's answer is good and I have only one thing to add: Inset Plus (http://www.weststreetconsulting.com/WSC_InsetPlus.htm) It's been a great plug in. That and the Sourcerer (www.advantica.biz/sourcerer), to filter attributes are great and get away from Frame's conditional text limitations, have been wonder tools. If there are enough frameusers in France who would like Russ to come over and speak or do a workshop, I bet we could twist his arm - answer me off-list. ([EMAIL PROTECTED] ) Russ, if you are reading this, tell me how much twisting it would take ;-) Regards, Ellen Lebelle KDS -- Forwarded message -- From: "Elisabeth SABOT" < [EMAIL PROTECTED]> To: Date: Thu, 7 Sep 2006 16:14:26 +0200 Subject: data reuse in structured FM... Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). --- I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa -- Forwarded message -- From: "Lynne A. Price" < [EMAIL PROTECTED]> To: "Elisabeth SABOT" <[EMAIL PROTECTED]>,< framers@lists.frameusers.com> Date: Thu, 07 Sep 2006 09:40:48 -0700 Subject: Re: data reuse in structured FM... At 07:14 AM 9/7/2006, Elisabeth SABOT wrote: But I am unable to import a specific part of a data flow from one section to another in the same FM file. Elisa, A text inset cannot consist of part of a flow. Instead, create a new flow containing only the reusable portion and import it into both sections. This flow can be the main flow of a new document, a body flow of a new document, or a reference flow in the document you are editing or another one. Since you can create multiple body flows or reference flows in one document, you have the option of storing all text insets in one document. Just remember that if you use reference flows of the containing document, you'll need to save it before importing the text insets. A structured text inset must have a root element. You might therefore want your EDD to define an element that can contain part of a section. For example, suppose you want a Section to contain a Title and then four Paragraph elements of which the three last ones are to be in a text inset. You might define an element called TextInset that can contain all of the children of a Section (except possibly the Title). You would then create a flow containing a TextInset element with the three reusable Paragraphs, and the section with the text inset would consist of the Title, the first Paragraph, and the imported TextInset. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training [EMAIL PROTECTED] http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284 ___ 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.
data reuse in structured FM...
Hi Elisa, First of all, Lynne's answer is good and I have only one thing to add: Inset Plus (http://www.weststreetconsulting.com/WSC_InsetPlus.htm) It's been a great plug in. That and the Sourcerer (www.advantica.biz/sourcerer), to filter attributes are great and get away from Frame's conditional text limitations, have been wonder tools. If there are enough frameusers in France who would like Russ to come over and speak or do a workshop, I bet we could twist his arm - answer me off-list. ([EMAIL PROTECTED]) Russ, if you are reading this, tell me how much twisting it would take ;-) Regards, Ellen Lebelle KDS -- Forwarded message -- From: "Elisabeth SABOT" < [EMAIL PROTECTED]> To: Date: Thu, 7 Sep 2006 16:14:26 +0200 Subject: data reuse in structured FM... Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). --- I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa -- Forwarded message -- From: "Lynne A. Price" < [EMAIL PROTECTED]> To: "Elisabeth SABOT" <[EMAIL PROTECTED]>, Date: Thu, 07 Sep 2006 09:40:48 -0700 Subject: Re: data reuse in structured FM... At 07:14 AM 9/7/2006, Elisabeth SABOT wrote: But I am unable to import a specific part of a data flow from one section to another in the same FM file. Elisa, A text inset cannot consist of part of a flow. Instead, create a new flow containing only the reusable portion and import it into both sections. This flow can be the main flow of a new document, a body flow of a new document, or a reference flow in the document you are editing or another one. Since you can create multiple body flows or reference flows in one document, you have the option of storing all text insets in one document. Just remember that if you use reference flows of the containing document, you'll need to save it before importing the text insets. A structured text inset must have a root element. You might therefore want your EDD to define an element that can contain part of a section. For example, suppose you want a Section to contain a Title and then four Paragraph elements of which the three last ones are to be in a text inset. You might define an element called TextInset that can contain all of the children of a Section (except possibly the Title). You would then create a flow containing a TextInset element with the three reusable Paragraphs, and the section with the text inset would consist of the Title, the first Paragraph, and the imported TextInset. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training [EMAIL PROTECTED] http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284 ___ 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.
data reuse in structured FM...
You may want to check into the tools at http://www.weststreetconsulting.com, specifically InsetPlus to see if they help. Try the tutorial and then start to develop based on ideas that Russ explains. Bernard Bernard Aschwanden Publishing Technologies Expert Publishing Smarter bernard at publishingsmarter.com www.publishingsmarter.com -Original Message- From: framers-bounces+bernard=publishingsmarter.com at lists.frameusers.com [mailto:framers-bounces+bernard=publishingsmarter@lists.frameusers.com] On Behalf Of Elisabeth SABOT Sent: Thursday, September 07, 2006 10:14 AM To: framers at lists.frameusers.com Subject: data reuse in structured FM... Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). In brief, I'm currently writing a user guide for an OpenSource ETL process designer. This designer allows me to use components to compose ETL process flowcharts. In one chapter of this guide, I detailed each component and in particular the component's specific property parameters. This chapter is divided into section per component and subsections for properties and use case scenario. Then within the properties subsection, the actual properties are organised in a table which differs more or less from one component to the other. I want to be able to reuse the content of part of the component properties table for another component which has almost the same properties although some differ... The idea behind this, being obviously to ease the maintenance and update of the component properties chapter... I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. Talend shall not therefore be liable for the message if modified. ___ You are currently subscribed to Framers as bernard at publishingsmarter.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/bernard%40publishingsmarter.com Send administrative questions to lisa at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
data reuse in structured FM...
Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). In brief, I'm currently writing a user guide for an OpenSource ETL process designer. This designer allows me to use components to compose ETL process flowcharts. In one chapter of this guide, I detailed each component and in particular the component's specific property parameters. This chapter is divided into section per component and subsections for properties and use case scenario. Then within the properties subsection, the actual properties are organised in a table which differs more or less from one component to the other. I want to be able to reuse the content of part of the component properties table for another component which has almost the same properties although some differ... The idea behind this, being obviously to ease the maintenance and update of the component properties chapter... I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. Talend shall not therefore be liable for the message if modified.
Re: data reuse in structured FM...
At 07:14 AM 9/7/2006, Elisabeth SABOT wrote: But I am unable to import a specific part of a data flow from one section to another in the same FM file. Elisa, A text inset cannot consist of part of a flow. Instead, create a new flow containing only the reusable portion and import it into both sections. This flow can be the main flow of a new document, a body flow of a new document, or a reference flow in the document you are editing or another one. Since you can create multiple body flows or reference flows in one document, you have the option of storing all text insets in one document. Just remember that if you use reference flows of the containing document, you'll need to save it before importing the text insets. A structured text inset must have a root element. You might therefore want your EDD to define an element that can contain part of a section. For example, suppose you want a Section to contain a Title and then four Paragraph elements of which the three last ones are to be in a text inset. You might define an element called TextInset that can contain all of the children of a Section (except possibly the Title). You would then create a flow containing a TextInset element with the three reusable Paragraphs, and the section with the text inset would consist of the Title, the first Paragraph, and the imported TextInset. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training [EMAIL PROTECTED]http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284 ___ 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.
data reuse in structured FM...
At 07:14 AM 9/7/2006, Elisabeth SABOT wrote: >But I am unable to import a >specific part of a data flow from one section to another in the same FM >file. Elisa, A text inset cannot consist of part of a flow. Instead, create a new flow containing only the reusable portion and import it into both sections. This flow can be the main flow of a new document, a body flow of a new document, or a reference flow in the document you are editing or another one. Since you can create multiple body flows or reference flows in one document, you have the option of storing all text insets in one document. Just remember that if you use reference flows of the containing document, you'll need to save it before importing the text insets. A structured text inset must have a root element. You might therefore want your EDD to define an element that can contain part of a section. For example, suppose you want a Section to contain a Title and then four Paragraph elements of which the three last ones are to be in a text inset. You might define an element called TextInset that can contain all of the children of a Section (except possibly the Title). You would then create a flow containing a TextInset element with the three reusable Paragraphs, and the section with the text inset would consist of the Title, the first Paragraph, and the imported TextInset. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training lprice at txstruct.comhttp://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284
data reuse in structured FM...
Hi all, Am on FM 7.1, structured (more or less coz I haven't defined a proper template/EDD yet). In brief, I'm currently writing a user guide for an OpenSource ETL process designer. This designer allows me to use components to compose ETL process flowcharts. In one chapter of this guide, I detailed each component and in particular the component's specific property parameters. This chapter is divided into section per component and subsections for properties and use case scenario. Then within the properties subsection, the actual properties are organised in a table which differs more or less from one component to the other. I want to be able to reuse the content of part of the component properties table for another component which has almost the same properties although some differ... The idea behind this, being obviously to ease the maintenance and update of the component properties chapter... I have never been very familiar with text insets but I thought this could be the right solution for this...But I am unable to import a specific part of a data flow from one section to another in the same FM file... anyone can help me on this? Maybe the text inset option isn't the right solution for this, as it is structured document? I hope my question isn't to messy. Many thanks in advance, Elisa This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. Talend shall not therefore be liable for the message if modified. ___ 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.
