With the new Move Static Member refactoring in the PhpStorm 7 EAP, we can move static fields and methods to another type. For example when classes contain static methods that are nothing but utility methods, we can move them into a separate type.
JetBrains PhpStorm Team is gearing up for an autumn conference tour: we are going to visit Web&PHP Conference (September 16-18, San Jose, California), DrupalCon (September 21-27, Czech Republic, Prague), PHPNW (October 4-6, Manchester, UK), ZendCon (October 7-10, Santa Clara, California).
At our booth, the team will be happy to show you some PhpStorm demos, answer any questions you have in mind, share information about upcoming PhpStorm 7 release, and of course have fun! Be sure to register for our free license raffle and grab one of our awesomeyoyos and other swag. Even if you don’t win a free license, we’ll send you a 20% discount for a new PhpStorm Personal License.
Just have a look at this screencast to understand why Live Edit is one of the main productivity-enhancing features for front-end web developers:
You can automatically create Run/Debug Configuration and run Debug Session for any HTML file by clicking Debug file_name item in the file context menu (or in the context menu of the editor when the file is opened). Run/Debug configuration will be created, file will be opened in the browser.
Otherwise, you can create Run/Debug Configuration manually.
By the way, Live Edit also provides a Reload in Browser action. Map it to a hotkey and reload any page in your browser you are working on right from the IDE (including PHP pages or Smarty/Twig templates).
How does this work? It’s pretty easy! After opening a project in PhpStorm, navigate to http://localhost:63342/<projectname>. For example when working in a project called HelloWorld, navigate to http://localhost:63342/HelloWorld/. This URL will serve our project files using the project root as the webserver’s content root.
We have a short tutorial available with some more details on this feature.
Developing for PHP can be done in several ways. Some like to install all components they want to work with themselves. Others prefer downloading and installing a full “LAMP” stack at once. The latter can be done using XAMPP (Windows, Mac OS X, Linux) or MAMP (Mac OS X).
MAMP and XAMPP are packages that consist of an Apache HTTP server, MySQL database, PHP interpreter and some libraries. They are easy to install and get a development environment up in no time and provide all the components required for developing, running, debugging, and unit testing of PHP applications.
On our tutorials space, we have posted two how-to guides that help you get started with any of these packages and PhpStorm. There is one tutorial available for MAMP and one for XAMPP.
While it’s very straightforward to set up PhpStorm’s debugger, nothing is more frustrating than not getting it to work because of a tiny configuration mistake in php.ini. Speaking for myself, I’ve missed xdebug.remote_enable on a number of occasions, which usually happen at the most inconvenient time.
Using the Debugger Configuration Validation introduced with the latest version of the PhpStorm 7 EAP, we can now easily validate our debugger setup and have PhpStorm tell us if we’ve missed something! PhpStorm can verify our configuration of Xdebug and Zend Debugger. Here’s how. Continue reading →
The latest version of the PhpStorm 7 EAP comes with Vagrant integration! Vagrant is a tool which helps us create reproducible development environments. By scripting a virtual machine, Vagrant allows us to share a development machine by sharing a simple script. Other developers can then launch an identical machine by running the vagrant up command. Or by doing this from within the IDE!
Once the Vagrant Box is up and running, we can also make use of the built-in SSH terminal in PhpStorm to work on the virtual machine remotely.