This is a first draft of how we'd like to deal with the user interface for events. Since every event can consist of many executables scripts, etc.. it's quite hard to provide an UI for it. So we decided that every event will have a XML file with this content:
- name - description of what this event does - description of every configurable option - option will have: attributes: - type: text, password, number (any others?) - name: name of the represented environment variable elements: - label: text to show in UI - empty: if the option can be empty (defaults to "no") - description a tooltip to show when move the mouse over the option widget... - others if you find anything anything else useful
example:
<name>Bugzilla</name> <description>Send the colelcted information to the Fedora bugzilla (you will need a bugzilla account to use this)</description> <options> <option type="text" name="bz_login"> <label>User name</label> <empty>no</empty> <description>Username to use to log into your bugzilla account</description> </option>
<option type="password" name="bz_password"> <label>Password</label> <empty>no</empty> <description>Password for your bugzilla account</description> </option> </options>
- these xml files will live in /usr/share/abrt/events/<EVENTS_NAME>.xml - the default values (like bz URL) for events will be stored in /etc/abrt/events/<EVENT_NAME>.conf - and can be also read from ~/.abrt/events/<EVENT_NAME>.conf - but not stored by any abrt application, this file will have to be provided by user if he don't want to use any of the options below: - gtk UI will store the settings in gnome-keyring - kde UI will store the settings in the kwallet - etc, ...