Lingon X 6 5 – Run Applications And Scripts Automatically

Run applications and scripts automatically. Battery Monitor. Display of battery information from your menu bar (was Battery Diag).

1. Lingon X 6 5 – Run Applications And Scripts Automatically Enable
2. Lingon X 6 5 – Run Applications And Scripts Automatically Start
3. Lingon X 6 5 – Run Applications And Scripts Automatically Allow
4. Lingon X 6 5 – Run Applications And Scripts Automatically Order

Starting Application Launcher

The following sections explain how to manually start Application Launcher and how to automate starting the applications:

1. Lingon X 6 For Mac Torrent is an easy to use utility that run things automatically on your Mac.It can build models quickly and easily, saving time and effort. Directly linking to your database Calling and modifying data Depending on the circumstances, Lingon X is intuitive to use and has no ambiguous components.
2. Kaspars Vilde at XenDesktop/XenApp 7.X Applications – Exporting / Importing at Citrix Discussions has scripts to export published apps from one farm and import to another farm. Studio Administrators Full Administrators. In the Studio, under Configuration, click the Administrators node. The first time you access the node you'll see a Welcome.
3. If you want application-consistent agentless backups, this step is required. Otherwise, your backups on VMs running SQL Server or Exchange Server will be crash-consistent only. For more information about the difference between these two states, see 'Understanding crash-consistent and application-consistent backups' in the Rapid Recovery User Guide.
4. The command pack will obfuscate the scripts automatically, do not try to pack the obfuscated the scripts. Note From PyArmor 5.5.0, it could improve the security by passing the obfuscated option -advanced 1 to enable Advanced Mode.

Windows 2000/XP File System Rights

To ensure that Application Launcher has the local file system access that it needs to distribute applications, make sure the user has the following rights on the workstation:

• At least Read access to the NAL cache directory (typically, c:nalcache). For more information, see Understanding File System Rights to the NAL Cache in ZENworks 6.5 and in ZENworks 6.5 Support Pack 1 (SP1).
• Full Control access to the user's temp directory (typically, c:documents and settingsusernamelocal settingstemp).
• Full Control access to the user's data encryption directory (typically, c:documents and settingsusernameapplication datamicrosoftcrypto). This is required only if the user is using the Desktop Management Agent without a network client.
• ReadWrite rights to the HKEY_CURRENT_USER SoftwareNetWareNAL.1.0 registry key.
• Read rights to the HKEY_LOCAL_MACHINESoftwareNetWareNAL1.0 registry key
• Read rights to the HKEY_LOCAL_MACHINESoftwareNovellZENworks registry key.

If you have not locked down the workstation, the appropriate rights can be granted through membership in the Users group.

In addition, the System user requires full access to all areas of the workstation so that the NAL Service (a component of Application Launcher) can distribute applications and launch applications configured to run in the 'system' space. By default, this access is granted to the System user as a member of the Administrators group. Do not limit the default rights given to the Administrators group or the System user account.

For more information about Application Launcher file system access requirements, see Novell Application Launcher: Managing Authentication and File System Access.

Manually Starting Application Launcher

The view (Application Window, Application Explorer, or Application Browser) you want to use determines how you start Application Launcher.

The following sections contain additional information:

Application Window

To start Application Launcher so that the Application Window view is displayed:

1. Click the Start menu > Programs > Novell ZENworks Desktop Management > Application Window.

   or

   Run nalwin.exe or nalwin32.exe from the c:program filesnovellzenworks directory.

   or

   Run nal.exe from the sys:public directory on the ZENworks Desktop Management Server.

   In previous releases, nal.exe copied the Novell Application Launcher files to the workstation and then started the Application Window. Beginning with ZENworks for Desktops 4, nal.exe does not copy the files to the workstation; it only starts the Application Window if the Novell Application Launcher files are installed on the workstation. The primary purpose of the nal.exe file on the ZENworks Desktop Management Server is to maintain backwards compatibility with login scripts created for previous versions.

   IMPORTANT: You must ensure that you are not executing nal.exe from a server that has ZENworks for Desktops version 4.x or earlier installed. Running the ZENworks for Desktops 3.x nal.exe will downgrade the Novell Application Launcher components on your workstation and will cause error in the Application Launcher processes.

   IMPORTANT: If you run nal.exe from the sys:public directory and receive an error stating 'The ordinal 6625 could not be located in the dynamic link library MFC42.DLL,' you need to update your server's sys:publicmfc42.dll file. The correct version of mfc42.dll is installed to workstations by the ZENworks Desktop Management Agent. You can copy the file from a workstation's c:winntsystem32 directory to the server's sys:publicmfc42.dll directory.

For information about command line switches that can be used when starting the Application Window, see Application Window Command Line Switches.

Application Explorer

To start Application Launcher so that the Application Explorer view is displayed:

