ewerybody
12-04-2008, 01:30 AM
Now I know there have been some ideas about installers for mel scripts but... just have a look at that: I like it! :]
http://img135.imageshack.us/img135/9779/meldropzr2.jpg (http://vimeo.com/2404942)
( its still not possible to actually embedd videos here huh? ;] )
So melDrop is a tool to help installing other tools. Let the user install melDrop and he can drop scripts like that. No more exploring, hacking, browsing.. just:0. get melDrop (http://www.highend3d.com/f/5514.html), open zip, drop it into Maya (only once)
1. get a new script in a zip (e.g. melDropEnabler (http://www.highend3d.com/f/5516.html), resetPivot (http://www.highend3d.com/f/2881.html)...)
2. drag & drop all files into the Maya viewport
3. click ok ok ...
thats it! It can:
copy the script and an icon file (to userScriptDir/userBitmapsDir)
create shelfButton
setup Hotkey
make the script run on Maya startup
all optionally.
Ok. It does not support just any script out of the box. melDrop needs to know what to do.
But you can really simply compile a nice zip package with melDropEnabler (http://www.highend3d.com/f/5516.html).:
http://img229.imageshack.us/img229/6743/meldropenabler0hr7.jpg
all features of melDrop can be easily set up with it.
The zip feature is actually the one I like the most :] Its very convenient if you like to publish a script. And it really doesn't touch your file at all.
On the other hand: The enabler can also write the melDrop-call to the file directly which is useful for a script repository in a LAN e.g.
To be honest: You may have seen that I posted the problems it has directly at the highend upload. I know this is not perfect.:
writes to userScriptDir ONLY
supports ONLY one script file (which is not so bad I think)
supports ONLY one icon file (this is worse!)
proc name is called without arguments ONLY (on created hotkeys and shelfButtons)
no python support yet
Ah and not to forget about the Maya behaviours:
Maya throws an Error on dropping a .txt file
Maya > 7 opens up fcheck on dropping an .xpm
Does someone know how to prevent Maya from nagging about that and opening fcheck completely useless? I mean, I could tell the user to select only the .mel-files BUT: icons wouldn't be extracted that way and its more convenient to just select all (ctrl+a) instead of specific stuff.
Besides that its already a really easy to use thing. And I think all in all it already covers 95% of my needs so far.
However I really like to read what you think about it.
Would you use it?
What are your concerns? ideas? critics? and even bugs! :D
Oh! One further addendum: scripts can be fetched here:
melDrop - http://www.highend3d.com/f/5514.html (http://www.highend3d.com/f/5514.html)
melDropEnabler - http://www.highend3d.com/f/5516.html (http://www.highend3d.com/f/5516.html)
have fun:buttrock:
http://img135.imageshack.us/img135/9779/meldropzr2.jpg (http://vimeo.com/2404942)
( its still not possible to actually embedd videos here huh? ;] )
So melDrop is a tool to help installing other tools. Let the user install melDrop and he can drop scripts like that. No more exploring, hacking, browsing.. just:0. get melDrop (http://www.highend3d.com/f/5514.html), open zip, drop it into Maya (only once)
1. get a new script in a zip (e.g. melDropEnabler (http://www.highend3d.com/f/5516.html), resetPivot (http://www.highend3d.com/f/2881.html)...)
2. drag & drop all files into the Maya viewport
3. click ok ok ...
thats it! It can:
copy the script and an icon file (to userScriptDir/userBitmapsDir)
create shelfButton
setup Hotkey
make the script run on Maya startup
all optionally.
Ok. It does not support just any script out of the box. melDrop needs to know what to do.
But you can really simply compile a nice zip package with melDropEnabler (http://www.highend3d.com/f/5516.html).:
http://img229.imageshack.us/img229/6743/meldropenabler0hr7.jpg
all features of melDrop can be easily set up with it.
The zip feature is actually the one I like the most :] Its very convenient if you like to publish a script. And it really doesn't touch your file at all.
On the other hand: The enabler can also write the melDrop-call to the file directly which is useful for a script repository in a LAN e.g.
To be honest: You may have seen that I posted the problems it has directly at the highend upload. I know this is not perfect.:
writes to userScriptDir ONLY
supports ONLY one script file (which is not so bad I think)
supports ONLY one icon file (this is worse!)
proc name is called without arguments ONLY (on created hotkeys and shelfButtons)
no python support yet
Ah and not to forget about the Maya behaviours:
Maya throws an Error on dropping a .txt file
Maya > 7 opens up fcheck on dropping an .xpm
Does someone know how to prevent Maya from nagging about that and opening fcheck completely useless? I mean, I could tell the user to select only the .mel-files BUT: icons wouldn't be extracted that way and its more convenient to just select all (ctrl+a) instead of specific stuff.
Besides that its already a really easy to use thing. And I think all in all it already covers 95% of my needs so far.
However I really like to read what you think about it.
Would you use it?
What are your concerns? ideas? critics? and even bugs! :D
Oh! One further addendum: scripts can be fetched here:
melDrop - http://www.highend3d.com/f/5514.html (http://www.highend3d.com/f/5514.html)
melDropEnabler - http://www.highend3d.com/f/5516.html (http://www.highend3d.com/f/5516.html)
have fun:buttrock:
