Mod Tool: Difference between revisions

325 bytes added ,  14 September 2012
m
one step away from addon creation?
mNo edit summary
m (one step away from addon creation?)
Line 49: Line 49:
'''[http://softimage.wiki.softimage.com/sdkdocs/cus_addons_WalkthroughBuildinganAddon.htm building .xsiaddon]'''
'''[http://softimage.wiki.softimage.com/sdkdocs/cus_addons_WalkthroughBuildinganAddon.htm building .xsiaddon]'''
* So far building an addon file seems to be the most difficult among those 'extension' files but for the end user it's best because it can hold all other files: toolbars, plugins, etc.
* So far building an addon file seems to be the most difficult among those 'extension' files but for the end user it's best because it can hold all other files: toolbars, plugins, etc.
'''new notes [in progress]'''
* so, simply putting scripts into folders didn't worked, they must be "plugins" (file extension is the same e.g. vbs but they do also something else)
* a script can run on anther computer if its content is found under a command, and plugin register that new command(s)
* [...]
'''old notes'''
** It Seems not to work with script file (but embedded code does), the [http://xsisupport.com/2012/04/30/packaging-toolbars-and-script-commands-into-addons/ alternate method] (File > Add-On > Package... ) doesn't work at all with ModTool ... "Add-Ons cannot be created with Softimage Demo Version."
** It Seems not to work with script file (but embedded code does), the [http://xsisupport.com/2012/04/30/packaging-toolbars-and-script-commands-into-addons/ alternate method] (File > Add-On > Package... ) doesn't work at all with ModTool ... "Add-Ons cannot be created with Softimage Demo Version."
** The problem with embedded code:
** The problem with embedded code:
8,452

edits