Difference between revisions of "AcpStyles"

 
(47 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category: Analytica Cloud Player]]
+
[[Category: Analytica Cloud Platform]]
 
[[Category: Attributes]]
 
[[Category: Attributes]]
[[Analytica_Cloud_Player#See_also|<<Back to Analytica Cloud Player]]
+
[[Analytica_Cloud_Player|<<Analytica Cloud Platform ]]
  
 
::{{ReleaseBar}}
 
::{{ReleaseBar}}
Line 7: Line 7:
 
ACP offers a wide variety of styles and options to control the look and functioning of the user interface. Many of these go beyond what is (currently) available in Desktop Analytica (DTA).  
 
ACP offers a wide variety of styles and options to control the look and functioning of the user interface. Many of these go beyond what is (currently) available in Desktop Analytica (DTA).  
  
The easiest way to set most of these styles and options is to use the [[ACP Style Library]].  Select '''Add Library...''' from the '''File''' menu and select the  [[ACP Style Library]] to add into your model. This library lets you select most ACP styles and options interactively from checkboxes and menus. You can configure Navigation styles, Node styles and [[https://wiki.analytica.com/index.php?title=Embed_table_or_graph_with_ACP#Frame_nodes|Frame nodes]]. For many options, it shows a preview of what it will look like in ACP.  When you set an option, it automatically sets the corresponding '''CloudPlatformStyles ''', ''so you don't need to worry about them, and can ignore the rest of this page.''
+
The easiest way to set these styles and options is to use the [[ACP Style Library]], which you can load into your model within ACP from the hamburger menu. As you change styles in ACP, you can see their effects immediately.
  
This page is for those geeks who want to know the details of these '''CloudPlatformStyles ''', or if you want to use those few '''CloudPlatformStyles ''' not (yet) accessible in the [[ACP Style Library]].  
+
If you use [[ACP Style Library]] you don't need to learn about the ACP Styles described below. The only reason to read the rest of this page is if you want to do something esoteric with AcpStyles, or use one of the few AcpStyles not accessible in the [[ACP_Style_Library]].  
  
You set general styles and options that apply to the whole model by adding flags to the '''CloudPlatformStyles ''' attribute for the main model. You set styles specific to a particular module or node by adding flags to the '''CloudPlatformStyles ''' attribute for that object.  
+
You can also load the  [[ACP Style Library]] in Analytica on the desktop from the '''Add Library...' option from the '''File''' menu. But, you won't be able to see the effects until you upload the model into ACP.
 +
 
 +
The styles and options are specified as keywords and tags in the AcpStyles  attribute. Most styles and options apply to the whole Model and are specified in the AcpStyles attribute of the Model.  When you want to specify special styles for individual modules or variables, you apply them to the ACPStyles attribute of the relevant object.
 
   
 
   
The easiest way to view and edit the CloudPlatformStyles attribute in Desktop Analytica is to use the [[Attribute panel]].  Select '''CloudPlatformStyles ''' from the list of Attributes at the top of that panel. By default, '''CloudPlatformStyles ''' is not shown in the [[Object window]], so you first need to set it to be shown in the [[Manage attributes|Attributes dialog]].   
+
The easiest way to view and edit the AcpStyles  attribute in Desktop Analytica is to use the [[Attribute panel]].  Select AcpStyles  from the list of Attributes at the top of that panel. By default, AcpStyles is not shown in the [[Object window]], so you first need to set it to be shown either with the [[Object_Window|right click menu]] in the Object window, or in the [[Manage attributes|Attributes dialog]].   
  
The '''CloudPlatformStyles ''' and their flags are not case sensitive.   
+
The AcpStyles  and their flags are not case sensitive.   
  
When you put multiple flags in a '''CloudPlatformStyles ''' attribute, you can separate them by commas, spaces, or newlines. We recommend putting each flag on a separate line for clarity. ACP just looks for the particular text values and doesn't care about the separators.
+
When you put multiple flags in a AcpStyles attribute, put each flag on a separate line.  
  
=== Model level styles  ===
+
== Model level styles  ==
  
These styles apply to the entire model. You set them in the '''CloudPlatformStyles ''' attribute for the Main Model. (They have no effect when set for a submodule.)
+
These styles apply to the entire model. You set them in the AcpStyles attribute for the Main Model. (They have no effect when set for a submodule.)
  
==== Navigation style  ====
+
=== Navigation style  ===
  
 
These Navigation_style options control how a user can view and access the module hierarchy:
 
These Navigation_style options control how a user can view and access the module hierarchy:
* '''<code>Navigation_style: Outline</code>''' -- Show an expandable tree of modules on the left of the ACP window, similar to the outline view in desktop Analytica (showing only modules not other objects). This is the default style when you upload a model with no ACP styles set or no Acp styles library embedded, or if you have not yet set the Navigation style in the Acp styles library. A navigation flag is not needed for this style, but if you want to explicitly set this style you can add '''<code>Navigation_style: Outline</code>''' to the top diagram's '''CloudPlatformStyles ''' attribute.
+
* '''<code>Navigation_style: Outline</code>''' -- Show an expandable tree of modules on the left of the ACP window, similar to the outline view in desktop Analytica (showing only modules not other objects). This is the default style when you upload a model with no ACP styles set or no Acp styles library embedded, or if you have not yet set the Navigation style in the Acp styles library. A navigation flag is not needed for this style, but if you want to explicitly set this style you can add '''<code>Navigation_style: Outline</code>''' to the top diagram's AcpStyles attribute.
  
 
*'''<code>Navigation_style: Top diagram only</code>''' -- Show only the top diagram, with no Outline and no tabs. This lets you make a simple web application with a single UI page.   
 
*'''<code>Navigation_style: Top diagram only</code>''' -- Show only the top diagram, with no Outline and no tabs. This lets you make a simple web application with a single UI page.   
Line 40: Line 42:
 
We describe each in more detail below.
 
We describe each in more detail below.
  
====Outline Tree====
+
===Outline Tree===
  
 
By default, when using the Outline Navigation style, ACP shows an expandable outline tree of modules on the left hand side of the window, similar to the Outline view in Analytica on the desktop. This makes it easy to navigate a model with an extensive hierarchy of modules.  
 
By default, when using the Outline Navigation style, ACP shows an expandable outline tree of modules on the left hand side of the window, similar to the Outline view in Analytica on the desktop. This makes it easy to navigate a model with an extensive hierarchy of modules.  
  
*'''<code>Show_outline: yes</code>''' -- The default, and unecessary for Outline Navigation style. It is generally redundant with other Navigation styles since the tabs or hierarchy show the same information, and the Outline takes up screen space. But you can add  it to the top diagram's CloudPlatformStyles attribute if you want to show the Outline tree with other Navigation styles.
+
*'''<code>Show_outline: yes</code>''' -- The default, and unecessary for Outline Navigation style. It is generally redundant with other Navigation styles since the tabs or hierarchy show the same information, and the Outline takes up screen space. But you can add  it to the top diagram's AcpStyles attribute if you want to show the Outline tree with other Navigation styles.
  
 
{{CalloutAnnotationBlock|[[File:Outline tree 6.0 01.png]]|{{CalloutAnnotation|Market model with<br>Outline Tree|v=80|pt=10,106}}}}
 
{{CalloutAnnotationBlock|[[File:Outline tree 6.0 01.png]]|{{CalloutAnnotation|Market model with<br>Outline Tree|v=80|pt=10,106}}}}
*'''<code>show_outline: no</code>''' --  When using the Acp Style library this is set by default for Navigation styles other than Outline. For small models, and most web apps, you may want to suppress the Outline view even when using the Outline Navigation style. Do this by inserting this text into the top diagram's CloudPlatformStyles attribute (See image below). (If a model has only one diagram,  i.e. with no modules, it never shows the outline tree.)<br/>
+
*'''<code>show_outline: no</code>''' --  When using the Acp Style library this is set by default for Navigation styles other than Outline. For small models, and most web apps, you may want to suppress the Outline view even when using the Outline Navigation style. Do this by inserting this text into the top diagram's AcpStyles attribute (See image below). (If a model has only one diagram,  i.e. with no modules, it never shows the outline tree.)<br/>
 
{{CalloutAnnotationBlock|[[File:Outline tree 6.0 02.png]]|{{CalloutAnnotation|Market model with <br/>'''<code>show_outline: no</code>'''|v=80}}}}
 
{{CalloutAnnotationBlock|[[File:Outline tree 6.0 02.png]]|{{CalloutAnnotation|Market model with <br/>'''<code>show_outline: no</code>'''|v=80}}}}
  
====Top Diagram Only====
+
===Top Diagram Only===
  
Set by adding '''<code>navigation_style: top_diagram_only</code>''' to the Cloudplayerstyle attribute of the top diagram. <!--Not to be confused with the Cloudplayerstyle flag of similar name: '''<code>top_diagram_only: yes</code>'''. -This is a navigation style most easily set with the ACP styles library. --><!--{DP - I don't know if it's mandatory or not so I am commenting it out for now) The style '''<code>Use_top_diagram_size:Yes </code>''' is  mandatory, so the diagram size is the size of the top diagram last saved in Desktop Analytica (in a non - maximized window). In addition, the--> The Styles library will set the flags <!--'''<code>top_diagram_only:yes</code>''',--> '''<code>show_outline:no</code>''' and '''<code>show_parent_diagram_button:no</code>''' .
+
Set by adding '''<code>navigation_style: top_diagram_only</code>''' to the AcpStyles attribute of the top diagram. <!--Not to be confused with the AcpStyles flag of similar name: '''<code>top_diagram_only: yes</code>'''. -This is a navigation style most easily set with the ACP styles library. --> The Styles library will set the flag <!--'''<code>top_diagram_only:yes</code>''',--> '''<code>show_outline:no</code>''' .
  
====Tabbed Module Navigation====
+
===Tabbed Module Navigation===
  
 
As an alternative to the Outline view, you can set the '''<code>Navigation_style</code>''' to use use a tabbed interface which is often more convenient and familiar for web applications. By default, the main model appears as the first tab. You can change this with the style [[AcpStyles_Attribute_Values#Exclude_the_top_level_diagram_from_tabs|show_as_tab:no]] described below.
 
As an alternative to the Outline view, you can set the '''<code>Navigation_style</code>''' to use use a tabbed interface which is often more convenient and familiar for web applications. By default, the main model appears as the first tab. You can change this with the style [[AcpStyles_Attribute_Values#Exclude_the_top_level_diagram_from_tabs|show_as_tab:no]] described below.
Line 80: Line 82:
 
There are two tabbed styles, Top_tabs, with a row of tabs across the top; and Side_tabs with a column of tabs down the side. Top_tabs works well if you have up to 5 to 8 modules in the main diagram (tabs), depending on the length of their titles and the width of the ACP window.  If you have a lot of modules, or they have long titles, it may be better to use Side_tabs.   
 
There are two tabbed styles, Top_tabs, with a row of tabs across the top; and Side_tabs with a column of tabs down the side. Top_tabs works well if you have up to 5 to 8 modules in the main diagram (tabs), depending on the length of their titles and the width of the ACP window.  If you have a lot of modules, or they have long titles, it may be better to use Side_tabs.   
  
'Top tabs or side tabs.' The first tab displays the top level diagram, and the remaining tabs display the modules present on the top level diagram of the model.  (The modules will not display on the diagram, so you need to tweak your diagram for playing in ACP so that it looks right without these present). <!--([DP]I don't know if this is mandatory or not - for now I will comment this out) The style '''<code>Use_top_diagram_size:Yes </code>''' is mandatory for tabbed navigation styles, so the diagram size for each tab (module) is the size of the top diagram last saved in Desktop Analytica (in a non-maximized window). -->
+
'Top tabs or side tabs.' The first tab displays the top level diagram, and the remaining tabs display the modules present on the top level diagram of the model.  (The modules will not display on the diagram, so you need to tweak your diagram for playing in ACP so that it looks right without these present).  
  
 
* '''<code>navigation_style: top_tabs</code>''' -- This setting instructs ACP to use the 'Tabs across top' navigation style.
 
* '''<code>navigation_style: top_tabs</code>''' -- This setting instructs ACP to use the 'Tabs across top' navigation style.
Line 90: Line 92:
 
[[File:Side tabs 6.0 01.png]]
 
[[File:Side tabs 6.0 01.png]]
  
==== Toolbar Tabs ====
+
=== Toolbar Tabs ===
 
*'''<code>show_tabs: no</code>''' -- By default, with the Outline Navigation style. ACP shows navigation tabs for "Diagram", "Object", "Table", "Graph" along the top. Use this flag to hide those tabs. If you display the model inputs and outputs on the diagram -- using embedded tables and graphs on the diagram -- your users may not need those tabs.  (You can also use '''<code>show_tabs: yes</code>''' to explicitly show the tabs in Outline and Top diagram only Navigation styles.)  
 
*'''<code>show_tabs: no</code>''' -- By default, with the Outline Navigation style. ACP shows navigation tabs for "Diagram", "Object", "Table", "Graph" along the top. Use this flag to hide those tabs. If you display the model inputs and outputs on the diagram -- using embedded tables and graphs on the diagram -- your users may not need those tabs.  (You can also use '''<code>show_tabs: yes</code>''' to explicitly show the tabs in Outline and Top diagram only Navigation styles.)  
 
{{CalloutAnnotationBlock|[[File:Show tabs no 6.0 0.1.png]]|{{CalloutAnnotation|Market model with <br/>'''<code>show_tabs: no</code>'''|v=80|pt=232,37|path=t!-}}}}
 
{{CalloutAnnotationBlock|[[File:Show tabs no 6.0 0.1.png]]|{{CalloutAnnotation|Market model with <br/>'''<code>show_tabs: no</code>'''|v=80|pt=232,37|path=t!-}}}}
 
<br/>
 
<br/>
  
====Module hierarchy bar ====
+
===Module hierarchy bar ===
 
Using tabbed navigation, ACP shows the model hierarchy in a bar at the top of the diagram by default. The model hierarchy header shows you where you are in a large model by listing the titles of the ancestor modules in which the current diagram is nested.  You can click any ancestor to click up levels in the hierarchy. The Hierarchy Bar takes up much less screen real estate than the Outline Tree. ACP doesn't show the hierarchy bar when you are viewing a top level module, or if the module title is already in the selected tab. <!--With a two-level tab navigation, it shows the hierarchy bar only when viewing a module nested 3 or more levels down. Basically, the hierarchy header does not duplicate what you can see in the tabs.-->
 
Using tabbed navigation, ACP shows the model hierarchy in a bar at the top of the diagram by default. The model hierarchy header shows you where you are in a large model by listing the titles of the ancestor modules in which the current diagram is nested.  You can click any ancestor to click up levels in the hierarchy. The Hierarchy Bar takes up much less screen real estate than the Outline Tree. ACP doesn't show the hierarchy bar when you are viewing a top level module, or if the module title is already in the selected tab. <!--With a two-level tab navigation, it shows the hierarchy bar only when viewing a module nested 3 or more levels down. Basically, the hierarchy header does not duplicate what you can see in the tabs.-->
  
Note that this setting is not based on a CloudPlayerstyle attribute, but rather on the ''Show module hierarchy'' check box in the model [[Preferences]] in Analytica.  If you want to set this preference manually, with the model opened in Analytica, on the [[Edit menu]], select '''Preference...''', and check (or uncheck) the ''Show module hierarchy'' checkbox.  
+
Note that this setting is not based on a AcpStyles attribute, but rather on the ''Show module hierarchy'' check box in the model [[Preferences]] in Analytica.  If you want to set this preference manually, with the model opened in Analytica, on the [[Edit menu]], select '''Preference...''', and check (or uncheck) the ''Show module hierarchy'' checkbox.  
  
 
If you are using the ACP styles library, the Styles library will set this to the default setting automatically once you select a Navigation style. But you have the option of changing it if, for instance you want to show the Outline and the Hierarchy bar.
 
If you are using the ACP styles library, the Styles library will set this to the default setting automatically once you select a Navigation style. But you have the option of changing it if, for instance you want to show the Outline and the Hierarchy bar.
  
 
<!--:[[Image:Acp hh.png]]-->
 
<!--:[[Image:Acp hh.png]]-->
====Use top diagram size for all ACP windows====
+
===Auto zoom ===
*'''<code>Use_top_diagram_size:Yes </code>''' -- Sets the size of all diagrams based on the size of the diagram window of the top level when the model was last viewed in Desktop Analytica (in non-maximized mode). <!--This is mandatory in all but Outline style, and optional in the Outline style.--> '''<code>Use_top_diagram_size:No </code>''' is the same as if the flag is not set, and is the default in Outline Navigation style - the ACP diagram will use the entire canvas.
+
*'''<code>auto_zoom_diagrams: yes</code>''' -- ACP automatically zooms the UI to fit the browser window -- the most constraining of width or height so it retains the aspect ratio of the diagram. Works with zoom in and zoom out. Auto Zoom will allow a model to go down to 50% of its size or up to 200% of its size. If the model does not fit at 50% size, the window will show scroll bars. This Acp style has no effect if '''<code>Use_top_diagram_size:Yes </code>''' is present, you can use only one or the other. You can also set '''<code>auto_zoom_diagrams: no</code>''' which is the default. (This is a model level setting and is added to the top diagram of a model).
 
+
'''New to ACP Build 153''' AcpStyles for controlling the max/min zoom when '''<code>auto_zoom_diagram: yes</code>''' is set. The default if these styles are not set is as above - 50% and 200%. The easiest way to set these is with the [[ACP_Style_Library]] - where the controls are in the Esoteric ACP styles module. This is available from the Hamburger menu in ACP. Note that in order to see this effect, the '''<code>Browser window size</code>''' needs to have the screen size pulldown menu set to '''<code>Auto zoom</code>''' as well.
====Go into Parent Button====
+
*'''<code>zoom_min_percent: 75</code>''' (means that the minimum zoom level will be 75% or .75)
The user clicks this button to display the parent module diagram of the current diagram: It appears by default in the Outline navigation style, but not in the tabbed styles.  The button does not appear in the top diagram, where it would have no function.
+
*'''<code>zoom_max_percent: 125</code>''' (means the that max zoom level will be 125% or 1.25)
 
 
* '''<code>show_parent_diagram_button: no</code>''' -- Set this flag to "no" to stop displaying the 'Go into Parent' button.
 
<!--[DP]not supported in ACP3
 
* '''<code>parent_diagram_button_coordinates: x, y</code>'''
 
::Show the 'Go to parent' button at a non-default location, where x and y are the number of pixels to the right and down, respectively, from the top left of the window.  E.g. <code>parent_diagram_button_coordinates:300,100</code> will change the position of this button to <code>x = 300</code>, and <code>y = 100</code>.  
 
  
'''Show the parent diagram button in 'tabs across the top' navigation style'''
+
===Use top diagram size for all ACP windows===
:If you want to display the 'Go to Parent' button when using the "Tabs across the top":
+
*'''<code>Use_top_diagram_size:Yes </code>''' --  Sets the size of all diagrams based on the size of the diagram window of the top level when the model was last viewed in Desktop Analytica (in non-maximized mode).  '''<code>Use_top_diagram_size:No </code>''' is the same as if the flag is not set, and is the default  - the ACP diagram will use the entire browser window.
:*Add the <code>parent_diagram_button_coordinates: xy</code> ACP attribute style flag, along with the <code>navigation_style: top_tabs</code> flag (see [[CloudPlatformStyles _Attribute_Values#Tabbed_Module_Navigation|Tabbed Module Navigation]] below) to the CloudPlatformStyles attribute. The actual coordinates of your parent diagram button may need to be tweaked.
 
  
*The button appears only in submodules of a tab, not in a tab diagram where it is not needed.
 
:[[File:Parentdiagbutton w top tabs01.PNG]]
 
-->
 
 
<!--Not in ACP3 yet - ER519
 
<!--Not in ACP3 yet - ER519
====Display Only a Single Diagram====
+
===Display Only a Single Diagram===
 
*'''<code>top_diagram_only: yes</code>''' -- Use this flag if you want to restrict users access to only the top diagram. With this flag, any action that would normally bring up a different diagram will just reload the top diagram.  (If you are using this setting, you will also want to also not display the Outline Tree as explained above, since clicking on the modules in the Outline will have no effect.)
 
*'''<code>top_diagram_only: yes</code>''' -- Use this flag if you want to restrict users access to only the top diagram. With this flag, any action that would normally bring up a different diagram will just reload the top diagram.  (If you are using this setting, you will also want to also not display the Outline Tree as explained above, since clicking on the modules in the Outline will have no effect.)
 
-->
 
-->
====Show or hide the Dashboard Title and Model title====  
+
===Show or hide the Dashboard Title and Model title===
 
*'''<code>show_model_title: no</code>''' -- Hide the title of the model, which appears by default in the top Teal bar.
 
*'''<code>show_model_title: no</code>''' -- Hide the title of the model, which appears by default in the top Teal bar.
  
 
*'''<code>show_diagram_title: yes</code>''' --  Use  to show the dashboard title at the top of the diagram. Or <code>show_diagram_title: no</code> to suppress the diagram title, but not really necessary because ACP does not show the diagram title by default.
 
*'''<code>show_diagram_title: yes</code>''' --  Use  to show the dashboard title at the top of the diagram. Or <code>show_diagram_title: no</code> to suppress the diagram title, but not really necessary because ACP does not show the diagram title by default.
 
<!--
 
<!--
====Hide the Banner and Logo====
+
===Hide the Banner and Logo===
Another flag it's easier to use the [[ACP Style Library]] to set, since it is only compatible with the parent button and toolbar tabs hidden. The Styles library changes all the flags at once, and prevents you from entering incompatible combinations.
+
Another flag it's easier to use the [[ACP Style Library]] to set, since it is only compatible with the toolbar tabs hidden. The Styles library changes all the flags at once, and prevents you from entering incompatible combinations.
  
 
*'''<code>show_banner: no</code>'''  
 
*'''<code>show_banner: no</code>'''  
Line 140: Line 133:
 
:*If you play a model without the banner area in ACP, there isn't a convenient way to close the model without closing the browser.
 
:*If you play a model without the banner area in ACP, there isn't a convenient way to close the model without closing the browser.
 
-->
 
-->
====Scroll Bars====
 
  
*'''<code>Add_scroll_bars: yes</code>'''
+
===Exclude diagram(s) from tabs===
::You can add this flag to the top level diagram's CloudPlatformStyles attribute if you want to add scroll bars on a large diagram. Scroll bars no longer show by default, since they take up screen space.
 
====Exclude diagram(s) from tabs====
 
  
 
When using tabbed navigation, you can select those modules (from the top model diagram) that you want to appear as a tab in ACP. The default is for all to appear as tabs. You should use the ''Show modules as tabs'' choice menu in the '''<code>ACP Navigation styles</code>''' section of the [[ACP Style Library]] if you want to set this flag,, and if you also want to hide the modules corresponding to these tabs [[ChangeNodeVisibility|hidden]], so that the model viewer cannot see them.
 
When using tabbed navigation, you can select those modules (from the top model diagram) that you want to appear as a tab in ACP. The default is for all to appear as tabs. You should use the ''Show modules as tabs'' choice menu in the '''<code>ACP Navigation styles</code>''' section of the [[ACP Style Library]] if you want to set this flag,, and if you also want to hide the modules corresponding to these tabs [[ChangeNodeVisibility|hidden]], so that the model viewer cannot see them.
  
*Optionally, Enter the text '''<code>Show_as_tab: no</code>''' in the CloudPlatformStyles attribute of the modules you don't wish to show as a tab. The modules themselves will not be hidden with this setting, only the tabs.
+
*Optionally, Enter the text '''<code>Show_as_tab: no</code>''' in the AcpStyles attribute of the modules you don't wish to show as a tab. The modules themselves will not be hidden with this setting, only the tabs.
 
<!--
 
<!--
 
*'''<code>show_as_tab: no</code>'''  
 
*'''<code>show_as_tab: no</code>'''  
Line 154: Line 144:
 
*When setting tabbed Navigation styles using the ACP Styles Library, the default is for the Top level diagram to be included, except with two tiers of tabs, for which it is (Currently) required to exclude the top diagram from the tabs.
 
*When setting tabbed Navigation styles using the ACP Styles Library, the default is for the Top level diagram to be included, except with two tiers of tabs, for which it is (Currently) required to exclude the top diagram from the tabs.
  
If you want to see what it looks like, play this model [[Media:Show as tab no.ana|Array examples]] in ACP, with the '''<code>show_as_tab: no</code>''' style in the cloud platform styles attribute, and set to tabs along top.
+
If you want to see what it looks like, play this model [[Media:Show as tab no.ana|Array examples]] in ACP, with the '''<code>show_as_tab: no</code>''' style in the AcpStyles  attribute, and set to tabs along top.
  
 
:[[File:Show as tab no02.png]]
 
:[[File:Show as tab no02.png]]
Line 162: Line 152:
 
:[[File:Show as tab no01.png]]
 
:[[File:Show as tab no01.png]]
 
-->
 
-->
====Tab color====
+
===Tab color===
  
When using Tabbed Navigation, you can use these flags to control how the color of the tabs display on your model in ACP. To use, add one of them to the CloudPlayerStyle attribute of the top level diagram of your model. They have no effect if added to a module other than the top diagram.
+
When using Tabbed Navigation, you can use these flags to control how the color of the tabs display on your model in ACP. To use, add one of them to the AcpStyles attribute of the top level diagram of your model. They have no effect if added to a module other than the top diagram.
  
 
*'''<code>Tab_color: Default </code>''' The default. Non-selected tabs are bluish white. The selected tab uses the background color for that diagram.
 
*'''<code>Tab_color: Default </code>''' The default. Non-selected tabs are bluish white. The selected tab uses the background color for that diagram.
Line 170: Line 160:
 
*'''<code>Tab_color: Node </code>'''  The selected Tab uses its diagram background color; The other tabs use the color of their Module node (not their diagram background color).  You can use this to change the color of the tabs by modifying their node color in an Analytica functions.
 
*'''<code>Tab_color: Node </code>'''  The selected Tab uses its diagram background color; The other tabs use the color of their Module node (not their diagram background color).  You can use this to change the color of the tabs by modifying their node color in an Analytica functions.
  
=== Model level styles for diagram nodes. ===
+
== Model level styles for diagram nodes. ==
  
You can set some styles for your model - at the top model diagram level - which will effect how nodes on the diagram are displayed.  All nodes in the model will be effected.
+
These model-level styles affect how all nodes are displayed in diagrams.   
  
*'''<code>show_hover_highlight: yes</code>''' Usually unnecessary because this is the default.
+
=== Node shadows and bevels ===
::By default, ACP displays a hover highlight -- a contrasting light rectangle behind a node -- when you move the cursor over the node. (The hover highlight is different from the [[help balloons|Help  Balloon]] described below.)
 
:[[File:acp hover hl.png]]
 
*'''<code>glow_hover_highlight: yes</code>'''
 
:: Set this flag to show a "glowing" highlight around each node, instead of the outline when you move the cursor over a node. <br>
 
  
*'''<code>glow_hover_highlight: no</code>'''  Switches off this behavior, and is usually unnecessary since it is the default behavior in ACP.
+
By default ACP displays nodes without shadows or bevels (for now) , so they look like this:
*'''<code>show_hover_highlight: no</code>''' You can suppress the hover highlight completely (no outline or glow) by including this style in the top level model object. It does have any effect currently when applied to individual nodes.
+
:[[Image:Nodes no shadow or bevel.png]]
==== Enhanced Diagram Graphics  ====
 
  
You can control the appearance of nodes, with bevels, shadows, by setting these in the CloudPlatformStyles for the model. By default (for now) ACP displays nodes without the bevels and shadows:<br>
+
Set this flag to show a drop shadow behind each node, giving a kind of 3D effect:
  
:[[Image:Nodes no shadow or bevel.png]]
+
*'''<code>node_drop_shadow: yes</code>'''
 
 
*'''<code>node_drop_shadow: yes</code>'''  
 
::Setting this flag, displays a drop shadow behind each node, giving a kind of 3D effect:<br>
 
  
 
:[[Image:Nodes drop shadow.png]]  
 
:[[Image:Nodes drop shadow.png]]  
  
*'''<code>bevel_node_border: yes</code>'''
+
Set this flag to display a bevel border for each node, giving another kind of 3-D effect:  
::Setting this flag, displays a bevel border for each node, giving another kind of 3-D effect:  
+
*'''<code>bevel_node_border: yes</code>'''
  
 
:[[Image:Nodes beveled border.png]]  
 
:[[Image:Nodes beveled border.png]]  
  
<br> These effects are off by default. You are welcome to try them out, by setting CloudPlatformStyles for the main model. Eventually, these effects may become the default. Then you'll be able to turn each one off using <code>Node_drop_shadow: no, Bevel_node_border: no</code>, and<code>Glow_hover_highlight: no</code>.-->
+
===Node hover highlighting===
  
==== Balloon Help  ====
+
By default, ACP displays a highlight -- a contrasting light rectangle behind a node -- when you move the cursor over the node:
  
When you move the cursor over a node, ACP usually shows a "balloon" popup next to the node with the title, units and description of the node (if it has one) to help end users understand what its for, or what to enter for a user input. If the node has no description, the [[help balloons|balloon help]] will not appear.
+
[[File:acp hover hl.png]]
  
*'''<code>show_id_in_balloon: yes</code>'''  
+
You can switch it off by setting:
::Use this flag to show each node's identifier below its title in the balloon -- unless the identifier and title are identical (except for spaces which are replaced by underscores).
+
*'''<code>show_hover_highlight: No</code>'''  
  
 +
=== Balloon Help  ===
 +
 +
When you move the cursor over a node, ACP usually shows a "balloon" popup next to the node with the description of the node (if it has one) to help end users understand what its for, or what to enter for a user input. If the node has no description, the [[help balloons|balloon help]] will not appear.
 +
 +
*'''<code>show_id_in_balloon: yes</code>''' Use this flag to show each node's identifier below its title in the balloon -- unless the identifier and title are identical (except for spaces which are replaced by underscores). This flag goes in the AcpStyles of the model and apply to all nodes in the model.
 
<!-- not implemented in ACP3  
 
<!-- not implemented in ACP3  
 
*'''<code>show_definition_in_balloon: yes</code>'''  
 
*'''<code>show_definition_in_balloon: yes</code>'''  
 
::Use this flag to show the node's definition in the balloon below the description.
 
::Use this flag to show the node's definition in the balloon below the description.
 
+
-->
 +
<!-- not implemented in ACP3
 
*'''<code>hover_balloon_delay</code>'''  
 
*'''<code>hover_balloon_delay</code>'''  
 
::When you mouse over a node, there's a short delay of about half a second before it displays the balloon (to prevent wild balloon appearance when you move the cursor rapidly over a diagram.) You can tweak this delay time measured in milliseconds by inserting this flag. E.g. '''<code>hover_balloon_delay: 200</code>''' to reduce the delay to .2 seconds.
 
::When you mouse over a node, there's a short delay of about half a second before it displays the balloon (to prevent wild balloon appearance when you move the cursor rapidly over a diagram.) You can tweak this delay time measured in milliseconds by inserting this flag. E.g. '''<code>hover_balloon_delay: 200</code>''' to reduce the delay to .2 seconds.
 +
-->
 +
<!--
 +
The flags above go in the AcpStyles of the model and apply to all nodes in the model. You can also modify some aspects of the balloon separately for each node by inserting these flags in AcpStyles for each node: -->
 +
*'''<code>show_hover_balloon: no</code>'''
 +
::Insert this flag in the AcpStyles for a node, to suppress display of its balloon.
 +
<!--title no longer shows in the balloon
 +
*'''<code>show_hover_balloon_title: no</code>'''
 +
::Insert this flag in the AcpStyles for a node, to suppress its title in the balloon.-->
  
The three flags above go in the CloudPlatformStyles of the model and apply to all nodes in the model. You can also modify some aspects of the balloon separately for each node by inserting these flags in CloudPlatformStyles for each node:
+
==ACP styles inheritance==
 
+
This is the order of inheritance for Acpstyles below that apply to tables and graphs. Styles at a higher level take precedence over the lower precedence styles. (Inheritance doesn't apply to the ACPstyles described above that apply only at the Model level.)
*'''<code>show_hover_balloon: no</code>'''
+
# '''Variable''' (includes Tall nodes): Acpstyles applied to an individual variable will take precedence over all other styles. A variable with a style of <code>show_title:no</code> will not show the title, even if the model level style is <code>show_title:yes</code>, and if that node shows it's result in a frame node the variable style will override the frame node style.
::Insert this flag in the CloudPlatformStyles for a node, to suppress display of its balloon.
+
# '''Frame''' : An Acpstyle set for a frame node will affect any variable shown in that frame that doesn't have its own settings. These will also override any styles at the model level.
 +
# '''Model ACP style defaults''': Acpstyles that you can enter into the Acptyles attribute of the top diagram of your model. These will override the ACP defaults, and will be inherited by frame nodes and variables in the model that don't have their own Acpstyle.
 +
# '''ACP style defaults for ACP''': The default style ACP uses if you have no specific setting for that style. Eg for show_index_menus the default is fly-in and that is what will show if you don't enter a different show_index_menus: Acpstyle flag in the Acpstyle for the top diagram (model level) or for frame nodes or variables.
  
*'''<code>show_hover_balloon_title: no</code>'''
+
==ACP Styles for tables and graphs==
::Insert this flag in the CloudPlatformStyles  for a node, to suppress its title in the balloon.
 
-->
 
<!--Not implemented yet in ACP3
 
*'''<code>show_copy_table_icon: no</code>'''
 
::Usually, ACP displays a copy table icon near the upper right hand corner of a result table (or edit table, but less useful here).  Clicking the icon copies the table as displayed so it can be pasted into another place, e.g. Excel.  If you want to hide this icon, this is the flag to use.  The Copy Table Icon is the icon shown in the image below. This style should be applied to the top level model object. It doesn't have any effect currently when applied to individual nodes.
 
  
:[[File:Copy table icon.png]]
+
These styles affect how result graphs and tables are displayed in ACP, including in [[Embed_table_or_graph_with_ACP#Frame_nodes|Tall nodes]] and [[Embed_table_or_graph_with_ACP#Tall_nodes|˞Frame nodes]]. They provide options not (yet) available in Desktop Analytica. ACP has default settings for these. You can override these settings for the entire model. You can also set them for [[Embed_table_or_graph_with_ACP#Frame_nodes|˞Frame nodes]], which will apply to all results shown in the Frame and override the ACP and model level settings. And you can set these styles for individual variables, which will override any settings in the Model or Frame. As always, it's easiest to set the using the [[ACP_Style_library]].
  
-->
+
None of these styles apply to tab result views using the default Navigation_style: Outline.
<!--Not implemented in ACP3 and replaced with blank button node style
 
*'''<code>ShowIONodeButtonText: no</code>'''
 
::Unchecking this will cause Result/Calc/Edit table buttons to show without the text label in ACP
 
*'''<code>show_unc_view_in_outputs: no</code>'''
 
::In Desktop Analytica, each user output node has a little icon on the right-hand side showing the uncertainty view last viewed (e.g. mid, mean, stats...). In ACP, you can suppress these with the flag <code>show_unc_view_in_outputs: no</code>. We recommend this for ACP since the icon is usually confusing to end users. This style should be applied to the top level model object. It does have any effect currently when applied to individual nodes.  
 
  
:[[Image:Uncertainty view icons.png]] -->
+
===Show or hide the Description===
<!--
 
===Acp styles that can be used only in Frame nodes and Tall nodes===
 
-->
 
===Acp styles used for both model  and nodes===
 
These styles can be set at the model level - which effects every node in the model. They can also be set at the node level and some of them can be set for [[Embed_table_or_graph_with_ACP#Frame_nodes|˞Frame nodes]]. When set for a Frame node, this style overrides the model level style and is used for all variables that display in the frame node. Unless there is an individual node style - which overrides both Model level and Frame node styles.
 
  
====Show or hide the Description====
+
*'''<code>Show_description: nn</code>'''' Where <code>nn</code> is a number between 0 and 100, where it uses up to nn% of the vertical space available to show the description. If that isn't enough to show the entire description, it shows a vertical scroll bar. Set <code>nn = 0</code>, if you don't want to show the description at all. Default if not mentioned, is one third, i.e. <code>Show_description: 33</code>.  This style can be used at the model level, for frame nodes or for individual nodes, but controls  whether or not the Description shows in tall nodes or Frame nodes.
  
*'''<code>Show_description: nn</code>'''' Where <code>nn</code> is a number between 0 and 100, where it uses up to nn% of the vertical space available to show the description, showing vertical scroller if that isn't enough to show the entire description. Set <code>nn = 0</code>, if you don't want to show the description at all (and no scroller). Default if not mentioned, is one third, i.e. <code>Show_description: 33</code>.  This style can be used at the model level, for frame nodes or for individual nodes, but controls  whether or not the Description shows in tall nodes or Frame nodes. The description is always present in tab result views.
+
===Show or hide the Object view icon===
 +
*'''<code>Object_in_Frame:yes/no</code>''': With this style set, it shows an object view hover icon at the top right of a frame node or tall node when showing a graph or table view. Click this icon to show the object window view. The object view shows the Table and Graph hover icon to go back to the table or graph view. You can set '''<code>Object_in_frame</code>''' style at either the top level of the model or in an individual frame node, which overrides the top level setting. When working with tall nodes, you can set '''<code>Object_in_frame</code>''' style at the top level or in the original variable's ACP style setting, which overrides the top level setting.
  
====Show or hide the title====
+
===Show or hide the title===
  
*<code>Show_title</code>: Set <code>Show_title: yes</code> to show or <code>Show_title: no</code> to stop showing the Title and units of a selected variable. This style can be used at the model level, for frame nodes or for individual nodes, but controls  whether or not the Title and units show in Frame nodes. Not yet implemented in tall nodes. The title is always present in tab result views.
+
*'''<code>Show_title</code>''': Set <code>Show_title: yes</code> to show or <code>Show_title: no</code> to stop showing the Title and units of a selected variable. This style can be used at the model level, for frame nodes or for individual nodes, but controls  whether or not the Title and units show in Frame nodes or tall nodes.  
  
====Show or hide the Graph-Table icon====
+
===Show or hide the Graph-Table icon===
  
*'''<code>Show_graph_table_icon:no</code>'''
+
*'''<code>Show_graph_table_icon:no</code>''' Hides the icon in the top right of a Result that lets you toggle between Graph and Table view. This applies to [[Embed_table_or_graph_with_ACP|Frame nodes and tall nodes]]. This style can be used for  the entire model, for frame nodes or for individual nodes . You set them in the AcpStyles attribute.  Conversely, you can set  '''<code>Show_graph_table_icon:yes</code>'''. This is the default so not usually necessary at the model level, but can be used in a frame node or variable to override the model default or override a frame node setting.
Hides the icon in the top right of a Result that lets you toggle between Graph and Table view. This applies to [[Embed_table_or_graph_with_ACP|Frame nodes and tall nodes]]. This style can be used for  the entire model, for frame nodes or for individual nodes . You set them in the '''CloudPlatformStyles ''' attribute.  Conversely, you can set  *'''<code>Show_graph_table_icon:yes</code>'''. This is the default so not usually necessary at the model level, but can be used in a frame node or variable to override the model default or override a frame node setting. This icon is irrelevant and does not display in tab result views.
 
  
====Show or hide the Uncertainty view menu====  
+
===Show or hide the Uncertainty view menu===
 
By default, in ACP, as in desktop Analytica, the [[Uncertainty views]] menu appears above each result graph or table to let you select [[Mid]] to display its deterministic value, or Mean, Probability distribution, and other ways to display a probabilistic value.   
 
By default, in ACP, as in desktop Analytica, the [[Uncertainty views]] menu appears above each result graph or table to let you select [[Mid]] to display its deterministic value, or Mean, Probability distribution, and other ways to display a probabilistic value.   
  
Line 262: Line 245:
 
*'''<code>Show_uncertainty_view: Yes</code>''' Always show the uncertainty menu even for variables that are not probabilistic, as in Desktop Analytica. This is the default and not normally necessary at the model level, but can be used to customize which frame nodes or variables to show the uncertainty view menu when the model level style is set to '''<code>Show_uncertainty_view: No</code>'''
 
*'''<code>Show_uncertainty_view: Yes</code>''' Always show the uncertainty menu even for variables that are not probabilistic, as in Desktop Analytica. This is the default and not normally necessary at the model level, but can be used to customize which frame nodes or variables to show the uncertainty view menu when the model level style is set to '''<code>Show_uncertainty_view: No</code>'''
  
====Show or hide the Index menus and Pivoters/slicers====
+
===Show or hide the Index menus and Pivoters/slicers===
 
*'''<code>Show_index_menus: Fly-in</code>''' By default (the same as if there is no show_index_menu: setting) the index menus are not shown in [[https://wiki.analytica.com/index.php?title=Embed_table_or_graph_with_ACP|frame nodes or tall nodes]] (but slicers are), since often the modeler has already chosen the pivot they want to use. And because these menus take up valuable screen space. But if you hover over the frame node (or tall node) there is a fly-in pivoter control. If you click this it toggles - on or off - the visibility of the pivoters; allowing you to pivot the result table or graph and then close the pivoters to give you more space.
 
*'''<code>Show_index_menus: Fly-in</code>''' By default (the same as if there is no show_index_menu: setting) the index menus are not shown in [[https://wiki.analytica.com/index.php?title=Embed_table_or_graph_with_ACP|frame nodes or tall nodes]] (but slicers are), since often the modeler has already chosen the pivot they want to use. And because these menus take up valuable screen space. But if you hover over the frame node (or tall node) there is a fly-in pivoter control. If you click this it toggles - on or off - the visibility of the pivoters; allowing you to pivot the result table or graph and then close the pivoters to give you more space.
 
*'''<code>Show_index_menus: Yes</code>''' If you do want to allow users to be able to pivot or change the slice of the table or graph, without using the fly-in, then use use show_index_menus:yes. Always present in tab result views.
 
*'''<code>Show_index_menus: Yes</code>''' If you do want to allow users to be able to pivot or change the slice of the table or graph, without using the fly-in, then use use show_index_menus:yes. Always present in tab result views.
 
*'''<code>Show_index_menus: No</code>''' If show_index_menus:no is set then the indexes and pivoters will not show and there is no fly-in, but the slicers will still be present.
 
*'''<code>Show_index_menus: No</code>''' If show_index_menus:no is set then the indexes and pivoters will not show and there is no fly-in, but the slicers will still be present.
*'''<code>Show_index_menus: Not_even_sicers</code>''' If you don't want to show any pivoters or slicers, you can set show_index_menus:Not_even_slicers.
+
*'''<code>Show_index_menus: Not_even_slicers</code>''' If you don't want to show any pivoters or slicers, you can set show_index_menus:Not_even_slicers.
 
 
====Autocalc====
 
in ACP3, This can be set by node or by Diagram, it is not  applicable to [[Embed_table_or_graph_with_ACP#Frame_nodes|Frame nodes]]. Note that the 2 styles from ACP1, '''<code>calc_on_open: yes</code>''' and '''<code>auto_recalc_results: yes</code>'''  have been replaced with the Desktop Analytica functionality  for [[Proactive_Evaluation]]. You can set this easily in the ACP styles library in the 'Styles for result variables' pane. When set to proactively evaluate, Tall nodes will show the result in the embedded node when calculated. Other nodes will calculate the result but will not actually show the result until the result is shown either in a frame node or in a tab.
 
 
 
<!--[DP]These next 2 do not work in ACPsuan so I assume we will not implement them and will replace with proactively evaluate. But will just comment them out for now.
 
*'''<code>calc_on_open: yes</code>'''
 
::By default, ACP, like Analytica, does not compute results when you first view a diagram, leaving any User output nodes showing the '''Calc''' button. The user must click on each to see its result, as a scalar embedded in the Diagram, or as a separate Result window. Unless some results take a long time to evaluate, it is usually friendlier to compute the values before showing the Diagram. You can make this happen by inserting <code>calc_on_open: yes</code> into the top level diagram's CloudPlatformStyles attribute. This flag doesn't have any effect currently when applied to individual nodes.
 
 
 
*'''<code>auto_recalc_results: yes</code>'''
 
::Causes ACP to immediately recalculate any result when the user changes an input on that diagram that affects the result.
 
-->
 
 
 
<!--
 
===Styles to adjust the ACP canvas===
 
  
From ACP1, not for ACP3
+
===Autocalc===
====Set the ACP canvas size====
 
  
The default ACP3 Flash Canvas is set to "100%". This means that the canvas is the same size as the browser window.  
+
In the  [[ACP Style Library]], Autocalc looks like a style you can set for a model, module or variable. It controls whether ACP evaluates each variable and shows its results automatically when you view a Diagram or tab showing the -- instead of the default Analytica behavior where the end user has to click on a Calc button to compute a result.  With Autocalc on, a result in view also recomputes automatically when you change an input that influences it.
  
There are two cloud player styles for optionally controlling screen size.
+
Autocalc is not actually an ACPStyle in ACP3. (It was in ACP1.)  Autocalc is implemented using the Desktop Analytica functionality  for [[Proactive_Evaluation]].
  
*'''<code>screen_width: 999</code>''', and '''<code>screen_height: 999</code>'''
 
::where 999 is the number of pixels to use for your ACP canvas. If you use these flags you need to add space for the Banner/Tabs/Hierarchy headers or the outline on the left.
 
 
===Other Model level styles===
 
-->
 
<!--[DP] not implemented yet in ACP3
 
====Message boxes====
 
 
*'''<code>message_box_location: x, y</code>'''
 
::By default, ACP shows error and other message boxes right in middle of the screen, but you can change where these display using this flag. Set this flag - with the x, y coordinates in pixels on the ACP canvas - where you want the message boxes to display. Needs to be put into the CloudPlatformStyles attribute for the top diagram of your model.
 
-->
 
 
== Node Level Settings  ==
 
== Node Level Settings  ==
  
These style flags and options apply to individual nodes (variables), rather than the model as a whole. So, you set these flags on the CloudPlatformStyles for selected objects (nodes).
+
These style flags and options apply to individual nodes (variables), rather than the model as a whole. So, you set these flags on the AcpStyles for selected objects (nodes).
 
 
=== Input nodes  ===
 
<!--
 
*'''<code>textalways</code>'''
 
::Usually in ACP and Desktop Analytica, to enter a text value into a user input node you have to enclose it in quotes. Insert this flag into the CloudPlatformStyles for each Input node if you want it treat the input as text without requiring the user to use quotes.  Note this flag is inserted into the Formnode's CloudPlatformStyles attribute and cannot be done in the Object window or attribute panel.  Instead figure out what the identifier of the formnode is and then set the CloudPlatformStyles in the typescript window.
 
-->
 
<!--Not implemented in flex so I will comment out for now
 
*'''<code>tabindex: ''n''</code>'''
 
::In ACP and Desktop Analytica, the user can press tab to go to the next input control to enter its input. You can control the tab order -- the sequence followed by tabbing through inputs -- by adding this flag. Put <code>tabindex: 1</code> into the CloudPlatformStyles of the first one. Put  <code>tabindex: 2</code> into the second, and so on.  Note this flag is inserted into the Formnode's CloudPlatformStyles attribute and cannot be done in the Object window or attribute panel.  Instead figure out what the identifier of the formnode is and then set the CloupPlayerStyles in the typescript window.
 
-->
 
  
 
=== Other node level flags ===
 
=== Other node level flags ===
==== Prevent nodes from showing on the diagram ====
+
=== Prevent nodes from showing on the diagram ===
  
 
*'''<code>Show_Object: no</code>'''  
 
*'''<code>Show_Object: no</code>'''  
::You can prevent nodes or modules from showing on the diagram of your model, by adding this flag to the CloudPlatformStyles attribute of the object you wish to hide.
+
You can prevent nodes or modules from showing on the diagram of your model, by adding this flag to the AcpStyles attribute of the object you wish to hide. Once the model is shown in ACP the objects aren't visible.
  
*Once played in ACP the objects aren't visible, and if the outline is displayed the module will not be shown in the Outline either.
+
== Modifying ACP menus==
<!--[DP] none of these work in ACP3 and I don't know if any of them will be implemented
 
==Special Flags==
 
  
===Download_Spreadsheet:xyz.xlsx===
+
Normally, ACP offers menus that appear when you press one of the three icons on the right of the top teal bar. These ACP styles let you modify these menus.
*This Cloud Player style allows you to download a spreadsheet while playing a model. You could of course have modified this Spreadsheet while working with the model.
 
*This flag can be added to the CloudPlayerStyle attribute of a button. E.g. if you want to download <code>xyz.xlsx</code> you add <code>download_spreadsheet xyz.xlsx</code> to the CloudPlayerStyle attribute of the button. Then when pressed the button will prompt you to save the file.  
 
*You can't download a spreadsheet in the same button click that causes a spreadsheet to be uploaded.
 
*If you don't specify the name of the spreadsheet file ACP downloads the last file uploaded without a dialog.
 
*This is not the same as using [[SpreadsheetSave]]() {If you evaluate a variable in your model using [[SpreadsheetSave]], it will save the spreadsheet to the server by default}.
 
  
*You can also do this "on the fly" in your model by having an [[OnClick]] attribute that sets this flag in the CPS attribute.
+
===Hide the Save options===
  
===Upload_Spreadsheet===
+
*'''<code>Hide_save_button: yes </code>''' Set this model ACP style option to exclude the  'Save this model' and 'Save model as...' from the ACP Close menu. It prevents  users from saving over your models or saving other versions.
 +
*''This style cannot currently be set from the ACP style library, since it would allow users to show the save and save as menu options and then save changes even if the modeler does not want to allow it.''
  
*This flag can also be added to the CloudplayerStyle attribute of a button. It results in the user being prompted with a file upload after the button onclick completes.
+
===Remove Help menu items===
  
*As with the <code>Download_Spreadsheet</code>, flag, you can do this "on the fly" in your model by having an [[OnClick]] attribute that sets this flag in the CPS attribute.
+
These styles add menu items to or remove items from the help (?) menu if added to the AcpStyles of the top diagram of your model. For [[ACP_Server_License|ACP installations]] on an intranet, these standard links may not be accessible. On the other hand you may want to offer a special help page for a particular model.
  
===Upload_filename_variable: Var_x:===
+
*'''<code>Remove_help_menu_options: Text</code>
Can be used in conjunction with <code>Upload_spreadsheet<\code>. When you upload a file using a button. In the button CPS attribute if you have the following:
+
This style allows you to list one or more of the standard options to remove from the help (?) menu. Replace <code>Text</code> with one or more of the following: <code>ACP_Online_docs, Analytica_Q_A_forum, Tech_support</code>.
  
<code>upload_spreadsheet<br/>
+
(Note: The help menu item <code>Connection status</code> cannot currently be removed).
Upload_filename_variable: Var_x</code>
 
 
 
After uploading the file, ACP will write the filename (e.g. "ssFile.xlsx" note current does not include full path) to the definition of Var_x
 
 
 
===Save_on_click:yes===
 
This flag can be added to the cloudplayerstyle attribute of a  button. Then it works as a "save as" button. Ie the save dialog opens when the button is pressed.
 
 
 
==="ACP_save_as_filename" variable===
 
Can be used to create a custom default model name in the save as dialog. Used in combination with the <code>save_on_click:yes</code> flag.
 
 
 
*In Desktop Analytica, add a variable to your model with the identifier <code>acp_save_as_filename</code>
 
 
 
[[Media:Saveasfilename.ana|Here is an example model]] using the <code>save_on_click:yes</code> and <code>acp_save_as_filename</code> flags.
 
 
 
<!--[DP]Removed as of 42
 
==="Save_as_Public:Yes===
 
Another flag which can be used with a button, only in combination with the cloudplayerstyle <code>save_on_click:yes</code>. This flag causes the access of a model snapshot saved in a group account to be public by default.
 
 
 
===Asychronous calls===
 
 
 
See the what's new page [[What%27s_new_in_ACP%3F#New_functionality_requiring_Asynchronous_calls|here]] also [[Future_ACP_Features#Async_calls|Explanation of ACP's use of Asynchronous polling]]
 
 
 
*'''<code>use_async_calls: no</code>'''
 
::This flag needs to be set in the top diagram of your model if you don't want to use asynchronous calls. This may  slightly speed up model playing for some models of course, you don't want to add this flag if you have features in your model which require [[Future_ACP_Features#Async_calls|asynchronous polling]])
 
 
 
*'''<code>use_async_calls: yes</code>'''
 
::This flag has been deprecated since asynchronous polling has been implemented as default in ACP, and will be removed from this wiki eventually.
 
 
 
==="ACP Current User" Variable===
 
Add a variable to your model which will show the current user's email address as a result.
 
 
*Open the model in Desktop Analytica.
 
*Add a variable with identifier <code>Acp_current_user</code> to the model and save it.
 
<br>
 
:[[File:ACP current user01.PNG]]
 
 
 
*When  you play the model in ACP, and evaluate Acp_current_user, the result is  the user e.g. <code>johndoe@gmail.com</code> {when playing an email invite the result will be "anonymous"}.
 
<br>
 
:[[File:ACP current user03.PNG]]
 
-->
 
== Embedded Tables and Graphs  ==
 
  
In ACP it is possible to display graphs and tables directly on the diagram. The '''CloudPlatformStyles ''' can be used to specify the region on the diagram to display these tables or graphs.
+
===Add Help menu item===
 +
*'''<code>Add_help_menu_option: Text|URL</code>'''  
 +
Adds another menu item, for example: <code>Add_help_menu_option: How to use this model...|https://www.lumina.com</code> adds a menu item to the help (?) menu with the text "How to use this model..." and opens the link when clicked.
  
More on [[ACP Rendering tables and graphs on the diagram |embedded tables and graphs]].
+
===Add download this model to the Close menu===
 +
*'''<code>save_menu_download: yes</code>'''
 +
This AcpStyle is controlled by a setting in the [[Customizing_an_ACP_server#The_acpConfig.json_file|AcpConfig.json]] file. On Lumina's acp.analytica.com server it is turned on.
 +
With this AcpStyle in the model, ''<code>"download this model"</code>'' is added to the close menu at the top right of the ACP GUI.
 +
When set, this will allow anyone to download the model - even a reviewer, and even from an email invite.
 +
*'''<code>save_menu_download: no</code>''' (default if not set)
 +
*'''<code>save_menu_download:Prompt_to_download_free</code>'''.  This adds a popup dialog with a download link and prompt to download the Analytica free installer.
 +
''This style cannot be set from the ACP Style library, since it would allow reviewers to change the style and download the model, even if the modeler does not  want to allow that.''
  
 
==See Also==
 
==See Also==
 
* [[ACP Style Library]]  
 
* [[ACP Style Library]]  
 
* [[media:ACP style library.ana]]
 
* [[media:ACP style library.ana]]
* [[Analytica Cloud Player]]
+
* [[Analytica Cloud Platform]]
 
* [[ACP Rendering tables and graphs on the diagram]]
 
* [[ACP Rendering tables and graphs on the diagram]]
 
* [[Putting ACP in a Web Page]]
 
* [[Putting ACP in a Web Page]]

Latest revision as of 14:21, 17 February 2025

<<Analytica Cloud Platform


Release:

4.6  •  5.0  •  5.1  •  5.2  •  5.3  •  5.4  •  6.0  •  6.1  •  6.2  •  6.3  •  6.4  •  6.5


ACP offers a wide variety of styles and options to control the look and functioning of the user interface. Many of these go beyond what is (currently) available in Desktop Analytica (DTA).

The easiest way to set these styles and options is to use the ACP Style Library, which you can load into your model within ACP from the hamburger menu. As you change styles in ACP, you can see their effects immediately.

If you use ACP Style Library you don't need to learn about the ACP Styles described below. The only reason to read the rest of this page is if you want to do something esoteric with AcpStyles, or use one of the few AcpStyles not accessible in the ACP_Style_Library.

You can also load the ACP Style Library in Analytica on the desktop from the Add Library...' option from the File menu. But, you won't be able to see the effects until you upload the model into ACP.

The styles and options are specified as keywords and tags in the AcpStyles attribute. Most styles and options apply to the whole Model and are specified in the AcpStyles attribute of the Model. When you want to specify special styles for individual modules or variables, you apply them to the ACPStyles attribute of the relevant object.

The easiest way to view and edit the AcpStyles attribute in Desktop Analytica is to use the Attribute panel. Select AcpStyles from the list of Attributes at the top of that panel. By default, AcpStyles is not shown in the Object window, so you first need to set it to be shown either with the right click menu in the Object window, or in the Attributes dialog.

The AcpStyles and their flags are not case sensitive.

When you put multiple flags in a AcpStyles attribute, put each flag on a separate line.

Model level styles

These styles apply to the entire model. You set them in the AcpStyles attribute for the Main Model. (They have no effect when set for a submodule.)

Navigation style

These Navigation_style options control how a user can view and access the module hierarchy:

  • Navigation_style: Outline -- Show an expandable tree of modules on the left of the ACP window, similar to the outline view in desktop Analytica (showing only modules not other objects). This is the default style when you upload a model with no ACP styles set or no Acp styles library embedded, or if you have not yet set the Navigation style in the Acp styles library. A navigation flag is not needed for this style, but if you want to explicitly set this style you can add Navigation_style: Outline to the top diagram's AcpStyles attribute.
  • Navigation_style: Top diagram only -- Show only the top diagram, with no Outline and no tabs. This lets you make a simple web application with a single UI page.


For the next two 'Tabbed application' styles, each module in the main model becomes a tab. The order of the tabs follows the sequence of the module nodes in the main diagram, from left to right then top to bottom.

  • Navigation_style: Top_tabs -- The main modules in the top model appear as a row of tabs across the top of the window. Click a tab to show the diagram for that module.
  • Navigation_style: Side_tabs -- The main modules in the top model appear as a column of tabs on the left of the window. Click a tab to show the diagram for that module.

We describe each in more detail below.

Outline Tree

By default, when using the Outline Navigation style, ACP shows an expandable outline tree of modules on the left hand side of the window, similar to the Outline view in Analytica on the desktop. This makes it easy to navigate a model with an extensive hierarchy of modules.

  • Show_outline: yes -- The default, and unecessary for Outline Navigation style. It is generally redundant with other Navigation styles since the tabs or hierarchy show the same information, and the Outline takes up screen space. But you can add it to the top diagram's AcpStyles attribute if you want to show the Outline tree with other Navigation styles.


Outline tree 6.0 01.png


Market model with
Outline Tree
  • show_outline: no -- When using the Acp Style library this is set by default for Navigation styles other than Outline. For small models, and most web apps, you may want to suppress the Outline view even when using the Outline Navigation style. Do this by inserting this text into the top diagram's AcpStyles attribute (See image below). (If a model has only one diagram, i.e. with no modules, it never shows the outline tree.)


Outline tree 6.0 02.png


Market model with
show_outline: no

Top Diagram Only

Set by adding navigation_style: top_diagram_only to the AcpStyles attribute of the top diagram. The Styles library will set the flag show_outline:no .

Tabbed Module Navigation

As an alternative to the Outline view, you can set the Navigation_style to use use a tabbed interface which is often more convenient and familiar for web applications. By default, the main model appears as the first tab. You can change this with the style show_as_tab:no described below.

There are two tabbed styles, Top_tabs, with a row of tabs across the top; and Side_tabs with a column of tabs down the side. Top_tabs works well if you have up to 5 to 8 modules in the main diagram (tabs), depending on the length of their titles and the width of the ACP window. If you have a lot of modules, or they have long titles, it may be better to use Side_tabs.

'Top tabs or side tabs.' The first tab displays the top level diagram, and the remaining tabs display the modules present on the top level diagram of the model. (The modules will not display on the diagram, so you need to tweak your diagram for playing in ACP so that it looks right without these present).

  • navigation_style: top_tabs -- This setting instructs ACP to use the 'Tabs across top' navigation style.

Top tabs 6.0 01.png

  • navigation_style: side_tabs -- This setting instructs ACP to use the 'Side tabs' navigation style. Side tabs work better than top tabs when there are more module nodes present.

Side tabs 6.0 01.png

Toolbar Tabs

  • show_tabs: no -- By default, with the Outline Navigation style. ACP shows navigation tabs for "Diagram", "Object", "Table", "Graph" along the top. Use this flag to hide those tabs. If you display the model inputs and outputs on the diagram -- using embedded tables and graphs on the diagram -- your users may not need those tabs. (You can also use show_tabs: yes to explicitly show the tabs in Outline and Top diagram only Navigation styles.)


Show tabs no 6.0 0.1.png


Market model with
show_tabs: no


Module hierarchy bar

Using tabbed navigation, ACP shows the model hierarchy in a bar at the top of the diagram by default. The model hierarchy header shows you where you are in a large model by listing the titles of the ancestor modules in which the current diagram is nested. You can click any ancestor to click up levels in the hierarchy. The Hierarchy Bar takes up much less screen real estate than the Outline Tree. ACP doesn't show the hierarchy bar when you are viewing a top level module, or if the module title is already in the selected tab.

Note that this setting is not based on a AcpStyles attribute, but rather on the Show module hierarchy check box in the model Preferences in Analytica. If you want to set this preference manually, with the model opened in Analytica, on the Edit menu, select Preference..., and check (or uncheck) the Show module hierarchy checkbox.

If you are using the ACP styles library, the Styles library will set this to the default setting automatically once you select a Navigation style. But you have the option of changing it if, for instance you want to show the Outline and the Hierarchy bar.

Auto zoom

  • auto_zoom_diagrams: yes -- ACP automatically zooms the UI to fit the browser window -- the most constraining of width or height so it retains the aspect ratio of the diagram. Works with zoom in and zoom out. Auto Zoom will allow a model to go down to 50% of its size or up to 200% of its size. If the model does not fit at 50% size, the window will show scroll bars. This Acp style has no effect if Use_top_diagram_size:Yes is present, you can use only one or the other. You can also set auto_zoom_diagrams: no which is the default. (This is a model level setting and is added to the top diagram of a model).

New to ACP Build 153 AcpStyles for controlling the max/min zoom when auto_zoom_diagram: yes is set. The default if these styles are not set is as above - 50% and 200%. The easiest way to set these is with the ACP_Style_Library - where the controls are in the Esoteric ACP styles module. This is available from the Hamburger menu in ACP. Note that in order to see this effect, the Browser window size needs to have the screen size pulldown menu set to Auto zoom as well.

  • zoom_min_percent: 75 (means that the minimum zoom level will be 75% or .75)
  • zoom_max_percent: 125 (means the that max zoom level will be 125% or 1.25)

Use top diagram size for all ACP windows

  • Use_top_diagram_size:Yes -- Sets the size of all diagrams based on the size of the diagram window of the top level when the model was last viewed in Desktop Analytica (in non-maximized mode). Use_top_diagram_size:No is the same as if the flag is not set, and is the default - the ACP diagram will use the entire browser window.

Show or hide the Dashboard Title and Model title

  • show_model_title: no -- Hide the title of the model, which appears by default in the top Teal bar.
  • show_diagram_title: yes -- Use to show the dashboard title at the top of the diagram. Or show_diagram_title: no to suppress the diagram title, but not really necessary because ACP does not show the diagram title by default.

Exclude diagram(s) from tabs

When using tabbed navigation, you can select those modules (from the top model diagram) that you want to appear as a tab in ACP. The default is for all to appear as tabs. You should use the Show modules as tabs choice menu in the ACP Navigation styles section of the ACP Style Library if you want to set this flag,, and if you also want to hide the modules corresponding to these tabs hidden, so that the model viewer cannot see them.

  • Optionally, Enter the text Show_as_tab: no in the AcpStyles attribute of the modules you don't wish to show as a tab. The modules themselves will not be hidden with this setting, only the tabs.

Tab color

When using Tabbed Navigation, you can use these flags to control how the color of the tabs display on your model in ACP. To use, add one of them to the AcpStyles attribute of the top level diagram of your model. They have no effect if added to a module other than the top diagram.

  • Tab_color: Default The default. Non-selected tabs are bluish white. The selected tab uses the background color for that diagram.
  • Tab_color: Background All tabs use their diagram background color, whether selected or not
  • Tab_color: Node The selected Tab uses its diagram background color; The other tabs use the color of their Module node (not their diagram background color). You can use this to change the color of the tabs by modifying their node color in an Analytica functions.

Model level styles for diagram nodes.

These model-level styles affect how all nodes are displayed in diagrams.

Node shadows and bevels

By default ACP displays nodes without shadows or bevels (for now) , so they look like this:

Nodes no shadow or bevel.png

Set this flag to show a drop shadow behind each node, giving a kind of 3D effect:

  • node_drop_shadow: yes
Nodes drop shadow.png

Set this flag to display a bevel border for each node, giving another kind of 3-D effect:

  • bevel_node_border: yes
Nodes beveled border.png

Node hover highlighting

By default, ACP displays a highlight -- a contrasting light rectangle behind a node -- when you move the cursor over the node:

Acp hover hl.png

You can switch it off by setting:

  • show_hover_highlight: No

Balloon Help

When you move the cursor over a node, ACP usually shows a "balloon" popup next to the node with the description of the node (if it has one) to help end users understand what its for, or what to enter for a user input. If the node has no description, the balloon help will not appear.

  • show_id_in_balloon: yes Use this flag to show each node's identifier below its title in the balloon -- unless the identifier and title are identical (except for spaces which are replaced by underscores). This flag goes in the AcpStyles of the model and apply to all nodes in the model.
  • show_hover_balloon: no
Insert this flag in the AcpStyles for a node, to suppress display of its balloon.

ACP styles inheritance

This is the order of inheritance for Acpstyles below that apply to tables and graphs. Styles at a higher level take precedence over the lower precedence styles. (Inheritance doesn't apply to the ACPstyles described above that apply only at the Model level.)

  1. Variable (includes Tall nodes): Acpstyles applied to an individual variable will take precedence over all other styles. A variable with a style of show_title:no will not show the title, even if the model level style is show_title:yes, and if that node shows it's result in a frame node the variable style will override the frame node style.
  2. Frame : An Acpstyle set for a frame node will affect any variable shown in that frame that doesn't have its own settings. These will also override any styles at the model level.
  3. Model ACP style defaults: Acpstyles that you can enter into the Acptyles attribute of the top diagram of your model. These will override the ACP defaults, and will be inherited by frame nodes and variables in the model that don't have their own Acpstyle.
  4. ACP style defaults for ACP: The default style ACP uses if you have no specific setting for that style. Eg for show_index_menus the default is fly-in and that is what will show if you don't enter a different show_index_menus: Acpstyle flag in the Acpstyle for the top diagram (model level) or for frame nodes or variables.

ACP Styles for tables and graphs

These styles affect how result graphs and tables are displayed in ACP, including in Tall nodes and ˞Frame nodes. They provide options not (yet) available in Desktop Analytica. ACP has default settings for these. You can override these settings for the entire model. You can also set them for ˞Frame nodes, which will apply to all results shown in the Frame and override the ACP and model level settings. And you can set these styles for individual variables, which will override any settings in the Model or Frame. As always, it's easiest to set the using the ACP_Style_library.

None of these styles apply to tab result views using the default Navigation_style: Outline.

Show or hide the Description

  • Show_description: nn' Where nn is a number between 0 and 100, where it uses up to nn% of the vertical space available to show the description. If that isn't enough to show the entire description, it shows a vertical scroll bar. Set nn = 0, if you don't want to show the description at all. Default if not mentioned, is one third, i.e. Show_description: 33. This style can be used at the model level, for frame nodes or for individual nodes, but controls whether or not the Description shows in tall nodes or Frame nodes.

Show or hide the Object view icon

  • Object_in_Frame:yes/no: With this style set, it shows an object view hover icon at the top right of a frame node or tall node when showing a graph or table view. Click this icon to show the object window view. The object view shows the Table and Graph hover icon to go back to the table or graph view. You can set Object_in_frame style at either the top level of the model or in an individual frame node, which overrides the top level setting. When working with tall nodes, you can set Object_in_frame style at the top level or in the original variable's ACP style setting, which overrides the top level setting.

Show or hide the title

  • Show_title: Set Show_title: yes to show or Show_title: no to stop showing the Title and units of a selected variable. This style can be used at the model level, for frame nodes or for individual nodes, but controls whether or not the Title and units show in Frame nodes or tall nodes.

Show or hide the Graph-Table icon

  • Show_graph_table_icon:no Hides the icon in the top right of a Result that lets you toggle between Graph and Table view. This applies to Frame nodes and tall nodes. This style can be used for the entire model, for frame nodes or for individual nodes . You set them in the AcpStyles attribute. Conversely, you can set Show_graph_table_icon:yes. This is the default so not usually necessary at the model level, but can be used in a frame node or variable to override the model default or override a frame node setting.

Show or hide the Uncertainty view menu

By default, in ACP, as in desktop Analytica, the Uncertainty views menu appears above each result graph or table to let you select Mid to display its deterministic value, or Mean, Probability distribution, and other ways to display a probabilistic value.

You can override this default behavior with this ACP style for the entire model, Frame nodes, or for individual variables. The Uncertainty view menu is always present in tab result views.

  • Show_uncertainty_view: No Never show the uncertainty menu in frame nodes or tall result nodes. Suitable for models with no probabilistic values, or if you want to fix a particular probabilistic view for each frame node or variable so that ACP users can't change it.
  • Show_uncertainty_view: Yes Always show the uncertainty menu even for variables that are not probabilistic, as in Desktop Analytica. This is the default and not normally necessary at the model level, but can be used to customize which frame nodes or variables to show the uncertainty view menu when the model level style is set to Show_uncertainty_view: No

Show or hide the Index menus and Pivoters/slicers

  • Show_index_menus: Fly-in By default (the same as if there is no show_index_menu: setting) the index menus are not shown in [nodes or tall nodes] (but slicers are), since often the modeler has already chosen the pivot they want to use. And because these menus take up valuable screen space. But if you hover over the frame node (or tall node) there is a fly-in pivoter control. If you click this it toggles - on or off - the visibility of the pivoters; allowing you to pivot the result table or graph and then close the pivoters to give you more space.
  • Show_index_menus: Yes If you do want to allow users to be able to pivot or change the slice of the table or graph, without using the fly-in, then use use show_index_menus:yes. Always present in tab result views.
  • Show_index_menus: No If show_index_menus:no is set then the indexes and pivoters will not show and there is no fly-in, but the slicers will still be present.
  • Show_index_menus: Not_even_slicers If you don't want to show any pivoters or slicers, you can set show_index_menus:Not_even_slicers.

Autocalc

In the ACP Style Library, Autocalc looks like a style you can set for a model, module or variable. It controls whether ACP evaluates each variable and shows its results automatically when you view a Diagram or tab showing the -- instead of the default Analytica behavior where the end user has to click on a Calc button to compute a result. With Autocalc on, a result in view also recomputes automatically when you change an input that influences it.

Autocalc is not actually an ACPStyle in ACP3. (It was in ACP1.) Autocalc is implemented using the Desktop Analytica functionality for Proactive_Evaluation.

Node Level Settings

These style flags and options apply to individual nodes (variables), rather than the model as a whole. So, you set these flags on the AcpStyles for selected objects (nodes).

Other node level flags

Prevent nodes from showing on the diagram

  • Show_Object: no

You can prevent nodes or modules from showing on the diagram of your model, by adding this flag to the AcpStyles attribute of the object you wish to hide. Once the model is shown in ACP the objects aren't visible.

Modifying ACP menus

Normally, ACP offers menus that appear when you press one of the three icons on the right of the top teal bar. These ACP styles let you modify these menus.

Hide the Save options

  • Hide_save_button: yes Set this model ACP style option to exclude the 'Save this model' and 'Save model as...' from the ACP Close menu. It prevents users from saving over your models or saving other versions.
  • This style cannot currently be set from the ACP style library, since it would allow users to show the save and save as menu options and then save changes even if the modeler does not want to allow it.

Remove Help menu items

These styles add menu items to or remove items from the help (?) menu if added to the AcpStyles of the top diagram of your model. For ACP installations on an intranet, these standard links may not be accessible. On the other hand you may want to offer a special help page for a particular model.

  • Remove_help_menu_options: Text

This style allows you to list one or more of the standard options to remove from the help (?) menu. Replace Text with one or more of the following: ACP_Online_docs, Analytica_Q_A_forum, Tech_support.

(Note: The help menu item Connection status cannot currently be removed).

Add Help menu item

  • Add_help_menu_option: Text|URL

Adds another menu item, for example: Add_help_menu_option: How to use this model...|https://www.lumina.com adds a menu item to the help (?) menu with the text "How to use this model..." and opens the link when clicked.

Add download this model to the Close menu

  • save_menu_download: yes

This AcpStyle is controlled by a setting in the AcpConfig.json file. On Lumina's acp.analytica.com server it is turned on. With this AcpStyle in the model, "download this model" is added to the close menu at the top right of the ACP GUI. When set, this will allow anyone to download the model - even a reviewer, and even from an email invite.

  • save_menu_download: no (default if not set)
  • save_menu_download:Prompt_to_download_free. This adds a popup dialog with a download link and prompt to download the Analytica free installer.

This style cannot be set from the ACP Style library, since it would allow reviewers to change the style and download the model, even if the modeler does not want to allow that.

See Also

Comments


Dpaine

47 months ago
Score 0

Autocalc was a combination of autorecalcresults and calc_on_open. They were in the diagram style section of this page, but I just commented them out since they do not work (yet) in ACP3/suan and I don't think we have any intention of including them, since proactively evaluate can I think replace the functionality. These are still mentioned in the style library wiki page, but I intend to remove it.

I'll put a link to the proactivelyevaluate page though, and I will add it to new DTA features in ACP with a link to its wiki page.

You are not allowed to post comments.