This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
mantis:wwwrig:start [2018/11/01 23:27] admin |
mantis:wwwrig:start [2018/11/05 13:28] (current) admin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | <typo fs:xx-large; fw:bold>wwwrig</typo> | + | {{:mantis:wwwrig:sailboat.png?240}} <typo fs:xx-large; fw:bold>wwwrig</typo> |
====== Introduction ====== | ====== Introduction ====== | ||
This software provides a simple framework for PHP applications. \\ | This software provides a simple framework for PHP applications. \\ | ||
Line 48: | Line 48: | ||
* Config files are often not particularly legible or concise | * Config files are often not particularly legible or concise | ||
* When working with revision control, monolithic config files that refer to multiple features will often be a source of contention between programmers working on different tasks | * When working with revision control, monolithic config files that refer to multiple features will often be a source of contention between programmers working on different tasks | ||
+ | * When code is generated from config, any parts of code that either need, or could benefit from, customization can't be preserved across the code-generation cycle | ||
+ | * Code that simply **reads** minimal configuration, in contrast to code generated **from** configuration, enjoys most/all of the benefits of configuration, without these significant problems | ||
------ | ------ | ||
Line 53: | Line 55: | ||
The best way into the technical details is to dive into the code ! | The best way into the technical details is to dive into the code ! | ||
- | That said, here's some basics ... | + | Have a look at ''rig.php'' and ''view.php'', for starters. |
+ | |||
+ | That said, here's some other basics ... | ||
==== Configuration File ==== | ==== Configuration File ==== |