| | 1 | = Toolboxes = |
| | 2 | |
| | 3 | == Where the documentation should be placed == |
| | 4 | |
| | 5 | * http://grass.osgeo.org/programming7/wxguitoolboxes.html (gui/wxpython/wxguitoolboxes.dox) |
| | 6 | |
| | 7 | == Creation of toolboxes from the old menu == |
| | 8 | |
| | 9 | Toolboxes which are now in GRASS distribution were created from the old menus and submenus and these toolboxes are used to create the same menu as it was before. Toolbox is a list of modules and it maps to one menu or submenu in the GUI. The same structure which is in the menu is also in the search module tab in the layer manager, so toolboxes are also there. If you are not using toolboxes, you get the same menu as before. |
| | 10 | |
| | 11 | == Which toolboxes could be created == |
| | 12 | |
| | 13 | Toolboxes which could be created now in the source code (and included in the GRASS distribution): |
| | 14 | * Temporal toolbox (not included in the default main menu). |
| | 15 | * Some special sets of modules designed for particular purpose. |
| | 16 | |
| | 17 | |
| | 18 | == What is missing and what can be done in the future == |
| | 19 | |
| | 20 | * connection to addons: |
| | 21 | * there are already some toolboxes in addons (installing a toolbox installs the set of modules) |
| | 22 | * toolboxes (in the sense of pure list of modules) from addons can be either included in user toolboxes or |
| | 23 | * GUI for creating toolboxes and editing main menu (see below) |
| | 24 | * command line in the GUI now offers all modules on the path it is not bad but toolbox depended autocomplete is also interesting |
| | 25 | * similar behavior for standard command line as for GUI command line |
| | 26 | * connection to toolbars (images needs to be added) |
| | 27 | * different handling of menu label for modules (e.g. including menu label into the module) |
| | 28 | * use toolboxes in wxIClass (and others) |
| | 29 | * redesign of handlers for non-module items (related to g.gui.* modules and plugins) |
| | 30 | * better mechanism to determine when to generate new menudata.xml file |
| | 31 | * translation of strings (currently there is some workaround which is not ideal) |
| | 32 | * prepared specialized menus in the distribution |
| | 33 | |
| | 34 | === GUI front-end === |
| | 35 | |
| | 36 | There is no GUI to create or edit toolboxes. However, it is not considered as a priority because advanced users can edit XML files directly and beginners are usually not able or not want to do the customization themselves and some advanced user have to do the customization for them. Thus, we suppose that there is no need for GUI. Still, it would be nice to have that but the GUI implementation would be very complicated, probably more than the implementation of toolboxes itself (at least the basic implementation). For the future, the GUI can be added at any point and is partially independent on the concrete toolboxes implementation. |
