Peter Wislander wrote:
> I just automated everything against the UI. It was a hell considering all the fcuked up generated id's, but works now. Took me 2 days.
I am also not to thrilled by the hash id's, but they have a purpose and can be useful. But a relational database probably would be better.
> But I just can't believe that somehow it's assumed that everything should be done by manually clicking. The webgui should be like the last feature to implement and dropping config files should be the first thing to implement.
The config files are implemented, but the JSON has been converted to binary and compressed for performance reasons. But as noted before, the lack of user direct access to the config files needs to be addressed. In the meantime, the other thread I linked to shows how to go back to human readable config files.
> How are you guys even managing to use tvheadend?
>
> All mouse clicking? Jeeezus. RSI 3.0.
My setup is quite simple, so between the automatic detection capabilities and a few mouse clicks I am configured. But I recognize that more complex configurations are not so easy using just the web gui. If you look through the forum you will find users who have created scripts/progs to work directly with the config files or through the HTTP/HTSP interface API. Unfortunately the APIs are not well documented, but you can look in src/api for hints.
