XSL components

Monthly planning

Graph associated with an X3 grid, that is used to view and modify a planning presented month by month.

The component displays:

• x groups of n months from a grid of data.
• A palette that can be used to browse through the month groups.
• A legend block that contains a list of activities associated to a selectable color. It is used to assign an activity to a period.

The possibilities linked to this monthly planning:

• Sub-division of all the days into 1 to 4 sections.
• Management of a maximum of 12 months, potentially overlapping two years.
• Display of 1 to 12 months simultaneously. According to the setup, it is possible to have a vertical scroll bar.
• Selection of sections, within the limit of one month, for the assignment of an activity.
• Three types of days (local menu 9836) : working, weekend, holiday
• An activity can only take place on a working day.
• Forbid any entry of activity on a given period, by assigning the -1 value to the sections to be forbidden.
• Reduce the number of sections, before the display of the planning, by graying out the header description of one or several PLAGn columns.  
• Personalization of activities and assignment of colors by local menus.

Use of the component

Right-click on a period:

call of the contextual menu for the line of the table corresponding to the period.

Right-click on a period or period selection:

With an activity type selected, the period changes to the new color.

The screen

The X3 grid contains one line per day, and can represent a maximum of 12 months, possibly overlapping on two years.
To operate, the XSL planning component needs to identify the columns of the X3 table. Therefore, these must be sorted by type in regards to the "Setup" section on the field tab.

Types of columns:

The type indicates to the XSL process how to use the column. Therefore, the table must contain fields of the following types:

If requiring to use the standard interaction program AMAJPLAN, the names of the next fields are imposed because they are hard coded into the program. It is possible to give another name to the fields by defining another interaction program.

XSL component options

The XSL monthly planning component APLANM proposes the following options: 

• NBMONT: Number of months displayed simultaneously (value 1 to 12).
• MENACT: Local menu type of activity (by default, 9837 with 5 values as standard). The elements of this local menu are modifiable. This parameter gives the possibility to call another local menu. 25 activities are authorized if their color is not personalized by the MENCOL parameter.
• MENCOL: Activity color local menu. Optional. This local menu must be consistent with the activity type local menu. 
• SDATA: Update of the graph following an interaction return. Value 1 or 2. Leave the default value No (1), because this XSL does not support the graph update.
• PINTER: Interaction program. By default, the AMAJPLAN program is called; however, it is possible to call another program, in this case it will be possible to give other names to the fields and to intervene on the acceptation, interaction or total rules.

The XSL setup

These three local menus are shipped as standard and associated with a code defined in the XSL parameterization:

• 9001: MONTH - Description for the months
• 9833: DAY - Description for the days
• 9834: ABRDAY - Abbreviated label for the days

There is the possibility to assign other local menus to these codes, which are themselves fixed.

Interactions

They are defined and modeled via a standard subprogram MAJPLAN from AMAJPLAN used as parameter:

The component expects 365 or 366 lines in the grid, representing 12 successive months that can overlap on 2 years.

Annual planning

Graph associated with an X3 grid, that is used to view and modify a planning presented by year. The context is the same as for the monthly planning.

The screen

same as monthly planning.

XSL component options

The annual XSL planning component APLANM proposes the following options: 

• MENACT: Local menu type of activity (by default, 9837 with 5 values as standard). The elements of this local menu are modifiable. This parameter gives the possibility to call another local menu. 25 activities are authorized if their color is not personalized by the MENCOL parameter.
• MENCOL: Activity color local menu. Optional. This local menu must be consistent with the activity type local menu. 
• SDATA: Update of the graph following an interaction return. Value 1 or 2. Leave the default value No (1), because this XSL does not support the graph update.
• PINTER: Interaction program. By default, the AMAJPLAN program is called; however, it is possible to call another program, in this case it will be possible to give other names to the fields and to intervene on the acceptation, interaction or total rules.

The XSL setup

same as monthly planning

Radar

View of a table with a graphical representation with the shape of a radar on which:

• each color represents a table line.
• each dimension type represents a value column of the table.

Possibilities relating to this radar:

