The tabular view

This is what the tabular view can look like for example:

How do I get the parts above the table?

You'll have to create most of them by hand. The example application can give you ideas how to do that, or you just copy it.

The navigation bar is created by hand. I once had a function that did it from all tables in the data dictionsary, but since then PHPDbEditTk has grown into a lot of uses, so that most of the tables would not be wanted in a navigation bar. I dropped the idea. It should be fairly simple to accomplish that however with extra code anyway.

The messages are created by the genericadmin class and can not be changed yet with an interface (only if you change them in the code). However, you can change the position where they appear in the template rowblock.tpl, which comes in the sample application.

The "Actions" links are created by hand. I cannot come up with others than insert/edit/delete/detail anyway for the moment. I do not plan a function to create them yet.

The Filters are created in a loop and use the filter functionality of the gadmfilter url variable. There is also much more detailed filter functionality available. Check out the Filterblock

The paging links are created in a loop as well. The handle_request() function supports paging of records on the database side, but there is nothing to create different blocks for the number of pages and the links to each page yet.

Colors of the rows

There are three values at table level, which control the coloring of the table rows. The values for the odd, even and highlighted row color each get assigned to placeholders in the template.
"coloring" => array( 
  "row_odd" => '#FFFFFF', 
  "row_even" => '#e5e5e5',
  "row_highlight" => '#FFE2B3'
You can of course use CSS class names or anything else, which will be used in the template.

Renaming the links

The text of the links for "Detail", "Edit" and "Delete" can be changed or replaced by a picture. They can also be omitted from each table separately through the data dictionary: The following block will of links will define the text in german:
"changetext" => "Aendern",
"deletetext" => "Loeschen",
"detailtext" => "Detail",
You can also omit each of the links by using on of these lines:
"nochangebutton" => "yes",
"nodeletebutton" => "yes",
"nodetailbutton" => "yes",
Note: PHPDBEditTk only looks for the entry in the array to omit the link. It doesn't matter, if you have yes or any other text as a value of the array, the link will be omitted. If you don't want it to be omitted, you have to delete or comment the whole line. This is due to the crude, but effective way how the data dictionary is stored - in an array. I may write an interface to the data dictionary later, I don't see the point for now.

Omitting fields from the table

You can omit a field from the table by using
"fields" => array(
  "band_code" => array(
  "omitintable" => "yes",
The same rules apply as for the Edit/ Detail/ Delete links.

How can I format a field

You can do any kind of fancy formatting by attaching a function to a field in the table view. Please read more in the section about attached functions. This section also deals with automatically displaying date/time values, looking up values from other tables (foreign keys) and enumerations.