Hot answers tagged

3

If you're looking for user friendly, then browser's back button should suffice, it's a known and expected behavior, and for one level navigation, it's what most users will look for. Now, if you want to keep context, you could use a modal window, but that will also depend on the content you have for those services and also the kind of behavior you're looking ...


2

Here are 2 links after a quick research with the keywords "Table UI" http://semantic-ui.com/collections/table.html http://www.noupe.com/design/better-ui-design-proper-use-of-tables.html


1

In think the first option of the two is the best. The pencil is a logical symbol for editing. And it would only be a waste of space if you would put the cross for deleting there, if it is not used often. However, I would prefer to not have the radio buttons there on your popup window. Instead, I would have a smaller [x] or trashcan button on the left of ...


1

I think you could solve the problem by not displaying any of those buttons, but instead: Facilitating the editing of an item by clicking on the relevant row, and Hiding the lesser-used action of deleting within an action menu. As in my mockup below: download bmml source – Wireframes created with Balsamiq Mockups


1

This is not clear in Material, kind of a grey zone. While you won't find any text edition example on a dialog, you will find other kind of forms in dialogs, specially on the Confirmation Dialogs sub-section. You'll notice there are all kind of form controls in dialogs, exception made of... text fields. However, read this (bold font added to show you the ...


1

In an enterprise webapp we are developing we make the distinction between: modals: can only be closed through very deliberate action, because closing would break some flow or may cause data loss. These have no X button, cannot be closed by clicking outside modal. Most do have a separate "abort" button, making it more explicit that closing may result in ...


1

I've got a lot of value out of putting create/edit interfaces in with the rest of the page content. Typically what I'd do is slide down the create/edit interface when the create/edit button is clicked, and slide it back up again when changes are saved. Fiddle here: https://jsfiddle.net/hr3mhufh/2/ Pros of displaying inline: No need to reload the page ...


1

You can use "breadcrumbs" which is very common and useful. It takes less space(unless you style it heavily) and users can easily navigate to various pages.


1

Here is the answer. You should give such kind of option like filter, search,export to above the table. because if you keep it inside the table that you will have bad interface as well as you can't manage space properly. So here is the solution I usually use in my work and luckily my boss never refuse it to use !


1

Neither of those option sound like an ideal experience for the user. A couple things to consider: You can't prevent a user from navigating. If they don't want to wait, users can just leave, refresh the page, etc. (Expect users to be impatient and circumvent your controls.) If you develop this as a SPA (Single Page Application) you can allow the user to ...



Only top voted, non community-wiki answers of a minimum length are eligible