Configure bar-descriptor

The bar-descriptor.xml file is the BlackBerry application descriptor file.

This file specifies the parameters for identifying, installing, and launching native applications on the BlackBerry 10 OS. You can configure the appearance and behavior of your application by specifying XML elements and values in the bar-descriptor.xml file. If you create an XML configuration file in your IDE project, it's automatically included in your .bar file. If you package your application from the command line, be sure to specify the bar-descriptor.xml file when you run the blackberry-nativepackager tool.

The root element in the bar-descriptor.xml file is <qnx>. Nest all other XML elements within this element.

You can set capabilities in the bar-descriptor.xml file by setting options from the General page, Application page, Assets page, and Localization page, or by directly modifying the bar-descriptor.xml options on the Source page. The Capabilities editor lets you:
  • Specify the application name, author, icon, window transparency, and other properties into the bar-descriptor.xml file.
  • Select the assets to include in the package.
Validation for the bar-descriptor.xml file's content is available in two ways:
  • Problem identifiers in the Problems view that link to the XML elements in the Source page. These identifiers are created by a validation builder for BlackBerry projects.
  • Annotations in the Source editor are automatically generated as you edit and modify the content.

The presentation of annotations in the various pages of the BAR descriptor editor takes two different forms, according to the nature of the problem: bad data is annotated in place (for example, an unresolved asset in the Assets page that's missing data can result in an annotation of the editor heading), or a "2 problem(s) found" type of label at the top of the page with a tooltip enumerating the problems.

Incremental updates of your assets (.bar)

You can overwrite specific assets for a project on the target during the debugging process. These assets are the individual files that make up the .bar file, which include, but are not limited to, application binaries, images, media files, language packs, and other assets you might want to bundle into a .bar file. For example, while you test your application, you notice that a change is required. You won't need to package and deploy a large bundle. Note that the IDE doesn't ensure binary compatibility of the assets that you replace.

Last modified: 2013-12-21

comments powered by Disqus