help files
Z505 | PasWiki | FUQ | Search | Main Docs | API Guide



Notes

About Jorge's web application framework...

The project started somewhere during June/2007 because the original author needed a complex layout and CGI framework, where code elements (classes) would be re-utilized between a set of applications, wich where being developed in order to administer a small Wireless Internet Service Provider.

The original code developed was too verbose and complex to the task, which programs ending bigger than if they were developed in a procedural fashion. While having thought about this problem for a long time before starting this endeavor, the author knew about some kind of solutions : the 1st possible solution uses templates with "stamps" where the cgi program outputs its data (aka the original PWU template engine). The second model puts the code INSIDE the html file (Like PHP does). A third solution was needed, where the programmer could rebuild their templates without breaking the model, and without all verbosity and complexity of having to bookkeep the emission of HTML tags inside code (Like even PHP does, you end up having html code inside your PHP Code blocks in order to generate more complex output).

The author them developed a, apparently, good solution : USER DEFINED TAGS. UDT, for short, are tags not originally present in HTML specification, that when encountered by the Template engine, actually causes the creation of objects with the capacity of adapting and generate output without having to include a single html code inside your CGI program.

The current state of the code library is alpha, meaning that nothing of it can be said to work, while being formally an "AS-IS" release, the author will attempt to be sure that the code library will be able to work as designed. The code structure is now locked, all interfaces will be kept as long as possible, changes, if needed, will be only done in the actual function internal code, and will not be felt by programs needing these functions. Classes will not "deprecate" fields, constructors, etc, and if a change is needed, overloaded or descendant classes will be created, as to not jeopardize third party code.






lufdoc, Powtils, fpc, freepascal, delphi, kylix, c/c++, mysql, cgi web framework docs, Z505