A local PHP interpreter is a PHP engine installed on your computer opposite to a remote PHP interpreter that can be installed on a remote host or in a virtual environment set up in a Vagrant instance, see Configure remote PHP interpreters.

1. NetBeans is another popular Java IDE. If you are a current user of NetBeans and want to migrate from it to IntelliJ then this will serve as a good starting point. This chapter discusses the importing of NetBeans projects in IntelliJ, its terminologies equivalent to NetBeans, popular shortcuts and frequently asked questions. Import NetBeans project.
2. NetBeans keymap for all IntelliJ-based IDEs.
3. Ein paar Dinge, die ich bei PHPStorm (von Jetbrains) geil finde:-).

1. In the Settings/Preferences dialog Ctrl+Alt+S, go to PHP.

2. On the PHP page that opens, click next to the CLI Interpreter list.

3. In the CLI Interpreters dialog that opens, click in the left-hand pane, then choose Local from the popup menu.

   If you already have a local interpreter configured in PhpStorm, it is also shown from the menu and the menu item changes to Other Local.

4. In the right-hand pane of the dialog, specify the PHP interpreter's settings.

   1. In the Name field, type the identifier to distinguish the interpreter from others, for example, php_installation_<version>.

   2. Specify the PHP engine installation directory in the PHP executable field. Type the path manually or click and select the relevant folder in the dialog that opens.

      PhpStorm displays the version of the PHP engine detected in the specified folder and the debugger associated with this PHP engine in the php.ini file.

5. In the Additional area of the CLI Interpreters dialog, you can optionally customize the configuration settings of the PHP installation.

   • In the Debugger extension field, specify the path to Xdebug. This enables PhpStorm to activate Xdebug when it is necessary if you have disabled it in the php.ini file, see Configuring Xdebug for Using in the On-Demand Mode.

   • In the Configuration options field, compose a string of configuration directives to be passed through the -d command line option and thus add new entries to the php.ini file. The directives specified in this field override the default directives generated by PhpStorm, such as -dxdebug.remote_enable=1, -dxdebug.remote_host=127.0.0.1, -dxdebug.remote_port=9001, -dxdebug.remote_mode=req.

     For example, if you specify the -dxdebug.remote_mode=jit directive it will override the default -dxdebug.remote_mode=req directive and thus switch Xdebug to the Just-In-Time (JIT) mode, see Debug in the Just-In-Time mode for details.

     To do that, click next to the Configuration options field, and then create a list of entries in the Configuration Options dialog that opens.

     • To add a new entry, click . In the new line, that is added to the list, specify the name of the new entry and its value in the Name and Value fields respectively.

       You can add as many entries as you need, just keep in mind that they will be transformed into a command line with its length limited to 256 characters.

     • To delete an entry, select it in the list and click .

     • To change the order of entries, click or .

     Upon clicking OK, you return to the CLI Interpreters dialog, where the entries are transformed into a command line.

6. Click to have PhpStorm display a separate information window with the installation details and the list of loaded extensions and configured options. Note that the additional options specified in the Configuration Options field of the PHP Interpreters dialog are not listed.

1. Press Ctrl+Shift+A and start typing Change PHP interpreter. In the suggestions list, select the Change PHP interpreter action.

   If necessary, you can assign a keyboard shortcut for this action either directly in the suggestions list by pressing Alt+Enter, or at a later point as described in Configure keyboard shortcuts.

2. In the popup menu that opens, select one of the configured local or remote PHP interpreters.

The selected interpreter will be set as the default project interpreter on the PHP page of the Settings/Preferences dialog Ctrl+Alt+S. This will also affect the run/debug configurations, test frameworks', and quality tools' configurations that are set to use the default project interpreter.

Visual Studio Code. VS Code is more than just a code editor, it provides the tools.

This chapter describes how to download and install NetBeans IDE, use it to create a new JavaFX FXML project, start Scene Builder from within the IDE, and run Scene Builder sample applications.

The integration of JavaFX Scene Builder with NetBeans IDE provides optimal development workflow. It is assumed that you have already installed Scene Builder before continuing with the rest of this chapter. Go to the JavaFX Scene Builder Installation Guide for installation information.

Downloading and Installing NetBeans IDE

