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

Next steps in LCDproc #3041

Open
markus2330 opened this issue Oct 7, 2019 · 3 comments

Comments

@markus2330
Copy link
Contributor

commented Oct 7, 2019

@kodebach wrote in #2815:

  • Using the ini plugin doesn't work, because of the multiline description metakeys. (I switched to ni for now, but its file format is not ideal).
  • Parts of the specifications are still commented out because of the max plugins issue.
  • Not all drivers are updated. The specification is based on the old example LCDd.conf; not all config keys for drivers are included. The updated drivers have a full specification.
  • Once all drivers are updated, the rather big specification for LCDd will probably slow down the server start-up time as well as any (cascading) kdb operation that calls the spec plugin on the relevant mountpoint. Dynamically enabling/disabling parts of the specification would be nice, although I don't see any way to do this right now.
  • Improving the spec plugin performance would also be nice, but again, I don't know how.
  • Various known issues with the kdb tool that make using it hard. Especially the fact that kdb set -N user <cascading-key>, may result in a broken configuration (because of the origvalue metadata).
@markus2330

This comment has been minimized.

Copy link
Contributor Author

commented Oct 7, 2019

Using the ini plugin doesn't work, because of the multiline description metakeys. (I switched to ni for now, but its file format is not ideal).

@bauhaus93 is working on it with the new TOML format

Parts of the specifications are still commented out because of the max plugins issue.

@vLesk is working on it

Not all drivers are updated. The specification is based on the old example LCDd.conf; not all config keys for drivers are included. The updated drivers have a full specification.

Yes, some more drivers would be nice, @bauhaus93 said he will add support for one driver.

Various known issues with the kdb tool that make using it hard. Especially the fact that kdb set -N user , may result in a broken configuration (because of the origvalue metadata).

@kodebach Which is the issue number for this?

@markus2330 markus2330 changed the title Problems in LCDproc Next steps in LCDproc Oct 7, 2019
@kodebach

This comment has been minimized.

Copy link
Contributor

commented Oct 7, 2019

Yes, some more drivers would be nice, @bauhaus93 said he will add support for one driver.

Adding new drivers is not much of a problem. It's quite straight forward, I also wrote instructions for it. The problem is more testing everything still works.

Which is the issue number for this?

[EDIT by @markus2330, moved to #3056]

@markus2330

This comment has been minimized.

Copy link
Contributor Author

commented Oct 11, 2019

Adding new drivers is not much of a problem. It's quite straight forward, I also wrote instructions for it. The problem is more testing everything still works.

As discussed with @haraldg this will be mostly community effort.

I have not yet investigated, where the origvalue metakey even comes from, as it should be removed by keySetString

Moved to #3056.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.