A Standard for Application Starters
Most X users start applications from an X terminal. To do this, you must know the names of the programs, pass parameters each time you run them and include the programs in your search path.
Instead of calling applications from the terminal, you can use an application starter, a program that shows a list or menu of installed applications and lets you choose the one to start. Some starters show pretty icons and are very appealing with features like clocks, load meters, etc.
The problem is that each starter has a different way of describing the list of installed applications. Usually, this information is written in a text file in some format. For example, the starter of FVWM reads the .fvwmrc file for this information. Other window managers (WM) use different formats and files. If you use various WMs, things can get a bit messy.
Creating a standard format, location and name for application starters simplifies the process of creating, changing and exchanging information. Another advantage is in program installation. The installation process can read this file (open format and location) and automatically add the necessary entries to access the installed components. For example, when installing StarOffice, it would be nice if a group called StarOffice was created automatically with scalc, swrite and the rest.
This article proposes a standard format and a standard location for this application starter file and presents QStart, a starter which I have written (using the Qt Toolkit) in this format.
The file, plain ASCII, consists of two parts: configuration parameters and menu definition.
The first part is used to define parameters, such as the directory in which icons are located. Each line starts with a reserved keyword, followed by the necessary parameters separated by a semicolon:
Only one standard reserved word, IconDir dir, is defined in which dir is the directory where the starter searches for the icons referred to in the Menu Definition.
Other reserved words can be added for different starters. For QStart, I have defined one more word (see next section).
As an example, the next lines can be used to configure QStart to search the icons in /usr/local/icons and place the button, which pops up the menu, at position 0,0 of the screen.
IconDir /usr/local/icons Position 0;0
To avoid future problems, consider carefully whether to add new reserved words. My idea with standard words is that these are words which are absolutely necessary to any application starter.
As new starters arrive, new words will appear. It might be a good idea to use generic words. Here are some ideas:
ConfigFile file: define a specific file for extra, specific configuration.
Show elem1;elem2;...: show a clock or the work areas in the starter, for example Show Clock;WorkArea;IconsOnly.
Style style: use a different style to show the list of applications, for example Style Modern.
In order to keep track of future development, I have mounted a site at http://w3.ualg.pt/~ranasta/starter/ to centralize all related information.
The second part is the menu definition with the same syntax: a reserved word at the start of the line, followed by the parameters separated by a semicolon. All the applications are defined inside groups or menus. The main menu has the name “Main” and is the starting point. The menu name, or id, should be interpreted in a case insensitive manner; that is, writing “Main”, “MAIN” or “main” should have the same effect. The reserved words should be interpreted in the same manner. Starting and ending a menu definition are the reserved words Menu and End.
Here, id is the name of the menu for internal identification; the menu with an id of main is the starting point. title is the title of the menu and icon is the icon file name.
Between Menu and End are menu items:
Separator: draw a separator, normally a horizontal line.
Text text: draw the text.
Image filename: draw the image stored in filename.
Program text;icon;command: an application. text is the text that appears on the menu entry; icon is the associated icon; command is the command invoked when this option is called.
SubMenu id: an entry point to menu id. The title and icon of the menu id should appear as data to this entry.
Two examples of Menu blocks are shown here:
Menu Main;Applications;apps.xbm Program Terminal;xterm.xbm;xterm Program Editor;edit.xmb;nedit Separator Text Groups SubMenu Graphics End Menu Graphics;Graphics;graph.xbm Text Image Program GIMP;gimp.xbm;gimp Program Paint;paint.xbm;paint Separator Text Draw Program tgif;tgif.xbm;tgif End
|Alice, the Turtle of the Modern Age||Mar 07, 2014|
|Using Django and MongoDB to Build a Blog||Mar 05, 2014|
|What virtualization solution do you use/manage at work?||Mar 04, 2014|
|Our Assignment||Mar 04, 2014|
|March 2014 Issue of Linux Journal: 20 Years of Linux Journal||Mar 03, 2014|
|Have Resume - Will Travel||Feb 28, 2014|
- You have to be careful there
1 week 4 days ago
- Wonder when LJ is going to
1 week 4 days ago
- Puerto Rico Free Software
1 week 5 days ago
2 weeks 3 hours ago
- I hate voice commands
2 weeks 17 hours ago
- usabilty --- AGAIN with this nonsense
2 weeks 19 hours ago
- Don't make excuses
2 weeks 22 hours ago
- Sorry to let you know, but
2 weeks 23 hours ago
- Ridiculous statement. Not a
2 weeks 1 day ago
2 weeks 2 days ago