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

Web-UI for LCDproc? #2795

Open
markus2330 opened this issue Jun 18, 2019 · 9 comments

Comments

Projects
None yet
3 participants
@markus2330
Copy link
Contributor

commented Jun 18, 2019

@haraldg: as now someone will again work on the Web-UI and reimplement the service on the device with Go: Is it a relevant use case that people want to configure their device with a Web-UI?

@markus2330 markus2330 added the question label Jun 18, 2019

@haraldg

This comment has been minimized.

Copy link

commented Jun 18, 2019

I don't really know. I think your Web-UI is probably not really useful for OpenWRT systems (though there are some fairly powerful systems running with OpenWRT these days, so who knows?) and on non-embedded systems there probably is some way to edit configuration, that is prefered over Web-UIs. OTOH lot's of people seem to use LCDproc on headless BSD servers. Maybe they would like it?

Does there actually depend something on the answer to the question?

@markus2330

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2019

Thank you for the quick answer!

Does there actually depend something on the answer to the question?

Yes, if the student should actually try it out (if the Web-UI works with LCDproc) as case study.

@haraldg

This comment has been minimized.

Copy link

commented Jun 18, 2019

@kodebach

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2019

I don't know what this person is interested in, but maybe a proper terminal UI would also be an option.
There seems to be good library support for go there is even some high level stuff.

@markus2330

This comment has been minimized.

Copy link
Contributor Author

commented Jun 19, 2019

Then feel free to ask on the ML whether there is interest.

I would like to avoid to ask such questions as long as the basics are not working properly.

I don't know what this person is interested in, but maybe a proper terminal UI would also be an option.

I do not know if @raphi011 is interested in this but this would be a separate work. I do not see how the Web-UI could be reused there.

But in general a terminal UI would be definitely nice for some tasks. But compared to Web-UI and kdb editor I think there is a rather limited group of people who are interested. Which does not mean we shouldn't implement it in the long term.

@kodebach for LCDproc a minimal ckdb which uses the high-level API could be also more interesting (if someone wants to run Elektra completely without C++).

@kodebach

This comment has been minimized.

Copy link
Contributor

commented Jun 19, 2019

I do not see how the Web-UI could be reused there

No of course it couldn't, it just occurred to me because of the connection to Go.

@kodebach

This comment has been minimized.

Copy link
Contributor

commented Jun 19, 2019

minimal ckdb which uses the high-level API could be also more interesting

The high-level API is absolutely not suited for such a tool. Where would the defaults and the type metadata come from? Would it only work for the parts of the KDB that have a spec mounted? How would you mount that spec? Mounting right now relies heavily on C++ so we could get avoid having kdb anyway.

@markus2330

This comment has been minimized.

Copy link
Contributor Author

commented Jun 19, 2019

It should work for the config of LCDproc?

@kodebach

This comment has been minimized.

Copy link
Contributor

commented Jun 19, 2019

A tool exclusively for LCDproc seems like a bad idea. Also you would still need C++ for mounting, unless somebody rewrites the code for that.

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