HTML-Merge
4 results

 view release on metacpan or  search on metacpan

docs/Repository.html  view on Meta::CPAN 

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>HTML::Merge::App::Repository - A sample of a complex application</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body style="background-color: white">

<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->

<ul>

	<li><a href="#name">NAME</a></li>
	<li><a href="#description">DESCRIPTION</a></li>
	<ul>

		<li><a href="#overview">Overview</a></li>
		<li><a href="#database">Database</a></li>
		<li><a href="#the_road_ahead">The road ahead</a></li>
	</ul>

	<li><a href="#copyright">COPYRIGHT</a></li>
</ul>
<!-- INDEX END -->

<hr />
<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>HTML::Merge::App::Repository - A sample of a complex application</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>
</p>
<h2><a name="overview">Overview</a></h2>
<p>The goal of the HTML::Merge::App::Repository is to provide a 
form builder multi language design environment. 
In order to accomplish that all form design meta data are stored 
in a databases where each record represent a form element. 
A rendering engine has been created to render the form from the database. 
The project is lacking a GUI interface for populating the form meta data database.</p>
<p>
</p>
<h2><a name="database">Database</a></h2>
<p>The entire project is stored on tables residing on HTML::Merge system database 
(tested on SQLite and MySQL). The table creation and initing code  reside 
in the class HTML::Merge::App::Repository and it is being utilize in the 
mergecreateinstance script. HTML::Merge::App::Repository also relay on 
definition stored on the tbl table populated by the 'private/sql/tbl.dat' 
pipe delimited file. This actually break the possibility of treating the 
Repository as an add-on module since it taints the mergecreateinstance 
and relay on default data from the basic system tbl table, but this 
design flows can easily be repaired.</p>
<dl>
<dt><strong><a name="item_tbl__2d_master_table">tbl - master table</a></strong>



( run in 1.005 second using v1.01-cache-2.11-cpan-119454b85a5 )