RPC-GUI » History » Revision 10
Revision 9 (Hans-Martin Haase, 08/24/2015 11:24 AM) → Revision 10/11 (Hans-Martin Haase, 08/24/2015 11:30 AM)
{{toc}}
h1. Abstract User Consent
h2. GUI Common Overview
Following the abstract user interface is depicted. As The implementation example we use with this abstract GUI is the EAC protocol which is described in more detail in http://dev.openecard.org/attachments/download/350/ISO24727%20EAC.ppt and the implementation of the protocol is available at https://github.com/ecsec/open-ecard/tree/stage/addons/tr03112. The usage of the GUI parts which are required by the protocol are in a separate package https://github.com/ecsec/open-ecard/tree/stage/addons/tr03112/src/main/java/org/openecard/sal/protocol/eac/gui there you'll find a an complex example of the usage of the abstract GUI. So how is the GUI called? The GUI is part of an SAL protocol and is called if the related SAL action is invoked, in this case this is the method @public DIDAuthenticateResponse perform(DIDAuthenticate request, Map<String, Object> internalData)@ in class PACEStep. See https://github.com/ecsec/open-ecard/blob/stage/addons/tr03112/src/main/java/org/openecard/sal/protocol/eac/PACEStep.java. More information about SAL protocols are available on the [[Add-on System]] page. https://github.com/ecsec/open-ecard/blob/stage/addons/tr03112/src/main/java/org/openecard/sal/protocol/eac/PACEStep.java
* UML diagrams for the GUI are shown in the following:
!gui_description.png!
!gui_navigator.png!
!swing_display.png!