Comments on: JVx Reference, of Technologies and Factories https://blog.sibvisions.com/2016/12/07/jvx-reference-of-technologies-and-factories/ Blog @ SIB Visions Wed, 05 Mar 2025 13:10:49 +0100 hourly 1 By: Michael Scharf https://blog.sibvisions.com/2016/12/07/jvx-reference-of-technologies-and-factories/comment-page-1/#comment-630 Michael Scharf Thu, 08 Dec 2016 01:05:41 +0000 http://blog.sibvisions.com/?p=5957#comment-630 > 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. What you describe here is a nice example of the Bridge Pattern [1]. I have seen the Bridge Pattern for the first time about 30 years ago, when I started working with the ET++ framework [2] (the Framework Erich Gamma and André Weinand created in the 80ies and and a lot of the GOF [3] design patterns have been discovered in this framework). In ET++, the bridge was used for a very similar purpose: to hide the actual (system dependent) UI implementation from the abstraction used in the UI. They also used a factory to create the window system dependent components. This shows to me, that patterns like the BridgePattern are very fundamental, because even without naming it, you have implemented it. So, big thumbs up! [1] https://en.wikipedia.org/wiki/Bridge_pattern [2] http://www.ubilab.org/publications/print_versions/pdf/wei94.pdf [3] https://en.wikipedia.org/wiki/Design_Patterns > 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.

What you describe here is a nice example of the Bridge Pattern [1].

I have seen the Bridge Pattern for the first time about 30 years ago, when I started working with the ET++ framework [2] (the Framework Erich Gamma and André Weinand created in the 80ies and and a lot of the GOF [3] design patterns have been discovered in this framework). In ET++, the bridge was used for a very similar purpose: to hide the actual (system dependent) UI implementation from the abstraction used in the UI. They also used a factory to create the window system dependent components.

This shows to me, that patterns like the BridgePattern are very fundamental, because even without naming it, you have implemented it. So, big thumbs up!

[1] https://en.wikipedia.org/wiki/Bridge_pattern
[2] http://www.ubilab.org/publications/print_versions/pdf/wei94.pdf
[3] https://en.wikipedia.org/wiki/Design_Patterns

]]>