Feature #4417
features to allow direct usage of _progres (and related executables) to be supported in FWD
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
version_reported:
version_resolved:
History
#1 Updated by Greg Shah over 4 years ago
Customers use _progres
(and other related executables) to launch 4GL sessions. oday, in each project a task must be executed to find these and replace this usage with the ClientDriver
.
We could automatically handle this in the following way:
- Create our own launcher binaries (with the same names) which parse the command line and map this into
ClientDriver
invocations. This will handle shell scripts/batch programs and even desktop shortcuts. - During processing of OS-COMMAND (and other shell commands) detect invocations of
_progres
etc... and map that to a launch ofClientDriver
. We already do something similar to this withquoter
.