Here here. These limitations are really a problem for any serious FDK
developer working on interactive software. I add my voice to the (small)
chorus of protest thus far. My personal thoughts are that this is an
important issue, because without third-party add-ons, FM would not be
nearly the powerhouse that it is.



Message: 1
Date: Tue, 8 Dec 2009 04:44:50 -0800 (PST)
From: Chris Despopoulos <>
Subject: FM9: Resource manager bugs?
To: framers at
Message-ID: <603716.41400.qm at>
Content-Type: text/plain; charset=us-ascii

I'm glad (in an ironic sense) to see that I'm not the only person who is
asking for the API to expose the GUI elements. In a more literal sense,
I'm sorry to see it. Please, please, please... Expose the new GUI to the
API so we can make plug-ins that interact reasonably with the user's
session. This is especially important now because the whole point of the
new GUI is to give the user more control over the environment. And yet,
any plug-in that adds documents or uses FrameMaker in any way to display
or capture information runs the risk of disrupting the user's setup.
This puts plug-in developers in the unfortunate position of being at
cross-purposes with Adobe and the FrameMaker users.

(And while you're at it, make a notification for every time you generate
an ID Val attribute -- PLEASE!!!! How hard can it be?)

The FM9 API does not expose methods 
for handling or dealing with actions in the new UI elements, and because

DITA-FMx requires the replacement of the core DITA DLLs many of the 
features in the resource manager are non-functional or don't work as 
expected. I'm hoping that a future patch will add access to the UI


Reply via email to