1. Click the Start menu > Programs > Novell ZENworks Desktop Management > Application Explorer.

   or

   Run nalview.exe or naldesk.exe from the c:program filesnovellzenworks directory.

   or

   Run nalexpld.exe from the sys:public directory on the ZENworks Desktop Management Server.

   In previous releases, nalexpld.exe copied the Novell Application Launcher files to the workstation and then started the Application Explorer. Beginning with ZENworks for Desktops 4, nalexpld.exe does not copy the files to the workstation; it only starts the Application Explorer if the Novell Application Launcher files are installed on the workstation. The primary purpose of the nalexpld.exe file on the Desktop Management Server is to maintain backwards compatibility with login scripts created for previous versions.

   IMPORTANT: You must ensure that you are not executing nal.exe from a server that has ZENworks for Desktops version 4.x or earlier installed. Running the ZENworks for Desktops 3.x nal.exe will downgrade the Novell Application Launcher components on your workstation and will cause error in the Application Launcher processes.

   IMPORTANT: If you run nalexpld.exe from the sys:public directory and receive an error stating 'The ordinal 6625 could not be located in the dynamic link library MFC42.DLL,' you need to update your server's sys:publicmfc42.dll file. The correct version of mfc42.dll is installed to workstations by the ZENworks Desktop Management Agent. You can copy the file from a workstation's c:winntsystem32 directory to the server's sys:publicmfc42.dll directory.

For information about command line switches that can be used when starting the Application Window, see Application Explorer Command Line Switches.

Application Browser

To start Application Launcher so that the Application Browser view is displayed:

1. Launch the Web browser, then click the Application Browser icon on the Standard Buttons toolbar.

Automating Application Launcher Startup

There are several ways to automatically start Application Launcher, including the following:

• Include the appropriate Application Window, Application Explorer, or Application Browser startup commands in the user's Windows or network login script.
• Add the Application Window or Application Explorer shortcut to the Windows Startup folder. The Desktop Management Agent installation program includes options to let you add either shortcut to the Startup folder.

This chapter describes the procedures and tools available for developing HTML5/JavaScript applications in the NetBeans IDE, including information on creating, running, integrating and debugging your application.

This chapter contains the following sections:

20.1 About Developing HTML5 Applications

An HTML5 application project is an application that is displayed in a browser on your desktop or a mobile device. An HTML5 application is typically comprised of HTML, CSS and JavaScript files. The JavaScript that is used to manipulate and process objects in the application is generally handled on the client side by the JavaScript engine in the web browser. An HTML5 application is often used as a client that consumes various web services.The IDE provides the following tools to support the development of HTML5 applications and HTML5 in PHP and Java web applications:

• Wizards for creating HTML5/JavaScript applications and files

• JavaScript code-completion, debugging and testing

• Code inspection using Chrome or bundled WebKit browsers

• CSS and CSS preprocessor file editors and styling tools

• Wizard to generate JavaScript clients for RESTful web services.

• Network Monitor for REST web service calls and WebSocket communication

The IDE also provides tools for packaging HTML5 applications as native mobile applications via Apache Cordova.

20.2 Working with HTML5/JavaScript Applications

The following work flow shows how to work with HTML5/JavaScript applications.

How to develop an HTML5/JavaScript application:

1. Create a new HTML5/JavaScript Application project in the New Project wizard. See Section 20.3, 'Creating an HTML5/JavaScript Application Project.'

2. Create and edit HTML, JavaScript and CSS files using wizards and the editor.

3. Specify the target web browser and platform. See Section 20.4, 'Running an HTML5 Application.'

4. Run the application and debug the JavaScript.

20.3 Creating an HTML5/JavaScript Application Project

The IDE provides wizards for creating HTML5 projects and the HTML, CSS and JavaScript files that HTML5 projects typically contain. When you use the New Project wizard to create an HTML5 project you have the option to create the project based on a site template. In the wizard you can specify a site template that is located on your local system or download one of the listed site templates from an online repository.

To create an HTML5/JavaScript application project:

1. Choose File > New Project from the main menu.

2. Select the HTML5/JS Application project template from the HTML5/JavaScript category.

   Alternatively, select the HTML5/JS Application with Existing Sources to import an existing project as an HTML5/JS application.

   Click Next.

3. Specify the project name and location.

4. Click Next in the Name and Location panel.

5. Specify a site template for the application or select No Site Template to create an empty application that only contains an index.html file. Click Next.

6. Specify the files to be created for such tools as npm, Bower, Grunt, Gulp and added to the project (optional).

7. Click Finish.

When you click Finish, the IDE creates the project and displays a node for the project in the Projects window.

20.3.1 How to Create HTML5/JavaScript Applications for Mobile Platforms

The IDE includes an HTML5/JavaScript site template that enables you to easily create a mobile application that is built on the Cordova platform. Cordova enables you to create applications that take advantage of some of the native functionality that is provided on Android and iOS mobile devices. You can create an HTML5/JavaScript application using the Cordova template or add support for Cordova to your HTML5/JavaScript application.

You must install Cordova on your local system before you can create a Cordova project. The IDE will prompt you to install Cordova if your Cordova installation is not detected when you create a Cordova application or when you add support for Cordova to an application. You can find the installation instructions and additional details about the platform at the following site.

Note:

To develop an application for a mobile platform you must first install the required platform software and the platform must be recognized by the IDE. If you are developing for the Android platform you need to specify the location of the Android SDK on your local system.

Note:

How to register the Android mobile platform with the IDE:

1. Open the Options window in the IDE.

2. Click the Mobile Platforms tab in the Miscellaneous category of the Options window.

3. Type the location of the Android SDK installation or click Browse to locate the installation on your local system.

How to create a new Cordova application:

1. Choose File > New Project from the main menu.

2. Select the Cordova Application project template from the HTML5/JavaScript category. Click Next.

3. Specify the project name and location.

4. Click Next in the Site Template panel.

   The Cordova Hello World template is already selected.

5. Specify the JavaScript files to add to the project (optional).

   You can modify the JavaScript Files that are included in the project at any time in the JavaScript Files category of the Project Properties window.

6. Specify the Cordova project configuration details (optional).

   You can edit the configuration details at any time in the Cordova category of the Project Properties window.

