Difference between revisions of "Uno/To-Dos"
From Apache OpenOffice Wiki
< Uno
m (Wording, added some links.) |
m (Added category.) |
||
Line 42: | Line 42: | ||
:This is basically what I meant with "alien type support" ~~[[kr]] | :This is basically what I meant with "alien type support" ~~[[kr]] | ||
+ | |||
+ | [[Category:Uno]] |
Revision as of 11:52, 21 April 2006
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