Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Q-PCD Programmability-4: UNO ease of Use | ||
---|---|---|---|
Product: | General | Reporter: | kay.ramme |
Component: | code | Assignee: | Stephan Bergmann <stephan.bergmann.secondary> |
Status: | CLOSED FIXED | QA Contact: | issues@framework <issues> |
Severity: | Trivial | ||
Priority: | P4 | CC: | issues |
Version: | OOo 1.0.0 | ||
Target Milestone: | OOo 2.0 | ||
Hardware: | Other | ||
OS: | Other OS | ||
Issue Type: | FEATURE | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
kay.ramme
2003-10-14 08:11:03 UTC
. added keyword Q-PCD Stephan, this is yours :-). Concentrating on the "UNO ease of use: map service concept to concrete types (e.g. Interfaces)" part. In agreement with KR, this task is now only about "UNO ease of use: map service concept to concrete types (e.g. Interfaces)." That boils down to: 1 Introduce multiple-inheritance interface types, to serve as a replacement for abstract UNOIDL service descriptions. Done, see internal bug #114000#. 2 Expand interface type attributes, to serve as a replacement for UNOIDL service description properties. 3 Introduce a new UNOIDL "component" construct, to serve as a replacement for instantiatable UNOIDL service descriptions. In language bindings, generate code for such components (e.g., static XSomeInterface com.sun...SomeComponent.create(XComponentContext)). 4 Update Dev. Guide. A next big step would be the introduction of generics/templates into UNO. It is unclear whether this can be done in the OOo 2.0 timeframe. See sub issue 26602 for the next incremental step. Subsequent tasks are: - Adapt Java--langugage-binding UNO-type reflection to new UNO features. - Adapt auxiliary tools to new type registry (registry/tools, rdbmaker). - Add simple generic structs to UNO, that can be used to model maybevoid etc. properties in the type system. In C++, map them to templates. In Java, map them to Object-polymorphism, with the future option of changing javamaker to directly generate class files, and use the Java 1.5 generic features in those class files. - Offer helpers in the C++ and Java language bindings that reflectively implement XPropertySet etc. on top of UNO interface attributes. - Retrofit existing udkapi/offapi services/singletons as (single-)interface--based ones. - Update DevGuide. Fixed. The last three items of the previous to-do list are tracked by individual issues: helpers: issue 29740 retrofitting: issue 29741 DevGuide: issue 29742 closed Created attachment 72301 |