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

Feature suggestion: pvxget and pvxmonitor could use more output options #66

Open
drm-slac opened this issue Mar 20, 2024 · 3 comments
Open

Comments

@drm-slac
Copy link

Output options for pvxget and pvxmonitor aren't as mature as caget/camonitor, including numeric formatting and more. This request is also being made of pvget/pvmonitor.

@mdavidsaver
Copy link
Member

Keeping the pvx* CLI tools "simple" so far is a deliberate decision on my part to maintain a "green field" until someone has time/effort to spec. out a reasonable (and testable) interface.

@chrisalguerrero
Copy link

What are the requirements for a reasonable interface? Does anyone know if there are any missing output options for the command line tools?

@mdavidsaver
Copy link
Member

What are the requirements for a reasonable interface? ...

To my mind, step one of making pvx* friendlier will be designing such an interface. Both the arguments, behaviors, and output format(s).

In parallel, step "zero" should be extending unit-test coverage to the CLI tools. As I am (slowly) starting with #78.

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

No branches or pull requests

3 participants