Writing /home/jrust/domains/codejanitor.com/public_html/docs/data/cache/5/52bcb2fec445b7b7740e1a57a02d8536.i failed
Writing /home/jrust/domains/codejanitor.com/public_html/docs/data/cache/5/52bcb2fec445b7b7740e1a57a02d8536.xhtml failed
Developing in FastFrame
The Basics
Check out the most recent version of the code from our
subversion server. If you don’t know what subversion/SVN is, you’ll want to start
here.
Read the
coding standards which contain both good tips for coding in FastFrame and the details of our coding style.
-
Start coding!
Debugging and Error Handling
One of the most useful development features in FastFrame is the error handling which allows you to easily capture errors and debug variables. No more var_dump($foo)! To use the error handler effectively do the following:
In FastFrame’s conf.php search for Error Handling and put the following line error reporters array:
'console' => array('level' => E_VERY_ALL),

The above line means that all errors and debugging statements will result in a small bomb icon at the bottom of the screen. Click on the bomb icon to see the error message, the context of the error, and a dump of the pertinent variables surrounding the error.
To debug a variable put the following line below the variable you want to debug:
$GLOBALS['o_error']->debug($variable, 'variable_name', __LINE__, __FILE__);
Note: If you are using VIM to do your developing you can put the following in your .vimrc to make it easy to debug variables:
let mapleader = ","
nmmap <leader>bug yiwo$GLOBALS['o_error']->debug(<esc>pa, '<esc>pbxA', __LINE__, __FILE__);<esc>
Now, all you have to do is put your cursor over the variable to be debugged and type ,bug
API Documentation
The purpose and arguments of every method are documented. To start understanding the underlying code the API Documentation is a good place to start.
The Path of Action
A description of what happens during a normal page load.