Hi, our discussion about native packages for UNO components is a little bit frustrating. I would prefer if someone in the know could provide us with a *complete* and *understandable* list of requirements that are the absolutely necessary ones.
I know, it's hard to write good requirements, because very often you get implementation directions instead, but I'm afraid without that we will never achieve anything. I expect that the first shot for a requirements document will not be the final result, but it could be a start and we could discuss together where changes are necessary, hopefully without a implementation dependent view. It doesn't help to say "that's the way we do it and there is no other way". Of course that should be true for both sides! Because I know one side a lot better ;-), I can give an example: if keeping the original packages in "canonic places" helped a lot we should reintroduce it. Maybe we can find more simle steps into a common direction. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
