Web Application Maker Philosophy
To avoid hard scripting at the web server and browser layers, WAM provides model-driven development, based on a declarative model based on SQL Servers built-in meta-data plus the WAMmodel tables; the WAM whole meta-model is simply the data engine built-in meta-data (data dictionary, relationship graph, view definitions, user permissions, constraints, stored procedure signatures) plus a few additional tables with no redundant information - the WAMmodel.
WAM acts like a runtime "function" that can either determine a whole "default" web interface automatically, or provide functional GUI fragments on demand, through a high level (ASP) developer API:
These fragments are inspired by high-level database concepts, and can get automatically assembled into single click/code-free full database front-ends. By running WAM's installer, which simply copies its runtime code to a web server and runs a generic SQL setup script on a target database, this gets immediately a functional, multi-user profile web application front-end, with zero lines of code. This can then be refined and maintained over several development axis:
Previous web interface generators clash against the inevitable need to fine-tune parts of the application; WAM addresses this problem by providing high level WAM objects that generate interface fragments at runtime, intermixed with the developer code, and not just at "developer/wizard" time as in other tools. These objects make ASP code more concise and robust to database changes because they dynamically introspect the WAMmodel; transparent caching mechanisms make this feasible.
Declarativa - Serviços de Informática, Lda.