• Graph in viewing mode only.
• Possible button on variable at the bottom of the table, on the graph, by right-clicking every color.
• Possibility to display a mark showing the maximum value.
• Possibility to display a scale.
• Several elements that can be viewed (table line). Limit the elements to a reasonable number, to keep the graph clear. 
• Several dimension types that can be viewed (table column). 3 minimum and limit the elements to a reasonable number, to keep the graph clear. 

Use of the component

Passing over a field:

• Increases the opacity of the field.
• Screentip description

Clicking a field:

• Positioning request for the server (line in a corresponding table).

Right-clicking a field:

• Positioning request (line in a corresponding table)
• Button for the contextual menu (line in a corresponding table)

Clicking a legend of color:

• Puts the corresponding field in the foreground.
• Increases the opacity.

Clicking the "eye" legend:

• Hides the corresponding field.

To operate, the XSL radar component needs to identify the following information, that is contained in the associated table and by the XSL setup.

The screen

To operate, the XSL planning component needs an X3 table. Each line of the table can be used to calculate a "surface".

Definition of columns:

• The first visible column of the table must be an identifier.
• The second visible column must be the description; it will be accessible from the palette.
• All the other columns are considered as analytical dimensions. They must be numeric (integer/decimal) and have a title. The table must contain at least 3 dimensions.

A dimension type can be hidden by not entering the title of the corresponding numerical column.

Therefore, these columns must be sorted by type using the "Setup" section on the field tab.

Types of columns:

The type indicates to the XSL process how to use the column. Therefore, the table must contain fields of the following types:

Type	Description
	Mandatory. Variable at the bottom of the grid
Key	Mandatory. Must contain a unique identifier.
Description	Mandatory. Must contain the title of the identifier.
Value	A field by analytical dimension whose title is stipulated in the title. These fields must be of type integer or decimal.

XSL component options

The XSL radar planning component ARADAR proposes the 3 options:

• SCALE : can be used to fix a representation (0 by default). If this scale is set to 0, the component adjusts its scale to the highest value to be represented, otherwise, the values use the scale set.
• MENSCA : Scale menu. It can be used to define a legend for the different scale values. This information must be a number of local menu. if the value is set to 0 (by default), there is no scale displayed.
• SDATA : Update of the graph following an interaction return from the graph. Value 1 or 2. No impact since the graph is set to read only.

Horizontal tree

Viewing a table with a graphical representation in the shape of an organization chart on which:

• each element represents a table line.

Here are the possibilities linked to this horizontal tree:

• possibility to move an element with everything that is attached to it (controlled by setup)
• possibility to display an image or different text lines inside the frames (controlled by setup)
• possibility to determine a style for the formatting of texts (controlled by setup)
• possibility to have a contextual menu for each element (deletion of an element using the action button)  
• possibility to execute a processing associated to double-click (controlled by setup)

Use of the component

Passing over a field:

• Screentip long description

Clicking a field:

• Positioning request for the server (line in a corresponding table).

Right-clicking a field:

• Positioning request (line in a corresponding table)
• Contextual menu request for the server (line in a corresponding table).

The screen

Table fields

The X3 table must contain one line by element of the tree.

To operate, the XSL tree needs to identify the columns of the X3 table. Therefore, these must be sorted by type in regards to the "Setup" section on the field tab.

Types of columns:

The type indicates to the XSL process how to use the column. Therefore, the table must contain fields of the following types:

In order to use the standard interaction program AMAJPLAN, the names of the next fields are imposed because they are hard coded into the program. It is possible to give another name to the fields by defining another interaction program.

The XSL component options

The XSL horizontal tree component ANOMH proposes 5 options: 

