Re: [IxDA Discuss] text changing on buttons

2009-04-01 Thread Tim Sherburne
Hi Julie... I like Dante's suggestion of using the auto-save concept
to solve the problem; will this approach fold into the rest of the
application well? In my experience, I've discovered that
auto-save works best when its used consistently throughout the
entire application rather than as an isolated surprise.

One approach I try to use when thinking about situtations like this
is, Am I trying to do too much in this view? I sense that there
are two competing purposes to this one view (Print vs. Edit) and you
might be better served by using another pattern.

The master-detail arrangement might help: The details of a check are
edited within a dedicated child dialog or panel that can be reached
from the view you've proposed. The Save and Cancel buttons are moved
to the child view, leaving Print and Close in the parent view along
side the list of checks. This approach should be less ambiguous - no
shifting labels or confusing buttons.

Good luck, and let us know how it turns out.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=40834



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


[IxDA Discuss] text changing on buttons

2009-03-31 Thread Julie Stanford
I wanted to solicit people's advice/examples on a small but interesting
interaction we're working on. Here's the scenario:

User launches a dialog that has a list of people who they need to handwrite
checks to (it's a payroll application; don't worry about why they are
handwriting and not printing checks). The dialog has a table of the people
and the amounts. For each line in the table, the user can do up to two
things:

- Add/Edit a check number for that person's check
- Print a paystub for that check

They can do any or all of these things, it is up to them. To support this,
we have two buttons on the dialog -- Save and Cancel -- however if someone
selects to Print a stub, the Save button changes to Save and Print'. 

Here's what it looks like in ASCII (the actual is obviously not in ASCII):
In the example below: [] = checkbox field  = text field


Print Stub  Name AmountCheck number
   [  ] John Doe $500  __
   [  ] Mary Smith   $200  __
   [  ] Billy Bob$300  __

 [Save]   [Cancel]

As soon as someone selects to print a stub (by checking of a box in that
column) the Save button changes to be Save and Print.

Questions:
- What do people think about this interaction?
- Another option would be to have three buttons to start - Save, Save and
Print, Cancel and just disable Save and Print till you've checked something.
I think that is just more cluttered and annoying. What do other people
think?
- Do you have examples of other UIs where the button name changes based on
your selection?

Julie

_
Julie Stanford
Principal, Sliced Bread Design
650-969-0400 x706



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] text changing on buttons

2009-03-31 Thread Dante Murphy
Why not just use auto-save and get rid of the save and cancel buttons 
altogether?  Then all you need is a single print button that only does 
something when one or more lines are checked.

Dante Murphy | VP/D User Experience| D I G I T A S  H E A L T H
100 Penn Square East| Wanamaker Building, 11th Floor | Philadelphia, PA 19107 | 
USA
Email: dmur...@digitashealth.com 
www.digitashealth.com  


-Original Message-
From: discuss-boun...@lists.interactiondesigners.com 
[mailto:discuss-boun...@lists.interactiondesigners.com] On Behalf Of Julie 
Stanford
Sent: Tuesday, March 31, 2009 1:40 PM
To: disc...@ixda.org
Subject: [IxDA Discuss] text changing on buttons

I wanted to solicit people's advice/examples on a small but interesting
interaction we're working on. Here's the scenario:

User launches a dialog that has a list of people who they need to handwrite
checks to (it's a payroll application; don't worry about why they are
handwriting and not printing checks). The dialog has a table of the people
and the amounts. For each line in the table, the user can do up to two
things:

- Add/Edit a check number for that person's check
- Print a paystub for that check

They can do any or all of these things, it is up to them. To support this,
we have two buttons on the dialog -- Save and Cancel -- however if someone
selects to Print a stub, the Save button changes to Save and Print'. 

Here's what it looks like in ASCII (the actual is obviously not in ASCII):
In the example below: [] = checkbox field  = text field


Print Stub  Name AmountCheck number
   [  ] John Doe $500  __
   [  ] Mary Smith   $200  __
   [  ] Billy Bob$300  __

 [Save]   [Cancel]

As soon as someone selects to print a stub (by checking of a box in that
column) the Save button changes to be Save and Print.

Questions:
- What do people think about this interaction?
- Another option would be to have three buttons to start - Save, Save and
Print, Cancel and just disable Save and Print till you've checked something.
I think that is just more cluttered and annoying. What do other people
think?
- Do you have examples of other UIs where the button name changes based on
your selection?

Julie

_
Julie Stanford
Principal, Sliced Bread Design
650-969-0400 x706



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... disc...@ixda.org
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help