The core is currently generating screens for it. I thought this would no longer be necessary? Or is that my mistake?

It'd be cool if the whole orbiter generation thing wasn't needed any more, just be told the layout and render it on the device.

David.

Well this is one quandry. QOrbiter doesnt need the core to generate screens, but because its an orbiter, code deeper in the system flags is for a regen. You can generally ignore the request to regen the orbiter screens if you know its wanting to do it for a QOrbiter as it does its own orbiter generation, which is a lot faster. Looking to get rid of the message, but its one of those things that falls under details atm and not core functionality.

-golgoj4

Logged

Linuxmce - Where everyone is never wrong, but we are always behind xbmc in the media / ui department.

I do web based dev in my day job, java on the server and lots of javascript type stuff on the clients (including a fair amount of GUI design)

My C++ is pretty ropey, I think I'd just cause problems, but I'm willing to help out there if its wanted (probably as QA/ tester)

I'm probably best off looking into the QML/ design aspects I think.

I can probably do some system tech documentation as well if you'd like (I can read C++ well enough for that)

David.

No worries, we need folks to take a look at my superbad qml to look for ways to improve it / abstract things so that multiple skins can interact effectively. Currently, the skinning engine seems to be holding up, but im sure there is room for improvement. My recommendation would be to play around with qml and get to know it. There is still the rather large task of documenting the skinning api so that we can provide skin designers with an document that shows the various functions available and how to interact with them.

-golgoj4

Logged

Linuxmce - Where everyone is never wrong, but we are always behind xbmc in the media / ui department.

No worries, we need folks to take a look at my superbad qml to look for ways to improve it / abstract things so that multiple skins can interact effectively. Currently, the skinning engine seems to be holding up, but im sure there is room for improvement. My recommendation would be to play around with qml and get to know it. There is still the rather large task of documenting the skinning api so that we can provide skin designers with an document that shows the various functions available and how to interact with them.

-golgoj4

Grand. I've got thursday/ friday mostly free this week, so I'll spend some time then do that.