7. Click Finish.

How to add Cordova support to an HTML5 application:

1. Right-click the project node in the Projects window and choose Properties.

2. Select the Cordova category in the Project Properties window.

3. Click Create Cordova Resources in the Cordova panel.

   After you click Create Cordova Resources, the IDE adds creates a Cordova configuration file in the project and enables two tabs in the Cordova panel where you can specify additional details.

4. Specify an application ID, name and version for the Cordova application. Click OK.

How to add Cordova plugins to a Cordova application:

1. Right-click the Cordova application in the Projects window and choose Properties in the popup menu.

2. Select the Cordova category in the Project Properties window and click the Plugins tab.

3. Select the Cordova plugin from the list of available plugins and click the right arrow ( > ) to move the plugin to the list of selected plugins. Click OK.

20.3.2 How to Add Support for HTML5 Features to an Application

You can incorporate JavaScript and CSS to Java web applications and PHP applications by adding the files to the project. You can also use the Project Properties window to include JavaScript libraries and configure CSS preprocessors that you want to use in the project. You can run the applications on mobile browsers and on Android and iOS devices and emulators and debug JavaScript files. It is not necessary to change the project type of an application or create a new project.

How to add JavaScript libraries to a Java web or PHP application:

1. Right-click the project node in the Projects window and choose Properties in the popup menu.

2. Select the JavaScript Libraries category.

3. Select the required category under the JavaScript Libraries node that you want to add, update, or remove from the project and click OK.

20.3.3 How to Create a Node.js Application

The IDE provides the following wizards for creating Node.js projects:

• Node.js Application

• HTML5/JS Application with Node.js

• Node.js Application with Existing Sources

To create a new Node.js application project:

1. Choose File > New Project from the main menu.

2. Select the Node.js Application project template from the HTML5/JavaScript category. Click Next.

3. Specify the name and location for your project. Click Next.

4. In the Tools panel select the options required for your project.

5. Click Finish.

When you click Finish, the IDE creates the project and displays a node for the project in the Projects window.

To create a new HTML5/JS Application with Node.js:

1. Choose File > New Project from the main menu.

2. Select the HTML5/JS Application with Node.js project template from the HTML5/JavaScript category. Click Next.

3. Specify the name and location for your project. Click Next.

4. In the Express panel select Express Generator options (optional). Click Next.

5. In the Tools panel select the options required for your project (optional). Click Next.

6. Click Finish.

When you click Finish, the IDE creates the project and displays a node for the project in the Projects window.

To create a Node.js Application with existing sources:

1. Choose File > New Project from the main menu.

2. Select the Node.js Application with Existing Sources project template from the HTML5/JavaScript category. Click Next.

3. Specify the source folder, site root, name and location for your project. Click Next.

4. Click Finish.

When you click Finish, the IDE creates the project and displays a node for the project in the Projects window.

20.4 Running an HTML5 Application

An HTML5 application project is typically run in a browser on your desktop or a mobile device. When you run an HTML5 application on your local system for testing or debugging you do not need to compile or deploy the application to a server because the JavaScript engine in the browser generally handles any scripts in the application. To run the application you first specify the browser and then run the application.

You can run an HTML5 application on an emulator for the mobile platform or deploy the application to the mobile device.

20.4.1 How to Specify the Browser

When you want to run an HTML5 application or file from the IDE you need to specify the target browser. The IDE enables you to easily select any of the browsers that are installed on your local system or the embedded WebKit browser. If you are developing an application for a mobile device you can choose to run the application in an emulator for the mobile device or deploy directly to a mobile device.

To specify the browser for an HTML5 application:

• To specify the target browser for the application, perform one of the following steps:

  • Select the application in the Projects window and then select the browser from the drop-down list in the Toolbar.

  • Open the Project Properties window and select the browser in the Run panel of the window.

The list of browsers is organized in a table to help you select the target browser. If you select a browser or device in the top row of the table you can debug the application in the IDE and use other features that are provided when the IDE is integrated with the browser. The table organizes the browsers in the following columns:

• The Browsers column displays the web browsers that are available on your local system. When you select a browser in the Browsers column the application will launch in a window in the selected browser when you run the application.

• The Mobile Device Browser column displays a list of mobile devices that you can select as the target platform and the browsers that are available on that platform. When you select a browser in the Mobile Device Browser column, the IDE will either run the application in the browser on the selected mobile device or in an emulator for the device.

• The Cordova column displays a list of mobile devices that you can select as the target platform. When you select a device in the Cordova column, the IDE will package the project as a native mobile application and deploy the application to the mobile device or emulator. Click Configure Cordova to open the Cordova panel in the Project Properties window.

You must install Apache Cordova on your local machine if you want to specify a target in the Cordova column.

If you want to run an application in a browser on an Android mobile device or in the Android emulator you need to install the Android SDK on your local system and register the location of the Android SDK in the Options window. The iOS device and simulator are only available on OS X.

If you want to debug an HTML5 application or file, or synchronize the IDE with your browser to inspect your code, you should select either Chrome with NetBeans Connector or Embedded WebKit Browser as the target browser.

20.4.2 How to Run an Application

After you specify the browser, you can run the application in the following ways.

• Right-click the project node in the Projects window and choose Run in the popup menu.

• Select the application in the Projects window and then click Run in the Toolbar or choose Run > Run Project (F6) in the main menu.

When you run an application, the IDE automatically opens the application in the selected browser or mobile device and opens the Browser Log in the Output window.

