The User Interface Extensibility Framework is largely event-driven; each module must register a callback function for the events it wishes to be notified about. There are a large number of events to which modules can subscribe. These events are raised as the user interacts with the user interface, or as events occur within the vault itself.

Reacting to events

There are numerous ways to register to be notified (section 3.2.4) when events occur within the User Interface Extensibility Framework. Our samples primarily use the IEvents.Register approach, as this allows multiple handlers to be registered for individual events.

function OnNewShellUI( shellUI )
{
	/// <summary>Executed by the UIX when a ShellUI module is started.</summary>
	/// <param name="shellUI" type="MFiles.ShellUI">The shell UI object which was created.</param>
	
	// This is the start point of a ShellUI module.

	// Register to be notified when a new normal shell frame (Event_NewNormalShellFrame) is created.
	// We use Event_NewNormalShellFrame rather than Event_NewShellFrame as this won't fire for history (etc.) dialogs.
	// ref: https://www.m-files.com/UI_Extensibility_Framework/index.html#Event_NewNormalShellFrame.html
	shellUI.Events.Register(
		Event_NewNormalShellFrame,
		function(shellFrame)
		{
			// The shell frame was created.
		} );
}

Often objects cannot be accessed until they are started; attempting to use them before this point will result in an error. In this case, register for the OnStarted event to be notified when the object can be used.

// Execute some code when the shell frame is created and available.

function OnNewShellUI( shellUI )
{
	/// <summary>Executed by the UIX when a ShellUI module is started.</summary>
	/// <param name="shellUI" type="MFiles.ShellUI">The shell UI object which was created.</param>
	
	// This is the start point of a ShellUI module.
	
	// Register to be notified when a new normal shell frame (Event_NewNormalShellFrame) is created.
	// We use Event_NewNormalShellFrame rather than Event_NewShellFrame as this won't fire for history (etc.) dialogs.
	// ref: https://www.m-files.com/UI_Extensibility_Framework/index.html#Event_NewNormalShellFrame.html
	shellUI.Events.Register(
		Event_NewNormalShellFrame,
		function(shellFrame)
		{
			// The shell frame was created but it cannot be used yet.
			// The following line would throw an exception ("The object cannot be accessed, because it is not ready."):
			// shellFrame.ShowMessage("A shell frame was created");

			// Register to be notified when the shell frame is started.
			shellFrame.Events.Register(
				Event_Started,
				function()
				{
					// The shell frame is now started and can be use.
					// Note: we are using the shellFrame from the outer function here.
					shellFrame.ShowMessage("A shell frame is available for use.");
				} );
		} );
}

Sometimes these nested registrations can lead to code lines getting excessively long. Alternatively, the code above could be written in a slightly different way:

// Execute some code when the shell frame is created and available.

function OnNewShellUI( shellUI )
{
	/// <summary>Executed by the UIX when a ShellUI module is started.</summary>
	/// <param name="shellUI" type="MFiles.ShellUI">The shell UI object which was created.</param>

	// This is the start point of a ShellUI module.

	
	// Register to be notified when a new normal shell frame (Event_NewNormalShellFrame) is created.
	// We use Event_NewNormalShellFrame rather than Event_NewShellFrame as this won't fire for history (etc.) dialogs.
	// ref: https://www.m-files.com/UI_Extensibility_Framework/index.html#Event_NewNormalShellFrame.html
	shellUI.Events.Register(
		Event_NewNormalShellFrame,
		handleNewShellFrame );
}

function handleNewShellFrame(shellFrame)
{
	/// <summary>Handles the OnNewNormalShellFrame event for an IShellUI.</summary>
	/// <param name="shellFrame" type="MFiles.ShellFrame">The shell frame object which was created.</param>

	// The shell frame was created but it cannot be used yet.
	// The following line would throw an exception ("The object cannot be accessed, because it is not ready."):
	// shellFrame.ShowMessage("A shell frame was created");

	// Register to be notified when the shell frame is started.
	// This time pass a reference to the function to call when the event is fired.
	shellFrame.Events.Register(
		Event_Started,
		getShellFrameStartedHandler(shellFrame) );
}

function getShellFrameStartedHandler(shellFrame)
{
	/// <summary>Returns a function that handles the OnStarted event for an IShellFrame.</summary>

	return function()
	{
		// The shell frame is now started and can be used.
		shellFrame.ShowMessage("A shell frame is available for use.");
	}
}

Module entry points

Modules must contain correctly-named methods to be informed when they been started. The method name varies according to the type of module being instantiated. Each method receives the main module object as a parameter:

ShellUI modules

function OnNewShellUI( shellUI )
{
	/// <summary>Executed by the UIX when a ShellUI module is started.</summary>
	/// <param name="shellUI" type="MFiles.ShellUI">The shell UI object which was created.</param>

	// This is the start point of a ShellUI module.
}

More information on ShellUI modules can be found here.

VaultUI modules

function OnNewVaultUI( vaultUI )
{
	/// <summary>Executed by the UIX when a VaultUI module is started.</summary>
	/// <param name="vaultUI" type="MFiles.VaultUI">The vault UI object which was created.</param>

	// This is the start point of a VaultUI module.
}

More information on VaultUI modules can be found here.

VaultCore modules

function OnNewVaultCore( vaultCore )
{
	/// <summary>Executed by the UIX when a VaultCore module is started.</summary>
	/// <param name="vaultCore" type="MFiles.VaultCore">The vault core object which was created.</param>

	// This is the start point of a VaultCore module.
} 

More information on VaultCore modules can be found here.

Dashboard entry points

Dashboards are user interfaces that are shown to the user as required. Dashboard content is held within HTML files which may reference external static content such as CSS files, JavaScript files or image files.

<!DOCTYPE html>
<html>
	<head>
		<title>Dashboard example</title>
		<script>
			function OnNewDashboard(dashboard)
			{
				/// <summary>Executed by the UIX when a dashboard is shown.</summary>
				/// <param name="dashboard" type="MFiles.Dashboard">Information about the dashboard being shown.</param>

				// This is the start point of a dashboard.
				dashboard.ShowMessage("The dashboard was started.");
			}
		</script>
	</head>
<body>
	The dashboard content goes here.
</body>
</html>

More information on dashboards can be found here.