To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=60696
User hro changed the following:
What |Old value |New value
================================================================================
CC|'cd,cmc,joergwartenberg,ke|'cd,cmc,joergwartenberg,ke
|ndy,mba,pl,st' |ndy,kso,mba,pl,st'
--------------------------------------------------------------------------------
Target milestone|OOo 2.x |OOo 2.4
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu May 31 15:07:10 +0000
2007 -------
Setting the target for 2.4 at least.
I really really want this feature but I'm not sure whether it can be realized
within 2.3 time line.
Performance is not only the startup time until the user can work with OOo but
the time until he get's the first UI feedback. For a desktop application quick
responsivenesses is as important as pure performance.
There are several design issues that have to be addressed beside the simple task
of implementing a working splashscreen along with a native pipe connection.
The key is creating the right pipename based on the right variables which depend
on the scenario where OOo is used.
My quick suggestions:
Desktop scenario pipe name = System User ID + Program Installation Path +
Normalized Display/Session (no need for bootstrap variable resolution)
For other scenarios the pipename may be constructed by
SystemUserID + UserInstallation Path + some context information.
I'd like to look at the design from a more abstract view: Given a scenario for
OOo - what information is needed to find the intended running process to connect
to ?
So first I want to collect all scenarios:
- OOo as single user/multi user desktop office suite
- OOo as UI-less server
- OOo as a plugin in other applications
- ...
@kso: Need some input about the possible scenarios and what is intended how OOo
should behave from an abstract point of view regardless of any currently
implemented bootstrap mechanism.
@mmeeks: Taking your patch and what is in my mind I guess I'll have to change
design a little bit. But the "core implementation" stuff of your patch seems to
be usable.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
