I am a Java developer (under Eclipse) of "in-house" automation tools
Since a couple of weeks, I am investigating the possibility to develop an application constraining the user to follow more strictly some predefined "models" during the editing of their (so called) "specification" documents The idea is to get all the specification looking "alike", more or less with the same fonts, headers, footers, mandatory chapters, etc ... Therefore, I have succeeded - to embed a "writer" frame in my top JFRAME custom java GUI = to remove some toolbars and menu entries (in a non-persistent manner) - to intercept some commands and listen some events from my java Ideally, I was expecting my "embedded" WRITER window to keep its tremendous capabilities ( insert tables, pictures, paragraph properties, etc ... ) EXCEPT the "style" management that I was willing to limit to a predefined (custom) set In summary, my goal was to provide a powerful editor (not the full WRITER) limited to the functionalities required to edit the content of a "chapter" (or a "section") It would have been up to my application to manage the overall document through the UNO API and a dedicated GUI Unfortunately, I have ran into several problems First, some WRITER feature activation/deactivation cannot be made "non-persistent" ( ruler, navigator, Styles and Formatting dialog, etc ... ) If my application toggles them, then any later unrelated use of WRITER will open accordingly I have try to workaround the problem with an alternate installation having a "registry" dedicated to my application At this point, on windows XP, I have not yet found a good way to do it (but my preference would remain to some kind of selectable "non-persistent" flag) Second, I have never found an API sequence to select (and lock) "Custom Styles" in the "Styles and Formatting" dockable dialog combobox Therefore, when my application starts the current list of styles in this combobox is unpredictable and, at any time, my user can create or use any non expected styles I am really impressed by the UNO API and the intrusive power that a remote application can have on the behavior of the tools It is enthusiastic for a programmer to interact with a complex software such as WRITER Unfortunately, few irritating details are preventing me to go to the end of my prototype Rather than providing a limited environment for the creation of "specification" correct by construct, I will probably write some kind checker rules to assert the proper usage of the styles and the overall structure of the documents Regards -- ----------------------------------------------------------------- To unsubscribe send email to [email protected] For additional commands send email to [email protected] with Subject: help
