Discuss: Package Install Wizard
Permalink
Just a thought that I'd like to get comments on. This is more of a feature request, but I think it's going to be necessary moving forward for more complex package development.
I'd like to see the ability for package developers to create an "Install Wizard" or custom steps during the install process. For instance, if you had a package you were developing that needs configuration or settings before it functions correctly, I'd like to take care of that during the Add-On install process in the Dashboard (say, entering an API key).
I guess I'm not sure if this can be done at this point, but it would be really helpful going forward.
I'd like to see the ability for package developers to create an "Install Wizard" or custom steps during the install process. For instance, if you had a package you were developing that needs configuration or settings before it functions correctly, I'd like to take care of that during the Add-On install process in the Dashboard (say, entering an API key).
I guess I'm not sure if this can be done at this point, but it would be really helpful going forward.
I do think there is value in having some custom steps to the installation
process. For example, the ability to specify whether sample content should
or should not be installed when installing eCommerce, Discussion Forums,
etc...
We will probably get around to doing this sooner or later, since it is a
good idea.
process. For example, the ability to specify whether sample content should
or should not be installed when installing eCommerce, Discussion Forums,
etc...
We will probably get around to doing this sooner or later, since it is a
good idea.
heh i suggested this months ago lol (about a year actually)
That's odd. I thought you were a man that could get things done. :)
heh, what i was also thinking (recently) is to move custom templates to the add/edit dialog, then have the add/edit dialog load a php file via ajax that would load options for the custom template,
I really like the idea of moving the template selection into the add/edit dialog.
I'm a little confused about what you mean by loading the settings. Are you suggesting allowing custom templates to create additional settings at the block level?
This would be extremely powerful, however the database end of it would be tricky.
I'm a little confused about what you mean by loading the settings. Are you suggesting allowing custom templates to create additional settings at the block level?
This would be extremely powerful, however the database end of it would be tricky.
yea, exactly, i was thinking that each custom template would have its own table
just a simple php file named form_interface.php off of the root of the package that posts to the package controller would be great.
We could take it from there, or make it open a dialog that loads up that file if present, otherwise it installs just like the packages do now.
We could take it from there, or make it open a dialog that loads up that file if present, otherwise it installs just like the packages do now.
also another much needed idea, package dependencies,
pkg 1 relies on pkg 2, pkg 1 won't install untill pkg 2 is installed (we can do that) and if something depends on pkg 2 (pkg 1) don't allow uninstallation (can hardcode packages currently)
pkg 1 relies on pkg 2, pkg 1 won't install untill pkg 2 is installed (we can do that) and if something depends on pkg 2 (pkg 1) don't allow uninstallation (can hardcode packages currently)
It would also be nice to include method that would allow a package developer to add a file dependency to their package.
This would allow for developers to charge for packages using libraries where the licensing may normally prohibit them.
These packages would definitely be categorized as "bleeding edge" due to the install process, however it would open add-ons to many more possibilities.