Using the Framework: Basics - Versionsgeschichte

Tm: /* MVC Approach */

2017-11-04T21:10:14Z

MVC Approach

← Nächstältere Version		Version vom 4. November 2017, 21:10 Uhr
Zeile 3:		Zeile 3:
	CodeCoupler use CodeIgniter as base. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:		CodeCoupler use CodeIgniter as base. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:

	To ~~"write"~~ a ~~page~~ you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers''' with the following code:		To create a webpage you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers''' with the following code:

	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">

Tm: /* MVC Approach */

2017-11-04T21:09:38Z

MVC Approach

← Nächstältere Version		Version vom 4. November 2017, 21:09 Uhr
Zeile 3:		Zeile 3:
	CodeCoupler use CodeIgniter as base. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:		CodeCoupler use CodeIgniter as base. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:

	To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:		To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers''' with the following code:

	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">

Tm am 9. Mai 2017 um 09:42 Uhr

2017-05-09T09:42:05Z

← Nächstältere Version		Version vom 9. Mai 2017, 09:42 Uhr
Zeile 21:		Zeile 21:
	</syntaxhighlight>		</syntaxhighlight>

	Now open the url <nowiki>"http://<yourdomain>/test"</nowiki>. You will see your first webpage created with this framework. If you look into the sourcecode you will see ~~one of the relevant differendes between CodeCoupler and CodeIgniter: You do not have to write~~ a complete html-structure~~, CodeCoupler will do it for you~~.		Now open the url '''<nowiki>http://<yourdomain>/test</nowiki>'''. You will see your first webpage created with this framework. If you look into the sourcecode you will see a complete html-structure.

	For further assistance on how the underlying framework CodeIgniter works, read the very clear and thorough documentation here: http://ellislab.com/codeigniter/user_guide		For further assistance on how the underlying framework CodeIgniter works, read the very clear and thorough documentation here: http://ellislab.com/codeigniter/user_guide

	== ~~Everything is Relative~~ ==		== Master Template with Components Concept ==

	In the ~~most applications~~ that ~~are using redirections and rewrites you have to modify at least the "RewriteBase" if you move them from one subfolder into another~~. ~~Some frameworks make our life unnecessarily difficult changing~~ the ~~domain name and some other need extra code to generate relative Url's.~~		One of the relevant differendes between CodeCoupler and CodeIgniter is that every output of a controller will be surrounded by a master template. The basic layout of the master template looks like this:

	~~With CodeCoupler you do not have to alter everytime configurations when migrating your application into another place. And all the links you have to use are clean and readable.~~

	~~Example for HTML:~~
	<syntaxhighlight lang="html">		<syntaxhighlight lang="html">
	~~<a href="controller/method/parameter">...</a>~~
	~~</syntaxhighlight>~~

	~~Example for JSON-Objects:~~
	~~<syntaxhighlight lang="js">~~
	{
	~~url: "controller/method/parameter"~~
	}
	~~</syntaxhighlight>~~

	~~For further informations how this was realized: [[Mods: Automatic Base Detection]]~~

	~~== Master Template with Components Concept ==~~

	~~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:~~

	~~<source lang="html4strict">~~
	<!DOCTYPE ... />		<!DOCTYPE ... />
	<html ... >		<html ... >
Zeile 60:		Zeile 40:
	</body>		</body>
	</html>		</html>
	</~~source~~>		</syntaxhighlight>

	But the ~~Master Template~~ do much more:		But the master template do much more:

	* Enabling JavaScript and CSS libraries using a component concept.		* Enabling JavaScript and CSS libraries using a component concept.
Zeile 69:		Zeile 49:

	Read the full documentation of the master-template library here: [[Libraries: Master]]		Read the full documentation of the master-template library here: [[Libraries: Master]]

			== Everything is Relative ==

			In the most applications that are using redirections and rewrites you have to modify at least the '''RewriteBase''' if you move them from one subfolder into another. Some frameworks make our life unnecessarily difficult changing the domain name and some other need extra code to generate relative Url's.

			With CodeCoupler you do not have to alter everytime configurations when migrating your application into another place. And all the links you have to use are clean and readable.

			Example for HTML:
			<syntaxhighlight lang="html">
			<a href="controller/method/parameter">...</a>
			</syntaxhighlight>

			Example for JSON-Objects:
			<syntaxhighlight lang="js">
			{
			url: "controller/method/parameter"
			}
			</syntaxhighlight>

			For further informations how this was realized: [[Mods: Automatic Base Detection]]

	== Asset Management ==		== Asset Management ==

