Using the Framework: Basics
Do you know CodeIgniter?
CodeCoupler use CodeIgniter as base. All those people who knows CodeIgniter should read this page carefully. It explains the most important differences.
MVC Approach
First of all you should learn to create a webpage. CodeCoupler use CodeIgniter as base. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. To "write" a page you need at least a controller and a view. Here a little "Hello World" example:
First of all create a file named test.php in the folder application/controllers/ with the following code:
<?php
class Test extends CI_Controller {
public function index()
{
$this->load->view('test');
}
}Then create a file named test.php in the folder application/views/ with the following code:
<h1>Hello World!</h1>
Now open the url "http://<yourdomain>/test". You will see your first webpage created with this framework. One of the relevant differendes between CodeCoupler and CodeIgniter ist, that you do not have to write a complete html-structure. CodeCoupler will do it for you.
Read the very clear and thorough documentation here: http://codeigniter.com/user_guide/index.html
Master Template
In contrast to the basic CodeIgniter framework, every output of a controller will be surrounded by a master-template. The basic layout of the master template looks like this:
<!DOCTYPE ... />
<html ... >
<head>
<charset ... />
<title> ... </title>
</head>
<body>
[YOUR CONTROLLER OUTPUT]
</body>
</html>
Read the full documentation of the master-template library here: Libraries: Master
Extended Form Handling
The whole usage of form-elements is packaged in a new form-class which encloses the existing form-validation-class of CodeIgniter. The goal was to avoid some always recurring coding. To insert a text-field, for example, it is not enough to write “form_input($data)”. You have to remember the validation of the field, set the value to the previous posted, set the correct class if an error occurred and so on. A radio-button group or a group of checkboxes you have to think much more about the whole roundtrip and validation. Or what in case if you want to add more than one form onto one page? Using the form-class you will not need doing all this.
Here is a simple example of a view including a form. You do not have to do anything more in the controller than loading this view. A validation of the form will be done for you automatically based on configuration file for this form:
<?=form_start('example_form')?>
<?=form_label('name')?>:<br /><?=form_field('name')?> <br /><br />
<?=form_label('amount')?>:<br /><?=form_field('amount')?> <br /><br />
<br />
<?=form_submit()?>
<?=form_end()?>
<br />
<?=form_errors()?>
<?=form_confirmation()?>Read the full documentation of the form-handling library here: Libraries: Form
Multilanguage Routing
- tbd -
Default Enabled Components
- tbd -