Book Image

PhpStorm Cookbook

By : Mukund Chaudhary
Book Image

PhpStorm Cookbook

By: Mukund Chaudhary

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
PhpStorm Cookbook
Mukund Chaudhary
Dec, 2014 | 254 pages
No titles found
Table of Contents (16 chapters)
PhpStorm Cookbook
PhpStorm Cookbook
Credits
Credits
About the Authors
About the Authors
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Cooking with PhpStorm
Cooking with PhpStorm
Introduction
Showing/hiding views
Customizing a view
Accessing any project file
Maximizing views and editors
Going back to the previous editor
Going back to the previous edit location
Linking views to editors
Creating a key binding
Creating a bookmark
Restoring deleted resources
Customizing with PhpStorm
Adding an include path
Excluding unwanted directories from the index
Using code completion
2
PHP Development
PHP Development
Introduction
Creating a PHP project using Composer
Creating an empty project
Reusing an existing project
Creating a new PHP class
Creating a new PHP method
Adding the getter/setter methods
Creating delegate methods
Surrounding code with control structures
Finding the matching brace
Commenting out a section of code and PHPDoc
Creating a working set
Creating TODO tasks
3
Refactoring and Building
Refactoring and Building
Introduction
Renaming elements
Copying elements
Moving elements
Moving a method
Moving a variable
Deleting elements
Searching code in a project
Comparing files
Restoring elements using comparison
Setting the run configuration
Running your code
4
Integrating Framework
Integrating Framework
Introduction
Cooking with Symfony
Creating a controller with Symfony
Creating a model with Symfony
Creating a view with Symfony
Creating a model with the Yii framework
Creating a controller with the Yii framework
Creating a view with the Yii framework
Creating a model with the Zend framework
Creating a controller with the Zend framework
Creating a view with the Zend framework
5
Testing and Debugging
Testing and Debugging
Introduction
Installing PHPUnit
Test case in PHPUnit
Testing an application with PHPUnit
Starting a debugging session
Setting a breakpoint
Configuring breakpoint conditions
Creating exception breakpoints
Stepping through your code
Running to a line of code selected
Watching expressions and variables
Changing code on the fly
Code coverage in PhpStorm
6
Using PhpStorm in a Team
Using PhpStorm in a Team
Introduction
Getting a VCS server
Creating a VCS repository
Connecting PhpStorm to a VCS repository
Storing a PhpStorm project in a VCS repository
Committing files to the VCS repository
Updating code from a VCS repository
Synchronizing your code with the VCS repository
Examining the VCS repository
Checking projects out of a VCS repository
Creating code patches
Creating VCS tags or branches
Creating a task for the team
7
PhpStorm and Phing
PhpStorm and Phing
Introduction
Connecting Phing and PhpStorm
Catching Phing build file syntax problems
Building a PhpStorm application using Phing
Using a different build file
Doing wonders with Phing
Using the Phing build view
8
Cooking Library Plugins
Cooking Library Plugins
Introduction
Creating a library plugin
Refining the plugin
Configuring the plugin with PhpStorm
Code hinting for the plugin
9
Code Quality Analysis
Code Quality Analysis
Introduction
Mess detector and PhpStorm
Code sniffer and PhpStorm
Locating code duplicates
Code formatting and arrangement
Index
Index

Introduction

Rome wasn't built in a day. Nor by a single person...

Whichever sport you play or wherever you go, it has always been a team game. They have always kept on saying that united you stand and divided you fall. A PhpStorm cookbook author also used to say that reinventing the wheel is an action that should be avoided. Thus, you should always work in a team. The reason is obvious: a task divided among a team is completed faster.

According to a principle of software engineering, you should program in a team of two. This way, both of you will be able to discover errors in each other's code in the development phase itself.

So, when you work in a team, how will you work on an application development in which someone else is working on another module? One way is to use that same machine to code so that you can continue from the point where the other person stops working. But, is it wise to wait? It's OK that you work in a different shift. But, what if that person is geographically remote...

Previous Section
End of Section 2
Next Section