Hi Joerg,
Joerg Budischewski wrote:
I am actually also not sure, whether this belongs in a core api. This
function is a nice helper for starting to program with the office but it
hides too much away imho ( if the office process cannot be reached, the
function loops endlessly, it always an office process even when an
office is running, etc.) to be used in a professional application.
that bootstrap currently starts an office process is an implementation
detail only. Actually we chose the wrong name for it, when we
implemented it. The right name would have been something like
Reference<XComponentContext> getComponentContext();
The semantics are, that this function returns the systems (which could
be a process, a user, a host, a LAN, a WAN, ...) component context.
The height of the abstraction allows us, to basically implement /
optimize everything behind the scenes, while providing a compelling and
simple to use interface for developers.
In my understanding, especially "professional" developers want to mostly
deal with the customers problem, and less with nasty API details.
Bye,
Joerg
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
