As the first one (that I know of) to suggest that this feature be implemented only in the Web UI, I fully stand behind that suggestion, and I think it’s a fabulous way to implement more advanced functionality not related to playback.
I think the core functionality of browsing the guide, recording, and playing back should be available and as consistent as possible across all platforms. But I think it’s perfectly reasonable and beneficial for more advanced functionality, especially things that would only need to be done in limited situations.
Several reasons for this:
- Just about EVERYONE can access the web interface.
- It’s far easier to implement changes on a single platform than on EVERY platform (especially as the number of platforms expands). Given the slow speed at which features have been added in the past, I think this provides a great opportunity to get some of our long-requested features added.
- The other platforms can get klunky if too many features are added since they are generally operated by a remote control. A web UI can be much more complex since it’s usually controlled by keyboard and/or mouse.
- Many devices can only have advanced features set through a web interface.
I hope the Tablo project managers and developers have enough sense to realize how beneficial a web-only advanced interface would be.