If more than one project is open you can specify one of the projects as the Main Project. After you specify the project as the Main Project, the F6 keyboard shortcut will always run the Main Project regardless of the project that is selected in the Projects window.

20.4.3 How to Run a File

You can run an HTML file in an HTML5 application in the following ways.

Lingon X 6 5 – Run Applications And Scripts Automatically Enable

• Right-click the HTML file in the Projects window and choose Run File from the popup menu (Shift-F6).

• If the HTML file is open in the editor, you can right-click in the file and choose Run File (Shift-F6) from the popup menu or click the Run File button in the Selection tab of the CSS Styles window.

When you run a file, the IDE opens the file in the target browser for the application.

20.5 Integrating an HTML5 Project with a Browser

A NetBeans extension is available for the Chrome browser that enables the IDE and the browser to communicate. To integrate the IDE with the Chrome browser, you need to install the NetBeans Connector extension from the Chrome Web Store or install the extension manually. After you install the extension you can perform the following tasks in the Chrome browser:

• Use Inspect mode to select and locate elements in your code

• Debug JavaScript files

• Select various browser sizes from the NetBeans actions menu

Do not close the infobar in the tab in the Chrome browser that informs you that 'NetBeans Connector is debugging this tab'. Closing the infobar will disconnect the IDE from the Chrome browser. To reconnect the IDE, close the tab where the application was running and re-run the application from the IDE.

Note: You only need to install the extension one time.

20.5.1 How to Install the Extension from the Chrome Web Store

After downloading, you can perform the following steps to install the NetBeans extension for the Chrome browser.

To install the NetBeans extension for Chrome:

1. Right-click an HTML5 project node in the Project Projects window and choose Properties in the popup menu.

   Alternatively, you can select a target browser for the project from the drop-down list in the toolbar.

2. In the Run panel of the Properties window, select Chrome with NetBeans Connector in the server drop-down list. Click OK.

3. Right-click the HTML5 project node in the Projects window and choose Run.

   When you click Run, the IDE opens a dialog that prompts you to install the extension from the Chrome Web Store.

4. Click Go to Chrome Web Store in the Install Chrome Extension dialog box.

5. Click Free in the Chrome Web Store to install the extension and confirm that you want to add the NetBeans Connector extension.

6. After the extension is installed in the Chrome browser, click Re-run Project in the Install Chrome Extension dialog box to open the HTML5 application in the Chrome browser.

   You will see an infobar in the tab in the Chrome browser that informs you that 'NetBeans Connector is debugging this tab'.

20.5.2 How to Install the Extension Manually

If you are unable to connect to the Chrome Web Store you can install the NetBeans Connector extension manually by performing the following steps.

To install the Chrome extension manually:

1. Open your Chrome browser to chrome://extensions/.

2. On your local system, navigate to the NETBEANS_INSTALL/webcommon/modules/lib directory, where NETBEANS_INSTALL is the installation of the IDE.

3. Drag the NetBeans Connector extension (netbeans-chrome-connector.crx) from the lib directory into the Extensions tab in the Chrome browser window and approve the addition of the extension.

4. Right-click the HTML5 project node in the Projects window and choose Run to open the application in the browser.

   You will see an infobar in the tab in the Chrome browser that informs you that 'NetBeans Connector is debugging this tab'.

20.6 Inspecting HTML5 Code with the Browser

You can use the Inspect mode to help you locate and edit the source code in an HTML5 application. When Inspect mode is enabled, information about some of the actions that you perform in the browser such as selecting and highlighting elements is communicated to the IDE. When you run the application, you can use your browser to help you locate HTML elements in your source code. When you select or place your cursor over elements in the browser window, the element is simultaneously highlighted or selected in the Browser DOM window of the IDE. When you select an element, the style rules for the element are automatically displayed in the Selection tab of the CSS Styles window.

To inspect your application with a browser:

1. Set the target browser for the application to one of the browsers or devices listed in top row in the browser selection drop-down list.

   The browsers and devices in the top row of the browser selection drop-down list support Inspect mode.

2. Run the application or file.

   When you run the application the target browser opens and displays the index page or file in the window.

3. Enable Inspect mode (Ctrl+Shift+S) in the browser.

   In the Chrome browser you can enable Inspect mode in the NetBeans Actions menu. In the Embedded WebKit Browser you can click the Inspect button in the toolbar. Alternatively, you can click the Inspect icon in the Browser DOM window.

4. Move your cursor over or select an HTML element in the page in the browser window.

When you move your cursor over or select an element in the browser the contents of the following windows in the IDE are updated to synchronize with your actions in the browser.

• Browser DOM window. The Browser DOM window displays a DOM tree of the current page. When you move your cursor over an element in the browser the element is highlighted in the Browser DOM window. You can double-click an element in the window to open the source file in the editor.

• CSS Styles window. The Selection tab of the CSS Styles window displays the style rules for the selected element. You can edit the rules for the element in the CSS Styles window.

When you enable the Inspect mode in the browser, any element that is in the 'hover' state remains in the state until you disable the Inspect mode. You can select an element in the hover state and inspect and modify the properties of the hover state and view the changes to the element in your browser.

To enable Inspect mode in the Chrome browser you need to install the NetBeans extension to integrate the IDE with the browser.

20.7 Changing Browser Screen Sizes

A single HTML5 application might be viewed on various devices with different screen sizes. The IDE can help you develop projects that can respond and adapt to different display devices by enabling you to view pages at different screen sizes. When you run the HTML5 application from the IDE you can choose to view the pages in one of the default screen sizes or create a custom screen size.

