Mel Expert Advice Is Needed Here!

http://www.highend3d.com/bookstore/maya/Ad...ghting-182.html

My Maya Dual Monitor script is featured in "Advanced Maya Texturing and Lighting" a new book out featured here on highend3d.com. I believe it's still in it's early stages. I would really like to incorporate the Attribute Editor into the paneLayout if at all possible. I'm not a polished scripter by any means, just have put a lot of hours in while working in the feild and found a need to develop a secondary interface for Maya on my 2nd monitor.

If anyone could run the script and look at the code and make some suggestions on how to incorporate the AE in there some how I would be greatly appreciative. This has been a script that many people use on a daily basis to simply and maximize some of Maya's functions.

CLIK HERE FOR THE .mel and screenshots http://www.mikestolworthy.com/mdm/

http://www.mikestolworthy.com/mdm/

First off, I have not looked closely at your script. I tried to create an AE embedded in a panel about 3 months ago, and it was such a pain that I decided to dump that idea. I can't remember how far I got, but there were so many little details to take care of that it was not worth the effort (at least for me).

So, it should be possible to do it (after all you can "Copy Tab" to get a standalone AE), but it is not a trivial thing to do.

Basically all the stuff required to build an AE is in C:\App\Maya6.0\scripts\others\showEditor.mel


Duplicating the channelbox is a lot easier, so you might consider placing the channelbox in your secondary window, so the channelbox and the AE can be displayed together which sometimes is a very handy thing to be able do.

Thanks for the advice! I have screenshots here now. I have a tabLayout included inside the paneLayout and I have the
"channel box" and the "outliner" worked in, which proved to be a fun little pain to accomplish but still having trouble with the AE integration. I had a guy download my script from here and he said that he had put an AE in the window then he refused to share his secret with me and they use it at work with their team. Shady deal as far as I'm concerned. Why would anyone be selfish with MEL....... it's free. and it helps everybody out.

Still looking for a solution, or creative ideas to make this a much more robust side dish. Most of the Professionals in the work place can't live without a second monitor, running Photoshop and other software side by side. This is one of those scripts that if given the right amount of TLC could be a great addition to anyones work flow.

THANKS FOR ANYONE WILLING TO HELP! It's all for the improvent of everyone wanting more from theirsoftware.

QUOTE(IAOY @ 04/14/07, 09:48 PM) [snapback]264094[/snapback]
Why would anyone be selfish with MEL....... it's free. and it helps everybody out.

well, thing is theres some arms race involved. Also its not free to write the mel. But mostly it can be a contractual thing. if you work in a company you may find your mel is owned by the company.

Thats right. If that guy did the extra MEL development in a production environment (sounds like he did), then his hands are likely tied by his boss. If the work was done on company time, chances are the company owns the IP.

neX:)

Ok I understand that part. Maybe that might be the case, but nevertheless it seems a little unjust.

Anyhow, outside the workplace like here at highend3d I was hoping to get some interested individuals that could evaluate the MDM WINOW script and give me feed back on how I could possibly tailor it to others people's needs besides my own. On my own time for nothing in return other than the satisfaction that I have maybe made someone's job a little more streamlined and effecient. Just wanting to contribute to the Maya community.

-MS

well yes, you should prepend a license grant similar to gpl to your code that way any modifications to it will always stay license free, However that still does not stop people from committing the changes back. But this would kind of absolve the secondary author from the dillema.

Anyway doing the same code 2 times is still contractually fishy since the original code owner might still dispute it.