subject:"FDK documentation links \(Subj was \"April 11th Webinar\: FrameMaker 11....\""

RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

2013-04-14 Thread Maxwell Hoffmann

Hi Roger,

I would recommend my technique only for escalating an issue with documentation 
that you believe needs special attention. Please do continue with the comments 
you described. Thank you for sharing this other technique with the group.



Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  |  c. 
503.805.3719  |  mhoff...@adobe.com 
http://twitter.com/maxwellhoffmann -  
http://www.linkedin.com/in/maxwellhoffmann  blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
http://adobe.ly/Pbdp0J


-Original Message-
From: Roger Shuttleworth [mailto:shutti...@gmail.com] 
Sent: Saturday, April 13, 2013 1:56 AM
To: framers@lists.frameusers.com; Maxwell Hoffmann
Subject: Re: FDK documentation links (Subj was April 11th Webinar: FrameMaker 
11

Hi Maxwell

Thanks for the information on how to submit comments regarding the 
documentation. However, when accessing the FM Help online, there is already the 
option to Discuss this page using a link at the bottom of each page. I have 
used it several times in the past. Are you recommending your PDF method over 
this? (I presume such comments are
harvested?)

Regards,
Roger Shuttleworth

On 12/04/2013 6:15 PM, Maxwell Hoffmann wrote:
 Hello Russ,

 I am very glad that you figured out a solution. You do not need to apologize 
 for whining; it was good constructive criticism, and our team welcomes 
 that. I should have made it clear in my response that I did recognize and 
 appreciate your difficult situation. -- I will certainly pass your insights 
 and solutions listed below onto our development team.

 FYI -- for the whole group, here is a way to ensure that your message is 
 crystal clear regarding documentation enhancements:

 == make a PDF file that contains only the relevant pages from FDK or 
 other documentation == use annotations in PDF to identify the 
 incomplete text and add either your request for more specific information, or 
 something new that you found works == if you discover a capability that is 
 not documented, but you think should be, please use the same short PDF 
 annotation solution.
 == email the PDF attachment with a brief request or explanation to me at: 
 mhoff...@adobe.com (one n). -- ask for a REPLY so I can acknowledge, and 
 you'll know that the message got through.

 Thanks everyone, for helping us identify areas where the product and/or 
 documentation can be improved.

 __
 Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  
 |  c. 503.805.3719  |  mhoff...@adobe.com http://twitter.com/maxwellhoffmann 
 -  http://www.linkedin.com/in/maxwellhoffmann  blogs.adobe.com/techcomm
 Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
 http://adobe.ly/Pbdp0J


 -Original Message-
 From: framers-boun...@lists.frameusers.com 
 [mailto:framers-boun...@lists.frameusers.com] On Behalf Of 
 r...@weststreetconsulting.com
 Sent: Wednesday, April 10, 2013 10:34 AM
 To: framers@lists.frameusers.com
 Subject: RE: FDK documentation links (Subj was April 11th Webinar: 
 FrameMaker 11


 Hi Maxwell,

 Thank you for taking the time to respond. I do have these documents and 
 unfortunately the content is insufficient. However... before I whined one 
 last time, I did some more experimentation and I think I finally figured it 
 out. If it is of any interest to your technical publications team, I've put a 
 summary of the problem and my recommendations below.
 Again, thanks for your time.

 Russ


 RE: Adding a custom dialog box to a workspace

 It took me a long time to figure this out because I think that the FDK 
 documentation is missing some details. Here is what it says now:

 Because FrameMaker provides support for workspaces, the client's modeless 
 dialogs can become a part of a workspace. To make this work, the client has 
 to handle the notification FA_Note_Dialog_Create, which is sent to the client 
 when the workspace has to launch the modeless dialog for a particular client.

 I guess the answer is in there, but there was not enough clarification for me 
 to figure it out initially. I finally figured out that when you save a 
 workspace with the dialog open, the notification then happens automatically 
 once you select or reset that workspace in the future.
 Also, there is the fact that sparm is set to the name of the dialog, which 
 you need to test in order to know how to respond. So, I would recommend 
 adding some verbiage similar to the following:

 When a workspace is saved with a custom modeless dialog open, the name and 
 positioning of that dialog are stored with the workspace. Then, when the user 
 selects or resets the workspace, FrameMaker sends the FA_Note_Dialog_Create 
 to the respective client with sparm set to the name of the dialog box. It is 
 then the responsibility of the client to handle this notification and execute 
 the required code to open the dialog box again. Once the dialog

Re: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

2013-04-13 Thread Roger Shuttleworth


Hi Maxwell

Thanks for the information on how to submit comments regarding the 
documentation. However, when accessing the FM Help online, there is 
already the option to Discuss this page using a link at the bottom of 
each page. I have used it several times in the past. Are you 
recommending your PDF method over this? (I presume such comments are 
harvested?)


Regards,
Roger Shuttleworth

On 12/04/2013 6:15 PM, Maxwell Hoffmann wrote:

Hello Russ,

I am very glad that you figured out a solution. You do not need to apologize for 
whining; it was good constructive criticism, and our team welcomes that. I 
should have made it clear in my response that I did recognize and appreciate your 
difficult situation. -- I will certainly pass your insights and solutions listed below 
onto our development team.

FYI -- for the whole group, here is a way to ensure that your message is 
crystal clear regarding documentation enhancements:

== make a PDF file that contains only the relevant pages from FDK or other 
documentation
== use annotations in PDF to identify the incomplete text and add either your 
request for more specific information, or something new that you found works
== if you discover a capability that is not documented, but you think should be, please 
use the same short PDF annotation solution.
== email the PDF attachment with a brief request or explanation to me at: 
mhoff...@adobe.com (one n). -- ask for a REPLY so I can acknowledge, and 
you'll know that the message got through.

Thanks everyone, for helping us identify areas where the product and/or 
documentation can be improved.

__
Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  |  c. 
503.805.3719  |  mhoff...@adobe.com
http://twitter.com/maxwellhoffmann -  
http://www.linkedin.com/in/maxwellhoffmann  blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
http://adobe.ly/Pbdp0J


-Original Message-
From: framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of 
r...@weststreetconsulting.com
Sent: Wednesday, April 10, 2013 10:34 AM
To: framers@lists.frameusers.com
Subject: RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 
11


Hi Maxwell,

Thank you for taking the time to respond. I do have these documents and 
unfortunately the content is insufficient. However... before I whined one last 
time, I did some more experimentation and I think I finally figured it out. If 
it is of any interest to your technical publications team, I've put a summary 
of the problem and my recommendations below.
Again, thanks for your time.

Russ


RE: Adding a custom dialog box to a workspace

It took me a long time to figure this out because I think that the FDK 
documentation is missing some details. Here is what it says now:

Because FrameMaker provides support for workspaces, the client's modeless dialogs 
can become a part of a workspace. To make this work, the client has to handle the 
notification FA_Note_Dialog_Create, which is sent to the client when the workspace has to 
launch the modeless dialog for a particular client.

I guess the answer is in there, but there was not enough clarification for me 
to figure it out initially. I finally figured out that when you save a 
workspace with the dialog open, the notification then happens automatically 
once you select or reset that workspace in the future.
Also, there is the fact that sparm is set to the name of the dialog, which 
you need to test in order to know how to respond. So, I would recommend adding some 
verbiage similar to the following:

When a workspace is saved with a custom modeless dialog open, the name and 
positioning of that dialog are stored with the workspace. Then, when the user 
selects or resets the workspace, FrameMaker sends the FA_Note_Dialog_Create to 
the respective client with sparm set to the name of the dialog box. It is then 
the responsibility of the client to handle this notification and execute the 
required code to open the dialog box again. Once the dialog box is open and the 
client code exits, the workspace configuration routine will continue and 
automatically position the dialog box as stored in the workspace.

Note the following:

- FA_Note_Dialog_Create is only sent when the workspace includes a custom 
dialog that was open when the workspace was saved. If multiple custom dialogs 
were open, individual notifications are sent for each.

- The client notification code must reopen the dialog itself 
(F_ApiOpenResource(), etc.), then the workspace will position it.

- Like all notifications, FA_Note_Dialog_Create must be enabled with 
F_ApiNotification().

  
Message: 17

Date: Tue, 9 Apr 2013 16:19:27 -0700
From: Maxwell Hoffmann mhoff...@adobe.com
To: r...@weststreetconsulting.com r...@weststreetconsulting.com
Cc: framers@lists.frameusers.com
Subject: FDK documentation links (Subj was April 11th Webinar

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

2013-04-13 Thread Roger Shuttleworth

Hi Maxwell

Thanks for the information on how to submit comments regarding the 
documentation. However, when accessing the FM Help online, there is 
already the option to "Discuss this page" using a link at the bottom of 
each page. I have used it several times in the past. Are you 
recommending your PDF method over this? (I presume such comments are 
harvested?)

Regards,
Roger Shuttleworth

On 12/04/2013 6:15 PM, Maxwell Hoffmann wrote:
> Hello Russ,
>
> I am very glad that you figured out a solution. You do not need to apologize 
> for "whining"; it was good constructive criticism, and our team welcomes 
> that. I should have made it clear in my response that I did recognize and 
> appreciate your difficult situation. -- I will certainly pass your insights 
> and solutions listed below onto our development team.
>
> FYI -- for the whole group, here is a way to ensure that your message is 
> crystal clear regarding documentation enhancements:
>
> == make a PDF file that contains only the relevant pages from FDK or other 
> documentation
> == use annotations in PDF to identify the incomplete text and add either your 
> request for more specific information, or something new that you found works
> == if you discover a capability that is not documented, but you think should 
> be, please use the same "short PDF" annotation solution.
> == email the PDF attachment with a brief request or explanation to me at: 
> mhoffman at adobe.com (one "n"). -- ask for a REPLY so I can acknowledge, and 
> you'll know that the message got through.
>
> Thanks everyone, for helping us identify areas where the product and/or 
> documentation can be improved.
>
> __
> Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  |  c. 
> 503.805.3719  |  mhoffman at adobe.com
> http://twitter.com/maxwellhoffmann -  
> http://www.linkedin.com/in/maxwellhoffmann  blogs.adobe.com/techcomm
> Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
> http://adobe.ly/Pbdp0J
>
>
> -Original Message-
> From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at 
> lists.frameusers.com] On Behalf Of russ at weststreetconsulting.com
> Sent: Wednesday, April 10, 2013 10:34 AM
> To: framers at lists.frameusers.com
> Subject: RE: FDK documentation links (Subj was "April 11th Webinar: 
> FrameMaker 11"
>
>
> Hi Maxwell,
>
> Thank you for taking the time to respond. I do have these documents and 
> unfortunately the content is insufficient. However... before I whined one 
> last time, I did some more experimentation and I think I finally figured it 
> out. If it is of any interest to your technical publications team, I've put a 
> summary of the problem and my recommendations below.
> Again, thanks for your time.
>
> Russ
>
>
> RE: Adding a custom dialog box to a workspace
>
> It took me a long time to figure this out because I think that the FDK 
> documentation is missing some details. Here is what it says now:
>
> "Because FrameMaker provides support for workspaces, the client's modeless 
> dialogs can become a part of a workspace. To make this work, the client has 
> to handle the notification FA_Note_Dialog_Create, which is sent to the client 
> when the workspace has to launch the modeless dialog for a particular client."
>
> I guess the answer is in there, but there was not enough clarification for me 
> to figure it out initially. I finally figured out that when you save a 
> workspace with the dialog open, the notification then happens automatically 
> once you select or reset that workspace in the future.
> Also, there is the fact that "sparm" is set to the name of the dialog, which 
> you need to test in order to know how to respond. So, I would recommend 
> adding some verbiage similar to the following:
>
> When a workspace is saved with a custom modeless dialog open, the name and 
> positioning of that dialog are stored with the workspace. Then, when the user 
> selects or resets the workspace, FrameMaker sends the FA_Note_Dialog_Create 
> to the respective client with sparm set to the name of the dialog box. It is 
> then the responsibility of the client to handle this notification and execute 
> the required code to open the dialog box again. Once the dialog box is open 
> and the client code exits, the workspace configuration routine will continue 
> and automatically position the dialog box as stored in the workspace.
>
> Note the following:
>
> - FA_Note_Dialog_Create is only sent when the workspace includes a custom 
> dialog that was open when the workspace was saved. If multiple custom dialogs 
> were open, individual no

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

2013-04-13 Thread Maxwell Hoffmann

Hi Roger,

I would recommend my technique only for escalating an issue with documentation 
that you believe needs special attention. Please do continue with the comments 
you described. Thank you for sharing this other technique with the group.



Maxwell Hoffmann |? Product? Evangelist? |? Adobe? |? p. 503.336.5952? |? c. 
503.805.3719? |? mhoffman at adobe.com 
http://twitter.com/maxwellhoffmann -? 
http://www.linkedin.com/in/maxwellhoffmann? blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
http://adobe.ly/Pbdp0J


-Original Message-
From: Roger Shuttleworth [mailto:shutti...@gmail.com] 
Sent: Saturday, April 13, 2013 1:56 AM
To: framers at lists.frameusers.com; Maxwell Hoffmann
Subject: Re: FDK documentation links (Subj was "April 11th Webinar: FrameMaker 
11"

Hi Maxwell

Thanks for the information on how to submit comments regarding the 
documentation. However, when accessing the FM Help online, there is already the 
option to "Discuss this page" using a link at the bottom of each page. I have 
used it several times in the past. Are you recommending your PDF method over 
this? (I presume such comments are
harvested?)

Regards,
Roger Shuttleworth

On 12/04/2013 6:15 PM, Maxwell Hoffmann wrote:
> Hello Russ,
>
> I am very glad that you figured out a solution. You do not need to apologize 
> for "whining"; it was good constructive criticism, and our team welcomes 
> that. I should have made it clear in my response that I did recognize and 
> appreciate your difficult situation. -- I will certainly pass your insights 
> and solutions listed below onto our development team.
>
> FYI -- for the whole group, here is a way to ensure that your message is 
> crystal clear regarding documentation enhancements:
>
> == make a PDF file that contains only the relevant pages from FDK or 
> other documentation == use annotations in PDF to identify the 
> incomplete text and add either your request for more specific information, or 
> something new that you found works == if you discover a capability that is 
> not documented, but you think should be, please use the same "short PDF" 
> annotation solution.
> == email the PDF attachment with a brief request or explanation to me at: 
> mhoffman at adobe.com (one "n"). -- ask for a REPLY so I can acknowledge, and 
> you'll know that the message got through.
>
> Thanks everyone, for helping us identify areas where the product and/or 
> documentation can be improved.
>
> __
> Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  
> |  c. 503.805.3719  |  mhoffman at adobe.com 
> http://twitter.com/maxwellhoffmann -  
> http://www.linkedin.com/in/maxwellhoffmann  blogs.adobe.com/techcomm
> Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
> http://adobe.ly/Pbdp0J
>
>
> -Original Message-
> From: framers-bounces at lists.frameusers.com 
> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of 
> russ at weststreetconsulting.com
> Sent: Wednesday, April 10, 2013 10:34 AM
> To: framers at lists.frameusers.com
> Subject: RE: FDK documentation links (Subj was "April 11th Webinar: 
> FrameMaker 11"
>
>
> Hi Maxwell,
>
> Thank you for taking the time to respond. I do have these documents and 
> unfortunately the content is insufficient. However... before I whined one 
> last time, I did some more experimentation and I think I finally figured it 
> out. If it is of any interest to your technical publications team, I've put a 
> summary of the problem and my recommendations below.
> Again, thanks for your time.
>
> Russ
>
>
> RE: Adding a custom dialog box to a workspace
>
> It took me a long time to figure this out because I think that the FDK 
> documentation is missing some details. Here is what it says now:
>
> "Because FrameMaker provides support for workspaces, the client's modeless 
> dialogs can become a part of a workspace. To make this work, the client has 
> to handle the notification FA_Note_Dialog_Create, which is sent to the client 
> when the workspace has to launch the modeless dialog for a particular client."
>
> I guess the answer is in there, but there was not enough clarification for me 
> to figure it out initially. I finally figured out that when you save a 
> workspace with the dialog open, the notification then happens automatically 
> once you select or reset that workspace in the future.
> Also, there is the fact that "sparm" is set to the name of the dialog, which 
> you need to test in order to know how to respond. So, I would recommend 
> adding some verbiage similar to the following:
>
> When a workspace is saved with a custom

RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

2013-04-12 Thread Maxwell Hoffmann

Hello Russ,

I am very glad that you figured out a solution. You do not need to apologize 
for whining; it was good constructive criticism, and our team welcomes that. 
I should have made it clear in my response that I did recognize and appreciate 
your difficult situation. -- I will certainly pass your insights and solutions 
listed below onto our development team. 

FYI -- for the whole group, here is a way to ensure that your message is 
crystal clear regarding documentation enhancements:

== make a PDF file that contains only the relevant pages from FDK or other 
documentation
== use annotations in PDF to identify the incomplete text and add either your 
request for more specific information, or something new that you found works
== if you discover a capability that is not documented, but you think should 
be, please use the same short PDF annotation solution.
== email the PDF attachment with a brief request or explanation to me at: 
mhoff...@adobe.com (one n). -- ask for a REPLY so I can acknowledge, and 
you'll know that the message got through.

Thanks everyone, for helping us identify areas where the product and/or 
documentation can be improved.

__
Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  |  c. 
503.805.3719  |  mhoff...@adobe.com 
http://twitter.com/maxwellhoffmann -  
http://www.linkedin.com/in/maxwellhoffmann  blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
http://adobe.ly/Pbdp0J


-Original Message-
From: framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of 
r...@weststreetconsulting.com
Sent: Wednesday, April 10, 2013 10:34 AM
To: framers@lists.frameusers.com
Subject: RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 
11


Hi Maxwell,

Thank you for taking the time to respond. I do have these documents and 
unfortunately the content is insufficient. However... before I whined one last 
time, I did some more experimentation and I think I finally figured it out. If 
it is of any interest to your technical publications team, I've put a summary 
of the problem and my recommendations below.
Again, thanks for your time.

Russ


RE: Adding a custom dialog box to a workspace

It took me a long time to figure this out because I think that the FDK 
documentation is missing some details. Here is what it says now:

Because FrameMaker provides support for workspaces, the client's modeless 
dialogs can become a part of a workspace. To make this work, the client has to 
handle the notification FA_Note_Dialog_Create, which is sent to the client when 
the workspace has to launch the modeless dialog for a particular client.

I guess the answer is in there, but there was not enough clarification for me 
to figure it out initially. I finally figured out that when you save a 
workspace with the dialog open, the notification then happens automatically 
once you select or reset that workspace in the future.
Also, there is the fact that sparm is set to the name of the dialog, which 
you need to test in order to know how to respond. So, I would recommend adding 
some verbiage similar to the following:

When a workspace is saved with a custom modeless dialog open, the name and 
positioning of that dialog are stored with the workspace. Then, when the user 
selects or resets the workspace, FrameMaker sends the FA_Note_Dialog_Create to 
the respective client with sparm set to the name of the dialog box. It is then 
the responsibility of the client to handle this notification and execute the 
required code to open the dialog box again. Once the dialog box is open and the 
client code exits, the workspace configuration routine will continue and 
automatically position the dialog box as stored in the workspace.

Note the following:

- FA_Note_Dialog_Create is only sent when the workspace includes a custom 
dialog that was open when the workspace was saved. If multiple custom dialogs 
were open, individual notifications are sent for each.

- The client notification code must reopen the dialog itself 
(F_ApiOpenResource(), etc.), then the workspace will position it.

- Like all notifications, FA_Note_Dialog_Create must be enabled with 
F_ApiNotification().



 
Message: 17
Date: Tue, 9 Apr 2013 16:19:27 -0700
From: Maxwell Hoffmann mhoff...@adobe.com
To: r...@weststreetconsulting.com r...@weststreetconsulting.com
Cc: framers@lists.frameusers.com 
Subject: FDK documentation links (Subj was April 11th Webinar:  FrameMaker 
11

Russ,

Thank you for your inquiry and the reminder. I consulted internal resources and 
URL links to current FDK documentation are listed below.
Note: some of the URLs below may have line breaks and require post e-mail 
format editing.

FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

FDK 11.0 Documentation :
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

2013-04-12 Thread Maxwell Hoffmann

Hello Russ,

I am very glad that you figured out a solution. You do not need to apologize 
for "whining"; it was good constructive criticism, and our team welcomes that. 
I should have made it clear in my response that I did recognize and appreciate 
your difficult situation. -- I will certainly pass your insights and solutions 
listed below onto our development team. 

FYI -- for the whole group, here is a way to ensure that your message is 
crystal clear regarding documentation enhancements:

== make a PDF file that contains only the relevant pages from FDK or other 
documentation
== use annotations in PDF to identify the incomplete text and add either your 
request for more specific information, or something new that you found works
== if you discover a capability that is not documented, but you think should 
be, please use the same "short PDF" annotation solution.
== email the PDF attachment with a brief request or explanation to me at: 
mhoffman at adobe.com (one "n"). -- ask for a REPLY so I can acknowledge, and 
you'll know that the message got through.

Thanks everyone, for helping us identify areas where the product and/or 
documentation can be improved.

__
Maxwell Hoffmann |? Product? Evangelist? |? Adobe? |? p. 503.336.5952? |? c. 
503.805.3719? |? mhoffman at adobe.com 
http://twitter.com/maxwellhoffmann -? 
http://www.linkedin.com/in/maxwellhoffmann? blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xIRecorded webinars: 
http://adobe.ly/Pbdp0J


-Original Message-
From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at 
lists.frameusers.com] On Behalf Of r...@weststreetconsulting.com
Sent: Wednesday, April 10, 2013 10:34 AM
To: framers at lists.frameusers.com
Subject: RE: FDK documentation links (Subj was "April 11th Webinar: FrameMaker 
11"


Hi Maxwell,

Thank you for taking the time to respond. I do have these documents and 
unfortunately the content is insufficient. However... before I whined one last 
time, I did some more experimentation and I think I finally figured it out. If 
it is of any interest to your technical publications team, I've put a summary 
of the problem and my recommendations below.
Again, thanks for your time.

Russ


RE: Adding a custom dialog box to a workspace

It took me a long time to figure this out because I think that the FDK 
documentation is missing some details. Here is what it says now:

"Because FrameMaker provides support for workspaces, the client's modeless 
dialogs can become a part of a workspace. To make this work, the client has to 
handle the notification FA_Note_Dialog_Create, which is sent to the client when 
the workspace has to launch the modeless dialog for a particular client."

I guess the answer is in there, but there was not enough clarification for me 
to figure it out initially. I finally figured out that when you save a 
workspace with the dialog open, the notification then happens automatically 
once you select or reset that workspace in the future.
Also, there is the fact that "sparm" is set to the name of the dialog, which 
you need to test in order to know how to respond. So, I would recommend adding 
some verbiage similar to the following:

When a workspace is saved with a custom modeless dialog open, the name and 
positioning of that dialog are stored with the workspace. Then, when the user 
selects or resets the workspace, FrameMaker sends the FA_Note_Dialog_Create to 
the respective client with sparm set to the name of the dialog box. It is then 
the responsibility of the client to handle this notification and execute the 
required code to open the dialog box again. Once the dialog box is open and the 
client code exits, the workspace configuration routine will continue and 
automatically position the dialog box as stored in the workspace.

Note the following:

- FA_Note_Dialog_Create is only sent when the workspace includes a custom 
dialog that was open when the workspace was saved. If multiple custom dialogs 
were open, individual notifications are sent for each.

- The client notification code must reopen the dialog itself 
(F_ApiOpenResource(), etc.), then the workspace will position it.

- Like all notifications, FA_Note_Dialog_Create must be enabled with 
F_ApiNotification().

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Message: 17
Date: Tue, 9 Apr 2013 16:19:27 -0700
From: Maxwell Hoffmann <mhoff...@adobe.com>
To: "russ at weststreetconsulting.com" 
Cc: "framers at lists.frameusers.com" 
Subject: FDK documentation links (Subj was "Ap

FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

2013-04-10 Thread Maxwell Hoffmann

Russ,

Thank you for your inquiry and the reminder. I consulted internal resources and
URL links to current FDK documentation are listed below. Note: some of the URLs
below may have line breaks and require post e-mail format editing.

FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

FDK 11.0 Documentation :
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkinstallguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkprogrammerguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkreference.pdf

The page with all these links: http://www.adobe.com/devnet/framemaker.html

I hope that these links contain what you are seeking. If you need more
information, please let me know.

_
Maxwell Hoffmann | Product Evangelist | Adobe | p. 503.336.5952 | c.
503.805.3719 | mhoff...@adobe.commailto:mhoff...@adobe.com
http://twitter.com/maxwellhoffmann - http://www.linkedin.com/in/maxwellhoffmann
blogs.adobe.com/mbhoffmannhttp://blogs.adobe.com/mbhoffmann
blogs.adobe.com/techcommhttp://blogs.adobe.com/techcomm
Upcoming webinar calendar: http://adobe.ly/Pbz6x

On Apr 7, 2013, at 5:25 AM,
r...@weststreetconsulting.commailto:r...@weststreetconsulting.com
r...@weststreetconsulting.commailto:r...@weststreetconsulting.com wrote:

Hi Maxwell,

Sounds like a good webinar to have. While you are on the subject of
workspaces and pods, I wanted to bring up an important issue to me - the
lack of information on how to make custom FDK dialog boxes (and
presumably ExtendScript dialogs as well) that can be added to
workspaces. The FDK documentation says you can do it, but doesn't say
how. I've asked on this list, the Adobe user-to-user forums, and the
Yahoo framedev list, with no results except crickets chirping.

Many of us rely heavily on FDK and/or ES extensions with custom pods. It
is a significant obstacle to the acceptance of workspace tools, etc.,
when we are unable to configure them with our custom interfaces as well.

Thanks,
Russ

[snip]

You may register for this webinar at: http://adobe.ly/11dYMCf

___
Maxwell Hoffmann |? Product? Evangelist? |? Adobe? |? p. 503.336.5952?
|? c. 503.805.3719? |? mhoff...@adobe.commailto:mhoff...@adobe.com
http://twitter.com/maxwellhoffmann -?
http://www.linkedin.com/in/maxwellhoffmann?
blogs.adobe.com/techcommhttp://blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xI Recorded webinars:
http://adobe.ly/Pbdp0J

___

You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@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: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

2013-04-10 Thread Rick Quatro

Hi Max,

 

Unless this documentation has been updated, these links will do Russ and others 
no good. We have been through the documentation with a fine-tooth comb, but the 
information is not in there. Yesterday I requested help on using the Alt key in 
keyboard shortcuts in ExtendScript. An Adobe engineer replied with a link to 
the FrameMaker 10 Scripting Guide. The information is not in the Scripting 
Guide, which is why I posted the question in the first place. I am surprised 
that the engineer did not know that the information is not in there.

 

Russ and I are long-time FrameMaker power users and programmers that read, 
search, and study any existing documentation before we ask questions. At the 
risk of sounding thin-skinned, I find it frustrating and a bit condescending 
to receive links to documentation that we already know about. Russ's problem 
was clearly stated: The FDK documentation says you can do it, but doesn't say 
how. So, he wants to know how.

 

I can't speak for Russ, but I would prefer more straightforward answers; for 
example,

 

It can be done, but it is not documented. Here is a brief outline on how to do 
it.

It can be done, but we are busy and don't have time to document it. Hopefully, 
we can document it in the near future.

It can be done, but it is not officially documented. However, here is a copy 
of an internal memo explaining how it is done.

We are too busy to help you, but we helped so-and-so with a similar problem. 
Maybe he can help you.

 

I am sorry for the negative tone, but I have spent the last day or two 
apologizing to a large potential FrameMaker customer for its shoddy 
documentation. I am ready to suggest that he take a look at InDesign.

 

Rick

 

Rick Quatro

Carmen Publishing Inc.

585-283-5045

r...@frameexpert.com

 

 

 

From: framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Maxwell Hoffmann
Sent: Tuesday, April 09, 2013 7:19 PM
To: r...@weststreetconsulting.com
Cc: framers@lists.frameusers.com
Subject: FDK documentation links (Subj was April 11th Webinar: FrameMaker 
11

 

 

Russ,

 

Thank you for your inquiry and the reminder. I consulted internal resources and 
URL links to current FDK documentation are listed below. Note: some of the URLs 
below may have line breaks and require post e-mail format editing. 

 

FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

FDK 11.0 Documentation :
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkinstallguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkprogrammerguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkreference.pdf


The page with all these links: http://www.adobe.com/devnet/framemaker.html

 

I hope that these links contain what you are seeking. If you need more 
information, please let me know.

 

_

Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  |  c. 
503.805.3719  |  mhoff...@adobe.com 

http://twitter.com/maxwellhoffmann -  
http://www.linkedin.com/in/maxwellhoffmann  

blogs.adobe.com/mbhoffmann  blogs.adobe.com/techcomm

Upcoming webinar calendar: http://adobe.ly/Pbz6x

___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@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: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

2013-04-10 Thread russ


Hi Maxwell,

Thank you for taking the time to respond. I do have these documents and
unfortunately the content is insufficient. However... before I whined
one last time, I did some more experimentation and I think I finally
figured it out. If it is of any interest to your technical publications
team, I've put a summary of the problem and my recommendations below.
Again, thanks for your time.

Russ


RE: Adding a custom dialog box to a workspace

It took me a long time to figure this out because I think that the FDK
documentation is missing some details. Here is what it says now:

Because FrameMaker provides support for workspaces, the client's
modeless dialogs can become a part of a workspace. To make this work,
the client has to handle the notification FA_Note_Dialog_Create, which
is sent to the client when the workspace has to launch the modeless
dialog for a particular client.

I guess the answer is in there, but there was not enough clarification
for me to figure it out initially. I finally figured out that when you
save a workspace with the dialog open, the notification then happens
automatically once you select or reset that workspace in the future.
Also, there is the fact that sparm is set to the name of the dialog,
which you need to test in order to know how to respond. So, I would
recommend adding some verbiage similar to the following:

When a workspace is saved with a custom modeless dialog open, the name
and positioning of that dialog are stored with the workspace. Then, when
the user selects or resets the workspace, FrameMaker sends the
FA_Note_Dialog_Create to the respective client with sparm set to the
name of the dialog box. It is then the responsibility of the client to
handle this notification and execute the required code to open the
dialog box again. Once the dialog box is open and the client code exits,
the workspace configuration routine will continue and automatically
position the dialog box as stored in the workspace.

Note the following:

- FA_Note_Dialog_Create is only sent when the workspace includes a
custom dialog that was open when the workspace was saved. If multiple
custom dialogs were open, individual notifications are sent for each.

- The client notification code must reopen the dialog itself
(F_ApiOpenResource(), etc.), then the workspace will position it.

- Like all notifications, FA_Note_Dialog_Create must be enabled with
F_ApiNotification().





 
Message: 17
Date: Tue, 9 Apr 2013 16:19:27 -0700
From: Maxwell Hoffmann mhoff...@adobe.com
To: r...@weststreetconsulting.com r...@weststreetconsulting.com
Cc: framers@lists.frameusers.com 
Subject: FDK documentation links (Subj was April 11th Webinar:
 FrameMaker 11
Message-ID: 4040-cc12-4822-974b-11eea0dde...@adobe.com
Content-Type: text/plain; charset=utf-8


Russ,

Thank you for your inquiry and the reminder. I consulted internal
resources and URL links to current FDK documentation are listed below.
Note: some of the URLs below may have line breaks and require post
e-mail format editing.

FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

FDK 11.0 Documentation :
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkinstallguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkprogrammerguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkreference.pdf


The page with all these links:
http://www.adobe.com/devnet/framemaker.html

I hope that these links contain what you are seeking. If you need more
information, please let me know.

_
Maxwell Hoffmann | Product Evangelist | Adobe | p. 503.336.5952 | c.
503.805.3719 | mhoff...@adobe.commailto:mhoff...@adobe.com
http://twitter.com/maxwellhoffmann -
http://www.linkedin.com/in/maxwellhoffmann
blogs.adobe.com/mbhoffmannhttp://blogs.adobe.com/mbhoffmann 
blogs.adobe.com/techcommhttp://blogs.adobe.com/techcomm
Upcoming webinar calendar: http://adobe.ly/Pbz6x

On Apr 7, 2013, at 5:25 AM,
r...@weststreetconsulting.commailto:r...@weststreetconsulting.com
r...@weststreetconsulting.commailto:r...@weststreetconsulting.com
wrote:

Hi Maxwell,

Sounds like a good webinar to have. While you are on the subject of
workspaces and pods, I wanted to bring up an important issue to me - the
lack of information on how to make custom FDK dialog boxes (and
presumably ExtendScript dialogs as well) that can be added to
workspaces. The FDK documentation says you can do it, but doesn't say
how. I've asked on this list, the Adobe user-to-user forums, and the
Yahoo framedev list, with no results except crickets chirping.

Many of us rely heavily on FDK and/or ES extensions with custom pods. It
is a significant obstacle to the acceptance of workspace tools, etc.,
when we are unable to configure them with our custom interfaces as well.

Thanks,
Russ

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

2013-04-10 Thread Rick Quatro

Hi Max,



Unless this documentation has been updated, these links will do Russ and others 
no good. We have been through the documentation with a fine-tooth comb, but the 
information is not in there. Yesterday I requested help on using the Alt key in 
keyboard shortcuts in ExtendScript. An Adobe engineer replied with a link to 
the FrameMaker 10 Scripting Guide. The information is not in the Scripting 
Guide, which is why I posted the question in the first place. I am surprised 
that the engineer did not know that the information is not in there.



Russ and I are long-time FrameMaker power users and programmers that read, 
search, and study any existing documentation before we ask questions. At the 
risk of sounding "thin-skinned", I find it frustrating and a bit condescending 
to receive links to documentation that we already know about. Russ's problem 
was clearly stated: "The FDK documentation says you can do it, but doesn't say 
how." So, he wants to know how.



I can't speak for Russ, but I would prefer more straightforward answers; for 
example,



"It can be done, but it is not documented. Here is a brief outline on how to do 
it."

"It can be done, but we are busy and don't have time to document it. Hopefully, 
we can document it in the near future."

"It can be done, but it is not officially documented. However, here is a copy 
of an internal memo explaining how it is done."

"We are too busy to help you, but we helped so-and-so with a similar problem. 
Maybe he can help you."



I am sorry for the negative tone, but I have spent the last day or two 
"apologizing" to a large potential FrameMaker customer for its shoddy 
documentation. I am ready to suggest that he take a look at InDesign.



Rick



Rick Quatro

Carmen Publishing Inc.

585-283-5045

rick at frameexpert.com







From: framers-bounces at lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Maxwell Hoffmann
Sent: Tuesday, April 09, 2013 7:19 PM
To: russ at weststreetconsulting.com
Cc: framers at lists.frameusers.com
Subject: FDK documentation links (Subj was "April 11th Webinar: FrameMaker 
11"





Russ,



Thank you for your inquiry and the reminder. I consulted internal resources and 
URL links to current FDK documentation are listed below. Note: some of the URLs 
below may have line breaks and require post e-mail format editing. 



FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

FDK 11.0 Documentation :
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkinstallguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkprogrammerguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkreference.pdf


The page with all these links: http://www.adobe.com/devnet/framemaker.html



I hope that these links contain what you are seeking. If you need more 
information, please let me know.



_

Maxwell Hoffmann |  Product  Evangelist  |  Adobe  |  p. 503.336.5952  |  c. 
503.805.3719  |  mhoffman at adobe.com 

http://twitter.com/maxwellhoffmann -  
http://www.linkedin.com/in/maxwellhoffmann  

blogs.adobe.com/mbhoffmann & blogs.adobe.com/techcomm

Upcoming webinar calendar: http://adobe.ly/Pbz6x

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20130410/56e07f2b/attachment.html>

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

2013-04-10 Thread r...@weststreetconsulting.com

Hi Maxwell,

Thank you for taking the time to respond. I do have these documents and
unfortunately the content is insufficient. However... before I whined
one last time, I did some more experimentation and I think I finally
figured it out. If it is of any interest to your technical publications
team, I've put a summary of the problem and my recommendations below.
Again, thanks for your time.

Russ

RE: Adding a custom dialog box to a workspace

It took me a long time to figure this out because I think that the FDK
documentation is missing some details. Here is what it says now:

"Because FrameMaker provides support for workspaces, the client's
modeless dialogs can become a part of a workspace. To make this work,
the client has to handle the notification FA_Note_Dialog_Create, which
is sent to the client when the workspace has to launch the modeless
dialog for a particular client."

I guess the answer is in there, but there was not enough clarification
for me to figure it out initially. I finally figured out that when you
save a workspace with the dialog open, the notification then happens
automatically once you select or reset that workspace in the future.
Also, there is the fact that "sparm" is set to the name of the dialog,
which you need to test in order to know how to respond. So, I would
recommend adding some verbiage similar to the following:

When a workspace is saved with a custom modeless dialog open, the name
and positioning of that dialog are stored with the workspace. Then, when
the user selects or resets the workspace, FrameMaker sends the
FA_Note_Dialog_Create to the respective client with sparm set to the
name of the dialog box. It is then the responsibility of the client to
handle this notification and execute the required code to open the
dialog box again. Once the dialog box is open and the client code exits,
the workspace configuration routine will continue and automatically
position the dialog box as stored in the workspace.

Note the following:

- FA_Note_Dialog_Create is only sent when the workspace includes a
custom dialog that was open when the workspace was saved. If multiple
custom dialogs were open, individual notifications are sent for each.

- The client notification code must reopen the dialog itself
(F_ApiOpenResource(), etc.), then the workspace will position it.

- Like all notifications, FA_Note_Dialog_Create must be enabled with
F_ApiNotification().

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Message: 17
Date: Tue, 9 Apr 2013 16:19:27 -0700
From: Maxwell Hoffmann <mhoff...@adobe.com>
To: "russ at weststreetconsulting.com" 
Cc: "framers at lists.frameusers.com" 
Subject: FDK documentation links (Subj was "April 11th Webinar:
 FrameMaker 11"
Message-ID: <4040-CC12-4822-974B-11EEA0DDE8AE at adobe.com>
Content-Type: text/plain; charset="utf-8"

Russ,

Thank you for your inquiry and the reminder. I consulted internal
resources and URL links to current FDK documentation are listed below.
Note: some of the URLs below may have line breaks and require post
e-mail format editing.

FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

FDK 11.0 Documentation :
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkinstallguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkprogrammerguide.pdf
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/framemaker/pdfs/fdkreference.pdf

The page with all these links:
http://www.adobe.com/devnet/framemaker.html

I hope that these links contain what you are seeking. If you need more
information, please let me know.

_
Maxwell Hoffmann | Product Evangelist | Adobe | p. 503.336.5952 | c.
503.805.3719 | mhoffman at adobe.com<mailto:mhoffman at adobe.com>
http://twitter.com/maxwellhoffmann -
http://www.linkedin.com/in/maxwellhoffmann
blogs.adobe.com/mbhoffmann<http://blogs.adobe.com/mbhoffmann> &
blogs.adobe.com/techcomm<http://blogs.adobe.com/techcomm>
Upcoming webinar calendar: http://adobe.ly/Pbz6x

On Apr 7, 2013, at 5:25 AM,
"russ at weststreetconsulting.com<mailto:russ at weststreetconsulting.com>"
<mailto:russ at weststreetconsulting.com>>
wrote:

Hi Maxwell,

Sounds like a good webinar to have. While you are on the subject of
workspaces and pods, I wanted to bring up an important issue to me - the
lack of information on how to make custom FDK dialog boxes (and
presumably ExtendScript dialogs as well) that can be added to
workspaces. The FD

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

2013-04-09 Thread Maxwell Hoffmann

Russ,

FDK Installer File:
http://download.macromedia.com/pub/developer/framemaker/FDK11_0380_4_Setup.zip

The page with all these links: http://www.adobe.com/devnet/framemaker.html

I hope that these links contain what you are seeking. If you need more
information, please let me know.

_
Maxwell Hoffmann | Product Evangelist | Adobe | p. 503.336.5952 | c.
503.805.3719 | mhoffman at adobe.com
http://twitter.com/maxwellhoffmann - http://www.linkedin.com/in/maxwellhoffmann
blogs.adobe.com/mbhoffmann &
blogs.adobe.com/techcomm
Upcoming webinar calendar: http://adobe.ly/Pbz6x

On Apr 7, 2013, at 5:25 AM, "russ at weststreetconsulting.com" mailto:russ at
weststreetconsulting.com>> wrote:

Hi Maxwell,

Thanks,
Russ

[snip]

You may register for this webinar at: http://adobe.ly/11dYMCf

___
Maxwell Hoffmann |? Product? Evangelist? |? Adobe? |? p. 503.336.5952?
|? c. 503.805.3719? |? mhoffman at adobe.com
http://twitter.com/maxwellhoffmann -?
http://www.linkedin.com/in/maxwellhoffmann?
blogs.adobe.com/techcomm
Upcoming webinars http://adobe.ly/Pbz6xI Recorded webinars:
http://adobe.ly/Pbdp0J

-- next part --
An HTML attachment was scrubbed...
URL:

RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

Re: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

RE: FDK documentation links (Subj was April 11th Webinar: FrameMaker 11....

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

FDK documentation links (Subj was "April 11th Webinar: FrameMaker 11...."

12 matches

Site Navigation

Mail list logo

Footer information