Test and implement some suitable pre-initializing
task that would improve first-usage
responsiveness. For more details see also issue
28591 and
http://www.netbeans.org/servlets/ReadMsg?msgId=395924&listName=nbdev

This should also help to solve issue 27710.

I've already started some work in warmup_40 branch
and succeeded in decreasing time of first java
file opening by one half (from 4 seconds to 2).
You may see the task in:
/cvs/editor/src/org/netbeans/modules/editor/EditorWarmUpTask.java
/cvs/editor/src/org/netbeans/modules/editor/resources/layer.xml

However, this is just an experiment, with detailed
knowledge of the module I believe more effective
preinitialization could be done.

The most important problems of first usage (so
good candidates for preinitialization) are:
- classes loading (about 30% of whole time),
- loading settings (tried to solve by pre-creating
JavaKit),
- creating actions,
- initializing NavigationView and toolbar,
- etc.

Some realization problems:
- how to ensure most classes are loaded and
resolved without loading them explicitly one by
one by name,
- there is a big danger of deadlock, as the
preinitialization runs in separate thread in
different concurent conditions than normally (all
operations should be thread safe),
- the task itself should not run (or run very
quickly) if not needed (e.g. when IDE starts with
the editor opened).