Alex, GT Staff,
I've a big problem with the installer.
Since the form & 'Install' button is hard coded into the 'plugin_manager_pre_install.html' template, there is not possible to create complex installer scripts, with more user interaction (multiple pre install pages).
If I could avoid displaying the original form & 'Install' button, I could create more complex installer with more user interaction about installing process (using multiple pre_install pages).
The solution would be to allow an $OPTION hashref variable in install.pm (similar to $META variable), which would contain several advanced options for the GT::Plugins::Manager::pre_install, pre_uninstall, and maybe for install, uninstall, too.
Example usage in installer.pm:
$OPTION = {
pre_install_button_display => 0,
pre_install_form_display => 0,
pre_uninstall_button_display => 1,
pre_uninstall_form_display => 1,
};
This is just an example, and there could be more options as required, even to completely control the lookout of the installer html codes.
Alex, I hope you see, why the multi screen pre install screens are required.
If you need more info about the idea, let me know.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
I've a big problem with the installer.
Since the form & 'Install' button is hard coded into the 'plugin_manager_pre_install.html' template, there is not possible to create complex installer scripts, with more user interaction (multiple pre install pages).
If I could avoid displaying the original form & 'Install' button, I could create more complex installer with more user interaction about installing process (using multiple pre_install pages).
The solution would be to allow an $OPTION hashref variable in install.pm (similar to $META variable), which would contain several advanced options for the GT::Plugins::Manager::pre_install, pre_uninstall, and maybe for install, uninstall, too.
Example usage in installer.pm:
$OPTION = {
pre_install_button_display => 0,
pre_install_form_display => 0,
pre_uninstall_button_display => 1,
pre_uninstall_form_display => 1,
};
This is just an example, and there could be more options as required, even to completely control the lookout of the installer html codes.
Alex, I hope you see, why the multi screen pre install screens are required.
If you need more info about the idea, let me know.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...