Tm: /* MVC Approach */

2017-05-09T09:35:14Z

MVC Approach

← Nächstältere Version		Version vom 9. Mai 2017, 09:35 Uhr
Zeile 1:		Zeile 1:
	== MVC Approach ==		== MVC Approach ==

	CodeCoupler use CodeIgniter as base~~. All those people who do not know CodeIgniter should learn how the underlying framework works~~. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:		CodeCoupler use CodeIgniter as base. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:

	To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:		To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:

Tm: /* MVC Approach */

2017-05-08T21:29:59Z

MVC Approach

← Nächstältere Version		Version vom 8. Mai 2017, 21:29 Uhr
Zeile 19:		Zeile 19:
	<syntaxhighlight lang="html">		<syntaxhighlight lang="html">
	<h1>Hello World!</h1>		<h1>Hello World!</h1>
	</~~source~~>		</syntaxhighlight>

	Now open the url <nowiki>"http://<yourdomain>/test"</nowiki>. You will see your first webpage created with this framework. If you look into the sourcecode you will see one of the relevant differendes between CodeCoupler and CodeIgniter: You do not have to write a complete html-structure, CodeCoupler will do it for you.		Now open the url <nowiki>"http://<yourdomain>/test"</nowiki>. You will see your first webpage created with this framework. If you look into the sourcecode you will see one of the relevant differendes between CodeCoupler and CodeIgniter: You do not have to write a complete html-structure, CodeCoupler will do it for you.

Tm: /* MVC Approach */

2017-05-08T21:29:32Z

MVC Approach

← Nächstältere Version		Version vom 8. Mai 2017, 21:29 Uhr
Zeile 5:		Zeile 5:
	To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:		To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:

	<~~source~~>		<syntaxhighlight lang="php">
	<?php		<?php
	class Test extends CI_Controller {		class Test extends CI_Controller {
Zeile 13:		Zeile 13:
	}		}
	}		}
	</~~source~~>		</syntaxhighlight>

	Then create a file named '''test.php''' in the folder '''application/views/''' with the following code:		Then create a file named '''test.php''' in the folder '''application/views/''' with the following code:

	<~~source~~ lang="~~html4strict~~">		<syntaxhighlight lang="html">
	<h1>Hello World!</h1>		<h1>Hello World!</h1>
	</source>		</source>

Tm: /* Everything is Relative */

2017-05-08T21:28:29Z

Everything is Relative

← Nächstältere Version		Version vom 8. Mai 2017, 21:28 Uhr
Zeile 29:		Zeile 29:
	In the most applications that are using redirections and rewrites you have to modify at least the "RewriteBase" if you move them from one subfolder into another. Some frameworks make our life unnecessarily difficult changing the domain name and some other need extra code to generate relative Url's.		In the most applications that are using redirections and rewrites you have to modify at least the "RewriteBase" if you move them from one subfolder into another. Some frameworks make our life unnecessarily difficult changing the domain name and some other need extra code to generate relative Url's.

	With CodeCoupler you do not have to alter everytime configurations when migrating your application into another place. ~~The only thing~~ you have to ~~remember: Your links should start everytime with the controller name~~. ~~Nothing else:~~		With CodeCoupler you do not have to alter everytime configurations when migrating your application into another place. And all the links you have to use are clean and readable.

	~~<source>~~		Example for HTML:
	~~In an~~ <~~a href~~>~~-Tag:~~		<syntaxhighlight lang="html">
	<a href="controller/method/parameter">...</a>		<a href="controller/method/parameter">...</a>
			</syntaxhighlight>

	~~Or in a~~ JSON-~~Object~~:		Example for JSON-Objects:
			<syntaxhighlight lang="js">
	{		{
	url: "controller/method/parameter"		url: "controller/method/parameter"
	}		}
	</~~source~~>		</syntaxhighlight>

	For further informations how this was realized: [[Mods: Automatic Base Detection]]		For further informations how this was realized: [[Mods: Automatic Base Detection]]

Tm am 8. Mai 2017 um 20:52 Uhr

2017-05-08T20:52:58Z