• MODHIE : Authorize moving an element and all that is attached to it. Value: 1=no / 2=yes. By default Yes (2).
• SIZEB: Size of the frame containing each element in pixel with the height and the width of the box, height of the text in this box. (Default size: 100,100). If there is no text size specified, 20px are saved for it.
• SDATA: Update of the graph following an interaction return. Value: 1=no / 2=yes. By default, YES (2). The graph is recalculated, everytime data are modified whatever the origin might be (table or graph) Set to NO, the graph is not recalculated after an interaction of the user on the graph (however, it is recalculated after a table update).   
• PINTER: Interaction program. By default, the AMAJHIER program is called, it is possible to call another program. Thanks to this, it will be possible to give other names to the fields and to intervene on the interaction acceptation rules.
• EXECFL: Authorize the call of a subprogram upon double-clicking the element of the last level.

The XSL parameterization

Interactions

They are defined and modeled via a standard subprogram MAJHIER from AMAJHIER used as parameter:

To delete an element, the button action on the variable at the bottom of the table must be used and there following must be written:

Local Char MESSAGE(100)
Local Integer CODRET
Call MAJHIER("D",nolign,"",0,MESSAGE,CODRET) From AMAJHIER
If CODRET<>1
   Call ERREUR(MESSAGE) From GESECRAN
Endif

Vertical tree

Viewing a table with a graphical representation in the shape of an organization chart on which:

• each element represents a table line.

Here are the possibilities linked to this horizontal tree:

• Expand/Collapse an element (click)
• Move an element with everything that is attached to it (controlled by setup)
• Delete an element with everything that is attached to it (right-click)
• Execute a processing upon double-clicking on the last element (controlled by setup)

Use of the component

Mousing over a field:

• Screentip short description
• Modification of the color and underlining of the text hovered by the cursor

Clicking a field:

• Positioning request for the server (line in a corresponding table).
• Reverse video on text

Right-clicking a field:

• Positioning request (line in a corresponding table)
• Contextual menu request for the server (line in a corresponding table).
• Reverse video on text

The screen

The X3 table must contain one line by element of the tree.

To operate, the XSL vertical tree needs to identify the columns of the X3 table. The "Setup" section on the field tab is used to specify a type for the columns of the X3 table.

Types of columns:

The type indicates to the XSL process how to use the column. Therefore, the table must contain fields of the following types:

The type indicates to the XSL process how to use the column. Therefore, the table must contain fields of the following types:

Field	Type	Description
NBCMP		Variable at the bottom of the grid. Mandatory.
PARENT	Key of the parent	Key of the parent for the current record. Empty, it is the head of the tree, otherwise, mandatory.
KEYC	Key	Key of the current record. Mandatory.
LIBL1	Long description	Element description. Mandatory.
INF	Information	Several fields can be of this type. This information is displayed after the long description, in the order of the declaration of fields in the table.
LIBSHORT	Short description	Displayed in a screentip. Optional.
ICO	Icon:	Icon displayed at the start of a line. The icon must be located in the folder of standard resources by folder (/X3_PUB/folder/RES). Optional.
EXP	Expanded/collapsed	Flag used to force expansion of a branch. (Local menu 1)

In order to use the standard interaction program AMAJPLAN, the names of the next fields are imposed because they are hard coded into the program. It is possible to give another name to the fields by defining another interaction program.

The XSL component options

The XSL vertical tree component ANOMV proposes 5 options: 

• MODHIE : Authorize moving an element and all that is attached to it. Value: 1=no / 2=yes. By default Yes (2).
• SDATA: Update of the graph following an interaction return. Value: 1=no / 2=yes. By default, YES (2). The graph is recalculated, everytime data are modified whatever the origin might be (table or graph) Set to NO, the graph is not recalculated after an interaction of the user on the graph (however, it is recalculated after a table update).   
• PINTER: Interaction program. By default, the AMAJHIER program is called, it is possible to call another program. Thanks to this, it will be possible to give other names to the fields and to intervene on the interaction acceptation rules.
• EXECFL: Authorize the call of a subprogram upon double-clicking the element of the last level.
• TYPPRE : Presentation type. Value:
• 1: no column,
• 2: no column new design,
• 3: one column for the description, another one for additional information
• 4: one column for the description, another one for each information

The XSL setup

Same for the horizontal tree

The icons available in the standard directory

Below is the list of icons available in the standard directory. Therefore, these icons can be used by this component.