2014-02-02, 22:31
Setup is the biggest hurdle right now in XBMC for the visually impaired. Most of the interface can be accessed with a remote UI, ether from the web or from some other remote application, but settings is almost entirely inaccessible though these methods.
Then, as byron27 said, other interface elements are not currently communicated to remote UIs, such as pop-up windows. XBMC's windowing system is non-standard, in order to work cross-platform and due to the legacy code that it is built upon.
I think expanding the remote APIs for remote applications, to handle settings and full interface interaction, is the best way forward. It's also the most likely method to be taken up by a developer, as expanding those APIs has vast uses in many directions. It would basically work as a "drop-in" interface, so in the future XBMC could be ran without the "normal" UI, and instead be completely ran from alternative UIs, while still having the core features be consistent.
Then, as byron27 said, other interface elements are not currently communicated to remote UIs, such as pop-up windows. XBMC's windowing system is non-standard, in order to work cross-platform and due to the legacy code that it is built upon.
I think expanding the remote APIs for remote applications, to handle settings and full interface interaction, is the best way forward. It's also the most likely method to be taken up by a developer, as expanding those APIs has vast uses in many directions. It would basically work as a "drop-in" interface, so in the future XBMC could be ran without the "normal" UI, and instead be completely ran from alternative UIs, while still having the core features be consistent.
