Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
protogrid:locally_hide_ui_elements [2018-03-21 20:27] druprotogrid:locally_hide_ui_elements [2022-04-14 23:19] (current) dru
Line 1: Line 1:
-====== Locally Hide Ui Elements ======+====== Locally Hide UI Elements (aka "Demo Mode"======
  
-This article explains how to locally hide UI elements like notifications, [[protogrid:tableview|TableView]] actions or [[Card]] menu entries.+This article explains how to locally hide UI elements like [[notifications]], [[protogrid:tableview_actions|TableView actions]] or [[protogrid:card_menu|Card menu]] entries.
  
 You can use the [[protogrid:script_library|Client Script Library]] helper functions "locally_hide_elements" and "locally_unhide_elements" to hide/unhide specific UI elements. You can use the [[protogrid:script_library|Client Script Library]] helper functions "locally_hide_elements" and "locally_unhide_elements" to hide/unhide specific UI elements.
 +
 +Please note: These settings apply only to the UI and must not be used for safety-related purposes.
  
  
Line 9: Line 11:
 To reduce distractions for less experienced users you could add the following code to the bottom of a newly created [[protogrid:script_library|Client Script Library]]: To reduce distractions for less experienced users you could add the following code to the bottom of a newly created [[protogrid:script_library|Client Script Library]]:
 <code javascript> <code javascript>
-mod_csl_helpers().locally_hide_elements(["warning", "error", "export_csv"]);+mod_csl_helpers().locally_hide_elements(["warning", "error"]);
 </code> </code>
  
-Then create a [[protogrid:trigger| Trigger]] which refers to the above prepared [[protogrid:script_library|Client Script Library]] and place that [[protogrid:trigger| Trigger]] somewhere on your [[Default Card]]. This ensures that your hide settings immediately take effect in the browser of every logging in user.+Then create a [[protogrid:trigger| Trigger]] which refers to the above prepared [[protogrid:script_library|Client Script Library]] and place that [[protogrid:trigger| Trigger]] somewhere on your [[Default Card]]. This ensures that your hide settings immediately take effect in the browser of every user opening your application.
  
  
Line 19: Line 21:
 == Notification Bar == == Notification Bar ==
 <code javascript> <code javascript>
-"message"            // (blue notifications) +"message"            // (hides all blue notifications) 
-"warning"            // (yellow notifications) +"warning"            // (hides all yellow notifications) 
-"error"              // (red notifications)+"error"              // (hides red notifications
 +"support_chat"       // (hides the chat option at the bottom right)
 </code> </code>
 +
 +Note: Hidden notifications can still be viewed by clicking on the small hamburger menu in the upper right corner of Protogrid.
  
 == Card Menu == == Card Menu ==
 <code javascript> <code javascript>
-"open_proto"         // Open Proto +"open_proto"            // Open Proto 
-"print_card        // Print +"card_properties      // Show Properties 
-"card_properties   // Show Properties +"card_mutation_history" // Show Mutation History 
-"trash_single"       // Put to Trash +"trash_single"          // Put to Trash 
-"to_menu"            // Put Selected Into Menu ...+"to_menu"               // Put Selected Into Menu ...
 </code> </code>
  
Line 37: Line 42:
 "trash_multiple"     // Put Selected To Trash "trash_multiple"     // Put Selected To Trash
 "card_update"        // Update Selected "card_update"        // Update Selected
-"import_csv"         // Import Spreadsheet 
-"export_csv"         // Export Selected as Spreadsheet 
 </code> </code>
Print/export