T4DataEntry is a WPF project that uses T4 templates to generate XAML and backing C# for data entry purposes. Currently, it uses a SQLite database wrapped with sqlite-net.

To use, clone the project and add text files into the DOM folder to represent the database schema you want. Each text file represents a single table. Within each file, each row represents a column and currently takes the format {column name}:{c# type}[:optional modifiers] or #{meta tag}:{value}. For example, the contents of Company.txt is:

#order:2
CompanyId:Guid
*Name:string!
*StockSymbol:string?
Founded:DateTime

These values are explained as follows:

The composite of Name, StockSymbol is displayed in the user interface. For example, Microsoft, MSFT. See Display of Records.

After adding all relevant files, invoke the T4 template engine. Currently, this is most easily done by opening MainWindow.tt and MainWindowCs.tt and re-saving.

This will generate a functional MainWindow.xaml and MainWindowCs.cs that work together. You can then run the app and see one tab per table, each of which has a DataGrid to represent records in the database and data entry elements for each column:

A column definition can include optional additional parameters. Currently, the only such definition is PK to explicitly identify a primary key. This can be useful when a table uses a composite key. For example:

#order:3
PersonId:Guid:PK
CompanyId:Guid:PK
Title:string
OfficeNumber:int?

An employee, therefore, is defined by the composite primary key {PersonId, CompanyId}. As of now, sqlite-net does not currently support multi-column primary keys in its ORM design. T4DataEntry will, therefore, generate an appropriate SQL query for these scenarios:

public UserDB(string databaseFile = DatabaseFile) : base(databaseFile)
{
    CreateTable<Person>();
    CreateTable<Company>();
    Execute("create table if not exists \"Employee\" (\"PersonId\" varchar(36) not null, \"CompanyId\" varchar(36) not null, \"Title\" varchar not null, \"OfficeNumber\" integer, primary key (PersonId, CompanyId))");
    Execute("create table if not exists \"Tenure\" (\"PersonId\" varchar(36) not null, \"CompanyId\" varchar(36) not null, \"StartDate\" datetime not null, \"EndDate\" datetime, primary key (PersonId, CompanyId))");
    CreateTable<Car>();
    Commit();
}

Any row starting with # is considered a meta tag that defines some behavior for the table instead of specifying a column. The list of tags is currently:

• #order:{number} - Specifies the order in which the table appears. Conflicts are not resolved. Default is int.MaxValue, so tables with any order specified come before unspecified.
• #heights:{datagrid height},{input elements height} - Specifies the height of this table's DataGrid (listing existing rows) and the input elements (for editing existing/creating new records). The values are specified in integers and correspond to the WPF convention for such. Default is 1,1.
• #tostring:{simple|detailed} - Specifies how a table will be displayed when it is referenced by another. See Display of Records. Default is simple

Relevant notes on building your schema:

• Columns ending with "Id" are considered to be identifier columns that reference another table, {table name}Id
• In the case where an ID column matches its own table (eg, CompanyId within the Company table), it is treated as the primary key and is not currently editable. Primary keys can also be explicitly specified by adding the PK modifier to a column definition.
• Valid column types are string, string? (the same as TEXT NOT NULL), string! (a column with application-level validation enforcing non-empty text), int, int?, double, double?, Guid, Guid?, bool, bool?, DateTime, and DateTime?.
• FOREIGN KEY constraints are not currently added.

When displaying a record (typically in a DataGrid when one column references another), column names starting with * are used in the UI to give an object reference a displayable name. For example, if the Company table is defined as follows:

CompanyId:Guid
*Name:string
*StockSymbol:string
Founded:DateTime

Then any references to a Company in the UI will display the combination of these columns instead of the (likely incomprehensible) primary key itself. The display can be switched between "simple" (default) and "detailed" by using the meta tag (described above). For example, a Company may be displayed as Microsoft, MSFT (simple) or Company(Name=Microsoft, StockSymbol=MSFT) (detailed).

If no display columns are explicitly specified and a Name column is present, it will be used. If no Name column exists, then the primary key will be used (ie, Employee.CompanyId). If no primary key exists, then the underlying object representation (eg, T4DataEntry.Company) is used.