- Name for a general view that displays output from a running program. Some perspectives have their own consoles (e.g. C-Build Console, Builder Console).
- .csj file
- The .csj file is used during the code-signing process to configure your keystore to sign applications. It is provided by RIM and contains a list of signatures and your registration information. After you receive your ,csj registration files, you can configure your computer to create debug tokens. When you create a debug token, you specify the PIN for each tablet on which the token can be used. You can distribute the debug tokens you create to developers to install on those tablets, or install them yourself.
- .csk file
- The .csk file is the code signing key that is used to generate a unique, trusted developer certificate. It is provided by the signing authority and contains the unique password and PIN information that you entered when you requested the debug token.
- RDK file
- The RDK (RIM Developer Key) is provided by the RIM signing authority and is used to sign your application.
- PBDT file
- The PlayBook debug token (PBDT) file is used to generate debug tokens. If you work for a corporation, your organization would own the signing account. In this case, you need to obtain a debug token from your corporate lead for your device. Debug tokens allow you to deploy unsigned applications to your tablet device. Debug tokens are valid for 30 days. When a debug token expires, the BlackBerry Tablet OS no longer allows unsigned apps that rely on that token to run.
- debug tokens
- You can run unsigned applications on a BlackBerry tablet by using a debug token. Debug tokens allow you to separate the process of application creation and publication. A developer can create and test an application using a debug token, then deliver the application for signing and publication.
- drop cursors
- When you move a floating view over the workspace, the normal pointer changes into a different image to indicate where you can dock the view.
- Name of a tools project and platform developed by an
open consortium of vendors (www.eclipse.org),
including QNX Software Systems.
The QNX Developer Tools Suite consists of a set of special plugins integrated into the standard Eclipse framework.
- Visual components within the workbench that let you edit or browse a resource such as a file.
- Project Explorer
- One of the main views in the workbench, the Project Explorer shows you a hierarchical view of your available resources.
- A view that shows a hierarchy of items, as the functions and header files used in a C-language source file.
- Visual containers that define which views and editors appear in the workspace.
- In the context of the Eclipse Project, plugins are individual tools that seamlessly integrate into the Eclipse framework. QNX Software Systems and other vendors provide such plugins as part of their IDE offerings.
- A QNX perspective that lets you gather sample snapshots of a running process in order to examine areas where its performance can be improved. This perspective includes a Profiler view to see the processes selected for profiling.
- A collection of related resources (i.e. folders and files) for managing your work.
- In the context of the workbench, resources are the
various projects, folders, and files that you work with.
In the context of the QNX System Information Perspective, resources are the memory, CPU, and other system components available for a running process to use.
- A special section within a QNX buildfile containing the command lines to be executed by the OS image being generated.
- Eclipse term for the head branch in a CVS repository.
- The host is the computer where the IDE resides (e.g. Windows, Linux).
- Has two meanings:
As a software term, refers to the file that the make command examines and updates during a build process. Sometimes called a make target.
As a hardware term, refers to the Neutrino-based PC or embedded system that's connected to the host PC during cross-development.
- A view showing the resources or the specific lines within a file that you've marked for later attention.
- User interface.
- Alternate ways of presenting the information in your workbench. For example, in the QNX System Information perspective, you have several views available: Memory Information, Malloc Information, etc.
- The Eclipse UI consisting of perspectives, views, and editors for working with your resources.