Prior to
The Graphic Editor supports two client-side, Px Target Media technologies:
The Graphic Editor advises you if you use a feature in a widget that is not supported by the target technology.
Consider carefully the basic capabilities and limitations of each technology. Obviously, a mobile phone is limited as to what it can usably display when compared to a graphic viewed in a web browser running on a computer. Keep this in mind, and test your views in all target media as you develop them.
The Niagara Graphics Guide documents in detail the capabilities of Hx and Px graphics. The Niagara Video Framework Guide documents the videoDriver module and palette.
Configuring a graphical representation of a facility begins by hiring a graphics artist to create a set of three-dimensional images to represent the building, including all areas, such as the parking lot or garage, to be monitored. The images should be readily recognizable as belonging to the facility, looking down from above each floor.

The screen capture shows an image of a single floor in a building with overlaid controls for visually monitoring access control.
The general process of creating presentation views for access control follows these general steps:
Creating a view sets up a canvas on which to construct a representation of your facility. This view establishes a relationship between a Px file and one or more components of various types, such as folders, doors and readers.
A widget is a graphic visualization of an access component. You add widgets to the canvas.
Data binding passes data collected from the access components to the widgets. These bound data objects animate (update) the widgets in real time.
A .nav file sets up a customized tree structure so that users can easily access your views. You edit the .nav file using the Nav File Editor and assign a particular nav file to a user in the user’s profile (using the User Manager view).
Reports display and deliver data to online views, printed pages, and for distribution via email.