On Wed, 9 Sep 2015 1:07 AM Nico Klaassen <[email protected]> wrote:
... 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?) Back when I *was* using Designer, my preference was always to compile ui/qrc files ahead of time, and only deploy: main.py + main_UI.py + main_rc.py Nowadays since I don't use designer, I just deploy python with hand written UI code, and optionally an rc python file, if I have static resources and it makes sense to do so. Marcus, is correct that you have the option to ditch the rc and set the image paths directly in your code. And I understand that you are, at this time, choosing to do it up front in Designer so that you can have visual feedback while you design. If you do that, as we have established, you will need to convert it before runtime. If you choose to not do images in Designer, then you now have the option of whether using an rc file makes sense to you and can either use direct paths in code, or a hand written qrc. 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 <https://groups.google.com/d/msgid/python_inside_maya/752df3dd-10e8-4573-a03e-2e5cecdd2443%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- 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/CAPGFgA31GLKKAWjdOXM627YuzP_e%3DzhvsLiDXV7Pj%2Bz5Q8H-NA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
