Navigation and pre-app configuration

Adding a navigation entry

Navigation entries for apps can be created by adding a navigation section to theappinfo/info.xml file, containing the name, order and route the navigation entry should link to. For details on the XML schema check theapp store documentation.

<navigation><name>MyApp</name><route>myapp.page.index</route><order>0</order></navigation>

Initialization events

Often apps do not need to load their JavaScript and CSS on every page. For thispurpose there are several events emitted that an app can act upon.

  • OCA\Files::loadAdditionalScripts (string): loaded on the files list page

  • OCA\Files_Sharing::loadAdditionalScripts (string): loaded on the public sharing page

  • OCA\Files_Sharing::loadAdditionalScripts::publicShareAuth (string): loaded on the public share authentication page

  • OCP\AppFramework\Http\TemplateResponse::EVENT_LOAD_ADDITIONAL_SCRIPTS (constant): loaded when a template response is finished

  • OCP\AppFramework\Http\TemplateResponse::EVENT_LOAD_ADDITIONAL_SCRIPTS_LOGGEDIN (constant): loaded when a template response is finished for a logged in user

You can subscribe listeners to these events in thebootstrapping code of the app. See theevents documentation for more details on the event dispatcher and available events.