Howdy Y'all, 'Whistling Dixie' - an American idiom.The freedictionay.com defines it as slang: "To engage in unrealistically rosy fantasizing".
Having a bit of feeling that this may be where I am at - and hoping it is just a case of the 80 / 20 rule catching up to me and I am simply into the 20% part of the work. A couple of questions: I have generated an apparently correct XCU file for use with an Addon zip file. Package manger understands it and successfully adds the basic library into the OOo configuration, it also successfully - well, almost, adds the menu items for calling the appropriate procedure in this library. My problem is that the menu ends up on every document type window in OOo. That is not a showstopper, as the routine catches when it is not a Base document and displays an appropriate message. But it is wrong. Can anyone help me with how I would attach this menu to only the Base document windows? For bonus points it would be great to also have it attached to the query designer window. Here is a sample of the XCU file I currently have ( it won't be the final - but the menu entry shouldn't change): <?xml version='1.0' encoding='UTF-8'?> <oor:node xmlns:oor="http://openoffice.org/2001/registry"; xmlns:xs=" http://www.w3.org/2001/XMLSchema"; oor:name="Addons" oor:package=" org.openoffice.Office"> <node oor:name="AddonUI"> <node oor:name="OfficeMenuBar"> <node oor:name="org.openoffice.Office.addon.BaseExportBeta1" oor:op="replace"> <prop oor:name="Context" oor:type="xs:string"> <value></value> </prop> <prop oor:name="Title" oor:type="xs:string"> <value>Export</value> </prop> <node oor:name="Submenu"> <node oor:name="menu01" oor:op="replace"> <prop oor:name="Context" oor:type="xs:string"> <value>com.sun.star.sdb.DatabaseDocument</value> </prop> <prop oor:name="Title" oor:type="xs:string"> <value>CSV</value> </prop> ........ ........ ........ I have tried changing these lines to <node oor:name="OfficeMenuBar"> <node oor:name="org.openoffice.Office.addon.BaseExportBeta1" oor:op="replace"> <prop oor:name="Context" oor:type="xs:string"> <value>com.sun.star.sdb.DatabaseDocument</value> </prop> Is it this line " <node oor:name="OfficeMenuBar"> " that I need to change? Am I completely missing a property ? I have expanded what I am trying to do here. The work on the CSV export has gone forward, although I have now slipped on my self-imposed release schedule for the beta of this. Fixing the above addon file is the last step to get that out. In parallel with this I have begun work on a second export file format, XML. To see where I am headed with this you can take a look at http://wiki.services.openoffice.org/wiki/XML_export . The code for this is getting very close to ready for an alpha release, perhaps 2 days. I am still in the 80% part of this piece of the work, I suppose. ;-) Oh, and don't get all excited...I am not going to try and build a full SQL/XML parser for the embedded Base database - maybe the Base developers will do that someday. Second question - actually not a question but a call for someone to help. Is there anyone here that has a good handle on the XForm document under OOo. As the final piece of the export utility I have in mind there will be a 'Export Manager' - http://wiki.services.openoffice.org/wiki/Export_Manager . Here I am at a stand still - one reason is just time, hoping to get some time for the first real work on it next week. But another reason is the idea to use an OOoXForm for the UI. I just really don't have a good handle for working with this document type. Mostly because I have not put in the time, there is that word again, to really study the documentation for it. ( what documentation there is anyway ) There will be three functional parts to the manager, one dealing with the datastore of the XML export definition. Another interacting with the worker functions in the CSV and XML export libraries and the third part is of course the XForm. This would be the document and the basic functions to set and retrieve the XML instance data. If someone on the list would have some time to help on this It would be great. Specifically I am looking for someone to create the third functional piece - the Xform document and basic routines to work with it. Please send me a direct email - or go to the discussion page at the wiki if you would like to help. We can talk about what the UI needs to do and I am wide open for ideas on this. IMO, it should not be that much work for someone that actually understands how to work with the OOoXForm document type. Thanks Drew Jensen
