Difference between revisions of "STP/GUILookAndFeelIntegrationProposal"
m (GUILookAndFeelIntegrationProposal moved to STP/GUILookAndFeelIntegrationProposal: Introducing wiki guidelines as part of project usability drive!)
Revision as of 13:27, 5 December 2007
GUI Proposal: XEF and WTP Editor Integration
This proposal provides GUI look and feel for integration of XEF and WTP-based editors.
As it was agreed, integration provides a way to combine the strengths of both editors: use the WTP-based editor to view and edit the policy document as a whole and the XEF editor as a detail editor when fragments in the policy document that contain individual assertions need to be edited.
1. Editing policy document as whole
On the first step user will open(create) policy file (or policy attachment in wsdl) with WTP-based editor. Here it is possible to add/delete new alternatives and assertions, combine and build the hierarchy of them. Additionally, WTP-based policy editor could provide following functionality:
- merge policies;
- intersect polices;
- normalize policy;
- validate policy.
Validation could be used in two modes:
- validate whole policy document;
- propose list with only allowed policy assertions (in GUI).
Draft look&feel of policy document editing is represented bellow:
2. Editing individual assertions
As soon as user chooses editing of individual assertion in WTP-based policy editor (via click on arrow), XEF editor will be activated. XEF editor represents GUI elements accordingly assertion schema. User can change assertion properties, save them and return to editing of whole policy document (via icon in left corner). It is possible to edit more than one assertion in parallel (idea is the same as in editing of WSDL inline schemas).
Draft look&feel of individual assertion editing is represented bellow: