- Creating a PhoneGap Build account
- Exploring the HTML structure of an app
- Configuring your mobile device for development
- Building from Dreamweaver, Edge Code, or the command line
- Setting up a config.xml file
- Setting parameters and permissions
- Deploying on iOS or Android
Application command-line interfaces
Application programs (as opposed to operating systems) may also have command line interfaces.
An application program may support none, any, or all of these three major types of command line interface mechanisms:
- Parameters: Most operating systems support a means to pass additional information to a program when it is launched. When a program is launched from an OS command-line shell, additional text provided along with the program name is passed to the launched program.
- Interactive command-line sessions: After launch, a program may provide an operator with an independent means to enter commands in the form of text.
- OS inter-process communication: Most operating systems support means of inter-process communication (for example; standard streams or named pipes). Command lines from client processes may be redirected to a CLI program by one of these methods.
Some applications support only a CLI, presenting a CLI prompt to the user and acting upon command-lines as they are entered. Some examples of CLI-only applications are:
Some computer programs support both a CLI and a GUI. In some cases, a GUI is simply a wrapper around a separate CLI executable file. In other cases, a program may provide a CLI as an optional alternative to its GUI. Both interfaces do not always offer similar functionality. For example, MATLAB, a numerical analysis computer program, provides no GUI for some calculations, but the CLI can handle any calculation MATLAB supports.
Build My Site