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 | ||
|
jvx:reference [2020/06/15 08:43] cduncan [The Special Case of Containers] |
jvx:reference [2020/06/15 08:49] cduncan [DataRow] |
||
|---|---|---|---|
| Line 457: | Line 457: | ||
| } | } | ||
| </code> | </code> | ||
| - | All we have to do there is start the launcher itself. As the comment suggests, there might be work required for a “real” application startup. For this example, it is all we need to do. Of course, we could also directly embed this little function into the launcher implementation itself to save us one class. | + | All we have to do there is start the launcher itself. As the comment suggests, there might be work required for a “real” application startup. For this example, however, it is all we need to do. Of course, we could also directly embed this little function into the launcher implementation itself to save us one class. |
| ===== The Launcher ===== | ===== The Launcher ===== | ||
| - | The ''%%ILauncher%%'' implementation, on the other hand, contains quite some logic but nothing not manageable: | + | The ''%%ILauncher%%'' implementation, on the other hand, contains quite a bit of logic but nothing unmanageable: |
| <code java> | <code java> | ||
| Line 576: | Line 576: | ||
| ===== Notes on the Launcher ===== | ===== Notes on the Launcher ===== | ||
| - | As you might have noticed, in our example the launcher is a (window) frame. That makes sense for nearly every desktop GUI toolkit as they all depend upon a window as main method to display their applications. But the launcher could also be simpler: for example, just a call to start the GUI thread. Or it could be something completely different: for example, an incoming HTTP request. | + | As you might have noticed, in our example the launcher is a (window) frame. That makes sense for nearly every desktop GUI toolkit, as they all depend upon a window as the main method to display their applications. But the launcher could also be simpler: for example, just a call to start the GUI thread. Or it could be something completely different: for example, an incoming HTTP request. |
| Also, don’t forget that the launcher is providing additional functionality to the application, like saving file handles, reading and writing the configuration, and similar platform and toolkit-dependent operations. See the [[https://sourceforge.net/p/jvx/code/HEAD/tree/trunk/java/swing/src/com/sibvisions/rad/ui/swing/impl/SwingApplication.java|launcher for Swing for further details]]. | Also, don’t forget that the launcher is providing additional functionality to the application, like saving file handles, reading and writing the configuration, and similar platform and toolkit-dependent operations. See the [[https://sourceforge.net/p/jvx/code/HEAD/tree/trunk/java/swing/src/com/sibvisions/rad/ui/swing/impl/SwingApplication.java|launcher for Swing for further details]]. | ||
| Line 602: | Line 602: | ||
| {{:jvx:reference:databook.png?nolink|DataBook Architecture, the DataBook contains DataPages, which contain DataRows.}} | {{:jvx:reference:databook.png?nolink|DataBook Architecture, the DataBook contains DataPages, which contain DataRows.}} | ||
| - | ===== RowDefinition ===== | + | ===== Row Definition ===== |
| - | The RowDefinition defines what columns are available in the row and stores some additional information about them, like the names of the [[https://en.wikipedia.org/wiki/Unique_key|primary key]] columns. You can think of the RowDefinition as the headers of a table. | + | The row definition defines what columns are available in the row and stores some additional information about them, like the names of the [[https://en.wikipedia.org/wiki/Unique_key|primary key]] columns. You can think of the row definition as the headers of a table. |
| - | Its creation and usage is rather simple, and if you’re working with RemoteDataBooks there is no need to create one at all, as it is automatically created when the DataBook is opened. A RowDefinition holds and manages ColumnDefinitions, which define the columns. | + | Its creation and usage is rather simple, and, if you’re working with RemoteDataBooks there is no need to create one at all, as it is automatically created when the data book is opened. A row definition holds and manages column definitions, which define the columns. |
| <code java> | <code java> | ||
| Line 628: | Line 628: | ||
| Most of the column definition is additional information about the column, like if it is nullable, the label of the column, default values, allowed values, and similar information. | Most of the column definition is additional information about the column, like if it is nullable, the label of the column, default values, allowed values, and similar information. | ||
| - | ==== DataType ==== | + | ==== Data Type ==== |
| - | Of course, we must define what type the value in the column has. This is done by setting a data type on the column definition. The data type defines what kind of values the column holds, like if it is a String, a Number, or something else. We provide the most often used data types out of the box: | + | Of course, we must define what type the value in the column has. This is done by setting a data type on the column definition. The data type defines what kind of values the column holds, like if it is a string, a number, or something else. We provide the most often used data types out of the box: |
| * BigDecimal | * BigDecimal | ||
| Line 642: | Line 642: | ||
| It is possible to add new data types by simply implementing ''%%IDataType%%''. | It is possible to add new data types by simply implementing ''%%IDataType%%''. | ||
| - | ===== DataRow ===== | + | ===== Data Row ===== |
| The data row represents a single row of data; it holds/references its own row definition and, of course, provides access to the values of the row. Accessing the data row can be done either by column index or column name, and the methods either return or accept objects. Let’s look at a simple usage example: | The data row represents a single row of data; it holds/references its own row definition and, of course, provides access to the values of the row. Accessing the data row can be done either by column index or column name, and the methods either return or accept objects. Let’s look at a simple usage example: | ||