You can view your application in any browser, but if you want to be able to quickly switch between screen sizes you need to specify one of the following integrated browsers as the target browser:

• Chrome with NetBeans Connector

• Embedded WebKit Browser

When you view the application in one of the integrated browsers you can choose the display size in a menu in the browser.

You can specify the target browser for the application in the Project Properties window or in the Set Project Configuration drop-down list in the toolbar of the IDE.

20.7.1 How to Switch Between Screen Sizes

The integrated browsers provide menus that enable you to switch between common screen sizes that are pre-configured in the menu. When you select a new screen size the display area of the browser resizes to the selected size. By changing the screen size you can view how the layout of the application responds to different sizes, for example, as a result of media queries that are specified in the style sheet.

After you launch the application you can select a screen size from the menu in the browser. The location of the menu for selecting the screen size options depends upon the target browser.

• Chrome with NetBeans Connector. Click the NetBeans icon in the URL location bar to open the menu and select a screen size.

• Embedded WebKit Browser. Select a screen size in the Other Options menu or click an icon in the toolbar. The toolbar in the Web Browser window contains the following elements.

  • Display device icons. Click a display device icon to resize the display area to the selected size. You can place your cursor over an icon to display the dimensions of the display device. You can modify which icons are displayed in the toolbar by choosing Customize in the Other Options drop-down list.

  • Other Options menu. Select a window size in the drop-down list to view the page contents in the selected window size. The drop-down list displays all the available window sizes. Choose Customize to open a dialog that enables you to modify, create or remove window sizes.

  • Magnification selector. Type a value in the text field or select a value in the drop-down list to change the magnification of the contents of the page.

  • Inspect icon. Select to enable Inspect mode in the page.

When you run an HTML5 application the location of the current page is displayed in the Location bar. Pages are rendered using the WebKit browser engine running on the embedded lightweight server (localhost:8383). You can modify the server details in the Project Properties window.

20.7.2 How to Create a Custom Screen Size

You can create custom sizes for windows by selecting Customize in the screen size menu. When you select Customize the browser displays a window that enables you to create a new size and to modify the default screen size options. You can also edit the contents of the menu.

20.8 Creating HTML5 Templates

An HTML5 template enables you to quickly create an HTML5 project that contains the files and a structure that is based on the template. A site template can help you quickly develop a project by providing some JavaScript, CSS and HTML files that you can then modify according to your needs.

When you create an HTML5 project in the New Project wizard, you can choose to use a site template .zip archive that is located on your local system, specify the URL of an online template or select a template from the list of popular site templates in the wizard.

20.8.1 How to Create a Site Template

You can use the IDE to create a site template that is based on your project by performing the following steps.

To create a site template:

1. In the Projects window, open the HTML5 project that is the model for your template.

2. Right-click the HTML5 project and choose Save as Template in the popup menu.

3. Specify the name and where you want to save the template.

4. Specify the files that you want to include in the template. Click Finish.

Any template that you save is automatically added to the Select Template drop-down list in the New HTML5 Application wizard.

20.9 Creating Cascading Style Sheets

You can generate a cascading style sheet (CSS) from an existing document type definition (DTD), create an empty style sheet and edit the file in the CSS editor or use a CSS preprocessor to generate style sheets.

When you are editing a CSS file the IDE provides windows and dialog boxes that can help you create CSS rules and declarations. After you create a rule you can add declarations to the rule by editing the style sheet in the editor or in the CSS Styles window. When editing CSS files, you can take advantage of standard editor features, including completion, indentation, syntax coloring, and standard clipboard commands.

If you want to use a CSS preprocessor to generate a style sheet the IDE supports the LESS and Sassy CSS syntax. To compile the LESS or Sass files and generate the style sheet you must first install the LESS or Sass preprocessor software on your local system. After you install the preprocessor software you can configure the software to compile the files and generate the CSS files each time that the LESS or Sass file is saved.

20.9.1 How to Create a Cascading Style Sheet

You can use the New File wizard to create a new cascading style sheet in your project. After you create the style sheet you can see the new file in the Projects window and Files window. When you create the style sheet the file opens in the Source Editor.

To create a cascading style sheet:

1. Choose File > New File from the main menu.

2. Choose HTML5/JavaScript > Cascading Style Sheet. Click Next.

3. Enter a name and location for the CSS file. Click Finish.

20.9.2 How to Add a CSS Rule to a Cascading Style Sheet

You can create a CSS rule in a style sheet by typing directly in the source editor or by using the Edit CSS Rules dialog box. You can open the Edit CSS Rules dialog box from the CSS Styles window.

To add a CSS Rule to a style sheet:

1. Open the CSS file in the source editor.

2. Open the CSS Styles window (Window > Web > CSS Styles).

3. Click Document in the CSS Styles window if the Style Sheets tree is not displayed in the CSS Styles window.

4. Click the Edit CSS Rules icon ( ) to open the Edit CSS Rules dialog box.

5. Select a Selector Type in the dialog box.

6. Type a name in the Selector text field for the id or class element or select an element from the drop-down list.

7. Confirm that the correct style sheet is selected in the Style Sheet drop-down list.

8. Specify any additional properties for the rule. Click OK.

After you click OK you can see that the new rule is listed in the CSS Styles window and the Navigator window and that the rule is added to the CSS file in the editor.

20.9.3 How to Add a Property to a CSS Rule

You can add properties and values to a CSS rule by manually editing the style sheet in the source editor, by selecting values in the CSS Styles window or by specifying values in the Add Property dialog box.

