Hi all, I'm obviously not asking the right questions of the developers on the SW project (or it is possible that they are not listening).
Anyway I'll like to get a few clarifications here before I go much further as this will help to ensure that I am asking the [EMAIL PROTECTED] guys the right questions : 1) we will break up the development of the new biblio code into at least X phases : a) parsing and importation of new elements b) making the relevant UNO interfaces available for manipulation c) exportation of the new elements d) UI specification and implementation 2) backward compatibility with the old elements must be maintained (and if possible backward compatibility with UNO objects); My comments on the above : - 1 (a) is half done as I think that I am correctly parsing all elements. However I am not sure how to change the existing code so that I can easily retain compatibility as per 2. - Once 1(a) is defined then 1(b) and 1(c) should not be too difficult ( I hope :) - Obviously once the UNO model is available then you can write your trial dialogs using the UNO API's to get the best possible interface. This will then need to be specified as per http://specs.openoffice.org If the above is reasonably agreeable then I'll try to rephrase my questions and try to get some answers. -- CPH : openoffice.org contributor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
