I want to be able to distribute a custom script and it seems that I cannot create a .tbx file, so I looked into the other methods, but they are all only for Python modules it seems.
What I want to be able to do is have the user still be able to pull up the dialog box prompting for input when they click on the tool, how do I go about packaging the external libraries that I used for this script and distribute it such that the user can simply import the tool into his toolbox and click on it and it will pull up the dialog box for user input?
-
Why can't you share your tbx file? What error do you get?MappaGnosis– MappaGnosis2012年04月16日 20:04:59 +00:00Commented Apr 16, 2012 at 20:04
-
well its not that I can't share a .tbx file, its that you cannot include scripts and external libraries in a .tbx file.Nightvein– Nightvein2012年04月16日 20:10:27 +00:00Commented Apr 16, 2012 at 20:10
-
I was considering using the tool share file system, but I can't seem to locate it?Nightvein– Nightvein2012年04月16日 20:12:22 +00:00Commented Apr 16, 2012 at 20:12
-
1I'm away from a computer with ArcGIS on it at the moment. Sorry! I don't want to seem rude not replying though!MappaGnosis– MappaGnosis2012年04月16日 20:14:06 +00:00Commented Apr 16, 2012 at 20:14
-
In 10.1, they are introducing the Python toolboxkenbuja– kenbuja2012年04月16日 21:24:26 +00:00Commented Apr 16, 2012 at 21:24
1 Answer 1
External libraries need to be installed separately. You can import standalone modules but if they require installation of dlls etc you are out of luck (ie SciPy, Numpy etc etc)
-
I'm not sure, but are python files that are imported considered dlls?Nightvein– Nightvein2012年04月17日 19:40:10 +00:00Commented Apr 17, 2012 at 19:40
-
not unless they have to be installed separately, most python modules (aka *.py) may need to be imported but will need to be distributed with the calling code or installed separately (ie SciPy or Numpy)user681– user6812012年04月18日 03:04:38 +00:00Commented Apr 18, 2012 at 3:04