Framers Template repository? Was: Re: Foxy stuff on master pages
At 09:25 -0700 7/8/07, Valerie Lipow wrote: >If anyone has one or more templates demonstrating the type of Master >pages/Reference pages discussed in the parent subject, if they're not >copyrighted, and if you're authorized and willing to disseminate them to the >group, would you please store a copy in the Framers' file archive? I would >love to study how they're designed, and I suspect others would like to study >them as well. Noted. I will diarize this action, but it might be a while, mainly due to the need to clean up and document the quick and dirty demos I hacked as proof of concept :-( No copyrighting is involved. -- Steve
Re: Framers Template repository? Was: Re: Foxy stuff on master pages
Whenever someone does add the templates to the repository, could that someone please post an ANN to the list to let us know? THANKS! Rene Steve Rickaby <[EMAIL PROTECTED]> wrote: At 09:25 -0700 7/8/07, Valerie Lipow wrote: >If anyone has one or more templates demonstrating the type of Master >pages/Reference pages discussed in the parent subject, if they're not >copyrighted, and if you're authorized and willing to disseminate them to the >group, would you please store a copy in the Framers' file archive? I would >love to study how they're designed, and I suspect others would like to study >them as well. Noted. I will diarize this action, but it might be a while, mainly due to the need to clean up and document the quick and dirty demos I hacked as proof of concept :-( No copyrighting is involved. -- Steve ___ 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/rinnie1%40yahoo.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.
Framers Template repository? Was: Re: Foxy stuff on master pages
Whenever someone does add the templates to the repository, could that someone please post an ANN to the list to let us know? THANKS! Rene Steve Rickaby wrote: At 09:25 -0700 7/8/07, Valerie Lipow wrote: >If anyone has one or more templates demonstrating the type of Master >pages/Reference pages discussed in the parent subject, if they're not >copyrighted, and if you're authorized and willing to disseminate them to the >group, would you please store a copy in the Framers' file archive? I would >love to study how they're designed, and I suspect others would like to study >them as well. Noted. I will diarize this action, but it might be a while, mainly due to the need to clean up and document the quick and dirty demos I hacked as proof of concept :-( No copyrighting is involved. -- Steve ___ You are currently subscribed to Framers as rinnie1 at yahoo.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/rinnie1%40yahoo.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Framers Template repository? Was: Re: Foxy stuff on master pages
At 09:25 -0700 7/8/07, Valerie Lipow wrote: >If anyone has one or more templates demonstrating the type of Master >pages/Reference pages discussed in the parent subject, if they're not >copyrighted, and if you're authorized and willing to disseminate them to the >group, would you please store a copy in the Framers' file archive? I would >love to study how they're designed, and I suspect others would like to study >them as well. Noted. I will diarize this action, but it might be a while, mainly due to the need to clean up and document the quick and dirty demos I hacked as proof of concept :-( No copyrighting is involved. -- Steve ___ 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.
Framers Template repository? Was: Re: Foxy stuff on master pages
If anyone has one or more templates demonstrating the type of Master pages/Reference pages discussed in the parent subject, if they're not copyrighted, and if you're authorized and willing to disseminate them to the group, would you please store a copy in the Framers' file archive? I would love to study how they're designed, and I suspect others would like to study them as well. Val -- Valerie Lipow [EMAIL PROTECTED] On 8/7/07, Steve Rickaby <[EMAIL PROTECTED]> wrote: > > Hi Framers > > In off-group discussions with Angela and others, it's become only too > clear that it's possible to create clever stuff on master pages that is > obvious to its designer but to no-one else ;-) For example, the auto > thumbtabs stuff which came up recently on the group, or anything that > involves a template with complex frames on master pages. Because this often > involves overlaying transparent objects, it can create a maintenance > headache for whoever comes afterwards, as recently witnessed by someone on > the group who had to get an expert to fox out how their template was working > [that was a thumbtabs thing]. It's real important therefore to document how > the template works, if only in a few lines. > > In the case I'm discussing with Angela, switchable page backgrounds, when > the technique is working there are multiple conditionalised anchored frames > on a master page, all the same size, all overlaying each other, and with > their boundaries and anchors nudged outside the displayed area to create the > required crop margins. That sort of thing would be enough to fox anyone. > > A way to ensure that the description travels around with the template is > to add one or more extra reference pages called 'Notes' or somesuch, and put > a brief potted description of how the template - or it's more foxy features > - operates there. That way the 'docs' can only be lost if someone > deliberately deletes the relevant reference page(s). > > When massing with multiple frames on master pages, it's a lot easier to > see what's going on if you give the various frames a temporary - and > different - fill pattern and/or colored border. When you've finished > dickering with them, you can use the Find > anchored frame feature to select > them one by one and remove the decorations. I use this when building frames > for moving thumbtabs to get the stacking order for the various frames > correct. > > Hope this helps someone. > > -- > Steve > ___ > ___ 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.
Foxy stuff on master pages
Hi Peter At 06:27 -0500 7/8/07, Peter Gold wrote: >On 8/7/07, Steve Rickaby wrote: > >> A way to ensure that the description travels around with the template is to >> add one or more extra reference pages called 'Notes' or somesuch, and put a >> brief potted description of how the template - or it's more foxy features - >> operates there. That way the 'docs' can only be lost if someone deliberately >> deletes the relevant reference page(s). > >I agree that documentation for any template is essential for making >their maintenance efficient and less prone to errors. In my classes, I >recommend placing information in a master page's tagged text frame. Yes, that would work too. >Tagged text frames (like Flow: A, etc.) on master pages do not display >their content on body pages; they only create text frames on body >pages they are applied to. In cases where there's a lot to document, >in the past I've suggested including a short instruction on where to >find a file with more complete documentation, and even creating a >cross-reference to that source file. Nice idea. >For authors who support others, including documentation with templates >can reduce their support load. It's as simple as asking "There is >documentation on thee reference pages of the file. Have you tried >using it for help before asking for support?" Heh ;-) Couple of years ago I was required to build a reusable structured book template. The stand-alone documentation for that ran to 44 pages :-( -- Steve
Foxy stuff on master pages
An even slicker way to document customized master pages is to put the explanatory text right in the master page because I think few people would ever think to prowl through the reference pages for this kind of information. The body text frame on the master page is nothing more than a placeholder, and any content that you place inside that frame will never show up on the body pages. This provides a very convenient place to self-document each custom master page. Fred Ridder >From: Steve Rickaby >To: framers at FrameUsers.com >Subject: Foxy stuff on master pages >Date: Tue, 7 Aug 2007 10:06:02 +0100 > >Hi Framers > >In off-group discussions with Angela and others, it's become only too clear >that it's possible to create clever stuff on master pages that is obvious >to its designer but to no-one else ;-) For example, the auto thumbtabs >stuff which came up recently on the group, or anything that involves a >template with complex frames on master pages. Because this often involves >overlaying transparent objects, it can create a maintenance headache for >whoever comes afterwards, as recently witnessed by someone on the group who >had to get an expert to fox out how their template was working [that was a >thumbtabs thing]. It's real important therefore to document how the >template works, if only in a few lines. > >In the case I'm discussing with Angela, switchable page backgrounds, when >the technique is working there are multiple conditionalised anchored frames >on a master page, all the same size, all overlaying each other, and with >their boundaries and anchors nudged outside the displayed area to create >the required crop margins. That sort of thing would be enough to fox >anyone. > >A way to ensure that the description travels around with the template is to >add one or more extra reference pages called 'Notes' or somesuch, and put a >brief potted description of how the template - or it's more foxy features - >operates there. That way the 'docs' can only be lost if someone >deliberately deletes the relevant reference page(s). > >When massing with multiple frames on master pages, it's a lot easier to see >what's going on if you give the various frames a temporary - and different >- fill pattern and/or colored border. When you've finished dickering with >them, you can use the Find > anchored frame feature to select them one by >one and remove the decorations. I use this when building frames for moving >thumbtabs to get the stacking order for the various frames correct. > >Hope this helps someone. > >-- >Steve _ Learn.Laugh.Share. Reallivemoms is right place! http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
Foxy stuff on master pages
At 10:06 +0100 7/8/07, Steve Rickaby wrote: >When massing with multiple frames on master pages, it's a lot easier to see >what's going on if you give the various frames a temporary - and different - >fill pattern and/or colored border. When you've finished dickering with them, >you can use the Find > anchored frame feature to select them one by one and >remove the decorations. I use this when building frames for moving thumbtabs >to get the stacking order for the various frames correct. Sorry - the 'Find > anchored frame' bit only applies to the specific case Angela and I are discussing: apologies for any confusion [including mine]. -- Steve
Foxy stuff on master pages
Hi Framers In off-group discussions with Angela and others, it's become only too clear that it's possible to create clever stuff on master pages that is obvious to its designer but to no-one else ;-) For example, the auto thumbtabs stuff which came up recently on the group, or anything that involves a template with complex frames on master pages. Because this often involves overlaying transparent objects, it can create a maintenance headache for whoever comes afterwards, as recently witnessed by someone on the group who had to get an expert to fox out how their template was working [that was a thumbtabs thing]. It's real important therefore to document how the template works, if only in a few lines. In the case I'm discussing with Angela, switchable page backgrounds, when the technique is working there are multiple conditionalised anchored frames on a master page, all the same size, all overlaying each other, and with their boundaries and anchors nudged outside the displayed area to create the required crop margins. That sort of thing would be enough to fox anyone. A way to ensure that the description travels around with the template is to add one or more extra reference pages called 'Notes' or somesuch, and put a brief potted description of how the template - or it's more foxy features - operates there. That way the 'docs' can only be lost if someone deliberately deletes the relevant reference page(s). When massing with multiple frames on master pages, it's a lot easier to see what's going on if you give the various frames a temporary - and different - fill pattern and/or colored border. When you've finished dickering with them, you can use the Find > anchored frame feature to select them one by one and remove the decorations. I use this when building frames for moving thumbtabs to get the stacking order for the various frames correct. Hope this helps someone. -- Steve
Framers Template repository? Was: Re: Foxy stuff on master pages
If anyone has one or more templates demonstrating the type of Master pages/Reference pages discussed in the parent subject, if they're not copyrighted, and if you're authorized and willing to disseminate them to the group, would you please store a copy in the Framers' file archive? I would love to study how they're designed, and I suspect others would like to study them as well. Val -- Valerie Lipow vallipow at gmail.com On 8/7/07, Steve Rickaby wrote: > > Hi Framers > > In off-group discussions with Angela and others, it's become only too > clear that it's possible to create clever stuff on master pages that is > obvious to its designer but to no-one else ;-) For example, the auto > thumbtabs stuff which came up recently on the group, or anything that > involves a template with complex frames on master pages. Because this often > involves overlaying transparent objects, it can create a maintenance > headache for whoever comes afterwards, as recently witnessed by someone on > the group who had to get an expert to fox out how their template was working > [that was a thumbtabs thing]. It's real important therefore to document how > the template works, if only in a few lines. > > In the case I'm discussing with Angela, switchable page backgrounds, when > the technique is working there are multiple conditionalised anchored frames > on a master page, all the same size, all overlaying each other, and with > their boundaries and anchors nudged outside the displayed area to create the > required crop margins. That sort of thing would be enough to fox anyone. > > A way to ensure that the description travels around with the template is > to add one or more extra reference pages called 'Notes' or somesuch, and put > a brief potted description of how the template - or it's more foxy features > - operates there. That way the 'docs' can only be lost if someone > deliberately deletes the relevant reference page(s). > > When massing with multiple frames on master pages, it's a lot easier to > see what's going on if you give the various frames a temporary - and > different - fill pattern and/or colored border. When you've finished > dickering with them, you can use the Find > anchored frame feature to select > them one by one and remove the decorations. I use this when building frames > for moving thumbtabs to get the stacking order for the various frames > correct. > > Hope this helps someone. > > -- > Steve > ___ >
RE: Foxy stuff on master pages
An even slicker way to document customized master pages is to put the explanatory text right in the master page because I think few people would ever think to prowl through the reference pages for this kind of information. The body text frame on the master page is nothing more than a placeholder, and any content that you place inside that frame will never show up on the body pages. This provides a very convenient place to self-document each custom master page. Fred Ridder From: Steve Rickaby <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Foxy stuff on master pages Date: Tue, 7 Aug 2007 10:06:02 +0100 Hi Framers In off-group discussions with Angela and others, it's become only too clear that it's possible to create clever stuff on master pages that is obvious to its designer but to no-one else ;-) For example, the auto thumbtabs stuff which came up recently on the group, or anything that involves a template with complex frames on master pages. Because this often involves overlaying transparent objects, it can create a maintenance headache for whoever comes afterwards, as recently witnessed by someone on the group who had to get an expert to fox out how their template was working [that was a thumbtabs thing]. It's real important therefore to document how the template works, if only in a few lines. In the case I'm discussing with Angela, switchable page backgrounds, when the technique is working there are multiple conditionalised anchored frames on a master page, all the same size, all overlaying each other, and with their boundaries and anchors nudged outside the displayed area to create the required crop margins. That sort of thing would be enough to fox anyone. A way to ensure that the description travels around with the template is to add one or more extra reference pages called 'Notes' or somesuch, and put a brief potted description of how the template - or it's more foxy features - operates there. That way the 'docs' can only be lost if someone deliberately deletes the relevant reference page(s). When massing with multiple frames on master pages, it's a lot easier to see what's going on if you give the various frames a temporary - and different - fill pattern and/or colored border. When you've finished dickering with them, you can use the Find > anchored frame feature to select them one by one and remove the decorations. I use this when building frames for moving thumbtabs to get the stacking order for the various frames correct. Hope this helps someone. -- Steve _ Learn.Laugh.Share. Reallivemoms is right place! http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us ___ 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.
Foxy stuff on master pages
On 8/7/07, Steve Rickaby wrote: > A way to ensure that the description travels around with the template is to > add one or more extra reference pages called 'Notes' or somesuch, and put a > brief potted description of how the template - or it's more foxy features - > operates there. That way the 'docs' can only be lost if someone deliberately > deletes the relevant reference page(s). I agree that documentation for any template is essential for making their maintenance efficient and less prone to errors. In my classes, I recommend placing information in a master page's tagged text frame. Tagged text frames (like Flow: A, etc.) on master pages do not display their content on body pages; they only create text frames on body pages they are applied to. In cases where there's a lot to document, in the past I've suggested including a short instruction on where to find a file with more complete documentation, and even creating a cross-reference to that source file. Steve's idea of using reference pages is even better, because there's no way to lose the documentation. For master pages that need documentation, I would add the suggestion to include a short comment in a tagged text frame on those pages that mentions that there is documentation on the reference page(s), and provide the reference page name(s). For authors who support others, including documentation with templates can reduce their support load. It's as simple as asking "There is documentation on thee reference pages of the file. Have you tried using it for help before asking for support?" HTH Regards, Peter ___ Peter Gold KnowHow ProServices
Re: Foxy stuff on master pages
Hi Peter At 06:27 -0500 7/8/07, Peter Gold wrote: >On 8/7/07, Steve Rickaby <[EMAIL PROTECTED]> wrote: > >> A way to ensure that the description travels around with the template is to >> add one or more extra reference pages called 'Notes' or somesuch, and put a >> brief potted description of how the template - or it's more foxy features - >> operates there. That way the 'docs' can only be lost if someone deliberately >> deletes the relevant reference page(s). > >I agree that documentation for any template is essential for making >their maintenance efficient and less prone to errors. In my classes, I >recommend placing information in a master page's tagged text frame. Yes, that would work too. >Tagged text frames (like Flow: A, etc.) on master pages do not display >their content on body pages; they only create text frames on body >pages they are applied to. In cases where there's a lot to document, >in the past I've suggested including a short instruction on where to >find a file with more complete documentation, and even creating a >cross-reference to that source file. Nice idea. >For authors who support others, including documentation with templates >can reduce their support load. It's as simple as asking "There is >documentation on thee reference pages of the file. Have you tried >using it for help before asking for support?" Heh ;-) Couple of years ago I was required to build a reusable structured book template. The stand-alone documentation for that ran to 44 pages :-( -- Steve ___ 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.
Re: Foxy stuff on master pages
On 8/7/07, Steve Rickaby <[EMAIL PROTECTED]> wrote: > A way to ensure that the description travels around with the template is to > add one or more extra reference pages called 'Notes' or somesuch, and put a > brief potted description of how the template - or it's more foxy features - > operates there. That way the 'docs' can only be lost if someone deliberately > deletes the relevant reference page(s). I agree that documentation for any template is essential for making their maintenance efficient and less prone to errors. In my classes, I recommend placing information in a master page's tagged text frame. Tagged text frames (like Flow: A, etc.) on master pages do not display their content on body pages; they only create text frames on body pages they are applied to. In cases where there's a lot to document, in the past I've suggested including a short instruction on where to find a file with more complete documentation, and even creating a cross-reference to that source file. Steve's idea of using reference pages is even better, because there's no way to lose the documentation. For master pages that need documentation, I would add the suggestion to include a short comment in a tagged text frame on those pages that mentions that there is documentation on the reference page(s), and provide the reference page name(s). For authors who support others, including documentation with templates can reduce their support load. It's as simple as asking "There is documentation on thee reference pages of the file. Have you tried using it for help before asking for support?" HTH Regards, Peter ___ Peter Gold KnowHow ProServices ___ 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.
Re: Foxy stuff on master pages
At 10:06 +0100 7/8/07, Steve Rickaby wrote: >When massing with multiple frames on master pages, it's a lot easier to see >what's going on if you give the various frames a temporary - and different - >fill pattern and/or colored border. When you've finished dickering with them, >you can use the Find > anchored frame feature to select them one by one and >remove the decorations. I use this when building frames for moving thumbtabs >to get the stacking order for the various frames correct. Sorry - the 'Find > anchored frame' bit only applies to the specific case Angela and I are discussing: apologies for any confusion [including mine]. -- Steve ___ 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.
Foxy stuff on master pages
Hi Framers In off-group discussions with Angela and others, it's become only too clear that it's possible to create clever stuff on master pages that is obvious to its designer but to no-one else ;-) For example, the auto thumbtabs stuff which came up recently on the group, or anything that involves a template with complex frames on master pages. Because this often involves overlaying transparent objects, it can create a maintenance headache for whoever comes afterwards, as recently witnessed by someone on the group who had to get an expert to fox out how their template was working [that was a thumbtabs thing]. It's real important therefore to document how the template works, if only in a few lines. In the case I'm discussing with Angela, switchable page backgrounds, when the technique is working there are multiple conditionalised anchored frames on a master page, all the same size, all overlaying each other, and with their boundaries and anchors nudged outside the displayed area to create the required crop margins. That sort of thing would be enough to fox anyone. A way to ensure that the description travels around with the template is to add one or more extra reference pages called 'Notes' or somesuch, and put a brief potted description of how the template - or it's more foxy features - operates there. That way the 'docs' can only be lost if someone deliberately deletes the relevant reference page(s). When massing with multiple frames on master pages, it's a lot easier to see what's going on if you give the various frames a temporary - and different - fill pattern and/or colored border. When you've finished dickering with them, you can use the Find > anchored frame feature to select them one by one and remove the decorations. I use this when building frames for moving thumbtabs to get the stacking order for the various frames correct. Hope this helps someone. -- Steve ___ 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.