class Test extends Controller {

	function page($offset = 0)
	{
		ob_start();
		$this->ajax_page( 0 );
		$initial_content = ob_get_contents();
		ob_end_clean();	

		$data['table'] = "<div id='content'>" . $initial_content . "</div>" ;

	    $this->load->view('page',$data);

	}

	function ajax_page($offset = 0)
	{
	  	$this->load->model('model');
		$this->load->library('Jquery_pagination');

		$config['base_url'] = site_url('test/ajax_page/');
		/* Here i am indicating to the url from where the pagination links and the table section will be fetched */

		$config['div'] = '#content';
		/* CSS selector  for the AJAX content */

		$config['total_rows'] = $this->model->num_rows();
	    $config['per_page'] = 20;

	    $this->jquery_pagination->initialize($config);

	    $this->load->library('table');

	    $html =  $this->jquery_pagination->create_links() . br(1)
				.  $this->table->generate($this->model->content( $limit, $offset));

		echo $html;
	}
}

Note: Don't forget to add the jquery.js in your view file, Jquery_pagination.php in your library folder.

Today i am going to show you or direct you to some of the contributions in CodeIgniter which will help you to develop a site rapidly ( :D ) . At least it's helping me out :

BackendPro Control Panel

Every site whether it's a commercial or a personal, you need a user management system including role management. This control panel provides the exact thing. With some additional features like asset management, page and view ... please go and discover it. The documentation is fair enough to learn. If you have heard about matchbox then you may like it more. It uses it. So, you can integrate your modules with it in no time.

Rabbit Forms ( A CRUD automate Library )
 
Now you have a Control Panel, and you need a CRUD system. Rabbit Forms is just the tool you need to have. I have included it with BackendPro and it helps me a lot. Including it with BackendPro is not that tough. Before you start with Rabbit Forms please view the video tutorial. Which helped me gr8.

GandyXT ( New CodeIgniter Package )

This one is new in town. But it can give you a quick start. It includes XAJAX scripts, Asset helper, facebox, lightbox, .htaccess modification bundled with codeigniter installation. 

CodeExtinguisher ( Plug and Play )

Though it  seems to me that it's a combination of BackendPro and RabbitForms but till now it did not impressed me. I personally like to have control on each and every simple things. But why should you listen to me ?? Go and have a look at it.

Bamboo Invoice ( Invoicing System )

I will never forget this one. If you need an invoicing system i prefer this one. To know my opinion you can see one of my post.

Blogmer ( Blog System )

It looks impressive. If you need one go for it ..

ORM

I saw some ORM like Datamapper, IgnitedRecord . 

[ Note: There are many other  contributions which can help you. Always keep an eye in wiki and forum of CodeIgniter. ]

I'm lazy when I code. By lazy I mean I detest retyping the same several codes of line multiple times throughout an app. My motto is (usually) if I have to use a/several line(s) more than 3 times it becomes a function so I can use and re-use it.

If you're like me, when you use the form features in CI you set up the controller part like so:


if($this->validation->run() == FALSE) {
$data["variable"] = "something";
$this->load->view("view_template",$data);
} else {
$process = $this->model_name->model_function($this->validation->variable);
//Success / error message here
}

That (extremely simple) example uses only 7 lines of code. However, if you have an add + edit function in each controller and you have 10 controllers, that's (7+7)*10 = 140 lines that are really similar. I hear a function calling my name!

With the function I created I took those six lines of code and reduced them to this:
$this->library_name->validation_run("model_name","model_function",$this->validation->variable,"view_template",array("variable"=>"something");

Pretty sweet, no? :)

Below is the function. I am assuming you have a basic to intermediate understanding of CI, so I won't go into a lot of depth explaining it. I placed validation_run in the custom forms library I use. You can use it in your own custom library or create a library out of it. If you put it in your own library, ensure that the method you are using to reference CI functions is reflected in validation_run ($this->obj,$ci,$this->ci, etc). Also ensure that the Validation and Model are loaded prior to calling validation_run.

function validation($model_name,$model_function,$model_function_variable,$layout_template,$data_array=NULL)
{
if($this->ci->validation->run() == FALSE) {
//This allows the view to be called with or without parameters.
if(!is_null($data_array)) {
$this->ci->load->view($layout_template,$data_array);
} else {
$this->ci->load->view($layout_template);
}
} else {
$process = $this->ci->$model_name->$model_function($model_function_variable);
//Use your favorite redirection method here
}
}

To use it, you'd simply call

$this->library_name->validation_run("model_name","model_function",$this->validation->variable,"view_template",array("variable"=>"something");

For better readability you could do alternatively do it this way:

$this->library_name->validation_run(
"model_name",
"model_function",
$this->validation->variable,
"view_template",
array("variable"=>"something"
);

Of course, you'd replace library_name with the library name you called it from.

Not everyone will have a use for this function; it's really only good for simple validation "running" . However, it's saved me so much time coding that I had to share it :)

Enjoy!

在 DataMapper > Download 頁中下載的檔案中，
除了必要的系統檔案之外，
還包含了一些範例的說明，
基本上，
只要依照 DataMapper > Installation Instructions 的說明，
複製「datamapper.php」、「datamapper_lang.php」即可。

複製後，再到 autoload.php 中去加入設定即可，

$autoload['libraries'] = array('database', 'masterpage');

以上，
就可以讓 CodeIgniter 增加對 ORM 的支援了。

What is IgnitedRecord?

IgnitedRecord is a relation handling ORM library, made for the PHP framework CodeIgniter.

The goal of IgnitedRecord is to provide an easy to use, easily customizeable, ORM library to CodeIgniter.

Features at a glance

• Easily configurable
• Uses default values if settings are not explicitly set
• Relations:
  • Belongs to
  • Has Many
  • Has One
  • Has And Belongs To Many (shorted to habtm)
• When fetching related objects, it is possible to filter, order and modify the query in a large quantity of ways
• Belongs To and Has One relations can be fetched easily through a JOIN with the help of join_related()
• Behaviours, which can add and modify the functionality of IgnitedRecord
• Hooks and triggers where you can put your own code
• Complete support for PHP 4, no "hacks" or anyting else is required for IgintedRecord to work under PHP 4.
• Method Chaining under PHP 5
• Nested WHERE statements and subqueries, with help from IgnitedQuery
• Partial support for multiple primary keys (relations are not supported, yet)

Benefits

• Repetitious work is minimized.
• You have a finished model base to builld on.
• You don't have to write SQL if you don't want to.
• The choice between updates and inserts is automatically determined.
• The result resources are automatically cleaned up, to improve speed and lower memory consumption.
• The code is easier to read, take this as an example:
  $posts = $user->related('posts')->order_by('name', 'desc')->get();
  // instead of:
  $posts = $this->db->from('posts')->where('user_id', $user->id)->order_by('name', 'desc')->get()->result();
  The difference will be even more obvious when more advanced queries are used.

Download location:

download latest version of Igniter Record

Beh, che posso dire? Sono molto soddisfatto dei risultati che sto ottenendo; infatti CI rispecchia pienamente la filosofia di sviluppo e i principi attraverso i quali viene sponsorizzato dalla EllisLab.

CodeIgniter è un Framework sviluppato in PHP4, compatibile con PHP5 che supporta una miriade di database (MySQL, MySQLi, Oracle, PostgreSql, e tanti altri ancora...).

Rilasciato sotto licenza GNU/GPL è composto da una attivissima comunità online e da una ricchissima documentazione (forse la più ricca che io abbia mai visto, per un Framework, Apple Cocoa esclusa ;) )

Beh, che posso aggiungere ancora?

Provatelo, programmatori web, ne rimarrete stupiti!

Nei prossimi giorni pubblicherò qualche brevissimo articolo su come realizzare semplici e validi struttere MVC, autenticazioni utenti, gestione delle sessioni e qualche upload di file.

在 CodeIgniter 的 Library 提供了一個 Layout 的方法，
檔案在「..\system\libraries\Layout.php」，
基本上只要稍微修改這個檔案即可，
但是在儘量不動到原始檔案的原則下，
這裡把檔案另外複製再來增加必要的功能。

ps. 除了設定的部份之外，個人習慣不去動 framework 原本的任何東西。

1. 新增 Library

初步動作其實只是複製修改原本的 library ，
先將「 ..\system\libraries\Layout.php」 複製為 「..\system\application\libraries\Masterpage.php」
他的功能其實和 Layout 一樣。開啟「Masterpage.php」，將「Layout 」都改為「Masterpage」，

class MasterPage
{
...
function MasterPage($MasterPage = "template")
{
$this->obj =& get_instance();
$this->MasterPage = $MasterPage;
}

function setMasterPage($MasterPage)
{
$this->MasterPage = $MasterPage;
}

在 function MasterPage()中的 template 就是版面設計的檔案，
也就是之後在 view 中要載入的版面。

如果要使用這個 Library 必須要在每個 view 中都 load ，

$this->load->library('Masterpage');

所以，還是到「..\system\application\config\autoload.php」修改就可以了。

$autoload['libraries'] = array('Masterpage');

2. 新增 「template.php」

在「..\system\application\view\」中新增「template.php」，並加入以下內容

something before
<hr/>
<?=$main?>
<hr/>
and something after that.

3. 修改 $loadedData[]

在「Masterpage.php」中修改

$loadedData = array();
$loadedData['main'] = $this->obj->load->view($view,$data,true);

4. 套用版面

回到你要套用這個版面的 view 中，
這裡用 Welcome.php 來示範，
原本載入「welcome_message.php」的方式是

$this->load->view('welcome_message');

修改為

$data = array();
$data['welcome_message'] = $this->load->view('welcome_message', $data, TRUE);
$this->masterpage->view('welcome_message', $data);

ps. 其實這樣會產生一個 unvalid 的網頁檔，在「welcome_message.php」中其實是一個 valid 的 html，
在加上 「template.php」中的東西，就會產生一個 unvalid 的網頁檔了，
必須把「welcome_message.php」最前面以及最後面的兩個部份剪下貼上到「template.php」中即可。

5. That's all!

只要在每個 view 中，加入最後四行的程式碼，
就可以讓每一個 view 都有一樣的畫面！

部份內容是參考 CodeIgniter 的 Forums

先到 Apache 下修改設定檔「httpd.conf」，啟動 rewrite_module，

LoadModule rewrite_module modules/mod_rewrite.so

在目錄下新增一個「.htaccess」檔案，
並加入以下內容。

DirectoryIndex index.php
RewriteEngine on
RewriteCond $1 !^(index\.php|images|css|js|robots\.txt|favicon\.ico)
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ ./index.php/$1 [L,QSA]

這樣，開啟

http://....../mvc/func/segm

即可得到與

http://....../index.php/mvc/func/segm

一樣的結果。

基本下載、安裝
1. 官方網站

到 http://codeigniter.com 下載，
官方網頁還有線上文件說明（User Guide），討論區（Forums），和一些大家開發的小元件（放在 wiki）

基本的系統安裝就如這樣，
接下來進行必要的系統修改。

必要系統設定修改

1. 解壓縮下載的檔案到 www 目錄下，這裡新建一個「ci」資料夾

2. 新增一個 database，名稱任意，這裡使用「ci」當作測試用的 database

3. 刪除 user_guide 資料夾

在原始的壓縮檔案中，CodeIgniter 自動壓入完整的線上說明，
本身系統其實不需要這份說明，
建議在完成自己的網站開發前移除或是更名。

僅是建議，可跳過此步驟。

在官方網站有說明，http://codeigniter.com/user_guide/general/urls.html

如果不用 rewrite_mod的話，網址列會保留 index.php，
像是這樣， http://your.domain.name/index.php/main/func/1
index.php 似乎是多餘的，
所以利用 rewrite_mod 把他刪掉。

僅是建議，可跳過此步驟。

4. 修改系統檔案

首先修改幾個重要的檔案，讓這個網站具備資料庫功能。

在 www\ci\system\application\config\config.php 檔案中修改根目錄

$config['base_url']    = "http://localhost/ci/";

在 www\ci\system\application\config\database.php 檔案中修改資料庫連結設定

$db['default']['hostname'] = "localhost";
$db['default']['username'] = "";
$db['default']['password'] = "";
$db['default']['database'] = "";
.....

Last fall I was working on a niche-oriented CMS and was getting majorly bored/burned out by all the procedural stuff; the code felt horribly messy to me and I wanted to get into OOP (Object Oriented Programming) but previous attempts had left me scratching my head.

Somehow I stumbled on CodeIgniter and I was immediately hooked. Once I figured out my way around MVC and their way of doing things I tripled the amount of code I was able to put out. Was my code the best you could ever find? No, but it was definitely a step ahead of where I'd been.

Once I finished the CMS I decided to tackle another project and turned again to CI. I've been working on this project for the majority of 2008, and might have it done by the end of the year.

Now, I really love CI because it's so easy and flexible, and it's pretty much agreed that they have the easiest to understand documentation. However, I began to get frustrated with some of the features the default CI lacks - Auth being the biggest -- so I started "shopping around" some other popular frameworks. Following are the ones I dabbled with. Note that there are no benchmarks because frankly that wasn't my concern -- realtive ease of use and the speeding up of my development were the primary concerns was.

Zend Framework - http://framework.zend.com:
Impression: After Symfony, I say ZF is probably the daddy of the frameworks. You can develop some really powerful stuff with it. That said, I found it to have a really steep learning curve and to be too loosely coupled for my taste. Requires more manual configuration than most other frameworks. It took me almost a full day to figure out the Zend_Db class and even then I wasn't able to move too far with it. I was really impressed with their ACL and Auth classes, although I didn't get far enough to really dabble with them.
Conclusion: If I had more time to play with it, I'm sure I could figure ZF out and develop some really cool stuff. For now, I will most likely stick with implementing components of ZF with other frameworks.

CakePHP - http://www.cakephp.org
Impression: One of the most popular frameworks. Pretty strict with naming conventions. Models are a must (this is not a bad thing). I actually played with this for a couple of days and got a lot farther with it than I did with ZF. The docs (2.2) are pretty good and I was able to find almost everything I needed to know within them. Because it's so popular, finding things that weren't in the docs -- like a form tutorial -- was really easy.

Conclusion: I may go back and try my hand developing something with Cake. If you have moderate experience with MVC, it's not (IMO) that hard to learn. It's a lot slower than pretty much any other framework but it also does a lot of stuff for you that could speed up your production.

KohanaPHP - http://www.kohanaphp.com
Impression: Kohana is a relative newcomer to the PHP Framework scene; it originated as a fork of CI when a bunch of CI developers got tired of waiting for EllisLab (creators of CI) to fix bugs with CI. Right now the current release is 2.2 (I think) and while a lot of things are different from CI, it's still feasible to port CI apps to Kohana by renaming a few things and following some different rules, like using helper::helper_function instead of $this->load->helper('helper') and helper_function(). I wasn't very impressed with their docs; I found reference to the "Forge" class, that helps consolidate form creating/validation rules, only to find out Forge has been depreceated in Kohana 2.2.
However, Kohana does seem very powerful and I don't think it would be too big of a leap to go from CI to Kohana. I really like that they have an advanced archive class as well as auth and payment modules.

Conclusion: I will probably use Kohana at some point; I may even recode the 2nd draft of my current project in Kohana since it provides more built-in functionality than CI does. I really like that it is community based; however, from what I've read the framework seems to depreceate things fairly often, which could make developing with it a pain in the ass.

CodeIgniter - http://www.codeigniter.com
Impression: As I said, I love CI. It was so easy to learn and really helped speed up my PHP production. The community is awesome, the docs are awesome, and it's so flexible I can do pretty much anything I want with it. The "bare-bones-ness" of it, though, is also frustrating at times, especially when I have to manually code something in that the other frameworks provide by default -- again, mainly Auth stuff. I think it's kind of neat that it's used and backed by a company (EllisLab, which produces the Expression Engine commercial CMS), which should provide security as far as it being around. The bad thing about that is that since it's developed and maintained by a company, fixes to bugs and other issues can take a lot longer than a community driven framework. I'd really like to see CI get into module-type stuff or at least include company-supported libraries like auth and payment.

Conclusion: I will likely stay with CI for now; when I get more time to dabble with Kohana more it will become more of a competition in my mind. I have to say, though, that for each (hee!) framework I tried, I ended up going back to CI with relief mostly for its flexibility. That could just be due to my being most familiar with CI, though.

To wrap it up, my choices would likely go like so:

1. CodeIgniter
2. Kohana
3. CakePHP
4. Zend Framework

I know that this hasn't been a very "techy" type of comparison; as the title suggests, these are merely my opinions on the 4 frameworks I've tried out. Eveyrone has one that clicks for them, and you're definitely entitled to use that one and call it the best (for you!).

I tried CakePHP but it was a little too rigid on its rules when it came to the data access layer, not enough flexibility. I don't like frameworks that box you in trying to get you to do things a certain way. I want a certain amount of freedom when I code. I've been reading lately about CodeIgniter which is a very lightweight MVC framework that gives you that freedom (from what I've read). So I will be trying it in the next couple of weeks.

I think that in the long run I'd like to be able to make Drupal modules and build applications on it. Besides, there is a crazy amount of people out there using Drupal for their portals, ecommerce, and other sites. All of those will need maintenance at some point and I will be ready to dive in if I ever get a contract like that. But if I ever want to write something from scratch I am going to use a framework like CodeIgniter. That way I have the best of both worlds.

I will update the blog as I learn more about both platforms...

Recently I've tried this PHP framework and I 've to say that it's a very good one but not for everyone in my opinion.

CodeIgniter(CI) have a lot of good features to stand up against the established or usual frameworks that people is using around like CakePHP or Symphony. This is very hard to do because ... well, ask yourself what new can you bring to the framework's world that people don't have yet.

And they come up with a very lightweight and flexible framework. Is it just the opposite at the ones I mentioned before? mmm, in someway It could be, but I can tell that I 've been researching around internet and everyone is highlighting the speed difference between other frameworks. CI is faster and that have a reason: CI don't load stuff you are not going to use. If you want to use it, do it by loading it yourself when you need it (also you have the option to autoload the component if you use it very often).

Let see the top features:

• Lightweight
• Fast
• Flexible
• MVC

But in the other hand have some issues:

• Don't have an ORM incorporated. It have a small ActiveRecord group of shortcuts but you can also use another one created by the community only if you need it.
• It isn't modularized. This is the worst issue because it retains people with more complex needs on their projects. Imagine a very big and complex application not being modular ... mmm ...
• More work. Because of the good CI's features we will have to do more work to create the functionality other frameworks already have. But maybe this is a good thing to you if you want to fully customize your functions.

One important thing is documentation. Compared with Django documentation (one of the best online framework documentation I ever see) it's a little bit far from them. It's very well organized but I think it could be better, more complete, with better examples, warnings, etc.

About modularity, I think I read in one of the thread's forum this is going to be present in the next version, which I don't know the release date or if it's confirmed. I hope so, meanwhile you can use one of the plugins created by the community, but it's not as good as an official solution.

In conclusion, it's a framework to people with previous experience wit PHP (you will have to write a lot) but we have the advantage of excellent performance with an MVC structure.

Solusi untuk hal ini dapat dilakukan dengan beberapa cara:

1. mengedit file driver database CodeIgniter: system/database/drivers/mysqli/mysqli_driver.php. Pada file ini dapat ditentukan port MySQL pada function ‘db_connect’ yaitu dengan menambahkan parameter $port pada function tsb:
   mysqli_connect ( [string $host [, string $username [, string $passwd [, string $dbname [, int $port [, string $socket]]]]]] )
2. mengedit file PHP.INI, pada bagian  mysql.default_port, ganti dari 3306 menjadi 3307
3. jika tidak punya akses ke file PHP.INI, bisa juga dicoba dengan mengedit file config/database.php nya CodeIgniter yaitu pada baris:
   $db['default']['hostname'] = "mysqlhost.yourdomain.com:3307";

Kumbia es un web framework libre escrito en PHP5. Basado en las mejores prácticas de desarrollo web, usado en software comercial y educativo, Kumbia fomenta la velocidad y eficiencia en la creación y mantenimiento de aplicaciones web, reemplazando tareas de codificación repetitivas por poder, control y placer.

Sus principales características son:

• Sistema de Plantillas sencillo
• Administración de Cache
• Scaffolding Avanzado
• Modelo de Objetos y Separación MVC
• Soporte para AJAX
• Generación de Formularios
• Componentes Gráficos
• Seguridad

y muchas cosas más.

Adicional a esto Kumbia integra lo mejor de la Web en un solo framework para producir las aplicaciones Web del mañana (prototypejs, phpMailer, Smarty, FPDF, Script.aculo.us)

Kumbia puede ser la solución que estabas esperando!

Lo mas importante de todo es que Kumbia está 100% en español, recomendado para proyectos medianos o grandes, preferentemente que lleven mas de 10 páginas dinámicas

Sitio web Kumbia

The following is what I'm thinking of using in a couple of months when I try to start a career in website development, as my history and experience in web technologies. Please tell me what you think!

My hobby and obsession for the internet and websites began seven years ago when I began secondary school in 2001. I started using a WYSIWYG Webpage editor that generated the HTML for me. It was when I came across sites that referenced tags like head, body and a that I began to learn the language.

After learning HTML for a while, I started with CSS to style the documents, and realising different technologies tied in together began my route to web development. 

A few years after that I delved in the server-side, as I was drawn to the way pages were generated by query strings. I installed a localhost using a WAMP configuration and started learning PHP. I now have advanced experience with procedure and object-orientated programming in PHP, along with creating basic frameworks with MVC and using large ones such as CodeIgniter.

When I started coding for databases, I chose the most discussed open-source variation available, MySQL, which I use for all database applications now (which I now see as bad practice and plan to extend my knowledge to other databases, including closed-source). I then looked at other ways of holding data, for transfer/export and flat file storage, and came across XML (and recently JSON).

About a year and a half ago, I started to concentrate on the client-side, most notably, Javascript (including experience with XMLHttpRequest and frameworks like jQuery and Mootools), and communication between client and server using HTTP Headers and Status Codes.

Now I spend my time catching up with newer technology like RSS 2.0 / Atom and Scalable Vector Graphics, practising standards-compliance (when it comes to syntax and markup, friends familiar to web development regard me as a perfectionist, although they don't regard it as a good thing), accessibility and semantics (such as microformats (hopefully to be replaced by RDFa), XFN and SEO), whilst keeping up to date with W3C recommendations and specification drafts for proposed technologies such as PHP 6, XHTML 2, CSS 3 and RDFa.

INSTALANDO CODEIGNITER

1.- Descargar la version mas actual de codeigniter : codeigniter.com, hasta este momento es la version 1.6.3. (menos de 1MB) :D

2.- Descomprimir, navegar dentro de la carpeta CodeIgniter_1.6.3\CodeIgniter_1.6.3, allí existen 4 archivos (dos directorios y dos archivos), system, user_guide, index.php, licence.txt.

3.- Imaginando que ya tienes instaladon un paquete bajo window de apache, php y mysql, yo utilizo WampServer. Lo siguiente es crear una caperta en tu document root (en mi caso esta en E: WAMP/WWW), alli dentro de WWW crear una carpeta llamada CI o CodeIgniter (en verdad como gustes), y copiar los 4 archivos en contrados dentro de CodeIgniter_1.6.3\CodeIgniter_1.6.3 [system, user_guide, index.php, licence.txt].

4.- luego de eso, creo que estamos listo para dar una mirada al http://locahost/ci

En la proxima entrega... como configurar CI para empezar nuestra propia aplicacion.

Image Source: Day 486 / 365 - Late Night High Level Coding Courtesy Of: JasonRogers

I think I will get back on more IT related blog post later. It's been a while since my last post about IT. After backing in the speed coding game, I have some issues to resolve.

Just has an error related to PHP5 running on Apache. Problem is solved and are ready at CodeIgniter - No input file specified error - .htaccess - PHP5 - Apache 2.

Feel freel to read and apply to your site, if you are having the same issues.

Have a look and if you haven't already signed up your South African business then fill you details in on the signup form.

CodeIgniter (CI) es un poderoso Framework PHP con una pequeña guia que nos detalla cada funcion del framework y como debemos usarla, esta construido para programadores PHP quienes necesitan un simple y elegante herramienta para crear aplicaciones completamente funcionales. Si eres web developer quien esta cansado de escribir tantas lineas de codigo y cansado de buscar y probar Frameworks los cuales no traen una buena guia para su utilizacion te recomiendo que pruebes CodeIgniter.

Though the use is same as the built in pagination system except another extra config parameter :

$config['div'] = '#content'; /* Here #content is the CSS selector for target DIV */

Requirements: Make sure you have added the Jquery.js file on top of the view file. Download latest Jquery from here. Put "Jquery_pagination.php" file in you application/library folder and use it as a separate library.

Files: Jquery_pagination

I will try to add an example and a little tutorial very soon. Be in touch... :D

Modification:

To add extra javascript code after clicking the links or do other binding add the extra javascript code in

$config['js_rebind'] = "alert('it works !!'); ";

Here is the new File: Jquery_pagination

Hatırlarsanız bir önceki yazımda, MVC yapısı, CodeIgniter framework'ü ve kurulumu hakkında bilgiler vermiştim. Bu bölümde ise CodeIgniter dosya yapısı hakkında bilgiler vermek istiyorum.

Daha öncede söylediğim üzere, CodeIgniter ile gelen arşiv dosyasını bilgisayarımıza açtığımızda, system ve user_guide klasörleri ile index.php ve license.txt dosyalarının geldiğini görmüştük. Şimdi bu klasör ve dosyaların ne olduğunu biraz açmak istiyorum.

System klasörü içinde farklı görevleri olan bir çok klasör bulunmaktadır. Bu klasörlerin içinde ki dosyalar da CI'nin iskeletini oluşturmaktadır. CI'nin sahip olduğu klasörleri şu şekilde sıralayabiliriz.

• application
  • config
  • controllers
  • errors
  • hooks
  • libraries
  • models
  • views
• cache
• codeigniter
• database
  • drivers
    • mssql
    • mysql
    • mysqli
    • oci8
    • odbc
    • postgre
    • sqlite
• fonts
• helpers
• language
  • english
• libraries
• logs
• plugins
• scaffolding
  • images
  • views

Application klasörü
Application klasörü bizim için büyük önem arz etmektedir. Çünkü yaptığımız geliştirmeleri burada saklamaktayız. Genel olarak işleyiş bu klasör içinde gerçekleşmektedir. Model-View-Controller dosyalarımız bu klasör içinde yer alan yardımcı klasörler içinde saklanacaktır. Ayrıca geliştirdiğimiz kütüphaneleri de yine burada bulunan libraries klasörü içine atarak projemize yine burada dahil edebileceğiz.

Cache klasörü
Adından da anlaşıldığı gibi, sistem üzerinde önbelleğe alınan veriler burada tekrardan kullanılmak üzere saklanmaktadır. Codeigniter klasörü CI'nin php 4+ ve php 5+ sürümlerinde çalışması için gerekli olan dosyalar burada bulunmaktadır.

Database klasörü
Veritabanı işlemleri için gerekli olan kütüphaneler burada bulunmaktadır. Halihazırda destek verdiği veritabanları başlıca : mssql, mysql, postgresql ve sqlite

Fonts klasörü
Aslına bakarsanız bu klasörün ne olduğu hakkında bir bilgim yok. Ancak tahmin ediyorum ki, captcha veya buna benzer bir sistemde kullanılmak üzere oluşturulmuş bir klasör. İçinde daha sonradan kullanmak üzere yazı tiplerinizi saklayabilirsiniz.

Helpers klasörü
Kullanılmak üzere hazırlanmış yardım fonksiyonlarının bulunduğu klasördür.

Language klasörü
Dil dosyalarının saklandığı klasördür.

Libraries klasörü
Kullanılmak üzere hazırlanmış sistem kütüphanelerinin bulunduğu klasördür.

Logs klasörü
Sistem kayıtlarını tutan klasördür.

Plugins klasörü
Eklentilerin bulunduğu klasördür.

Scaffolding klasörü
İlk önce bu terimin ne olduğuna dair fikir edinmemizin yararı olacağını düşünüyorum. Scaffolding, Ruby On Rails dünyasında adını sıkça duyduğumuz, veritabanı üzerinde ki bilgileri kod yazmaya gerek duymadan işleyebileceğimiz, sisteme verilen ad. Scaffolding klasörüde bu sistemi içinde barındıran depodur.

Kabaca CI'nin klasör yapısı bu şekilde özetlenebilir. Daha detaylı bilgi için CI ile birlikte gelen kullanım rehberine bakabilirsiniz.

Bu kadar kaba bilgiden sonra esas işlerimizi yürüteceğimiz Application klasörünün yapısına deyinmek istiyorum.

Hatırlarsanız Application klasörü bizim için büyük önem arz etmekteydi. Çünkü büyük çoğunlukla bu klasör ile haşır neşir olacağız.

Application klasörü içinde bulunan Config klasöründe çeşitli ayarlamalar yapabileceğimiz dosyalar bulunmaktadır. Burada bulunan dosyalar ile veritabanı ayarları ve CI ile ilgili çeşitli sistem ayarları yapabilirsiniz.

Controller klasöründe ise istekte bulunduğumuz işlemleri ve model yapısı ile sağladığımız verileri işleyeceğimiz dosyalar saklanacaktır. (İş katmanı)

Errors klasöründe hata dosyaları bulunmaktadır. İsterseniz siz de kendinize göre hata sayfaları hazırlayıp bunları CI'nin işlemesini sağlayabilirsiniz.

Hooks klasörü hakkında henüz bilgi sahibi olmadığım için hakkında birşey söyleyemiyorum. Öğrenir öğrenmez sizlerle paylaşacağım. (:

Libraries klasöründe, daha önce de bahsettiğim gibi kendi yazdığımız kütüphaneleri daha sonra kullanmak üzere burada saklayacağız.

Model klasöründe uygulamamız için yazdığımız veritabanı işlemlerinin bulunduğu dosyalar saklanacaktır. (Veri katmanı)

View klasöründe ise arayüz dosyalarımız saklanacaktır. (Sunum katmanı)

Evet CI'nin Application klasöründe bulunan, klasör ve dosya yapısına da kabaca değinmiş olduk. Umuyorum ki bu yazım ile CI hakkında biraz daha bilgi sahip oldunuz.

Bir sonra ki yazımda CI dosyaların yapılandırılması hakkında bilgiler vermek istiyorum. Sonra ki yazımda görüşmek üzere...

Alıntı : http://www.katodivaihe.com

The Includes of the system map out of the dependencies of the system. [ Here ]

Tools Used to Develop Such maps are.. [here] and [ here ]

Check this for CodeIgniter: