Difference between revisions of "Uno/To-Dos"
From Apache OpenOffice Wiki
< Uno
m (Added category.) |
m (Added links.) |
||
Line 1: | Line 1: | ||
== ToDos and potential ToDos == | == ToDos and potential ToDos == | ||
− | Clear | + | ===Clear Separation between C and C++=== |
− | * Move C++ stuff from cppu to cppuhelper. | + | * Move C++ stuff from [http://udk.openoffice.org/source/browse/udk/cppu cppu] to [http://udk.openoffice.org/source/browse/udk/cppuhelper cppuhelper]. |
− | Module | + | ===Module Naming Clean up=== |
* Rename module [http://udk.openoffice.org/source/browse/udk/cppu/ cppu] to reflect that it is implementing [[Uno/Binary | Binary Uno]]. | * Rename module [http://udk.openoffice.org/source/browse/udk/cppu/ cppu] to reflect that it is implementing [[Uno/Binary | Binary Uno]]. | ||
* Rename module [http://udk.openoffice.org/source/browse/udk/cppuhelper cppuhelper] to reflect that it is implementing [[Uno/Cpp | C++ Uno]]. | * Rename module [http://udk.openoffice.org/source/browse/udk/cppuhelper cppuhelper] to reflect that it is implementing [[Uno/Cpp | C++ Uno]]. | ||
− | Simplification and Performance | + | ===Simplification and Performance=== |
* Remove the Binary Uno ABI and friends, replace it with one of the platform C++ ABIs. | * Remove the Binary Uno ABI and friends, replace it with one of the platform C++ ABIs. | ||
− | * Support direct access of Uno types in IDL, without includes. | + | * Support direct access of Uno types in [[Uno/Spec/IDL | IDL]], without includes. |
* Let the *makers retrieve type information from the type providers and not from rdb files. | * Let the *makers retrieve type information from the type providers and not from rdb files. | ||
* Harmonize initial object access for [[Uno/Remote | Remote Uno]] and components -> it is actually the same. | * Harmonize initial object access for [[Uno/Remote | Remote Uno]] and components -> it is actually the same. | ||
Line 20: | Line 20: | ||
* Unify command line interface for all Uno tools. | * Unify command line interface for all Uno tools. | ||
− | Features | + | ===Features=== |
* Introduce process lifecycle based on living threads. | * Introduce process lifecycle based on living threads. | ||
* Have Uno package support for the [[Uno/Spec/Ure | URE]]. | * Have Uno package support for the [[Uno/Spec/Ure | URE]]. | ||
− | * Move the UCB into the URE. | + | * Move the UCB into the [[Uno/Spec/Ure | URE]]. |
− | * Move the configr mgr. into the URE. | + | * Move the configr mgr. into the [[Uno/Spec/Ure | URE]]. |
* Uno alien type support e.g. for Java (e.g. a type description provider implemented in Java based on Java reflection). | * Uno alien type support e.g. for Java (e.g. a type description provider implemented in Java based on Java reflection). | ||
* A Uno-SOAP Bridge. | * A Uno-SOAP Bridge. |
Revision as of 11:28, 25 April 2006
Contents
ToDos and potential ToDos
Clear Separation between C and C++
- Move C++ stuff from cppu to cppuhelper.
Module Naming Clean up
- Rename module cppu to reflect that it is implementing Binary Uno.
- Rename module cppuhelper to reflect that it is implementing C++ Uno.
Simplification and Performance
- Remove the Binary Uno ABI and friends, replace it with one of the platform C++ ABIs.
- Support direct access of Uno types in IDL, without includes.
- Let the *makers retrieve type information from the type providers and not from rdb files.
- Harmonize initial object access for Remote Uno and components -> it is actually the same.
- Leverage protocol bridges for global variables, e.g. the "ServiceManager" or the "ComponentContext".
- Remove all exception specifications.
- Consolidate the Binary Uno structs "uno_Environment" and "uno_ExtEnvironment".
- Remove
#ifndef EXCEPTIONS_OFF
macros, actually C++ Uno is not useable without exceptions anyway. - Is SAL_CALL really necessary for "inline" stuff? If not, remove it.
- Unify command line interface for all Uno tools.
Features
- Introduce process lifecycle based on living threads.
- Have Uno package support for the URE.
- Move the UCB into the URE.
- Move the configr mgr. into the URE.
- Uno alien type support e.g. for Java (e.g. a type description provider implemented in Java based on Java reflection).
- A Uno-SOAP Bridge.
- Allow (remote) proxy detection, needed for remote detection and optimizations.
- Zones.
- Write
man
pages. - Various IDE integrations.
- Allow connection parameters in environment descriptions for URP environments, e.g. "urp,socket=<port>,host=<name>".
Comments
How about type providers for Java Archive files, .NET assemblies?
That way, we can hold types the way that best fits, i.e. the target language of the component (→ no need to deploy both rdb and jar anymore). And this embraces the "*makers read from type manager/type providers" feature (→ I can generate types for lang A out of types from lang B without an intermediate format).
- This is basically what I meant with "alien type support" ~~kr