To add a property to a CSS rule in the CSS Styles window:

1. Open the CSS file in the source editor.

2. Open the CSS Styles window (Window > Web > CSS Styles).

3. Click Document in the CSS Styles window if the Style Sheets tree is not displayed in the CSS Styles window.

4. Select the rule that you want to edit in the top section of the CSS Styles window.

   The properties of the selected rule are displayed in the bottom section of the CSS Styles window.

5. Click Add Property in the left column of the table in the bottom section of the CSS Styles window and choose a property in the drop-down list.

6. Type a value for the property in the text field or choose a value from the drop-down list in the right column of the table and hit the return key on your keyboard.

When you hit the return key the property and value are added to the rule in the CSS editor.

Lingon X 6 5 – Run Applications And Scripts Automatically Start

To add a property to a CSS rule in the Add Property dialog box:

1. Open the CSS file in the source editor.

2. Open the CSS Styles window (Window > Web > CSS Styles).

3. Click Document in the CSS Styles window if the Style Sheets tree is not displayed in the CSS Styles window.

4. In the source editor, place the insert cursor between the brackets of the CSS rule that you want to edit.

5. Click the Add Property icon ( ) in the bottom section of the CSS Styles window to open the Add Property dialog box.

6. Select a value for the property from the drop-down list or type a value in the text field in the right column of the table.

7. Specify any additional properties for the rule. Click OK.

20.9.4 Creating a CSS Preprocessor File

You can create Sass or LESS preprocessor files that can be compiled to generate your CSS files. The IDE provides wizards to generate the preprocessor files and to configure the preprocessor software to watch a location for changes to the files. You must install the CSS preprocessor software on your local system if you want to locally compile the preprocessor files to generate the CSS files.

You can use code completion and syntax coloring in the editor to help you edit CSS preprocessor files.

How to create a CSS preprocessing file:

1. Choose File > New File from the main menu.

2. Choose Sass File or LESS File in the HTML5/JavaScript category. Click Next.

3. Enter a name and location for the new file.

4. (Optional) Select Compile Sass (or LESS) files on Save.

   When you enable compile on save for CSS preprocessor files you can specify the directory that contains the preprocessor files and the directory that will contain the compiled CSS file.

5. (Optional) Modify the input and output directories.

   When the preprocessor file in the input directory is modified and saved the CSS file is automatically recompiled and created in the specified output directory.

6. Click Finish.

20.9.5 How to Generate CSS Files Using a CSS Preprocessor

The IDE can be configured to compile LESS and Sass preprocessor files to generate CSS files. When you are editing the CSS preprocessor files in your project you can compile the files locally to view how your changes affect the layout of the application. The CSS preprocessor software must be installed on your local system if you want to compile the files locally.

You can find instructions for installing LESS and Sass at the following sites.

If you want the preprocessor files automatically compiled when you save them you need to register the CSS preprocessor software with the IDE. You can specify the location of the executables for the CSS preprocessor software in the Options window.

How to register the CSS preprocessor software in the IDE:

1. Open the Options window.

2. Click the CSS Preprocessors tab in the HTML/JS category.

3. Type the path to the executable of the preprocessor software or click Browse to locate the executable on your local system.

4. (Optional) Select Open Output on Error if you want the IDE to open the Output window when an error is encountered during compilation. This option is enabled by default.

5. (Optional) Select Generate extra debug information if you want debug information generated in the CSS file. This option is enabled by default.

You can configure the software to watch the location of your preprocessor files in your application and automatically compile the CSS file when the preprocessor file is saved. You can enable compile on save for CSS preprocessor files when you create the file or in the Project Properties window.

Note:

How to enable compile on save in the Project Properties window:

1. Right-click the project node in the Projects window and choose Properties in the popup menu.

2. Select the CSS Preprocessors category and select the tab for the preprocessor for your project (LESS or Sass).

3. Select Compile Sass Files on Save (or Compile LESS Files on Save).

   If you see a warning in the Project Properties window that the executable is not selected, click Configure Executables to open the Options window and specify the location of the preprocessor executable.

4. In the Watch table, specify the Input directory that contains the preprocessor files.

5. Specify the Output directory for the CSS file that is generated.

6. (Optional) Specify any compiler options. Click OK.

20.10 Creating JavaScript Files

The IDE provides a wizard for creating JavaScript files and support for JavaScript in the source editor. When you run the application the Browser Log tab opens in the Output window.

20.10.1 How to Create a JavaScript File

You can add JavaScript files to your project in one of two ways:

• as a JavaScript file

• as a JavaScript library

You can use the New File wizard to add a JavaScript file to a project at any time. You can also use the wizard to create a file of common JavaScript functions which you can use to provide functionality to multiple HTML5 or web projects. If the HTML or Web categories are not available in your installation you can choose JavaScript File in the Other category in the New File wizard. If you want the JavaScript file to be visible in the Projects window, create the JavaScript file in an appropriate subfolder of the project, such as public_html or src.

The default template that is used for JavaScript files contains only licensing information. You can use the Templates Manager to modify the JavaScript template.

To create a standalone JavaScript file:

1. Select File > New File > HTML5/JavaScript > JavaScript File.

2. Enter the desired file name in the File Name field.

3. Click Finish to save the file.

To edit the JavaScript File template:

1. Select Tools > Templates in the main menu to open the Templates Manager.

2. Expand the HTML5/JavaScript node in the list of templates and select the JavaScript File template.

