Atelier 1.1 Release Notes
Atelier Release 1.1.391
Atelier Release 1.1.391 is the initial Atelier 1.1 release. It is available as a plug-in for Eclipse Oxygen (4.7). This release provides the following improvements and bug fixes:
- The debugger has been made more robust.
- Debugging by attaching to and detaching from a running process is supported in server versions 2017.2.0 and later, and depends on fixes available in 2017.2 maintenance releases. A problem with the disconnect button being disabled when it should be enabled has been fixed.
CSP files can be used as a debugging entry point
You can create debug configurations that use a CSP page as an entry point. Create a project mapped to the namespace where the CSP application is located. Open the Debug Configurations dialog by selecting Run > Debug Configurations.... Create a new Atelier Application launch configuration. When completing the form, select the CSP entry point radio button. In the URL field specify the path to the CSP page starting with the CSP application. For example,
/csp/samples/lotteryjoin.csp. Files must be compiled for debugging to work as expected.
Note that breakpoints and stepping through CSP pages are not supported in this release, but are planned future work. You can set breakpoints in code called from a CSP page.
Also note that, like many Eclipse menu items, Run > Debug Configurations... is context dependent. For example, it is not available if an editor has focus while editing a CSP file.
- Improved handling of legacy file format
If you have been using source control by exporting classes and routines to individual XML or RTN files from Studio, you can now modify those files without first converting them to the UDL format. These files will be presented in an Atelier editor as if they were UDL files.
Use the File System import wizard to Import XML or RTN files and add them to an Atelier project. Open these files in an Atelier editor by double-clicking in the Atelier Explorer view. Double-clicking in the Project Explorer opens the file in the default XML editor according to your user preferences. Note that XML files containing more than one class or routine are not supported. You must convert these files to UDL using the Legacy XML import wizard as you did previously.
- Additional support for legacy file format:
- Syntax checking has been enabled.
- File encodings other than UTF-8 are supported
- The Windows-specific problem of a file system exception being thrown when you delete a project that includes a legacy class has been fixed.
- Compile Project now compiles legacy files in the project.
- The legacy editor displays the correct background color for read-only files.
- Known bugs in legacy format support:
- code completion fails in XML files opened in an Atelier editor
- open declaration fails from XML files opened in an Atelier editor
- breakpoint setting fails for XML files opened in an Atelier editor
- Exception thrown when Atelier project is deleted that contains a class or routine file in XML format
- Synchronization skips copy of deployed files when copying from the Server Explorer.
- For InterSystems IRIS, the copyright comment in the syntax checker and legacy XML import wizard is supported.
Configure any Eclipse project as an Atelier project
Easily migrate your existing code base to be used with Atelier. Import your code base from source control using the appropriate wizard contributed by the source control plugin you have installed. You can also import existing Eclipse projects using the Existing Projects into Workspace import wizard. Select the imported project and right-click to open the context menu. Select Configure > Configure Atelier. Complete the dialog that pops up by selecting a connection and namespace for this project and press the OK button.
Note that projects that are not configured to work with Atelier might be filtered from your Atelier Explorer view. You can either view these projects in the Project Explorer view, or open the Atelier Explorer filters from the view's menu and adjust filtering behavior.
- Macro support
Open Declaration support for macros. You can easily unpack macros by jumping directly to their definition.
Select the macro in an Atelier editor and invoke Open Declaration with the key binding (F3 by default) or by selecting it from the editor context menu (right-click in the editor). In order for this feature to work, the server connection associated with a given file (inherited from its project) must be accessible when you invoke Open Declaration.
Code completion for Macros is available in projects with connections to servers 2017.2 and higher.
This feature provides assistance for completing macro references.
To use this feature, open any file where
$$$syntax is legal in the Atelier editor. The server must be accessible. Invoke code assist with CTRL+Space after
$$$syntax. Note that only macros with an associated description are listed.
- Server-side text search is available in projects with connections to servers 2017.2 and higher (available in the Field Test Portal). This feature enables you to discover declarations and references for any pattern. Searches take place on the server in a given a namespace. The scope definition can include system and/or generated items. To use this feature, configure a connection, then open the Atelier Search tab from the Search dialog.
- Atelier editor improvements
- The Atelier editor automatically closes parentheses and double quotes. The editor also automatically closes curly braces and indents the cursor. These features speed up code writing by predicting characters and formatting.
- The Atelier editor copies indentation of the previous line when you add a new line after a comment.
- Server credentials are required when you create new server connections or edit existing ones. This restriction supports the license management requirement for valid credentials.
- Secure server connections using Transport Layer Security (TLS) are supported. This feature enhances security. To use this feature the server must be correctly configured according to documentation.
- You can compare local and server file versions using the Compare With > Server’s Copy command on the Atelier Explorer context menu.
- You can open the Management Portal from the Server Explorer view context menu.
- XML import and export no longer require an active server connection; in addition, the import wizard is more robust and can handle large XML files.
- Support has been added for Feature Tracker, which is a safe and trustworthy approach for InterSystems to periodically collect information about feature use while maintaining the integrity of our relationship with our clients. For Atelier, only compilation times are collected to get a sense of the number of active Atelier users. See documentation for details.
- BPL is supported for the Ubuntu platform. Please note that some related server fixes are only available from 2018.1.0.
Note: Due to recent security enhancements, if you are running on a Mac using macOS Version 10.12 or later,
your Eclipse instance must be installed in the
/Applications directory for Eclipse updates to work correctly.