User Tools
mantis:wwwrig:start
Differences
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:17] 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 37: | Line 37: | ||
| If so, then you may appreciate the rig's complete avoidance of any such notions. | If so, then you may appreciate the rig's complete avoidance of any such notions. | ||
| + | Seriously ... \\ | ||
| + | Moving application development from highly-structured programming languages into configuration solutions has many significant drawbacks for the programming process: | ||
| + | * Compile time errors are moved to runtime errors (this is the cause of many other problems) | ||
| + | * Type-safety is thrown out the window | ||
| + | * Refactoring is significantly more complex AND tedious | ||
| + | * Modern IDEs are very adept at editing code, but such tools are usually not available for editing configuration files | ||
| + | * Understanding config files requires learning a one-off DSL (Domain-Specific Language) - a waste of time | ||
| + | * Understanding config files requires following a tedious 'trail of breadcrumbs' of string identifiers | ||
| + | * Config files are parse-fragile - typos are easy to make, but hard to find (a bad combination) | ||
| + | * 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 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 | ||
| + | |||
| + | ------ | ||
| ====== Technical Details ====== | ====== Technical Details ====== | ||
| 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 ==== | ||
mantis/wwwrig/start.1541132232.txt.gz · Last modified: 2018/11/01 23:17 by admin
Page Tools
