The Google approach...
http://specials.rediff.com/money/2008/mar/11google1.htm
Cheers
Rony
Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe
I'm working on an internal application where users need to add, edit,
delete and cancel rows in a table. In this case, the items are names of
salespeople, however, this pattern of adding and editing rows is used
quite frequently in the application. This is a home grown application
written in .NET
I'm working on an internal application where users need to add, edit,
delete and cancel rows in a table. In this case, the items are names of
salespeople, however, this pattern of adding and editing rows is used
David,
Now knowing what kind of a product this is, who is using it, or the style
Not sure if I'm following this correctly - but there's a couple of
ways you can solve this:
Have 1 icon set at the top of the table (in the title bar - right -
almost like your windows close and minimise actions) which is
relevant to the selected row you're in.
Another option would be to reduce
On Wed, Mar 12, 2008 at 6:04 AM, Fine, David [EMAIL PROTECTED] wrote:
PS Does anyone have any good suggestions or software for converting
.ico to gifs?
Hi David,
Give IcoFX a try. It's an excellent free icon editor that can export an icon
in several different image formats. File | Export
On Mar 12, 2008, at 9:04 AM, Fine, David wrote:
Can anyone point me to some good examples where this pattern is
implemented? I'm trying to get out of listing the four actions icons
(add, edit, delete and cancel) next to each row.
I work with lists of editable items a lot. There are a number
This is similar to a question I asked a little while ago, the solution
I decided upon is #2 and #4 from Jack's list, and it's working very
well.
Matt.
On Wed, Mar 12, 2008 at 12:29 PM, Jack Moffett [EMAIL PROTECTED] wrote:
On Mar 12, 2008, at 9:04 AM, Fine, David wrote:
Can anyone point
Two small additions to Jack's list:
1) The Tool Tip Invitation pattern
(http://developer.yahoo.com/ypatterns/pattern.php?pattern=tooltipinvitation)
could be helpful to address the drawback with Jack's option 2.
2) If your application is designed for frequent use, and editing
specific items is
3. Row selection
In this pattern, the user selects a row (or multiple rows) and then
presses a button found on a toolbar above the list. Buttons should
enable and disable based on the selection. Benefits: removes screen
clutter, allows for actions on multiple items. Drawbacks: two-click
On Mar 12, 2008, at 2:35 PM, Meredith Noble wrote:
3. Row selection
In this pattern, the user selects a row (or multiple rows) and then
presses a button found on a toolbar above the list. Buttons should
enable and disable based on the selection. Benefits: removes screen
clutter, allows for
Jack, you mention buttons should enable and disable based on the
selection. Have you had success with this in the past? I am worried
about randomly disabling buttons -- what if the user doesn't
understand
why it's happening?
My philosophy is that it would be more confusing to allow
On Mar 12, 2008, at 4:29 PM, Meredith Noble wrote:
So we have:
List Page (list of all items, with buttons allowing the user to
perform
any actions that can be applied to any combination of items in the
list,
including multiples)
Item Detail Pages (what you get when you click on an
12 matches
Mail list logo
