Did uplink_ not like qOrbiter?
That's a tame response. Expected something more... fiery.
Well... I couldn't find the beginning of it
Also, didn't have the time. On the other hand, the thing that Andy filmed will probably never control LinuxMCE or LinuxMCE-based Dianemo, so don't view it as "competition" (yet). It's following different patterns of thought that are not easily adapted to current Orbiter logic. I would have showed you a media browser sample too, but I broke it yesterday while working on some grid stuff.
Consider this part of the "rewrite" that people keep moaning about but don't leave their cozy couch to actually do it or learn how to do it (kudos to golgoj4 for actually doing it in the form of qOrbiter).
On the other hand, I'm just finding out that GUI programming isn't easy if you're not doing run of the mill business logic
I wrote a Message Router in a day (it's pretty useless right now: only forwards messages around, without any cleverness, and nothing to actually send and receive messages yet, except some crude test code), but the GUI requires me to pause and think a lot. So far, what Andy filmed has 638 lines of Python code, 251 lines of YAML for the screen definitions, and 147 lines of YAML for the mock data, and I can feel that I slipped in some places, so I need to go back and do it properly (i.e. in a way that doesn't hurt my own brain). I don't have proper data bindings yet, nor message communication. The file itself is aptly named Mockup.py