Thanks for the discussion everybody! I see now that I ofcourse the uic process is probably expecting the output file of pyside-rcc.
Unfortunately I won't be able to test this until later this week, but I will definitely post an update on the 'situation'. *@Marcus*; I personally don't experience this workflow as 'jumping through hoops'. Instead it makes for some genuinely RAPID prototyping when it comes to changing up the UI. It's just that my process right now is heavily leaning on QtDesigner doing the lifting. Implementing the images in there automatically means getting involved with a qrc file. I'm not sure yet if I would be able to just leave out the images in QtDesigner and hook 'm up to the UI that's being generated at runtime. Although I'm certainly expecting that this will be possible, it's not the route I'm preferring to take. Also, the deployment Justin wrote: *Maybe that boilerplate thing can be extended to suit your workflow and detect and perform the rcc at runtime before the uic happens. This would not be suitable for production, since it would be slower, and still require all the images to be present and the pathing to be correct. But it could at least suit the prototyping workflow you have chosen.* *@Justin: *Yeah, ideally it would only be for prototyping. Seeing as I just recently started as a Jr. TD, I'm still trying to figure out a lot of stuff. This is one of those things. Deployment would, ideally imho, only consist of *main.py + main.ui + main.qrc (in one form or another). *Do I understand correctly that you always compile the ui-file and qrc-file both? (While implementing the result of the pysideuic in directly into the main.py & NOT load the UI file at runtime?) Thanks again for everybody's time and input, really insightful! *EDIT: Sorry for the double post yesterday. This google-groups thing is very unlike other boards online.* -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/752df3dd-10e8-4573-a03e-2e5cecdd2443%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
