I have been participating in building some sites in the past that where completely driven by metadata from the database both from system tables and from extra added meta data for tables and columns.
One table for each table UI representation and one table for each column representations (one table can be represented one or many times as list, detail...).
With the data from the tables the webform/list/detail was genereted with the controls wanted, in the correct order with the correct controltype and so on.
No compilation was needed if a table was added/changed, just meta data in the tables.

I am trying to see how this is going to be implemeted with the Dynamic Data pattern.
I like all this new stuff and want reinvent the same dynamic application once more but with new patterns

Anyone going in that direction?

Dynamic Data (DD) is the opposite of what you describe. The UI is in large part inferred from the data model (a static snapshot). You can annotate the data model to get different UI's. If you want to change a boolean filter from the default of check box to radio, you would annotate the entity partial class or change the filter (to make the change on the entire scaffold). That doesn't stop you from fetching data at run time to make decisions, but that is not the general approach of DD.

I'll post some links to getting started (when the MSDN blog server is back up).

Dynamic Data FAQ