Difference between revisions of "Uno/To-Dos"

From Apache OpenOffice Wiki
< Uno
Jump to: navigation, search
m (Wording, added some links.)
Line 1: Line 1:
−
ToDos and potential ToDos
+
== ToDos and potential ToDos ==
  
−
module naming
+
Clear separation between C and C++
−
* rename cppu -> binary uno
+
* Move C++ stuff from cppu to cppuhelper.
−
* rename cppuhelper -> cppu
+
  
−
clear separation between C and C++
+
Module naming clean up
−
* move C++ stuff from cppu to cppuhelper
+
* 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]].
  
−
simplification / performance
+
Simplification and Performance
−
* remove <code>uno_Interface</code> and friends, replace 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 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 "remote" and libraries, it is actually the same
+
* Harmonize initial object access for [[Uno/Remote | Remote Uno]] and components -> it is actually the same.
−
* leverage purpose environments for global variables, e.g. the "ServiceManager" or the "ComponentContext"
+
* Leverage protocol bridges for global variables, e.g. the "ServiceManager" or the "ComponentContext".
 
* Remove all exception specifications.
 
* Remove all exception specifications.
−
* Consolidate "uno_Environment" with "uno_ExtEnvironment".
+
* Consolidate the [[Uno/Binary | Binary Uno]] structs "uno_Environment" and "uno_ExtEnvironment".
−
* remove "#ifndef EXCEPTIONS_OFF" macros
+
* Remove <code>#ifndef EXCEPTIONS_OFF</code> macros, actually [[Uno/Cpp | C++ Uno]] is not useable without exceptions anyway.
−
* SAL_CALL really necessary for "inline" stuff?
+
* Is SAL_CALL really necessary for "inline" stuff? If not, remove it.
−
* a unified 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 URE
+
* Have Uno package support for the [[Uno/Spec/Ure | URE]].
−
* move the UCB into the URE
+
* Move the UCB into the URE.
−
* move the configr mgr. into the URE
+
* Move the configr mgr. into the URE.
−
* 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).
−
* web services bridge
+
* A Uno-SOAP Bridge.
−
* (remote) proxy detection - needed for remote detection and local optimizations
+
* Allow (remote) proxy detection, needed for remote detection and optimizations.
−
* Zones
+
* Zones.
−
* man pages
+
* Write <code>man</code> pages.
−
* various IDE integrations
+
* Various IDE integrations.
−
* connection parameters in environment descriptions for URP environments
+
* Allow connection parameters in environment descriptions for [[Uno/Remote/Spec/URP | URP]] environments, e.g. "urp,socket=<port>,host=<name>".
 +
 
  
  

Revision as of 11:51, 21 April 2006

ToDos and potential ToDos

Clear separation between C and C++

  • Move C++ stuff from cppu to cppuhelper.

Module naming clean up

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
Retrieved from "https://wiki.openoffice.org/w/index.php?title=Uno/To-Dos&oldid=8867"
Personal tools