← Nächstältere Version		Version vom 8. Mai 2017, 20:52 Uhr
Zeile 1:		Zeile 1:
	== MVC Approach ==		== MVC Approach ==

	CodeCoupler use CodeIgniter as base. All those people who ~~knows~~ CodeIgniter should ~~read this page carefully. It explains the most important differences. The other ones have to~~ learn how the underlying framework works. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:		CodeCoupler use CodeIgniter as base. All those people who do not know CodeIgniter should learn how the underlying framework works. CodeIgniter is a web application framework using the Model-View-Controller approach, which allows separation between logic and presentation. Here a little "Hello World" example:

	To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:		To "write" a page you need at least a controller and a view. Create at first a file named '''test.php''' in the folder '''application/controllers/''' with the following code:

	<~~syntaxhighlight~~>		<source>
	<?php		<?php
	class Test extends CI_Controller {		class Test extends CI_Controller {
Zeile 13:		Zeile 13:
	}		}
	}		}
	</~~syntaxhighlight~~>		</source>

	Then create a file named '''test.php''' in the folder '''application/views/''' with the following code:		Then create a file named '''test.php''' in the folder '''application/views/''' with the following code:

	<~~syntaxhighlight~~ lang="html4strict">		<source lang="html4strict">
	<h1>Hello World!</h1>		<h1>Hello World!</h1>
	</~~syntaxhighlight~~>		</source>

	Now open the url <nowiki>"http://<yourdomain>/test"</nowiki>. You will see your first webpage created with this framework. If you look into the sourcecode you will see one of the relevant differendes between CodeCoupler and CodeIgniter: You do not have to write a complete html-structure, CodeCoupler will do it for you.		Now open the url <nowiki>"http://<yourdomain>/test"</nowiki>. You will see your first webpage created with this framework. If you look into the sourcecode you will see one of the relevant differendes between CodeCoupler and CodeIgniter: You do not have to write a complete html-structure, CodeCoupler will do it for you.
Zeile 47:		Zeile 47:
	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:		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:

	<~~syntaxhighlight~~ lang="html4strict">		<source lang="html4strict">
	<!DOCTYPE ... />		<!DOCTYPE ... />
	<html ... >		<html ... >
Zeile 58:		Zeile 58:
	</body>		</body>
	</html>		</html>
	</~~syntaxhighlight~~>		</source>

	But the Master Template do much more:		But the Master Template do much more:

Tm: /* Everything is Relative */

2017-05-08T20:51:03Z

Everything is Relative

← Nächstältere Version		Version vom 8. Mai 2017, 20:51 Uhr
Zeile 27:		Zeile 27:
	== Everything is Relative ==		== Everything is Relative ==

	In the most applications you have to modify at least ~~some rewriting rules~~ if you move them from one subfolder into another. ~~And other~~ frameworks make our life unnecessarily difficult ~~if you want to change~~ the domain~~. With CodeCoupler you do not have~~ to ~~alter everytime configurations when migrating your application into another place~~.		In the most applications that are using redirections and rewrites you have to modify at least the "RewriteBase" if you move them from one subfolder into another. Some frameworks make our life unnecessarily difficult changing the domain name and some other need extra code to generate relative Url's.

	The only thing you have to remember: Your links should start everytime with the controller name. Nothing else:		With CodeCoupler you do not have to alter everytime configurations when migrating your application into another place. The only thing you have to remember: Your links should start everytime with the controller name. Nothing else:

	<source>		<source>
			In an <a href>-Tag:
	<a href="controller/method/parameter">...</a>		<a href="controller/method/parameter">...</a>

			Or in a JSON-Object:
			{
			url: "controller/method/parameter"
			}
	</source>		</source>

Tm am 8. Mai 2017 um 18:36 Uhr

2017-05-08T18:36:47Z

← Nächstältere Version		Version vom 8. Mai 2017, 18:36 Uhr
Zeile 24:		Zeile 24:

	For further assistance on how the underlying framework CodeIgniter works, read the very clear and thorough documentation here: http://ellislab.com/codeigniter/user_guide		For further assistance on how the underlying framework CodeIgniter works, read the very clear and thorough documentation here: http://ellislab.com/codeigniter/user_guide

			== Everything is Relative ==

			In the most applications you have to modify at least some rewriting rules if you move them from one subfolder into another. And other frameworks make our life unnecessarily difficult if you want to change the domain. With CodeCoupler you do not have to alter everytime configurations when migrating your application into another place.

			The only thing you have to remember: Your links should start everytime with the controller name. Nothing else:

			<source>
			<a href="controller/method/parameter">...</a>
			</source>

			For further informations how this was realized: [[Mods: Automatic Base Detection]]

	== Master Template with Components Concept ==		== Master Template with Components Concept ==