This interfaces describes a model which encapsulates a workflow for navigating the contents of a vault. Navigation consists of a Parent entity and it's child content and methods to move up and down the content hierarchy
Gets the child content for the Parent entity that was navigated to. The Content loads in the background and will be available after the ContentLoaded event is fired.
Gets the hierarchy of the current Parent all the way up to the root Navigation object. The NavigationPath loads in the background and will be available after the NavigationPathLoaded event is fired.
Changes the data in the model to represent a new entity. The Content for the new entity is supplied and thus doesn't need to be loaded in a background thread.
After the ParentChanged notification is sent as a result of a Navigate, the model will begin to load the child content associated with the Parent. This event is fired when the Content is finished loading.
This event is fired when entities are update manually in the Content of the model. The event allows all views a chance to refresh their display to represent the new data.
After the ParentChanged notification is sent as a result of a Navigate, the model will begin to compute the NavigationPath. This event is fired when the computation is complete.