----- Original Message -----
From: "Jamal Mazrui" <[log in to unmask]>
To: <[log in to unmask]>; <[log in to unmask]>;
<[log in to unmask]>; <[log in to unmask]>; <[log in to unmask]>;
<[log in to unmask]>; <[log in to unmask]>; <[log in to unmask]>;
<[log in to unmask]>
Sent: Thursday, February 23, 2006 12:25 PM
Subject: Introducing DbDialog: an open source, accessible database manager
(fwd)
>
>
> ---------- Forwarded message ----------
> Date: Thu, 23 Feb 2006 12:13:49 -0500 (EST)
> From: Jamal Mazrui <[log in to unmask]>
> Reply-To: [log in to unmask]
> To: [log in to unmask]
> Subject: Introducing DbDialog: an open source, accessible database
> manager
>
> Now available at
> http://www.empowermentzone.com/dbdsetup.exe
>
> Since developing database applications under DOS in the early 1990s, I
> have had a goal of developing them under Windows. Thus, I am excited to
> announce DbDialog: a free, open source, and accessible database manager.
> Since this is its initial release, I am posting the documentation below to
> help readers decide whether it is worth trying.
>
> I welcome feedback and contributions toward the improvement of DbDialog.
> Jamal
>
>
> DBDialog
> Copyright 2006 by Jamal Mazrui
>
> Description
> DbDialog is an open source, accessible database manager. It supports
> tables of records in Microsoft Access 2000 format. Once a table is
> defined, records may be created, modified, browsed, searched, and output
> in an efficient and accessible manner.
>
> Installation
> The installation program for DbDialog is called dbdsetup.exe. When
> executed, it prompts for an installation folder for the program. The
> default folder is
> C:\Program Files\DbDialog
> The installation process creates a program group for DbDialog on the
> Windows start menu, containing choices to launch DbDialog, read
> Documentation for DbDialog, and uninstall DbDialog. Also created is a
> desktop shortcut with an associated hot key, enabling DbDialog to be
> launched by pressing Control+Alt+D.
>
> Three Regions
> As its name implies, DbDialog is oriented around a single, main dialog for
> most operations. This dialog is divided into three major regions from
> left to right, corresponding to action buttons, input fields, and the
> record list. At the top of each region is an associated heading.
>
> Action Buttons
> The ACTION heading is in the upper left corner of the dialog. Below it is
> an alphabetized series of about 20 buttons, one under the other, until
> near the bottom of the dialog. The number of buttons may seem
> overwhelming at first, but they are named in a mnemonic manner, and may be
> navigated easily with either the Tab/Shift+Tab or Down/UpArrow keys As
> one learns the buttons, they may be invoked more directly and efficiently
> by pressing Alt plus the initial letter of the name, e.g., Alt+C for the
> button to Create a new record.
>
> The complete series of buttons is as follows: Action, Beginning, Create,
> Delete, End, Filter, Go To, Help, Index, Jump, List, Modify, Next, Output,
> Previous, Quit, Repeat Jump, Select, Tag, Untag, View, /Tag All, and
> \Untag All. Note that the first button is Action. It serves as both a
> button and the heading for the region of action buttons. When invoked, it
> moves focus to the start of the series of action buttons from other parts
> of the dialog. Also note that a minor departure from initial letter
> invocation of buttons--though still fairly mnemonic--is the use of Alt+/
> to tag all records or Alt+\ to untag them.
>
> Input Fields
> The central region of the dialog contains a series of input fields
> corresponding to a single record in the current database table. Each
> field is on a line by itself with an associated label to its left. By
> default, the input fields are in a display mode and the heading for the
> region is VIEW. Depending on the action button invoked, this mode may be
> changed to CREATE, MODIFY, or another that permits you to type in the
> fields.
>
> DBDialog works with any Microsoft Access table that has some structural
> constraints (explained later). Upon installation, the Contact table is
> the default. It is intended to capture almost all regularly occuring data
> items that one would store about an individual or organization. The many
> fields have been named such that each has a unique initial letter. Just
> like with the action buttons, this naming technique permits each field to
> be accessed directly by pressing its initial letter in combination with
> the Alt key.
>
> For the Contact table, the series of input fields is as follows: Title,
> First Name, Middle Name, Last Name, Job, Enterprise, Address1, Address2,
> City, State, Zip, Nation, Office Phone, Home Phone, Wireless Phone,
> Business Email, Personal Email, URL, Date of Birth, Gender, and Extra
> Info. Some minor, though still mnemonic departures from initial letter
> invocation are Alt+1 for Address1, Alt+2 for Address2, and Alt+X for Extra
> Info. The latter field is a multi-line edit field for storing any amount
> of extra information about the contact.
>
> Record List
> The heading for the region on the right of the dialog is LIST. Below it
> is a list box containing summary information for each record of the table.
> Each record displays the same selection of fields, ones that are most
> likely to identify the record. The left-most field is always Tagged,
> indicating whether the record is currently tagged by the presence or
> absence of the asterisk (*) character. By default, the Contact table then
> shows Last Name, First Name, and Enterprise (enterprise is a synonym for
> company or organization, whose initial letters are already being used by
> other fields).
>
> The record list is a standard list box that supports navigation by
> Down/UPArrow, PageDown/Up, and End/Home as expected. In addition, some
> action buttons perform similar navigation, such as Alt+B for Next, Alt+P
> for Previous, Alt+E for End, and Alt+B for Beginning.
>
> Remaining Controls
> Below the input fields near the bottom of the dialog are the pair of
> buttons: OK and Cancel. These are used to confirm or cancel a mode of
> operation such as creating or modifying a record. They may be reached via
> tab navigation, or invoked by pressing Enter for OK or Escape for Cancel.
> In either case, the VIEW mode is activated again, and focus is moved to
> the current record in the list box.
>
> The status bar spans the width of the dialog along the bottom. It
> displays tracking-related data about the current record that DbDialog
> assigns automatically. This data is the unique numeric ID of the record,
> followed by its original creation date, and then the date it was last
> modified. Dates in DBDialog are formatted as a four digit year, two digit
> month, and two digit day delimited by a forward slash (/), e.g.,
> 2006/02/23.
>
> Jump and Repeat Jump
> Press Alt+J to jump to a particular record based on a string of characters
> in any of its fields, regardless of case. For example, respond to the
> input box by typing "Smith" in order to jump to the first record
> containing this word. If found, focus is placed on this record in the
> list box. If the record is not what you want, press Alt+J and then Enter
> to accept the previous jump string and move to the next matching record.
> Alternatively, press Alt+R to repeat the jump command.
>
> Setting a Filter
> Another way of focusing on records with certain text is by setting a
> filter. Pressing Alt+F lets you choose a filter method: Fields, Reverse,
> Tagged, Untagged, and Clear. For the Fields choice, press F, or just
> Enter since this button is the default. The heading of the input fields
> region changes to FILTER, and focus is moved to the first field--Title in
> the case of the Contact table. You could type a title such as Mr., Ms.,
> or Dr if that is what you want to match. You navigate to the fields of
> interest either with Tab or the Alt letter combination that accesses the
> field directly.
>
> Press Enter to confirm the input, and then DbDialog will set a filter
> containing only records with matching values. The text must match
> completely, but it is not case sensitive. So, if you had entered "XYZ
> Corporation" in the Enterprise field and "U.S" in the Nation field, the
> only records appearing in the list box would be contacts who work for XYZ
> Corporation in the U.S.
>
> If you pressed Alt+F again and chose the Reverse button instead, the
> filter would show everyone except those at XYZ Corporation in the U.S.
> The Tag or Untagged filter choices show only tagged or untagged records,
> respectively. The Clear choice clears any filter, showing all records in
> the table.
>
> Setting an Index
> By default, the Contact table shows records in order by Last Name, First
> Name, and Enterprise. Thus, Jane Doe would appear before John Doe, and
> John Doe at UVW Corporation would appear before John Doe at XYZ
> Corporation. You can change the order by setting a different index for
> the table.
>
> An index is specified with a prioritized sequence of field names. Press
> Alt+I to enter the mode for specifying these fields. Navigate to the
> first priority field and type the number 1 in it. Then type 2 in the
> second priority field, and so on. Press Enter to confirm the field
> sequence, and DbDialog will show records in the new order.
>
> Selecting Fields to Display
> Suppose you want to examine other fields in the list of records. Press
> Alt+S to enter SELECT mode. Similar to INDEX mode, you type numpers
> indicating the sequence of fields to be used. If you type 1 for Nation, 2
> for Zip, 3 for Last Name, and then press Enter, DbDialog will show those
> fields in the record list--preceded by the Tagged field.
>
> Tagging and Untagging
> If you press Alt+T to tag a record in the list, DbDialog places an
> asterisk to its left, and then automatically moves focus to the next
> record. Similarly, Untag makes the Tagged indicator blank, and then moves
> to the next record.
>
> Output
> Press Alt+O to output the current list of records to the clipboard. You
> can then paste the information into another application such as a word
> processor document or email message. The first line of output contains
> the field names that correspond to the Select command in effect.
> Subsequent lines are in the order corresponding to the Index command, and
> those chosen correspond to the Filter command.
>
> Going to Another Table
> Press Alt+G to go to another table. DbDialog presents a list of those
> configured. The default installation has two other tables: Events and
> Albums. These tables are managed by the user in the same ways, and in
> fact, use the same programming code to do so.
>
> The Events table contains the following fields: Topic, Begin Date, Start
> Time, End Date, Finish Time, Location, Contact, and Extra Info. The
> Albums table contains the following fields: Title, Artist, Publisher,
> Date, and Extra Info. Although the Contact table was designed with
> comprehensive attention to data requirements, the Events and Albums tables
> were designed primarily to illustrate management of diffent tables with
> the same user interface. The Events table, for example, is not intended
> to replace a dedicated calendering program.
>
> Configuring New Tables
> At this time, DBDialog does not offer a convenient mechanism for defining
> new tables. Instead, one has to use Microsoft Access or another program
> that can define Microsoft Access tables. Within Microsoft Access, this
> task is generally accessible with a screen reader.
>
> In Microsoft Access, press Control+O to open the DbDialog.mdb database,
> located by default at
> C:\Program Files\DbDialog\DbDialog.mdb
> Choose the option to create a new table in design view. The first fiew
> fields should be defined as Tagged (text 1), Created (text 10), Modified
> (text 10), and ID (autonumber). Press F6 to toggle between the page for
> field name and type, and that for size and other attributes.
>
> The last field may have any name, but should have a type of memo. Up to 20
> intervening fields may be defined with a type of text, and any name or
> size. Press Control+S to save the table structure, and give it the
> desired name when prompted.
>
> Now configure additional table settings in the DbDialog.ini file, located
> by default at
> C:\Program Files\DbDialog\DbDialog.ini
> Using any text editor, add a new section to the file based on that of an
> existing table, e.g., via copy and paste. Change settings for the new
> table, including the window title, list of field labels, select fields,
> index order, and filter condition. When configured, the table is presented
> as a choice with the Go To command.
>
> Miscellaneous Tips
> When focus is in the region of action buttons, pressing the Alt modifier
> key is not actually necessary to invoke a button--the invocation letter
> can be pressed by itself. If focus is on the record list, however,
> pressing Alt is necessary because the list box processes keystrokes unless
> bypassed via the Alt modifier.
>
> Since the record list is a standard list box, it supports initial
> character navigation. To indicate tagged status, an asterisk or space is
> always the initial character of a record in the list, so pressing asterisk
> will move to the next tagged record, and Space will move to the next
> untagged one.
>
> When focus is in the record list, the region of input fields displays data
> for the current record in the list. The controls in the region are
> disabled, however, so they are not visited in the tab navigation sequence.
> You can press Alt+V to enter the region in VIEW mode. Although you are
> not blocked from typing into the fields, no data will be saved in this
> mode. If focus is in the record list, you can also enter VIEW mode by
> pressing Enter. Thus, pressing Enter toggles between the record list and
> VIEW mode.
>
> Development Notes
> For the technically curious, I developed DbDialog with the AutoIt
> programming language from
> http://AutoItScript.com
> The manipulation of Microsoft Access tables is done via an API called
> ActiveX Data Objects (ADO). Most Windows installations already include
> ADO, but the latest, 2.8 version may also be freely downloaded from
> http://microsoft.com/data
>
> Located in the program folder, the complete source code for DbDialog is in
> the file DbDialog.au3. Also used is the file LbC.au3: the function
> library I developed called Layout by Code. Documented in the file
> LbC.txt, this library is public domain--any use permitted. While also
> open source, the file DbDialog.au3 is covered by the GNU General Public
> License in the file gpl.txt, also explained at
> http://gnu.org/copyleft/gpl.html
>
> I welcome feedback, which will help DbDialog and LbC improve over time.
> The latest version of the package is available at
> http://www.EmpowermentZone.com/dbdsetup.exe
>
> Jamal Mazrui
> [log in to unmask]
> February 23, 2006
>
> _____________________________________________________________
> To leave this list, send a blank message to
> [log in to unmask]
> For information about this list, visit
> http://blindprogramming.com/mailman/listinfo/programming_blindprogramming.com
> For problems with the list, email [log in to unmask]
> Information about all of our lists:
> http://blindprogramming.com/mailman/listinfo
> Other blindness lists:
> http://www.visionrx.com/library/resources/resource_int1.asp
> Web site address: http://www.BlindProgramming.com
VICUG-L is the Visually Impaired Computer User Group List.
To join or leave the list, send a message to
[log in to unmask] In the body of the message, simply type
"subscribe vicug-l" or "unsubscribe vicug-l" without the quotations.
VICUG-L is archived on the World Wide Web at
http://listserv.icors.org/archives/vicug-l.html
|
