After the discussion between Willem, Micha, and June on it being a great hassle that protocol shortcuts can't be expanded/resolved when exporting a protocol, I decided to finally try to create a tool that will do this.
So, here's version 0.1. The only guarantee I can give you is that it works on my machine for the set of protocols I tested it with. I am willing to tighten it up if you're willing to help me identify problem cases.
This is currently a Windows app, and it requires the .NET 2.0 redist package to be installed on your machine. It can run on any machine that has network access to your PP server. (I hope to eventually create a component that will run in PP -- windows only here -- and resolve the protocol.gz for the running protocol, which is my ultimate goal with this exercise.)
To run:
Hopefully it'll work and you'll find your result file. The result files will (by default) be annotated with sticky notes where the shortcuts were resolved. I added this in there because it was too hard for me to remember where the shortcuts used to be. (If you want to turn this off, check the config file. See below.)
There's also a config file where you can enter initial default values for the UI elements and whether or not to annotate with stickies.
Please let me know how this works for you. I'd like to make sure this works reliably, because I want to use it myself! I'll be happy to provide source code also, as long as you promise to share enhancements.
thanks,
Chris
So, here's version 0.1. The only guarantee I can give you is that it works on my machine for the set of protocols I tested it with. I am willing to tighten it up if you're willing to help me identify problem cases.
This is currently a Windows app, and it requires the .NET 2.0 redist package to be installed on your machine. It can run on any machine that has network access to your PP server. (I hope to eventually create a component that will run in PP -- windows only here -- and resolve the protocol.gz for the running protocol, which is my ultimate goal with this exercise.)
To run:
- Launch ProtocolShortcutResolveORama.exe
- Enter your server url in the form "http://server:9944/"
- Enter your username and password. Currently it won't work with https, so keep in mind these are sent as plain text. Sorry, but it's late on Sunday night.
- Enter the name/path to the component/protocol to resolve. Your protocol must exist in the xmldb in this version of the app.
- Enter the path to the xml file you want created for your resolved protocol. Not very friendly right now, sorry.
- If you want scitegic-owned shortcuts to be resolved, check the checkbox. I figured that most of the time there's no need to resolve those.
- press export.
- Wait and watch the log message area at the bottom of the app window.
- If it finishes, you'll see "Finished" in the log window. If it fails, you'll see some "ERROR" message.
Hopefully it'll work and you'll find your result file. The result files will (by default) be annotated with sticky notes where the shortcuts were resolved. I added this in there because it was too hard for me to remember where the shortcuts used to be. (If you want to turn this off, check the config file. See below.)
There's also a config file where you can enter initial default values for the UI elements and whether or not to annotate with stickies.
Please let me know how this works for you. I'd like to make sure this works reliably, because I want to use it myself! I'll be happy to provide source code also, as long as you promise to share enhancements.
thanks,
Chris
