Mobile Development 10.11 | webMethods Mobile SuiteWeb Help | webMethods Mobile Development Help | Introduction to the Mobile Development User Interface | Mobile Development Perspective
 
Mobile Development Perspective
The Mobile Development perspective contains the views and editors needed to work with mobile applications.
Ant view
The Ant view is a standard Eclipse view. It shows Ant scripts that you can use for a mobile project.
Mobile Designer provides several Ant scripts that you use to perform various tasks for a mobile project. For example, you use an Ant task to build a project. The build Ant tasks compile your application code and package the application so that you can install it on a mobile device.
Jenkins Build Explorer view
The Jenkins Build Explorer view is a Mobile Development-specific view. It lists your Jenkins builds, their state, and the final binaries for iOS and Android. These binaries can be downloaded and installed on devices.
Mobile Explorer view
The Mobile Explorer view is a Mobile Development-specific view. It contains a subset of the information in the Package Explorer. The Mobile Explorer view displays information only for mobile projects. For each mobile project, the Mobile Explorer view displays:
*Root application
*Single, main window for the project
*Each view defined for the project
*Each dialog defined for the project
Use the Mobile Explorer view to navigate to the project information you want to view and work with in the Outline Editor. For example, if you want to work on one of the views in the project, you can navigate to that view in the Mobile Explorer view and display it in the Outline Editor so that you can edit the view.
Outline view
The Outline view is a standard Eclipse view. It shows previews for editors, such as the Outline Editor, the Asset Editor, and the App Icon Editor.
Package Explorer view
The Package Explorer is a standard Eclipse view. It shows a Java-specific view of your projects, including mobile projects.
The Package Explorer tree structure contains a top-level node for each mobile project. The name of the top-level node matches the name of the mobile project.
The Package Explorer allows access to all information in a project, including the application code, resource handler code, application resources, properties files, and information about the devices a project supports.
App Icon Editor
The App Icon Editor is a Mobile Development-specific editor that allows you to import and customize the app icon (icon displayed when an application starts) and launch screen (the first screen displayed).
ASL Editor
The ASL Editor is a Mobile Development-specific editor that allows you to configure Android styles.
Asset Editor
The Asset Editor is a Mobile Development-specific editor that allows you to create and customize an asset file. The asset file defines how an icon looks like, and Mobile Development creates different icon sizes based from this asset definition.
EML Editor
The EML Editor is a Mobile Development-specific editor that allows you to edit a project-specific data model.
Layout Builder
The Layout Builder is a Mobile Development-specific editor that is used to model constraint layouts.
Outline Editor
The Outline Editor is a Mobile Development-specific editor that will be shown when you add or display a mobile object. It shows an outline of the mobile project. The Outline Editor consists of the following:
*A Model section, which displays the tree structure, or outline, of the mobile project. It lists, for example, the window, views, and dialogs in the project. Child nodes of a window, view, or dialog list the user interface elements, such as buttons or text entry fields, that the window, view, or dialog contains. Additionally, the outline of the project lists the languages that the project supports.
*A Properties section, which displays the properties for the node that is selected in the Model section. Use the Properties section to view and edit properties.
*A palette, which lists all objects that can be added to the mobile project. To add an object, you drag it to the appropriate node in the Model section.