Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
visionx:eplug_guide [2020/06/05 16:58] cduncan [Features] |
visionx:eplug_guide [2020/06/05 17:08] cduncan [DataBooks] |
||
---|---|---|---|
Line 47: | Line 47: | ||
{{:visionx:eplug_guide:preferences-license.png?nolink|The EPlug License Preference Page.}} | {{:visionx:eplug_guide:preferences-license.png?nolink|The EPlug License Preference Page.}} | ||
- | In the preferences you can also view various information about the license, including the time remaining until it is expiring if it is a trial license. | + | In the preferences, you can also view various information about the license, including the time remaining until it is expiring if it is a trial license. |
====== Using EPlug ====== | ====== Using EPlug ====== | ||
Line 67: | Line 67: | ||
===== Commands ===== | ===== Commands ===== | ||
- | [[https://eplug.sibvisions.com/|EPlug]] provides various commands which can be used to navigate the project. These are either available from the context menu on a source file, or can be assigned custom keybindings through the Eclipse preferences. | + | [[https://eplug.sibvisions.com/|EPlug]] provides various commands which can be used to navigate the project. These are either available from the context menu on a source file or can be assigned custom keybindings through the Eclipse preferences. |
{{:visionx:eplug_guide:eplug-context-menu.png?nolink|The EPlug context menu that can be accessed through the editor.}} | {{:visionx:eplug_guide:eplug-context-menu.png?nolink|The EPlug context menu that can be accessed through the editor.}} | ||
Line 79: | Line 79: | ||
Opens the complement class of the currently open file. | Opens the complement class of the currently open file. | ||
- | The complement class is the "counterpart" of every class on the client or server. So when invoked on a workscreen (client-side), it will open the server-side LCO class, and vice versa. | + | The complement class is the "counterpart" of every class on the client or server. So, when invoked on a workscreen (client-side), it will open the server-side LCO class and vice versa. |
==== Go To application.xml ==== | ==== Go To application.xml ==== | ||
Line 105: | Line 105: | ||
The biggest and most important feature of [[https://eplug.sibvisions.com/|EPlug]] is the support for DataBooks, both ''%%RemoteDataBook%%''s and ''%%MemDataBook%%''s to be exact. | The biggest and most important feature of [[https://eplug.sibvisions.com/|EPlug]] is the support for DataBooks, both ''%%RemoteDataBook%%''s and ''%%MemDataBook%%''s to be exact. | ||
- | Because DataBooks are using ''%%String%%''s to identify columns (instead of properties or Enums), it cannot be covered by the default functionality of Eclipse and the Java compiler. [[https://eplug.sibvisions.com/|EPlug]] extends Eclipse with additional functionality to be able to provide various features on and around DataBooks and column names. | + | Because DataBooks use ''%%String%%''s to identify columns (instead of properties or Enums), it cannot be covered by the default functionality of Eclipse and the Java compiler. [[https://eplug.sibvisions.com/|EPlug]] extends Eclipse with additional functionality to be able to provide various features on and around DataBooks and column names. |
- | Both, the ''%%RemoteDataBook%%'' and the ''%%MemDataBook%%'' are supported out of the box. In the case of a ''%%MemDataBook%%'', the metadata is not requested from the data source (because there is none), but the metadata is directly extracted from the code itself. | + | Both the ''%%RemoteDataBook%%'' and the ''%%MemDataBook%%'' are supported out of the box. In the case of a ''%%MemDataBook%%'', the metadata is not requested from the data source (because there is none), but the metadata is directly extracted from the code itself. |
==== Compile time checks ==== | ==== Compile time checks ==== |