On Sun, Aug 5, 2018, 6:03 AM Rudi Hammad <rudiham...@gmail.com> wrote:
> Hi Cedric, thanks for sharing your thoughts. > > Before writing a plugin, I try to produce the same result using maya's > nodes. So I could distribute the rig without any plugins if I wanted, but > usually a c++ node, if done right, performs faster than 20 maya nodes > network. > Since I want to offer the best to the client, I think rigs with plugins > are not a bad idea. Also I find it more interesting from a learning point > of view, and you can't do everything with maya nodes. > > Now let me ask you something. Imagine that you spent a year developing a > muscle plugin system. So you spend a year studying math, anatomy and any > other useful resources to finally write your plugin from scratch. Would you > not consider that intellectual property? After all,muscles are not > original, we have maya cMuscles, Ziva muscles now etc...Also math is not > original. But any way, original or not, how would you approach that > situation? Would you simply distribute it without any kind of protection? > what if the client ask you to do one rig, and then he rips off the plugin > and do 20 rigs using it. or worst, what if the client and resell it? > Don't use that client again. Or sue the client for breaking your contract and reselling your technology? Consider other commercial applications that use a license key. What if the agreement is that a license is for one seat, but the company just installs it on 10 machines with that one key? It can happen. And a company probably worked very hard on that software. You are hoping to deal with reputable clients that want to pay you to support your products and not act like criminals. It's the same reason you don't put a snack into your pocket and walk out of the convenience store without paying, because it's easy. If everything you deliver is in C++ then you can at least make it harder to reuse unless some common hashes match between the plugin and the other custom nodes you write. > (Besides, I think protection methods is a very interesting subject on its > own.) > > Cheers, > R > > El sábado, 4 de agosto de 2018, 17:02:53 (UTC+2), Cedric Bazillou escribió: > >> Im not even sure if its worth the effort: >> >> lets be honest, rigging tool box or plugins are for the most part >> extremely elementary ( im not even sure how one can talk about intellectual >> property on something less than original, and for the most part inspired by >> community effort). >> Personally i think the rig is the result produced from some tool, so its >> not that important: its the way you get to the result which is valuable. >> >> Otherwise you can convert the rig to use factory nodes from maya:( much >> more difficult to decipher 12000 node network) >> if you dont want to distribute plugins you can unpack the code logic into >> regular nodes ( python have some good abstract syntax tree / ast module >> and the same concept exists for c++). >> > -- > 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 python_inside_maya+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/c0f6d7f4-10bb-4ddc-b1bb-9231afcb6fb3%40googlegroups.com > <https://groups.google.com/d/msgid/python_inside_maya/c0f6d7f4-10bb-4ddc-b1bb-9231afcb6fb3%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 python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0d0x-zQMpNvfp%3DyMrZAAX_zKGkAVY65c%2BfQrb6s6Fdew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
