We’re not very good at keeping secrets, we’ve actually put the sourcecode online.
What we can do is show a ‘list of actions’ that is about to be done, so you can review those before running the installer. In theory we could even make a system where you could uncheck those you don’t want.
I like that idea; to have the same list of actions visible (perhaps after the click of a “what will this installer do?” button) prior to installing.
Similarly, the installer will keep a log of the actions performed. That bit is already implemented actually.
All the toolbar/ribbon/hotkey assignments will have to be confirmed by the user, so you’ll have some control there as well.
Indeed. It might be nice to group these under a single option/confirmation, so that you won’t have to confirm every button that is added to a new toolbar for example.
I’ve made a little video preview of the “installer editor” (we have to come up with a better name for that, hehe). It shows how to create a complete installer for a relatively complex script (the Outliner), in just a few minutes.
A few notes about the vid:
-Notice the export target, you can use tags such as {id}, {version} etc to build the filename.
-The “installing” page in the installer isn’t very spectacular yet. That’s still WIP.
-Since this installer uses the script id when copying files, I could not run the Outliner after installing (you have to take that into account when doing fileIn’s for example). So the files in the script directory were copied to [userscripts]/pierjanssen.outliner/[files]. I think that this should be a standard for all installations, to keep scripts separated.
-I added a Toolbar button action, but it doesn’t actually seem to work, hehe.
-The first time I added a “Copy Directory” action it took a while before it appeared. I think this is due to the fact that it was running in debug mode inside Visual Studio.
Wow, this is very very cool. Keep up the great work!
Here you can read more about the whole concept: http://forums.cgsociety.org/showthread.php?f=6&t=982471