NEWS!!! This lapper addon has now been superseded by the Common Interface Framework (CIF): http://www.lfsforum.net/showthread.php?t=72589
Hi guys,
This is a big update in the fact that it could make life a bit easier for us and newcomers to Lapper. Thius initial release is mainly for the framework, but I have additional modules that will be released over the next few weeks to allow a lot of Lapper admin tasks to become easier and the user experience to be a lot friendlier.
*** NOTE: This addon will ONLY work for Lapper v6.0.1.0 ***
Q. What do the main competitors for Lappers "InsIm of Choice" crown offer?
A. A common look & feel across their interface taht makes the user experience that much more underwhelming and friendly.
Q. How do we combat this?
A. See below.
This addon provides wrapper functions for the tabbed GUI system.
This can be used by scripters to create a multi-page interface that has a common look and feel so that Lapper becomes easier to use and promotes a clean style of coding to make scripts easier to edit and maintain.
New modules should follow the following naming guidelines and .lpr heirarchy to keep in sync with other available modules:
gui.lpr (this is the main module that must always exists)
|-> gui_<module_name>.lpr
|-> gui_<module_name>_<sub_module_name>lpr
Luckily, I have provided some GUI templates for you to use. So if we were creating a new module called "foo" with an item tab called bar", we would do the following:
1. Copy the base template (gui_template.lpr) to gui_admin_foo.lpr and then update any variable definitions to new names
2. Copy the mdule template ( gui_template_module1.lpr) to a new file called gui_foo_bar.lpr and update vars etc.
3. Add those filenames to the includes in addonsused.lpr, ensuring that they are listed in heirarchical order (gui_foo.lpr first, then gui_foo_bar.lpr) below the gui.lpr include
4. test it using whatever command you set (default is "!module1")
To kick things off, I have included a version of the multi-page help that uses this system, so have a look at the screenshot and the code. To install save the files to your include directory, rename them from *.lpr.txt to just *.lpr and then add the following lines to your "addonsused.lpr file" somewhere near the top, but below the utils.lpr:
Have a look at the addons below for further examples.
*** Recent changes ***
7/7/2010 - Updated Help.lpr to include Cruise help and to be more readable and allow easy additions
7/7/2010 - Updated gui.lpr to support grouping of buttons in the tab using a leading colon on group name (see gui_help.lpr for examples)
Hi guys,
This is a big update in the fact that it could make life a bit easier for us and newcomers to Lapper. Thius initial release is mainly for the framework, but I have additional modules that will be released over the next few weeks to allow a lot of Lapper admin tasks to become easier and the user experience to be a lot friendlier.
*** NOTE: This addon will ONLY work for Lapper v6.0.1.0 ***
Q. What do the main competitors for Lappers "InsIm of Choice" crown offer?
A. A common look & feel across their interface taht makes the user experience that much more underwhelming and friendly.
Q. How do we combat this?
A. See below.
This addon provides wrapper functions for the tabbed GUI system.
This can be used by scripters to create a multi-page interface that has a common look and feel so that Lapper becomes easier to use and promotes a clean style of coding to make scripts easier to edit and maintain.
New modules should follow the following naming guidelines and .lpr heirarchy to keep in sync with other available modules:
gui.lpr (this is the main module that must always exists)
|-> gui_<module_name>.lpr
|-> gui_<module_name>_<sub_module_name>lpr
Luckily, I have provided some GUI templates for you to use. So if we were creating a new module called "foo" with an item tab called bar", we would do the following:
1. Copy the base template (gui_template.lpr) to gui_admin_foo.lpr and then update any variable definitions to new names
2. Copy the mdule template ( gui_template_module1.lpr) to a new file called gui_foo_bar.lpr and update vars etc.
3. Add those filenames to the includes in addonsused.lpr, ensuring that they are listed in heirarchical order (gui_foo.lpr first, then gui_foo_bar.lpr) below the gui.lpr include
4. test it using whatever command you set (default is "!module1")
To kick things off, I have included a version of the multi-page help that uses this system, so have a look at the screenshot and the code. To install save the files to your include directory, rename them from *.lpr.txt to just *.lpr and then add the following lines to your "addonsused.lpr file" somewhere near the top, but below the utils.lpr:
<?php
# GUI Framework main include - this MUST be first
include ("./gui.lpr");
# Help GUI
include ("./gui_help.lpr"); # Multi-tabbed help (all in one)
include ("./gui_help_cruise.lpr"); # Cruise help file (remove if not reqd)
?>
*** Recent changes ***
7/7/2010 - Updated Help.lpr to include Cruise help and to be more readable and allow easy additions
7/7/2010 - Updated gui.lpr to support grouping of buttons in the tab using a leading colon on group name (see gui_help.lpr for examples)
)