3. Click Open in Editor to edit the template in the source editor.

20.10.2 How to Edit a JavaScript File

You can edit JavaScript files in the source editor. The source editor provides standard features such as code completion and syntax coloring. The editor provides code highlighting for methods and variables, as well as global variables and properties of literal objects. When a JavaScript file is open in the source editor the Navigator window displays the structure of the JavaScript file and enables you to easily navigate to elements in the code. JavaScript editing features also work for JavaScript code embedded in PHP, JSP and HTML files.

The IDE provides some JavaScript code templates to help you to generate code. You can view the list of default JavaScript code templates and add your own code templates in the Code Templates tab in the Editor category in the Options window.

The IDE provides tools to help you with your JavaScript code. When you are editing your code a parser runs in the background and provides detailed warnings and hints to resolve potential problems. You can configure the JavaScript hints that are displayed in the Options window.

JavaScript code completion gives you a choice of the IDE's built-in JavaScript core classes to insert into your code and can show you the methods available for JavaScript strings. Code completion works with all the literal types in JavaScript. The type analysis and code completion machinery also knows about prototype style classes (regular functions only) and the operator for constructing them.

Lingon X 6 5 – Run Applications And Scripts Automatically Allow

NetBeans IDE consults type parameters for function parameters and return types (@type, @param, and other JSDoc tags). These types are shown in code completion: in the list, in the documentation, and in parameter hints. Return types are also shown in the code completion dialog after the function name, separated by a colon. The IDE can determine the return type for many functions. This function is essential for JSQuery support. For example, methods which return true or false have a Boolean return type, those returning literal numbers have a Number return type, and so on. The IDE both infers types and explicitly tracks declared types via comments. The most important implication is that the IDE follows types through calls.

To edit a JavaScript file:

• Expand the project node in the Projects window and double-click the JavaScript file to open the file in the editor.

20.10.3 How to Debug a JavaScript File

You can use the IDE to debug JavaScript files in HTML5 applications. JavaScript debugging starts automatically when you run the application or unit tests in one of the browsers that support debugging. When you are debugging the application the following windows provide debugging details.

Table 20-1 JavaScript Debugging Windows

When you run the application the debugger will pause execution of the application at the first breakpoint in the JavaScript that is encountered and the JavaScript file that contains the breakpoint opens in the editor. The IDE also automatically opens the JavaScript debugger windows. You can use the debugging buttons in the toolbar to step through the JavaScript files.

To debug JavaScript files in the IDE the IDE needs to be able to communicate with the debugger. To use the JavaScript debugger in the IDE, you need to select one of the following browser options as the target browser.

Table 20-2 Browsers that support JavaScript Debugging

20.10.4 How to Set JavaScript Breakpoints

To debug the JavaScript in your application in the IDE, you need to specify breakpoints that will pause execution of the scripts when they are hit. You can set the following JavaScript breakpoints in the IDE:

Lingon X 6 5 – Run Applications And Scripts Automatically Order

Table 20-3 Types of JavaScript Breakpoints

To open the New Breakpoint dialog box:

• Choose Debug > New Breakpoint from the main menu.

  Alternatively, you can open the Breakpoints window by clicking the New Breakpoint icon ( ) in the left margin.

The steps for setting JavaScript breakpoints will depend upon the type of breakpoint.

To set a DOM breakpoint:

1. Open the HTML file in the editor.

2. Open the Browser DOM window, if not already open.

3. In the Browser DOM window, locate the object in the DOM tree that you want to debug.

4. Right-click the object and choose one of the DOM breakpoint properties in the popup menu.

To set a line breakpoint:

1. Open the JavaScript file in the editor.

2. Click in the left margin of the editor next to the line where you want to set the breakpoint.

   The breakpoint icon ( ) will appear in the margin.

To set an event breakpoint:

1. Open a JavaScript file or HTML file in the editor.

2. Place the insert cursor in the file and choose Debug > New Breakpoint in the main menu to open the New Breakpoint dialog box.

3. Select JavaScript in the Debugger drop-down list and select Event in the Breakpoint Type drop-down list.

4. Select any actions that you want to trigger the breakpoint. Click OK.

To set an XMLHttpRequest breakpoint:

1. Open a JavaScript file or HTML file in the editor.

2. Place the insert cursor in the file and choose Debug > New Breakpoint in the main menu to open the New Breakpoint dialog box.

3. Microsoft office. Select JavaScript in the Debugger drop-down list and select XMLHttpRequest in the Breakpoint Type drop-down list.

4. Specify the URL that will trigger the breakpoint when it is requested by a script. Click OK.

20.10.5 How to Run Unit Tests on JavaScript Files

You can configure the IDE to use Karma, JS Test Driver or Mocha to run the unit tests for your JavaScript files. To use the test runner you need to install the test runner and then configure the test runner to specify the browsers and testing framework that you want the test runner to use and the files to load when running the tests. After you configure the test runner for your application you can run the tests from the Projects window. You can view the results of the tests in the Output window of the IDE.

Debugging of unit tests is automatically enabled if you specify Chrome with NetBeans Connector as one of the JS Test Driver browsers when you configure JS Test Driver in the Services window.

To run unit tests with Karma:

1. Prior to installing Karma on your local system you need to download and install Node.js. For more information see http://karma-runner.github.io/latest/intro/installation.html.

2. Choose File > New File to open the New File wizard.

3. Select Karma Configuration File in the Unit Tests category in the New File wizard. Click Next.

