Re: finding Mif2Go macros to replace WWP functionality
I recommend Steve Wiseman. He's a Mif2Go expert. [EMAIL PROTECTED] Regards, Shmuel Wolfson 052-763-7133 Jim Owens wrote: We're currently using WWP 2003 to generate CHM from our Frame docs, but since there's no support past FM 7.2, we're evaluating our options. This week I've been looking at Mif2Go. We want to make the most of our existing Frame markup for Related Topic buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support the WWP system for drop-down hotspots, and it doesn't support buttons based on a Related Topics list. (ALinks and KLinks are supported.) But Mif2Go has a macro language that seems to be up to the task. The necessary macros would be virtually the same for anyone contemplating a migration from WWP. This leads me to ask whether anyone has already developed boilerplate macros that they are willing to share. ___ 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/sbw%40actcom.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.
finding Mif2Go macros to replace WWP functionality
I recommend Steve Wiseman. He's a Mif2Go expert. swiseman at context.co.il Regards, Shmuel Wolfson 052-763-7133 Jim Owens wrote: > We're currently using WWP 2003 to generate CHM from our Frame docs, but > since there's no support past FM 7.2, we're evaluating our options. This > week I've been looking at Mif2Go. > > We want to make the most of our existing Frame markup for Related Topic > buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support > the WWP system for drop-down hotspots, and it doesn't support buttons > based on a Related Topics list. (ALinks and KLinks are supported.) > > But Mif2Go has a macro language that seems to be up to the task. The > necessary macros would be virtually the same for anyone contemplating a > migration from WWP. This leads me to ask whether anyone has already > developed "boilerplate" macros that they are willing to share. > > ___ > > > You are currently subscribed to Framers as sbw at actcom.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/sbw%40actcom.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > >
Re: finding Mif2Go macros to replace WWP functionality
- Original Message - From: Jeremy H. Griffith [EMAIL PROTECTED] To: framers@lists.frameusers.com Cc: Jim Owens [EMAIL PROTECTED] Sent: Thursday, April 10, 2008 1:02 PM Subject: Re: finding Mif2Go macros to replace WWP functionality We want to make the most of our existing Frame markup for Related Topic buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support the WWP system for drop-down hotspots, We do have one of our own with the usual large set of options. See User's Guide par. 6.9, Including expandable sections in Help topics. We're not familiar with the WWP method, but if you tell us what the markup for it is in Frame, we'll see what we can do to support that out of the box. The WWP method is simple: you select the paragraph where you want to place the expand/collapse control, and map it to one of two WWP styles: DropDownClosed (if you want the hotspot closed by default) or DropDownOpen (if you want the hotspot open by default). All text and other elements that follow this paragraph are included in the drop-down content up to the next paragraph marked DropDownClosed, DropDownOpen, or Heading1-6. You can force the drop-down content to end earlier by inserting a marker called DropDownEnd anywhere in the last paragraph of the drop-down area. However, our topic design is such that we don't need DropDownEnd markers. and it doesn't support buttons based on a Related Topics list. (ALinks and KLinks are supported.) I don't quite understand that; Related Topics *are* ALinks. See par. 8.6.3, Configuring ALink and KLink jumps for HTML Help. HTML Help has support for ALinks and KLinks; WWP has support for Related Topics and See Also links (ALinks); and RoboHelp 7 HTML Help has support for all three, but only if you use the RoboHelp editor to create them (Frame authoring for these Help features is not supported in RH.) Unlike ALinks and KLinks, Related Topics don't require any specal markup in the destination topics. In the source topic, you create a list of standard cross-references to other topics, one per paragraph, and then you tag the paragraphs with a dedicated tag such RelatedTopics. Then you map the dedicated tag one of two WWP tags: RelatedTopic (if you want the links to be displayed in the topic body and included in a button-enabled list) or RelatedTopicOnly (if you want them in a button-enabled list only). We're using Related Topics for historical reasons, but now that I look at these options, I'm thinking that ALinks or KLinks muight be a better choice. This is a subject I'may raise in another thread. To run with our current Frame docs, RelatedTopicOnly support is what we'd need. ___ 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.
finding Mif2Go macros to replace WWP functionality
- Original Message - From: "Jeremy H. Griffith" <jer...@omsys.com> To: Cc: "Jim Owens" Sent: Thursday, April 10, 2008 1:02 PM Subject: Re: finding Mif2Go macros to replace WWP functionality > >We want to make the most of our existing Frame markup for Related Topic > >buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support > >the WWP system for drop-down hotspots, > > We do have one of our own with the usual large set of options. > See User's Guide par. 6.9, "Including expandable sections in > Help topics". We're not familiar with the WWP method, but if > you tell us what the markup for it is in Frame, we'll see what > we can do to support that out of the box. The WWP method is simple: you select the paragraph where you want to place the expand/collapse control, and map it to one of two WWP styles: DropDownClosed (if you want the hotspot closed by default) or DropDownOpen (if you want the hotspot open by default). "All text and other elements that follow this paragraph are included in the drop-down content up to the next paragraph marked DropDownClosed, DropDownOpen, or Heading1-6. You can force the drop-down content to end earlier" by inserting a marker called DropDownEnd anywhere in the last paragraph of the drop-down area. However, our topic design is such that we don't need DropDownEnd markers. > >and it doesn't support buttons based on a Related Topics list. > >(ALinks and KLinks are supported.) > > I don't quite understand that; "Related Topics" *are* ALinks. > See par. 8.6.3, "Configuring ALink and KLink jumps for HTML Help". HTML Help has support for ALinks and KLinks; WWP has support for Related Topics and "See Also" links (ALinks); and RoboHelp 7 HTML Help has support for all three, but only if you use the RoboHelp editor to create them (Frame authoring for these Help features is not supported in RH.) Unlike ALinks and KLinks, Related Topics don't require any specal markup in the destination topics. In the source topic, you create a list of standard cross-references to other topics, one per paragraph, and then you tag the paragraphs with a dedicated tag such "RelatedTopics." Then you map the dedicated tag one of two WWP tags: RelatedTopic (if you want the links to be displayed in the topic body and included in a button-enabled list) or RelatedTopicOnly (if you want them in a button-enabled list only). We're using Related Topics for historical reasons, but now that I look at these options, I'm thinking that ALinks or KLinks muight be a better choice. This is a subject I'may raise in another thread. To run with our current Frame docs, RelatedTopicOnly support is what we'd need.
Re: finding Mif2Go macros to replace WWP functionality
- Original Message - From: Jeremy H. Griffith [EMAIL PROTECTED] Cc: Jim Owens [EMAIL PROTECTED] Sent: Thursday, April 10, 2008 1:02 PM Subject: Re: finding Mif2Go macros to replace WWP functionality On Thu, 10 Apr 2008 13:40:44 -0400, Jim Owens [EMAIL PROTECTED] wrote: We're currently using WWP 2003 to generate CHM from our Frame docs, but since there's no support past FM 7.2, we're evaluating our options. This week I've been looking at Mif2Go. Good! You're not the only WWP user doing that... ;-) We want to make the most of our existing Frame markup for Related Topic buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support the WWP system for drop-down hotspots, We do have one of our own with the usual large set of options. See User's Guide par. 6.9, Including expandable sections in Help topics. We're not familiar with the WWP method, but if you tell us what the markup for it is in Frame, we'll see what we can do to support that out of the box. and it doesn't support buttons based on a Related Topics list. (ALinks and KLinks are supported.) I don't quite understand that; Related Topics *are* ALinks. See par. 8.6.3, Configuring ALink and KLink jumps for HTML Help. You might also want to look at our browser-based OmniHelp; we have a different way of using ALinks in it that provides a more consistent navigation UI. We added a tab in the left navigation pane for Related, and show all the topics that share an ALink with the current topic in it. No button or popup list needed. But Mif2Go has a macro language that seems to be up to the task. The necessary macros would be virtually the same for anyone contemplating a migration from WWP. This leads me to ask whether anyone has already developed boilerplate macros that they are willing to share. We'd like to know that too; if they exist, we'd be happy to include them in the User's Guide, and in a macro library file that would be part of the distro. We don't actually have WWP ourselves, so we'll need the help of those migrating to Mif2Go from WWP to do that. Thank you for raising this issue! -- Jeremy H. Griffith, at Omni Systems Inc. [EMAIL PROTECTED] http://www.omsys.com/ ___ 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.
finding Mif2Go macros to replace WWP functionality
- Original Message - From: "Jeremy H. Griffith" <jer...@omsys.com> Cc: "Jim Owens" Sent: Thursday, April 10, 2008 1:02 PM Subject: Re: finding Mif2Go macros to replace WWP functionality > On Thu, 10 Apr 2008 13:40:44 -0400, Jim Owens wrote: > > >We're currently using WWP 2003 to generate CHM from our Frame docs, but > >since there's no support past FM 7.2, we're evaluating our options. This > >week I've been looking at Mif2Go. > > Good! You're not the only WWP user doing that... ;-) > > >We want to make the most of our existing Frame markup for Related Topic > >buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support > >the WWP system for drop-down hotspots, > > We do have one of our own with the usual large set of options. > See User's Guide par. 6.9, "Including expandable sections in > Help topics". We're not familiar with the WWP method, but if > you tell us what the markup for it is in Frame, we'll see what > we can do to support that out of the box. > > >and it doesn't support buttons based on a Related Topics list. > >(ALinks and KLinks are supported.) > > I don't quite understand that; "Related Topics" *are* ALinks. > See par. 8.6.3, "Configuring ALink and KLink jumps for HTML Help". > > You might also want to look at our browser-based OmniHelp; we > have a different way of using ALinks in it that provides a more > consistent navigation UI. We added a tab in the left navigation > pane for Related, and show all the topics that share an ALink > with the current topic in it. No button or popup list needed. > > >But Mif2Go has a macro language that seems to be up to the task. The > >necessary macros would be virtually the same for anyone contemplating a > >migration from WWP. This leads me to ask whether anyone has already > >developed "boilerplate" macros that they are willing to share. > > We'd like to know that too; if they exist, we'd be happy to include > them in the User's Guide, and in a macro library file that would > be part of the distro. We don't actually have WWP ourselves, so > we'll need the help of those migrating to Mif2Go from WWP to do that. > > Thank you for raising this issue! > > -- Jeremy H. Griffith, at Omni Systems Inc. > http://www.omsys.com/
Re: finding Mif2Go macros to replace WWP functionality
On Thu, 10 Apr 2008 13:40:44 -0400, Jim Owens [EMAIL PROTECTED] wrote: We're currently using WWP 2003 to generate CHM from our Frame docs, but since there's no support past FM 7.2, we're evaluating our options. This week I've been looking at Mif2Go. Good! You're not the only WWP user doing that... ;-) We want to make the most of our existing Frame markup for Related Topic buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support the WWP system for drop-down hotspots, We do have one of our own with the usual large set of options. See User's Guide par. 6.9, Including expandable sections in Help topics. We're not familiar with the WWP method, but if you tell us what the markup for it is in Frame, we'll see what we can do to support that out of the box. and it doesn't support buttons based on a Related Topics list. (ALinks and KLinks are supported.) I don't quite understand that; Related Topics *are* ALinks. See par. 8.6.3, Configuring ALink and KLink jumps for HTML Help. You might also want to look at our browser-based OmniHelp; we have a different way of using ALinks in it that provides a more consistent navigation UI. We added a tab in the left navigation pane for Related, and show all the topics that share an ALink with the current topic in it. No button or popup list needed. But Mif2Go has a macro language that seems to be up to the task. The necessary macros would be virtually the same for anyone contemplating a migration from WWP. This leads me to ask whether anyone has already developed boilerplate macros that they are willing to share. We'd like to know that too; if they exist, we'd be happy to include them in the User's Guide, and in a macro library file that would be part of the distro. We don't actually have WWP ourselves, so we'll need the help of those migrating to Mif2Go from WWP to do that. Thank you for raising this issue! -- Jeremy H. Griffith, at Omni Systems Inc. [EMAIL PROTECTED] http://www.omsys.com/ ___ 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.
finding Mif2Go macros to replace WWP functionality
We're currently using WWP 2003 to generate CHM from our Frame docs, but since there's no support past FM 7.2, we're evaluating our options. This week I've been looking at Mif2Go. We want to make the most of our existing Frame markup for Related Topic buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support the WWP system for drop-down hotspots, and it doesn't support buttons based on a Related Topics list. (ALinks and KLinks are supported.) But Mif2Go has a macro language that seems to be up to the task. The necessary macros would be virtually the same for anyone contemplating a migration from WWP. This leads me to ask whether anyone has already developed "boilerplate" macros that they are willing to share.
finding Mif2Go macros to replace WWP functionality
On Thu, 10 Apr 2008 13:40:44 -0400, Jim Owens wrote: >We're currently using WWP 2003 to generate CHM from our Frame docs, but >since there's no support past FM 7.2, we're evaluating our options. This >week I've been looking at Mif2Go. Good! You're not the only WWP user doing that... ;-) >We want to make the most of our existing Frame markup for Related Topic >buttons and drop-down hotspots. Out of the box, Mif2Go doesn't support >the WWP system for drop-down hotspots, We do have one of our own with the usual large set of options. See User's Guide par. 6.9, "Including expandable sections in Help topics". We're not familiar with the WWP method, but if you tell us what the markup for it is in Frame, we'll see what we can do to support that out of the box. >and it doesn't support buttons based on a Related Topics list. >(ALinks and KLinks are supported.) I don't quite understand that; "Related Topics" *are* ALinks. See par. 8.6.3, "Configuring ALink and KLink jumps for HTML Help". You might also want to look at our browser-based OmniHelp; we have a different way of using ALinks in it that provides a more consistent navigation UI. We added a tab in the left navigation pane for Related, and show all the topics that share an ALink with the current topic in it. No button or popup list needed. >But Mif2Go has a macro language that seems to be up to the task. The >necessary macros would be virtually the same for anyone contemplating a >migration from WWP. This leads me to ask whether anyone has already >developed "boilerplate" macros that they are willing to share. We'd like to know that too; if they exist, we'd be happy to include them in the User's Guide, and in a macro library file that would be part of the distro. We don't actually have WWP ourselves, so we'll need the help of those migrating to Mif2Go from WWP to do that. Thank you for raising this issue! -- Jeremy H. Griffith, at Omni Systems Inc. http://www.omsys.com/
