<rim:filter>

Syntax:

<rim:filter>
    <rim:action>string</rim:action>
    <rim:mime-type>mime_type</rim:mime-type>
    <rim:property var=["exts" | "uris"] value="string" />
</rim:filter>

Description

The <rim:filter> element specifies the target filter. For each target, filters must be declared to describe the kinds of unbound invocation they support. Each filter defines the associated action performed for MIME types that match the filter. Clients perform unbound invocation by sending the invocation without specifying a target. Unbound invocations should generally provide an action, but must provide either a MIME type, URI, or both.

Occurrences:

Zero or more.

Parent elements

<rim:invoke-target>

Child elements:

Name Occurrences

<rim:action>

zero or more

<rim:mime-type>

one or none

<rim:property>

one

Content:

None.

Attributes:

None.

Example

Registering bound and unbound invocations

<widget xmlns:rim="http://www.blackberry.com/ns/widgets">
.
.
.
    <platform name="blackberry10">
        <rim:invoke-target id="com.domain.subdomain.appname.app">
            <rim:type>APPLICATION</type>
            <rim:filter>
                <rim:action>bb.action.OPEN</rim:action>
                <rim:action>bb.action.SET</rim:action>
                <rim:mime-type>text/*</rim:mime-type>
                <rim:property var="exts" value="bmp,css,html,js" />
                <rim:property var="uris" value="data://local,file://" />
            </rim:filter>
        </rim:invoke-target>
    </platform>
</widget>

Last modified: 2015-04-16



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus