From fc457d96c4ed415ec74e3913e4bba58bd2793849 Mon Sep 17 00:00:00 2001 From: vwheeler Date: Mon, 28 Apr 2014 23:37:36 +0000 Subject: [PATCH] Minor clarification (better wording) regarding the Bridge Pattern. Author:vwheeler Date:2014-04-28T23:37:36.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1332 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../gui-building/eiffelvision-2/eiffelvision-introduction.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-introduction.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-introduction.wiki index 7d35b5d5..20effcc8 100644 --- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-introduction.wiki +++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-introduction.wiki @@ -79,7 +79,7 @@ Boolean properties have a different convention. Instead of one set-routine, it h ==Implementation== -For flexibility, EiffelVision 2 is built using the bridge pattern. This means that every platform-dependent component of the library consist of two classes, plus an implementation class for each platform (currently two). One is the interface. All the features of interfaces do nothing except delegate the call to the implementation object which is coupled to it. This object has the static type of the implementation-interface with the name of the interface class, with an "_I" suffix. The implementation classes (with an "_IMP" suffix) then inherit from this implementation-interface class to implement platform-specific features. At run time, the implementation objects (instantiated from these "_IMP" classes) are then polymorphically attached to the to the "_I"-type attributes (typically named "implementation") to provide the platform-specific services. +For flexibility, EiffelVision 2 is built using the bridge pattern. This means that every platform-dependent component of the library consist of two classes, plus an implementation class for each platform (currently two). One is the interface. All the features of interfaces do nothing except delegate the call to the implementation object which is coupled to it. This object has the static type of the implementation-interface with the name of the interface class, with an "_I" suffix. The implementation classes (with an "_IMP" suffix) then inherit from this implementation-interface class to implement platform-specific features. At run time, these platform-specific implementation objects (instantiated from these "_IMP" classes) are then polymorphically attached to the to the "_I"-type attributes (typically named "implementation") to provide the platform-specific services.