Pebble url with home remoter how to#
Pebble url with home remoter code#

Get an EventSource object in the start method of the ALCL class that represents the source of the custom URL event:ĮventSource openURLEventSource = EventSourceFactory.getEventSource(EventSourceFactory.OPEN_URL_EVENT_SOURCE_NAME) Ĭreate and add an object of the custom URL event listener class to the event source: Register an application lifecycle event listener (ALCL) class.įor more information, see Chapter 11, 'Using Lifecycle Listeners in MAF Applications.' For more information, see the Event class in Oracle Fusion Middleware Java API Reference for Oracle Mobile Application Framework. To get the application state at the time of URL event, use the Event.getApplicationState method. To get URL payload, use the Event.getPayload method. The Event object can be used to retrieve useful information about URL payload and the application state. Override and implement the onMessage(Event e) method that gets called with the URL that is used to invoke the MAF mobile application. For more information on the .EventListener interface, see Oracle Fusion Middleware Java API Reference for Oracle Mobile Application Framework. This class must implement the .EventListener interface that defines an event listener. In the application controller project, create a custom URL event listener class (for example, CustomURLEventListener) that is notified of the URL. The URL with this scheme can then be used to invoke the MAF mobile application and pass data to it. You configure this URL scheme in the overview editor of the maf-application.xml file using the URL Scheme field. To invoke a MAF mobile application from another application, perform the following steps: See also Section 13.3, 'Creating and Using UI Components.'Ģ0.4 Invoking MAF Applications Using a Custom URL SchemeĪ custom URL scheme can be used to invoke a native application from other applications. In such a case, you can create an anchor tag or an component with a url attribute for the component that points outside of the application, such as the url attribute in in the following example. Such pages would otherwise open in the device browser instead of the MAF web view. Use a whitelist for pages that contain links to URLs that point to another domain. See Section B.1, 'Using MAF APIs to Create a Custom HTML Springboard Application Feature' for more information.Ģ0.2 Creating Whitelists for Application Components

Pebble url with home remoter code#

MAF then reads the file from the file system in the container code and sends the local file content to the web view. When the container code reads /~maf.device~/ in the requested URL it then resolves the URL locally and treats it as a native request.

Pebble url with home remoter how to#

The following example shows how to include base.js from a device HTML page or from a remote HTML page: This approach works in both remote as well as local HTML pages and is the best way to include base.js in an HTML feature (regardless of where it is being served from). In order to access MAF or Cordova JavaScript APIs from within a server-rendered web application (for example, getting and setting EL expressions, getting information about the application, taking a photo, or accessing contacts), you must use the virtual path /~maf.device~/ when including base.js so that the browser will identify the request as being for a MAF resource and not for the remote server. You use a JavaScript tag that references the base.js libraries to enable this access.

Remote URL applications that open within the MAF web view use Apache Cordova JavaScript APIs to access device features and MAF JavaScript APIs to access the MAF container services. 20.1.2 Enabling Remote Applications to Access Container Services