Documentation

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
visionx:eplug_guide [2020/06/05 17:02]
cduncan [Commands]
visionx:eplug_guide [2020/06/05 17:07]
cduncan [DataBooks]
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 classand vice versa.+The complement class is the "​counterpart"​ of every class on the client or server. Sowhen 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.
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information