Go to http://netbeans.org/downloads for the latest NetBeans IDE 7.4 download and installation information.

Creating a New JavaFX FXML Project

In NetBeans IDE, you use the New wizard to create a new JavaFX FXML Application, which is a JavaFX project that is based on an FXML layout. After the project is created, you can edit the FXML file using Scene Builder.

1. From the NetBeans IDE Main menu, select File, and then choose New Project.

2. In the New Project dialog box, choose the JavaFX category and JavaFX FXML Application project, as shown in Figure 1-1. Click Next.

   Figure 1-1 Create New JavaFX FXML Application Project

   
   Description of 'Figure 1-1 Create New JavaFX FXML Application Project'
   

3. In the New JavaFX Application dialog box, enter the values you would like to use for the project name, project location, and FXML file name. Click Finish to complete the project creation. Figure 1-2 gives an example with sample values.

   Figure 1-2 Set the Name and Location of the New JavaFX Application

   
   Description of 'Figure 1-2 Set the Name and Location of the New JavaFX Application'
   

   The IDE's Projects window is updated with the new JavaFX application you just created.

Starting Scene Builder from NetBeans IDE

As shown in Figure 1-3, you can either choose Open to edit the FXML file with the Scene Builder tool or choose Edit to edit the FXML file with the Netbeans FXML editor.

Figure 1-3 Open FXML File from NetBeans IDE

Description of 'Figure 1-3 Open FXML File from NetBeans IDE'

When you right-click the node for the FXML file and choose Open, then NetBeans IDE automatically locates the latest installed Scene Builder on your system and the Scene Builder window appears on top of the Netbeans window, as shown in Figure 1-4.

If you want to use a different installation of Scene Builder or if NetBeans cannot locate the installed Scene Builder, use the following steps to set the location of the Scene Builder installation you would like to use with NetBeans IDE.

1. From the Main menu, select Tools and choose Options.
   On the Mac OS platform, select NetBeans and choose Preferences from the Main menu.

2. In the Options window, click Java and then the JavaFX tab.

3. Specify the location of the Scene Builder installation folder and then click OK.

Figure 1-4 Open FXML File in Scene Builder (Click image to enlarge.)

Description of 'Figure 1-4 Open FXML File in Scene Builder'

Netbeans Vs Phpstorm

To open the FXML file in the NetBeans FXML editor, from the File menu, right-click the file's node and choose Edit. The FXML source file contents are shown in the IDE's source editor window, as shown in Figure 1-5.

Figure 1-5 Open FXML File in NetBeans FXML Editor

Description of 'Figure 1-5 Open FXML File in NetBeans FXML Editor '

Synchronizing With the Controller Source Code

The NetBeans IDE's Make Controller feature allows you to synchronize the modifications you make in the FXML file that is currently opened in Scene Builder and the controller source code opened in NetBeans IDE. To illustrate this feature, do the following:

Visual Studio Code Vs Phpstorm

1. In Scene Builder, drag a Button control from the Library panel to the Control panel.

2. In the Code panel, assign a new value for the new button's fx:id field and a new method name for the onAction method.

3. Select File in the main menu and then Save.

4. In NetBeans IDE 7.4 or later, right click the project node for the FXML file that you just edited and select Edit from the contextual menu.

5. From the main menu, select Source and then Make Controller.
   The @FXML private variable and the new onAction method for the button you just added in Scene Builder are created in the controller source file. Use the Make Controller command if you delete an element in the Control panel or update an fx:id value or a method name in Scene Builder.

Phpstorm Vs Eclipse

Where to Go From Here

Now that you are familiar with the integration between the Scene Builder tool and NetBeans IDE, look at JavaFX Scene Builder User Guide to learn more about the available Scene Builder features. Use the steps described in Getting Started with JavaFX Scene Builder to create a simple issue tracking application.

You can also try the sample applications provided with the Scene Builder release. These samples are Netbeans projects, which means they can be compiled and ran directly after being opened in the NetBeans IDE. You can download the Scene Builder samples from http://www.oracle.com/technetwork/java/javafx/downloads/index.html. Right-click the project's node in the IDE's Project window and choose Run, as shown in Figure 1-6.

Figure 1-6 Run Scene Builder Sample Application

Description of 'Figure 1-6 Run Scene Builder Sample Application '