Home
HCL Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
Programming
XPages uses JavaScript™ for programming while the forms-based design elements use the formula language, LotusScript®, Java™, and JavaScript.
Eclipse-based language interfaces
Java™ and LotusScript® have interfaces based on Eclipse as well as the older interfaces based on Notes®.
Eclipse-based Java™ interface
The Java™ interface for agents, libraries, and Web services now opens the Eclipse Java editor. You can switch back and forth between the Eclipse and Notes® editor by selecting or clearing the related Designer editor Preferences.

HCL Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
- Product overview
  HCL Domino® Designer supports applications development for the HCL Domino platform using XPages, forms, views, and other elements such as controls.
- Tutorials
  This section contains tutorials and information about tutorials.
- Administering applications
  HCL Domino Designer provides features for administering and managing your work and related files while developing your application projects.
- Designing XPages applications
  HCL Domino® Designer provides the means to populate an XPage with controls and other artifacts, and to associate an XPage with data stores.
- Designing composite applications
  You can create composite applications from XPages.
- Programming
  XPages uses JavaScript™ for programming while the forms-based design elements use the formula language, LotusScript®, Java™, and JavaScript.
  - Scripting in XPages
    The scripting contexts are event handlers and formulas. The scripting language is JavaScript™ supplemented by simple actions and expression language (EL).
  - Eclipse-based language interfaces
    Java™ and LotusScript® have interfaces based on Eclipse as well as the older interfaces based on Notes®.
    - Eclipse-based Java™ interface
      The Java™ interface for agents, libraries, and Web services now opens the Eclipse Java editor. You can switch back and forth between the Eclipse and Notes® editor by selecting or clearing the related Designer editor Preferences.
      - Enabling and disabling the Eclipse interface
        The Eclipse interface is enabled by default.
      - Interface description
        The Java™ interface for agents, libraries, and Web services administers the source files and invokes the editor.
      - Copying and pasting files
        You can copy and paste files.
      - Deleting files
        You can delete files.
      - Renaming files
        You can rename files.
      - Compiling and saving
        You can compile and save files.
      - Exporting files
        You can export files.
      - Importing files
        You can import files.
      - Importing script libraries with the Eclipse Java interface
        You can import script libraries.
      - Refactoring
        You can refactor elements.
      - Adding Java™ archives to the Domino® classpath
        You can extend the Domino® classpath, for example, to add third-party JAR files.
      - Debugging Java™ code
        You can debug Java™ code running under control of a Notes® client JVM (Java Virtual Machine).
    - Eclipse-based LotusScript® editor
      The LotusScript® editor in Eclipse (LSEE) is an alternative to the Notes-based LotusScript editor. LSEE takes advantage of the many editing features of Eclipse while retaining most of the Notes® features. You can switch back and forth between the Eclipse and Notes editor by selecting or clearing the related Designer editor Preferences.

Eclipse-based Java™ interface

The Java™ interface for agents, libraries, and Web services now opens the Eclipse Java™ editor. You can switch back and forth between the Eclipse and Notes® editor by selecting or clearing the related Designer editor Preferences.

The Eclipse Java™ editor is the same editor you open if you are in the Java™ perspective and click File > New > Class or edit an existing Java™ file.