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]
