RPC-GUI » History » Revision 9
Revision 8 (Hans-Martin Haase, 08/24/2015 11:10 AM) → Revision 9/11 (Hans-Martin Haase, 08/24/2015 11:24 AM)
{{toc}}
h1. Abstract User Consent
h2. GUI Common Overview
Following * Information about ISO/IEC 24727 and the abstract user interface is depicted. The implementation example with this abstract GUI is the EAC (Extended Access Control) protocol which is described in more detail in can be found at
** http://dev.openecard.org/attachments/download/350/ISO24727%20EAC.ppt and the implementation of the protocol is available
* The EAC implementierung can be found at https://github.com/ecsec/open-ecard/tree/stage/addons/tr03112. The usage of the
** https://github.com/ecsec/open-ecard/tree/stage/addons/tr03112
* GUI parts which are required by the protocol are in a separate package elements for EAC can be found at
** https://github.com/ecsec/open-ecard/tree/stage/addons/tr03112/src/main/java/org/openecard/sal/protocol/eac/gui there you'll find 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 via 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
* UML diagrams for the GUI are shown in the following:
!gui_description.png!
!gui_navigator.png!
!swing_display.png!