I probably should have posted this some time ago, but the reality of the situation is that I have no idea when I'll get back to the Maya/Qt materials. I haven't done any further work with Qt at Reel FX since I initially wrote about it. Part of that is because our current projects are all using Maya 2010, but the biggest issue is that the majority of the Maya tools that I develop at Reel FX need to work both in-house and for our ever-morphing collection of remote animators.
While the crew at the studio have set up an efficient Maya/Qt workflow for internal use, setting up a home system to get Maya and Qt talking nicely appears to be a bit of a chore (to put it mildly). It's tricky enough troubleshooting the problems that remote animators sometimes encounter while setting up their systems to work with our pipeline and tools. Putting them through Qt setup process on top of that would be asking a bit too much.
Once we have a project that will use Maya 2011 and I dive back into Qt work, I may bring this back up, but the remote situation is the key factor. Without a way to ensure that our remote artists can *easily* get the same Qt UI results that we do, it's not worth the development effort.
1 comment:
That's a shame! I was enjoying those posts. And I'm personally going to be moving from 2010 to 2011 / 2012 shortly, so PyQt is coming up on me quickly.
I hope you get back to it soon!
Post a Comment