Return to GuidanceExplorer

---

Guidance Explorer - New User Interface

Design Checklist

*Search UI
*Search For field will search both content and body. This includes attributes bullets that we generate into the body.
*Quoted search (eg, “Search Text”) will allow searching for a phrase.
*You can type into attribute search boxes or select an option from dropdown
*Drop downs show only values that exist in the current node (view or library). Dropdown contents will be like current GE, not polymorphic yet.
*Don’t search/filter until user presses Show Results button
*Clear will clear all search fields
*Search is always scoped to the currently selected node in tree. If library is selected you search entire library, if a view is selected you search just that view.
*Tree
*Node structure
*Library Node - First node cannot be deleted or modified. It contains all guidance of all types in the library.
*Type Nodes - Next 6 nodes cannot be deleted or modified – these show all available guidance for each guidance type.
*Search Views - Web app security node is a search node that we ship out of the box but can be modified by user
*Custom Views - The rest of the nodes in the mockup are custom views that we ship but can be modified
*Custom views and search views can contain arbitrary combinations of guidance and types
*The user can add a custom view or search view just as they are added in current GE.
*We will continue to support folders and nested views
*The new item context menu is only available from the Type Nodes not from library node or custom/search views.
*Drag/drop items only works when drop target is a custom view
*Icons need to be updated to look more professional
*Library and type nodes should be distinct from each other and also easily recognized as a special type different from search/custom views. See how ITunes does this.
*ListView
*List view should have a new col. Guidance type
*Cols sort on click – no autofilter on header
*Details pane
*Details pane should have guidance type included in title (eg. Guideline: Title or Checklist Item: Title
*Menus
*File menu create new item results in a dlg box like Word of VS that you can use to select the type to create.
*All menu choices that change to specify guidance type can be changed to just use the word ‘item’. Eg. Edit Guideline would be Edit Item.
*Search views
*If you create a search view you get a modal dlg with same ui as filter/search criteria than then persists as the view criteria

Design Questions

*Search for is scoped to current view or entire library?
*Scoped to current node.
*Should we have icon for each guidance type in listview? Or is a col better? Or both?

Mockup

http://channel9.msdn.com/wiki/images/mock.jpg

---

Return to GuidanceExplorer