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
jvx:reference [2020/06/10 11:22]
cduncan [Extension]
jvx:reference [2020/06/10 11:23]
cduncan [UI]
Line 48: Line 48:
 ==== Implementation ==== ==== Implementation ====
  
-After that comes the implementation layer. These implementations of the [[https://​sourceforge.net/​projects/​jvx/​|JVx]] interfaces are the actual objects returned by the factory. This is some sort of “glue” layerit binds the technology or extended components against the interfaces which are provided by [[https://​sourceforge.net/​projects/​jvx/​|JVx]].+After that comes the implementation layer. These implementations of the [[https://​sourceforge.net/​projects/​jvx/​|JVx]] interfaces are the actual objects returned by the factory. This is some sort of “glue” layerit binds the technology or extended components against the interfaces which are provided by [[https://​sourceforge.net/​projects/​jvx/​|JVx]].
  
 <code java> <code java>
Line 55: Line 55:
 ==== UI ==== ==== UI ====
  
-Last but for sure not least is the UI layer, which wraps the implementations. It is completely ​Implementation ​independent, ​that means that one can swap out the stack underneath:+Lastbut definitely ​not leastis the UI layer, which wraps the implementations. It is completely ​implementation-independent, ​which means that one can swap out the stack underneath:
  
 {{:​jvx:​reference:​swappable-layers.png?​nolink|The Extension, Implementation and Technology can be swapped at will}} {{:​jvx:​reference:​swappable-layers.png?​nolink|The Extension, Implementation and Technology can be swapped at will}}
  
-This is achieved because the UI layer is not extending the Implementation ​layerbut wrapping instances provided by the factory. It is oblivious to what Technology ​is actually underneath it.+This is achieved because the UI layer is not extending the implementation ​layer but wrapping instances provided by the factory. It is oblivious to what technology ​is actually underneath it.
  
 <code java> <code java>
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information