I have been in contact with Andreas Martens, the Project Lead for the word-processor project. I outlined the scope, approach and objectives of our project in December 2004. He has discussed them with Oliver Specht the User Interface project leader. Andreas responded -
"The support of a useful bibliographic interface is on my wish list and we're willing to spent development effort on the Writer side of this. What we need to know are your requirements. The first step should be that your project members agree on an interface which should be supported by the Writer. This has to be discussed with our developers, Oliver Specht will be responsible. After we come to an agreement we create a new feature issue via issuezilla. The (Writer-)implementation could start in March, April.. when the OOo2.0 is finished. So my request for you is to come up with a specification about the interface Writer should support. Oliver will have a look at it [to determine] if we could implement it technically. Then I'll organize development resources to do so." So we need to develop a good understanding of the interface which writer needs to support and propose it to Oliver and Andreas. They are or should be aware of the genreal trend of our proposals and have not issued any warnings or reservations so far. So is the feedback from the potential coders ensured? We can try our best to keep them informed, but they will be very busy until OOo version 2.0 is released. regards David On Sunday 27 February 2005 8:23 am, Matthias Basler wrote: > Hi bibliographers, > > what came into my mind when I just read Marthas comments: > > Is one of those code developers that will eventually work on OOoBib reading > our mailing list? > > If not, we need to involve them even in early decisions, because they have > a clearer idea what features are easy/hard to implement and what of our > "whishes" for OOoBib are more or less unrealistic to code. > Those of us with programming skills certainly have some ideas of that > aspect, but since most of us have not worked with the actual source code of > OOo (in C++) we might propose things that can hardly realized within the > current OOo framework. (I for one can only GUESS what is easy/hard/not to > realize.) In cases like f.e. the "standalone OOoBib" questions they might > tell us some side effects of our design decisions that we did not yet > foresee. > > I simply want to avaoid that Martha builds a nice GUI concept with us ... > and at the end the actual coders tell us they cannot do this or that in a > reasonable time frame or cannot do other things at all. > > So, is the feedback from the potential coders ensured? > > Matthias Basler > [EMAIL PROTECTED] > > ---------------------------------------------------------------- > This mail was sent through http://webmail.uni-jena.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