4. Use the default name karma.conf for the File Name. Click Finish.

   When you click Finish the IDE creates the karma.conf.js file and opens the file in the editor.

5. Edit karma.conf.js to specify the location of the JavaScript files to be included and excluded when you run the tests and Karma plugins that are required to run the tests with this configuration.

6. Right-click the project node in the Projects window and choose Properties in the popup menu.

7. Select JavaScript Testing category in the Categories pane of the Project Properties window.

8. Select Karma in the Testing Provider drop-down list.

9. To specify the location of your Karma configuration file, click Search and the IDE will find the default Karma configuration file. Alternatively, click Browse to manually locate a configuration file.

10. Click OK.

    When you click OK a Karma node appears under the project node in the Projects window.

11. To start the Karma server, right-click the Karma node in the Projects window and choose Start in the popup menu.

12. (Applies if Karma script is not automatically found by the IDE and the path to Karma needs to be set manually.) In the Options: HTML/JS: Karma window specify the path to the Karma executable file. Click OK.

    When you click OK the Karma server starts.

13. Right-click the project node in the Projects window and choose Test in the popup menu.

    The IDE runs the unit tests. You can open the Test Results window to view the results. You can see details about the specific tests in the Output window.

To run unit tests with JS Test Driver:

1. Download the js-test-driver JAR to your local system.

   Note:

   To use JS Test Driver in the IDE you need to download the JS Test Driver JAR that is available from the following location:

   The JS Test Driver site also provides documentation and details about using JS Test Driver.

2. In the Services window, right-click the JS Test Driver node and choose Configure in the popup menu.

3. In the Configure JSTestDriver dialog box, click Browse and locate the js-test-driver JAR that you downloaded.

4. Select the browsers that you want to run the tests against. Click OK.

   Only browsers that are installed on your local system are displayed in the list.

5. Right-click the JS Test Driver node and choose Start to start the js-test-driver server.

   When you choose Start, each of the browsers that you specified will open a window and will wait to run the unit tests. You can see the status in the js-test-driver server tab in the Output window.

6. Choose New > New File to open the New File wizard.

7. Select JsTestDriver Configuration File in the Unit Tests category in the New File wizard.

8. Use the default name jsTestDriver for the File Name. Click Finish.

   When you click Finish the IDE creates the jsTestDriver.conf file and opens the file in the editor.

9. Edit jsTestDriver.conf to specify the location of the JavaScript source files and test files.

10. Right-click the project node and choose Test in the popup menu.

11. In the Select Testing Provider dialog choose JS Test Driver from the drop-down list and click OK.

    When you click OK the IDE runs the unit tests. You can open the Test Results window to view the results. You can see details about the specific tests in the Output window.

To run unit tests with Mocha:

1. Prior to installing Mocha on your local system you need to download and install Node.js. For more information see https://mochajs.org/#installation.

2. Right-click the project node in the Projects window and choose Properties in the popup menu.

3. Select JavaScript Testing category in the Categories pane of the Project Properties window.

4. Select Mocha in the Testing Provider drop-down list.

5. To specify the location of Mocha install location, click Browse to manually locate a installation directory. Alternatively, if the location automatically found by the IDE is correct, click OK to accept it.

6. Click OK.

7. Right-click the project node in the Projects window and choose Test in the popup menu.

   When you click OK the IDE runs the unit tests. You can open the Test Results window to view the results. You can see details about the specific tests in the Output window.

20.10.6 How to Add a JavaScript Library to a Project

If you are using a JavaScript library that will provide specific functionality in your project you can add JavaScript libraries to a project in the Project Properties window.

To add the npm library to an HTML5/JavaScript application:

1. Download and install Node.js from https://nodejs.org.

2. Open the selected project in the IDE.

3. Right-click the project node in the Projects window and choose Properties.

4. Select the JavaScript Libraries: npm category in the Project Properties window.

5. Select a required tab to add a library from the list of available tabs and click Add.

   Note:

   Choose the Regular tab for npm dependencies that the project requires when it is run, the Development tab for npm dependencies that are not required for the execution of the project (for example, testing tools), and the Optional tab for optional npm dependencies.

6. In the Add npm package dialog type in the name of an npm dependency and click Search.

7. When the dependency is found click Add.

   The npm dependency is added to the project.

8. Click OK to confirm the use of the added npm library.

To add the Bower library to an HTML5/JavaScript application:

Note:

1. Download and install Node.js from https://nodejs.org

2. Download and install Git from https://git-scm.com

3. Run npm install -g bower from your command line.

4. Open the selected project in the IDE.

5. Right-click the project node in the Projects window and choose Properties.

6. Select the JavaScript Libraries: Bower category in the Project Properties window.

7. Select a required tab to add a library from the list of available tabs and click Add.

   Note:

   Choose the Regular tab for Bower dependencies that the project requires when it is run or the Development tab for Bower dependencies that are not required for the execution of the project (for example, testing tools).

8. In the Add Bower package dialog type in the name of a Bower dependency and click Search.

9. When the dependency is found click Add.

   The Bower dependency is added to the project.

10. Click OK to confirm the use of the added Bower library.

To add the CDNJS library to an HTML5/JavaScript application:

1. Open the selected project in the IDE.

2. Right-click the project node in the Projects window and choose Properties.

3. Select the JavaScript Libraries: CDNJS category in the Project Properties window.

4. Click Add.

5. In the Add CDNJS Library dialog type the name of the library and click Search.

6. When the library is found click Add.

   The CDNJS library is added to the project.

7. Click OK to confirm the use of the added CDNJS library.