To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=66635
------- Additional comments from [EMAIL PROTECTED] Mon Nov 13 04:26:45 -0800 2006 ------- @ramon_garcia: - "The issue is not so much performance as compatibility." Sorry, I do not understand this. Why would something different than XTypeProvider be necessary? - "My personal view is that objects should not implement XTypeProvider nor anything like that." Ideally, functionality like XTypeProvider should be part of each UNO language binding, instead of the UNO API (however, UNO language bindings are already supporting the existing functionality well, e.g., cppuhelper's C++ implementation helpers provide the necessary stuff). "an object could have a method getSerivceGUID that returns an identifier for a service" There is a fundamental mismatch between UNO objects and UNO services---a UNO object can implement more than one service, or none at all. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- 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]
