Reported by heikofolkerts on 2014-08-02 19:18
Applications written in interpreted languages such as java applications use a kind of player when being run. So java aplications are all identified by javaw.exe or java.exe from NVDA. Since the applications ,may need very different and conflicting tweaks from an app module one cannot put the code for different applications in one app module.

Here is a proposal how this could be supported:

1. an app module for the application player like javaw.exe or python.exe is loaded every time NVDA sees an java or python application. thius is the current and standard behaviour of NVDA.
2. the application player app module can then forward the application support to a specific app module. 'To do so it must identify the application for which it was loaded. It can try to get the command line for the process ID. This is at least possible with VBA and should hopefully also be possible in python. The identification of an application from its process ID should be done from the application player's app module since the parsing of the command lines will be different for the players.

In case of java one would have to extract the package and class name of the main class that was given on the command line. In case of a python application one would need to identify the name of the main python file.

The support for example java applications is crucial for situations where a user would have to work with more than one java application and an specific application module willb be needed for one or more of them. In case of java applications this can happen quite often since keyboard support in those applications is usually very poor.

Blocked by #4556
Blocking #4454, #4569