Issue 57291 - Performance: Native starter application
Summary: Performance: Native starter application
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-03 13:09 UTC by carsten.driesner
Modified: 2013-08-07 15:31 UTC (History)
4 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description carsten.driesner 2005-11-03 13:09:13 UTC 
We have two performance issues with the current solution:

1. Splash screen. The splash screen can only be displayed when the Office
process bootstraps UNO, initialized the configuration and VCL. These components
needs several different libraries which makes the splash screen performance

2. Double-clicking on a document starts a second Office instance. This also
needs some time as we have to bootstrap UNO and load several libraries.

The solution is to create a native starter application which is responsible to
show the splash and check if there is a running Office instance to pipe the
command line arguments. A native starter application is currently part of OOo
2.0 which restarts the Office after a crash, so we only need to enhance it.
Comment 1 carsten.driesner 2005-11-03 14:05:05 UTC 
cd: Started.
Comment 2 thorsten.ziehm 2006-01-13 14:22:13 UTC 
The CWS for this task is shifted to OOo2.0.3, therefore the tasks will be
retargeted too.
Comment 3 carsten.driesner 2006-05-15 15:31:39 UTC 
cd: Changed target to OOo 2.x.
Comment 4 Mathias_Bauer 2007-12-04 16:18:45 UTC 
according to release status meeting -> target 3.x
Comment 5 joergwartenberg 2008-08-23 20:17:42 UTC 
Any news? Will the CWS be ready for 3.1?