Hi Ariel, > [Side comment: why is this service OfficeDatabaseDocument still > "unplubished"? interface publishing policy is a mystery I do not > understand yet; looks like a question to [EMAIL PROTECTED]
Well .... once I declare a service "published", I am forbidden to add more interfaces or properties to them, except I declare them "optional". This leaves me with a problem: When I add new functionality to the implementation, I want to document it. Adding it as "optional" does not capture the fact that this functionality *has* to be (and always is) present. Adding prosa like "Though this is declared as optional, it really isn't." is not a solution, IMO. Thus, I simply don't like the "published" concept, in the form it is right now. More precise, I think it does not capture some aspects of an evolving, living API. There are different opinions on this, of course :) For instance, some people claim I should add a OfficeDatabaseDocument2, OfficeDatabaseDocument3, and so on, with every change I do. Not really feasible IMO. Artificial hurdles as the current - immature, IMO - "published" concept are one (though not the major) reason why people pay way too little attention to API design. > You can throw a veto to close the document [not in OOoBasic AFAIK], IIRC, there is some component you can instantiate in Basic, which, as long as it lives, vetoes the closing. Not sure how it's called, however. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
