1,655
edits
m (→Items) |
m (→System 2) |
||
(One intermediate revision by the same user not shown) | |||
Line 14: | Line 14: | ||
=== System 2 === | === System 2 === | ||
In the utils directory there must be a file ''CutilsMenu.def''. If this file is not present you get the default menu. The | In the utils directory there must be a file ''CutilsMenu.def''. If this file is not present you get the default menu. The contents of this file as delivered in the distribution is shown at the end of this page. | ||
You recognize the standard menu of CumulusUtils. User items can be added to the standard menu as is indicated above. While generating the website this menu will be incorporated. The System 1 menu will be generated in addition to System 2 (i.e. those items will be on the rightmost side of the menu). | |||
You recognize the standard menu of CumulusUtils. | |||
User items can be added to the standard menu as is indicated above. While generating the website this menu will be incorporated. The System 1 menu will be generated in addition to System 2 (i.e. those items will be on the rightmost side of the menu) | |||
==== Items ==== | ==== Items ==== | ||
Line 40: | Line 23: | ||
Item <name> <type> <destination> EndItem | Item <name> <type> <destination> EndItem | ||
This Item definition line has space separated words. | |||
The <name> is what you will see in the menu and may consist of one or more words. If <name> is a valid filespec on the seerver or a valid URL, it will display the contents of that filespec or URL. It is intended to be used as a specification for a small | The <name> is what you will see in the menu and may consist of one or more words. If <name> is a valid filespec on the seerver or a valid URL, it will display the contents of that filespec or URL. It is intended to be used as a specification for a small images to be displayed in the menu. It is the users responsibility to have a correct filespec or URL. No validation is done other than: | ||
# | #<name> starts with <code>'./' OR '../'</code> | ||
# | #<name> starts with <code>'http' OR 'https'</code> | ||
In which | In which cases the <name> is interpreted as an URL. | ||
The Type can be of : | The Type can be of : | ||
Line 57: | Line 40: | ||
#'''Separator''': No further arguments. Creates a thin horizontal line below the last item | #'''Separator''': No further arguments. Creates a thin horizontal line below the last item | ||
<destination> is the URL of what you want to see. An URL can be a full specification or just a filename in which case the report must be present on the server in the webroot ( | <destination> is the URL of what you want to see. An URL can be a full specification or just a filename in which case the report must be present on the server in the webroot (produced by Cutils or by the user). | ||
Example lines are shown at the bottom of this page and in the distribution file ''CutilsMenu-example-for-use.def'' | Example lines are shown at the bottom of this page and in the distribution file ''CutilsMenu-example-for-use.def'' | ||
Line 68: | Line 51: | ||
== Output == | == Output == | ||
There is no output of the user menu, only a visible appearance on the website. | There is no output of the user menu, only a visible appearance on the website. | ||
System 2 however may produce menufiles on the server of the form: ''<main menu item><subitem number>.txt''. | |||
== Inifile parameters == | == Inifile parameters == |