Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-design the nxagent dialog callbacks #387

Open
wants to merge 7 commits into
base: 3.6.x
Choose a base branch
from

Conversation

sunweaver
Copy link
Member

This PR will provide a new and more generic implementation of the NXTransDialog callbacks.

Currently W-i-P...

@sunweaver sunweaver self-assigned this Mar 7, 2017
@sunweaver sunweaver added this to the 3.6.1.0 milestone Mar 7, 2017
  pkg-config --libs zlib in Debian jessie returns buggy linker parameters. It
  includes the system's default multi-arch path for shared libs.

  When linking nxagent, having the system's default shared library path
  explicitly listed as a "-L" linker option confuses linking against the
  libXcomp*.so files in the build path.

  When linking nxagent, we don't want to link against the system's
  libXcomp*.so files, we want it to get linked explicitly against
  the just built libXcomp*.so files in nxcomp/ and nxcompshad/.

  This change assumes that -lzlib is always available in the system's
  default shared library path.
… components get mentioned first in the nxagent linker command.
…11/exports/lib when linking nxagent. As -L../../exports/lib is already present and points to the same location.
…cksDispatcher.

  - As a starting point for newly implementing a callbacks dispatcher
    scenario that allows for capturing various session events and executing
    external tools (like dialog boxes, pulldown menus, etc.).
  - The callbacks dispatcher approach will finally deprecate the NX_CLIENT
    env var related code path in later releases of nxcomp/nxagent.

 In the nxagent binary:
 For now, the callbacks dispatcher code path is taken if the env var
 NX_CALLBACKS_DISPATCHER is set to an application that handles
 the dispatching of callbacks from nxagent.

 in /usr{/local}/bin/nxagent:
 If NX_CALLBACKS_DISPATCHER is an empty string, callbacks are disabled.

 If NX_CALLBACKS_DISPATCHER is unset and the dispatcher command
 /usr/{local/}{<multiarch>/]nx/bin/nxagent-callbacks-dispatcher cannot be
 found, nxagent falls back to its old NX_CLIENT related code path.
…ispatcher exists in the system's PATH, use this script's full path to set NX_CALLBACKS_DISPATCHER env var.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant