I remember long ago, i maya there where an web interface, where you could pass commands from the web browser, cant remember well, but was something like mel:// and your command.
That’s interesting! Looks like it’s still going. - http://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2015/ENU/Maya/files/Interface-overview-Install-the-Maya-Web-browser-plugin-htm.html Haven’t heard nor tried that, but I’ll have to give it a go. Is there any easy - open source -tool to do those “screen captures turned into gif” you usually post? I’m sure Google would have a better answer for you, but if you ain’t got Photoshop to do Save for Web.. then there’s also FFMpeg that can supposedly do similar things; although from what I gather you’ll need to first convert your videos to images and then to .gif. I have been using redis for my application communications. Hi Damon, thanks for sharing. Redis is a message queue/broker much like ZeroMQ and has similar advantages and disadvantages. One of the reasons not to go with ZeroMQ or Redis is their binary requirements - Redis requiring an externally running server and ZeroMQ requiring binaries especially compiled for Maya; per version of Python. What is nice is that it allows back and forth communications, not just 1-way.. Makes it so I am not completely stuck with just Maya’s versions of python and Qt. I can even execute commands in other open mayas on the network. That is quite useful, however the same is true for any type of inter-process communication; including HTTP calls. It’s called brokerless messaging <http://zeromq.org/whitepapers:brokerless>. To summarize; HTTP communication: - Supports bi-directional communication - Runs natively in any language that supports HTML; which includes Python, but also JS and C# and so on. Whereas a message queue requires an initial setup, and in the case of Redis, a central broker. I may even be so bold as to claim that the only real benefit of an MQ is performance; however as Python is only capable of producing a certain amount of information per second, that benefit may never actually surface. Thoughts? It sounds like the RESTful interface would serve a very specific purpose as opposed to a more open solution. I’d love for you to elaborate on this. What does “open” mean, if not standardized HTTP calls following a widely used architectural pattern like REST? And in what way does it strike you as specific? Thanks again! Best, Marcus -- 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/CAFRtmOA6Lde7ce63zRxLdfF%2BV3O9rfAMnoxmA%3D2Bt65pvuCJ8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
