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

Screenpath is overloaded #31

Closed
slominskir opened this issue Dec 20, 2021 · 1 comment
Closed

Screenpath is overloaded #31

slominskir opened this issue Dec 20, 2021 · 1 comment
Labels
question Further information is requested

Comments

@slominskir
Copy link
Member

slominskir commented Dec 20, 2021

Currently screenpath field often contains one of four things:

  1. Absolute file system path to EDM file
  2. Human instructions for navigating JMenu (using Unicode arrow characters)
  3. On-the-fly (OTF) Screen Generator command
  4. EDMRun command (optionally with macros)

Do we want to keep a single field, or should we break this into multiple fields? For example it may be useful for both Human JMenu instructions and programmatic path.

Note: Other things to consider include:

  1. Read-only web view of EDM screens are available too, but at a URL, not filesystem path.
  2. Some EDM screens are network mounted in various different places making path aliases or host-dependent.
@slominskir slominskir added the question Further information is requested label Dec 20, 2021
@slominskir
Copy link
Member Author

Using instance-level "screencommand"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant