GitHub Sale: sign up for any paid plan this week and pay nothing until January 1, 2009!  [ hide ]

public
Description: A lightweight MVC framework on top of Grok-PHP
Homepage: http://chippino.googlecode.com
Clone URL: git://github.com/Jakobo/chippino.git
commit  d3a79fdb286807a98533ba4eb4e7eff7ca9cfe7f
tree    7c6b63bb63bc9b7e97e345e1be19a82d040b9f0a
parent  cb83fceff9a2a9c0fe1c1545735896384ea84800
name age message
file LICENSE Wed Jul 02 09:33:41 -0700 2008 fixed license info, updated a bit of the readme... [Jakobo]
file README Wed Jul 02 09:52:40 -0700 2008 removed grok ref from readme since it doesn't n... [Jakobo]
file chippino.php Wed Jul 02 08:07:15 -0700 2008 added readme file [Jakobo]
file chippino_core.php Sun Aug 24 18:52:15 -0700 2008 modified the way php files were handled to impr... [Jakobo]
file grok.php Tue Oct 28 23:48:43 -0700 2008 new grok file [Jakobo]
directory library/ Fri Jul 04 09:38:34 -0700 2008 moved xss ro protected space, updated sanitizer... [Jakobo]
directory tests/ Tue Aug 19 11:06:31 -0700 2008 moved files around to create a more model struc... [Jakobo]
README
README
======

Welcome to Chippino, an add-on to Grok-PHP which adds MVC Support. If you're not already familiar with Grok, now's a 
good time to go over the basics.

Grok, the underlying engine of Chippino is a Input, Process, Output model. Each Grok file is the smallest encapsulated 
piece of logic to perform a given task. Think of it like a function library, on steroids. Once you have that concept, 
Chippino's layer becomes more clear.


Chippino brings to the table:
=============================

*   Simple functions for creating Chippino calls
*   A free flow syntax to make calling easier
*   Support for "instance level" calls (reuse same call as last time)
*   A base library of functionality, including
    *   Modular config file support
    *   Input sanitization and filtering
    *   Canonical routing through PATH_INFO or $_GET if you want MVC shinies


Getting Started
===============

MVC Setup
---------

Copy the mvc.php file to a public directory. Change the line:

require_once dirname(dirname(__FILE__)) . 'chippino.php';

To refer to the path where Chippino is located. Absolute paths tend to be easier to work with, which is why you see 
dirname(dirname( in the example above. Then change the line:

chippino_config()->base_path = dirname(__FILE__);

To be the absolute path to your application directory. This way Chippino knows where to find your stuff. Inside of your 
applications directory, either symlink or copy the library/chippino directory to your-apps/chippino

Hit up http://www.example.com and you should see the Chippino welcome page. Yep, you're golden. Time to start building!


NON MVC Setup (Because sometimes, that's just overkill)
-------------------------------------------------------

just require_once the chippino.php file and you're off and running. It's recommended you also add a line:

chippino_config()->base_path = dirname(__FILE__);

to refer to where your application will be stored. For most people, they're looking for the MVC. But, if you just want 
the config functionality and the chip() functions, this is the way to go.


A Sample Chippino Setup
=======================

/your-root-dir
    |- public_html
        |- index.php (moved and edited mvc.php)
    |- chippino (git link to chippino project)
    |- apps (your application directory)
        |- [your app]
        |- chippino (symlink to ../chippino/library/chippino or copied in)
        |- [your app]
        |- [your app]...

The above setup is the most ideal. Grok and Chippino are both below the public directory, the index.php file is the only 
public entry point. Grok.php and the Chippino library are linked, making it easier to update both without issue.