Tag Info

Definately keep the order of the buttons the same on all parts. There is nothing more disturbing than clicking a delete button where on the previous page there was a edit button. As for the order, I would suggest ordering them by what you want users to click most often. Use UI design to guide the application user.

It is best to order them logically and group similar actions together. In your case with only three, the order that you have them now is good. However one thing that you really should do it to move the delete button away so that it is not with other action buttons. I would place it aligned to the right to reduce the likelihood that it is accidentally ...

Personalization is good for frequent users of software with different applications (i.e. some people use Word to write love notes, others hook it up with an access DB to generate form letters). [edit] Jim Rush elaborates these reasons, below. Personalization is bad if it's just an excuse for not making decisions. Every option in your program is a decision ...

Considder if you can't change your design a bit further than by just changing the ordering of your buttons. Ask yourself if the buttons really make sense in the first place. You currently have two types of buttons above your list: one button that creates a new item in the list, and two buttons that act on the currently selected item. The item has to be ...

Here's a couple of options - but I think li's value is deprecated in HTML4 - and I don't know if it can be done in CSS. <ol start="1"> <li>Item 1</li> <li>Item 2</li> <li>Item 3</li> <li value=59>Item 4</li> <li>Item 5</li> </ol> <DL> <DT>1 <DD>Item 1 ...

The usual way that I've seen this done is with an ellipsis. Something like: Edit: For markup I would use an unordered list and insert the numbers into the name and use the ellipsis as an item. Otherwise you end up with some difficult situations when the user is #4, as you would have an ellipsis where it doesn't make sense, or when the user is #2.

Netflix combines three methods in their queue. You can drag-and-drop, but also specify a particular row number, or click to move it to the very top: What I find interesting about their approach is that they have put the "Top" icon (circled in green) right there on each row, as opposed to requiring the user to make a selection and then click somewhere at ...

In my opinion New is very different from Edit and Delete, as it does not require an item to be selected. Edit and Delete refer to some item, thus should kept hidden while no item is selected, and shown in a different position from New. If you really can't put them inside the list, consider putting them on the side. I usually like to put the New (or Add, +, ...

Trying to find a more complicated solution that feels natural is a recipe for failure. Keep it simple. Even if it isn't 100% perfect for all cases, as long as it's clear, you get most of the benefit. News feeds should use a top posting as the newest feed is the most important. This can also apply to commenting if the newest comments are more important. ...

If I'm reading the HTML5 spec correctly you can do as suggested in Roger's answer and use an ordered list and then use a value attribute on one of the li elements to skip a few numbers: The first item in the list has the ordinal value given by the ol element's start attribute, unless that li element has a value attribute with a value that can be ...

From you description this is what you got today: download bmml source – Wireframes created with Balsamiq Mockups This is perfect to drag and drop, and it has a nice direct feeling of control to the user. A 150 products is hard to organize in one category, and I think you need to categorize the products. Having the categories as filters, the ...

The first thing you need to ask yourself before you try to figure out how to do it is how frequently users are going to be doing it. If it's going to be used often I would try to create it so that you use drag and drop and simply auto-scroll the page once a user hit's a certain treshold. It's a good rule of thumb to say that if a user needs to do something ...

peterchen has a good answer. Here are some additional factors: Good reasons: Application has a lot of corner case features that aren't useful for the majority. This is common in the perversion of the 80/20 rule: 80% of the users want their own unique blend of 20% of the product features. Product has a variety of work flows. I want display X with ...

It seems unlikely that a user will actually reorder 150 items. That's why you typically see large lists (think a list of files) with the ability to order by column. This gives some control and order to a large list without making the user deal with each item. Now I understand why you might want to provide some more fine grained ordering, so perhaps this ...

Consider facebook: The newsfeed is top-down with posting on the top. The chat windows, the posting is bottom-top with posting on the bottom. Does this irritate you? Did you even notice this? My opinion (not based on any research that I am aware of), for a top-down reading audience (english language) we have been accustomed to scrolling down to find ...

I realize that this is a question one may ponder. However, when it comes to a set of similar list views, each containing a similar/or exact set of buttons you should keep the order of the buttons consistent. Otherwise this will be an obstructive feature in your UI and a user will then have to play hide and seek in every view looking for the correct button. ...

Magento (an e-commerce platform) provides a "Ship to Multiple Addresses" option that's worth studying: "As a customer is in their shopping cart, they simply select "One Address" or "Multiple Addresses" before proceeding to a check-out page. Selecting "Multiple Shipping" allows them to select a shipping address for each individual item. Once they've entered ...

The common way of showing that a Y (or X) axis has a gap is to make a strike through or dots.. similar to: I 50 I 40 I 30 / I 0 or I 50 I 40 I 30 ... I 0 None is more correct than the other, more of a aesthetic point of view...

The best way to determine if your "navigation" is correct is to test it. You can use card sorting, user testing, interviews, etc. to determine if your interface makes the most sense and/or is too cluttered. You may also get some other ideas on how to improve your app (for example - just at first glance, those icons on that screen are too generic and too ...