Differences

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

--- jvx:reference [2020/06/15 09:49]
cduncan [The Simplest JVx Application: Just the GUI]
+++ jvx:reference [2020/06/15 09:50]
cduncan [Anatomy of a remote JVx application]
@@ Line 823: / Line 823: @@
 That’s it! That is the most simple way to start a [[https://sourceforge.net/projects/jvx/|JVx]] application. We can use all controls, and we can use ''%%MemDataBook%%''s without any problem or limitation. Best of all, we can simply switch to another technology by using another factory.
-===== Anatomy of a remote JVx application =====
+===== Anatomy of a Remote JVx Application =====
-Of course [[https://sourceforge.net/projects/jvx/|JVx]] wouldn’t be that useful if it would just provide static GUI components. Now, to explain what else is required for a remote [[https://sourceforge.net/projects/jvx/|JVx]] application I have to go far afield, so let’s head down the rabbit hole.
+Of course, [[https://sourceforge.net/projects/jvx/|JVx]] wouldn’t be that useful if it would just provide static GUI components. Now, to explain what else is required for a remote [[https://sourceforge.net/projects/jvx/|JVx]] application, I have to go far afield, so let’s head down the rabbit hole.
 {{:jvx:reference:jvx-client-server.png?nolink| Layers}}
-What you are seeing here is a rough sketch of how the architecture of [[https://sourceforge.net/projects/jvx/|JVx]] looks like. Let’s walk through the image step by step. We will look at each successive layer and work our way from the database on the server to the databook on the client.
+What you are seeing here is a rough sketch of how the architecture of [[https://sourceforge.net/projects/jvx/|JVx]] looks like. Let’s walk through the image step by step. We will look at each successive layer and work our way from the database on the server to the data book on the client.
 ==== DBAccess, accessing a database ====