![]() ![]() This was the first approach we took to moving pages and what we found is many people who were not particularly confident with their mouse, inadvertently moved pages around when trying to do other things such as open pages. Re the "reorder" button, there are some usability issues with removing it and just letting users drag the pages in the same way they would if dragging files around using windows explorer as proposed, If the 'Reorder' button were removed, where should we put the instructions "To reorganise your site, drag the pages around as desired."? Should I add a "Go" button to the "Reports" drop-down in the left frame in order to make the it consistent with the "Add Page" drop-down?Įdit: I'll plan on changing the links into buttons, but until I get confirmation that it is a good idea, I won't remove the 'Reorder' button. I will change the "Create" and "Delete" links into "Create." and "Delete." buttons. I'll also work on removing the "Reorganize" button and making drag and drop the default. I'll plan on just moving the "Go" button to be on the same line as the page type drop-down. it's also a major action in the interface, so i'd be explicit about the creation-action - automatic select-triggering is too much "magic" for my taste :) i'd recommend just moving it in the same line to save space." ![]() > "select-actions by javascript without a "go"-button can be confusing: they don't work if the DOM is loaded and the javascript isn't applied to it (in which case you're stuck with the current selection). it also takes away precious space for page-labels. The functionality of checkboxes would be a bit ambigous if shown without a prior action ("can i drag multiple pages when i check them?"). We could just show the check boxes by default along with always showing the "Delete the selected pages" button and "Add page" drop-down. > If we carried this on, we could get rid of the "Create" and "Delete" buttons as well. Hm, perhaps performace issues to apply these behaviours every time the tree is loaded - but from a usabilty-perspective i don't see any issues. ![]() > Indeed, the only thing that the "Reorganise" button does is enable drag and dropping on the page list (along with showing the message). it's also a major action in the interface, so i'd be explicit about the creation-action - automatic select-triggering is too much "magic" for my taste :) i'd recommend just moving it in the same line to save space. Select-actions by javascript without a "go"-button can be confusing: they don't work if the DOM is loaded and the javascript isn't applied to it (in which case you're stuck with the current selection). Would the addition of checkboxes and drag-and-drop by default make the left pane harder to use? If we carried this on, we could get rid of the "Create" and "Delete" buttons as well. Would allowing dragging and dropping be default cause any usability issues? I can't think of any. ![]() Indeed, the only thing that the "Reorganise" button does is enable drag and dropping on the page list (along with showing the message). I think it would be a good idea to either just remove that button and info or show the info by default (maybe at the bottom) and remove the button.Īny unnecessary button makes it just more difficult for new users to use the system. it has NO functionality at all, it just shows some information. > Regarding the Reorganise button I'm wondering if it is really needed. I plan to, as shown in the screenshot here: > Remove it, but add an empty line (or something like "Do nothing") in the drop-down box so if someone changes opinion after having clicked on the box can stop the action that way. In light of the above, should I remove the 'Go' button from the 'Create' drop-downs in the "Site Content" and "Newsletters" sections? However, this is not too big of a problem, it's not like pages are getting deleted. However, I think the one main reason to keep the main button would be to prevent pages from accidentally being added. * Page Version History drop-down (I plan to change this to a checkbox, since it makes more sense) I looked around the CMS and everywhere else that drop-down is used, no "Go" button is also used in all of these places: R: Try to be consistent in the actions required of users for the same display element." "Users may get confused as to when they need to click a ‘Go’ button in order to activate a drop down box selection and when they don’t. I have a question about Usability Issue "#12 Inconsistent Go Buttons": ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |