Visual Chefs PHP Standards
For all projects, developers should follow PSR-0, PSR-1, PSR-2 coding standards.
In this repository you will find a .editorconfig
file. This helps standardize your IDE to what is suggested by this document.
To use this file:
- put it in the root of your project.
- Get the plugin for your IDE: editorconfig.org
When working on ExpressionEngine or CodeIgniter projects, developers should follow the class and method naming conventions specified by the framework, for compatibility reasons.
All standalone classes should be namespaced for better compatibility and packaging. For ease of writing, the VC
namespace should be used, or alternatively VisualChefs
if the first is not available. Secondary namespaces are encouraged, in order to better organize code into modules or packages (example: VC\Logger\Logger
, VC\Logger\Handler
).
/**
* desc
*
* @author
* @copyright (C) 2013. All rights reserved.
* @version 1.0
*/
/**
* desc
*
* @category
* @package
* @subpackage
* @since 1.0
*/
class MyClass
{}
/**
* My awesome var does the following thing.
*
* @var boolean
* @scope protected
*/
protected $my_awesome_var;
/**
*
*
* @param string $my_var A concise description of my_var
* @return boolean
* @access public
* @static
*/
public static function myMethod($my_var = 'hello world')
{}
- Sentry Full featured basic authentication.
- Sentry Social Social auth add-on for Sentry.
- DebugBar for Laravel Helpful debug/profiling bar for Laravel 4.
- Swiftmailer free feature-rich PHP mailer.
- Geotools comprehensive set of geographic tools.
- Guzzle is a PHP HTTP client & framework.
- Monolog sends your logs to files, sockets, inboxes, databases and various web services.
- Markdown for Laravel Markdown library for Laravel 4.
- Twig the best templating engine for php.
- TwigBridge for Laravel bridge for Twig so it works with Laravel 4.
- PHP the Right Way
- net.tutsplus.com
- Laravel
- Design Patterns PHP
- Debugging Laravel 4 Weirdness - Checklist
@TODO more to come