Yes, if software is depending on API:s they have to keep pace with the API. Then I may not expect a solution to this issue as fast as the MultiEpg issue, which was solved within a couple of days only!
Well, basically it would be as easy as merging current changes into the OpenPLi git.
OpenWebif is still a very capable a user-friendly plugin even when the AutoTimer function only works as a browser.
Well, how to say it politely?
Progress isn't exactly what OpenPLi is into.
They prefer to take working code, rewrite it, after a phase where the new code doesn't work yet ending up with working code again.
If you are lucky it even produces the same result as before, just a little bit more complicated.
If they would develop cars, it would look like this:
Brand X has switched to aluminium wheels and OpenPLi could easily do the same.
Instead, they decide that aluminium wheels are crappy and too heavy (
Everything others do is crappy in their eyes, Vu+ devs are idiots, DM devs are idiots, oe-a devs are idiots, only OpenPLi devs can code properly and if it doesn't work it's the others that have to adopt to their solution, which will happen when hell freezes over).
So they work on their own type of wheels and experiment with different types of plastic. In the end, they have to accept that plastic doesn't offer the same stability as aluminium, but as they have already decided
not to go the aluminium way, they end up with plain old steel wheels plus wheel hub caps.
My decision has been not to disturb the OpenPLi pros anymore while waiting for the Vu+ idiots to fix their "crappy drivers" and other things that will never happen.