Yes .. I've been asking for this for a while. In particular, it would be nice to be able to specify that a custom modeless dialog should NOT be opened in a pod (when it's too big to fit). Also, it would be great to be able to open a DITA map in document view instead of the resource manager.
But also .. complete access to configuring and managing the UI elements. :) ...scott Chris Despopoulos wrote: > 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 features. > ************************************************* > > >
