Anca Luca wrote:
>
> Guillaume Lerouge wrote:
>> Hi Devs,
>> Anca asked me to finalize the overall look of dialog boxes in the WYSIWYG so
>> that she can work on it and polish it for the 2.0 release. Right now the
>> issue is that we're using a different look for the link, image & macro
>> dialog boxes which poses a consistency problem.
>>
>> I've been working with Cati on a proposal for the look of the overall box -
>> not for the inner part of the box. Proposals for the standardization of the
>> inner part of the box will come later. The dialog box uses a wizard-like
>> look and follows the vertical form principles proposed by Cati in a previous
>> email (thus the primary action button at the bottom left, to follow the
>> user's eye flow). Its "hidden" features are:
>>
>> - Buttons can be in an enabled or disabled mode depending of what the
>> current step is
>> - All buttons are displayed all the time so that they don't move from one
>> screen to the next
>
> Actually, Marius suggested that we keep the "invalid" buttons hidden (but
> without changing the positions of the displayed buttons), for the following
> reasons:
> 1/ the interface should be as light as possible, we shouldn't crowd the
> interface with buttons that the user can never push
> 2/ disabled buttons can be a little confusing, the user wouldn't know if
> there
> is something he needs to do to enable those buttons.
> To help, imagine the following interaction model (which we envisage but it's
> not
> a priority right now): in a wizard step, if the step form is invalid, the
> "Next"
> button is disabled (for example if the user has to make a selection, the
> "Next"
> button will only become enabled after the selection has been made). Now,
> given
> that the "Finish" button would be present on _all_ steps but disabled, I
> think
> it can become a little confusing for the user, who wouldn't know if there is
> something he needs to select, fill in, etc to enable it.
>
> I'd go for minimal UI (i.e. all buttons on the footer strip, but invalid
> buttons
> are invisible).
>
> wdyt?
Big +1!
Thanks Anca,
Marius
>
> Thanks,
> Anca
>
>> - Buttons' labels are configurable
>> - There is no "Cancel" button, the cross at the top right of the dialog
>> box plays that role
>> - The title in the top bar doesn't change and its name is the same as the
>> associated toolbar button (clicking on "Link" opens a dialog box called
>> "Link")
>> - The "Wizard Step Title" reflects what's happening at the current step:
>> "Page Selection" , "Code Macro" , "Image Selection"
>> - The description tells the user what to do at the current step: "Select
>> the page to link to" , "Select the image to insert" , "Fill in macro
>> parameters"
>> - Double-clicking on an item (an image, a page name) acts in the same
>> fashion as selecting it and clicking the "Next" button. If the "Next"
>> button
>> is disabled at the current step, double-clicking works as the primary
>> action
>> ("Insert" , "Create")
>>
>> The mockups are located at:
>> http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GenericMacroDialog
>>
>> WDYT?
>>
>> Guillaume
>>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
