Hi,
On Wed, Aug 5, 2009 at 3:51 PM, Anca Paula Luca <[email protected]>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
> > - 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 user never clicks on just "Link", it is always a submenu item that it
> chooses ("Wiki page", "Attached file", etc). I assume the dialog title
> should be
> a combination of the two, since only the name of the submenu item is far
> from
> suggestive.
>
> wdyt?
I still think that keeping the tab's label as dialog box title is easier
since it doesn't require an additional rule (how should both things be
combined?). Clicking on something under the "Link" button opens a dialog box
called "Link" -> simple, easy, effective.
> > - 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"
>
> After discussion we came to the conclusion that the description will tell
> the
> user what will be the result of the current step, and not instructions
> about how
> to do it. All instructions will go next to the field in the form of the
> wizard step.
>
> Also this description can be skipped if the title is good enough, to avoid
> redundancy.
>
> > - 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")
>
> Also, webforms usually are submitted when enter is hit in one of their
> fields.
> We also do this currently in our dialog forms. In the case when "Finish"
> and
> "Next" are both enabled, which one should be the one executed by enter? I'd
> go
> for "Next" for consistency.
Me too. Hitting enter should behave in the same fashion as double-clicking
-> trigger "Next" (unless the user is on the last screen).
Also, for the case when the wysiwyg dialog is not a wizard (table, importer
> dialogs for the moment), we have two options for the wizard step title:
>
> 1/ keep the Wizard Step and Descriptions in place, to contain detailed
> description of the action to be executed, for consistency reasons. While
> the
> dialog title will be the same as the toolbar button / menu clicked, the
> Wizard
> Step title will contain a more detailed description of the action and the
> description will probably be missing most of the times since it's
> redundant.
>
> 2/ we remove the top bar completely, as it currently is the case for the
> table &
> importer dialogs, to avoid crowding the dialogs with redundant information
> (the
> title of the dialog should be enough information, as it's only one action
> and
> that is the actual name of the action -- as opposed to wizard steps where
> differentiation of various subactions is needed).
>
> Guillaume's suggestion was for strong consistency, therefore 1/. I think
> that,
> while it could turn out useful, it can be confusing to have multiple titles
> for
> a dialog when they refer to the same action.
>
> wdyt?
I'm still in favor of 1/ for consistency reasons. I think that if the
wording is done correctly, the redundancy can be kept to a minimum.
In general, we would love some feedback about the UI / UX of the wysiwyg
> dialogs, things that should be polished for a final version.
Indeed, please feel free to join the discussion and shed some light on our
ideas :-)
Guillaume
> Thanks,
> Anca
>
> > 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
>
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
