MetaChat REGISTER   ||   LOGIN   ||   IMAGES ARE OFF   ||   RECENT COMMENTS




artphoto by splunge
artphoto by TheophileEscargot
artphoto by Kronos_to_Earth
artphoto by ethylene

Home

About

Search

Archives

Mecha Wiki

Metachat Eye

Emcee

IRC Channels

IRC FAQ


 RSS


Comment Feed:

RSS

13 March 2007

Ask Mecha: I have a web page where the user enters a bunch of details on a PDA. I'm looking for vague advice on how to show the user what actions are available... [pictures, & more inside]
≡ Click to see image ≡

So, the user can do 1 of three things. They can Save changes to a call, they can complete the call and they can complete the call and create a new call (RTF).

I don't want people accidentally clicking complete when they want to simply save changes. In the past, this was achieved by having them tick the "Complete the Call" /"RTF" tickboxes and having "Apply" do one of three actions.

How would you do this? How would you visually separate the three actions? Should the buttons be next to each other, or should the be underneath each other? Maybe the tickbox & single button idea was the best solution? Help Me Please?
posted by seanyboy 13 March | 06:04
I find the three button solution to be a bit dangerous on the same fronts you do. Even as my expertise with the interface were to rise, there is still opportunity for error.

Is there an order of operations between the three activities? Maybe this is too early for my brain, but I might either group buttons with activities (but maybe that doesn't work here). How do you feel about radio buttons through the options? Similar to check but more restrictive.
posted by safetyfork 13 March | 06:22
Also, some of those check boxes look like they further describe the thing whereas others take action on the thing. I'd want to keep 'em separated. Unfortunately, I have to get ready for work now myself. Good Luck.
posted by safetyfork 13 March | 06:25
There's no order of operations. A user may simply fill in the details and choose to "Complete with RTF".

The tickbox solution would work perfectly except that RTF Completion requires a combo-boxes worth of extra information to be entered. I was thinking of using javascript to display the extra required fields when the RTF checkbox is ticked, but that's a problem because an RTF may be forced if a call has parts outstanding on it.

Having Rubber ducked this, I may stick with the tickboxes. Despite Completion being a process, users see "completion" as a status rather than an action.

Hmm. I'm not 100% sure that's the right way to go.
posted by seanyboy 13 March | 06:30
What's confusing is that it's mixing up two aspects that seem quite separate to me: (a) whether this call completed or not; and (b) whether I want to just save this, or to save this and have a new call to be created as a convenience.

At the moment, what happens when you click 'Apply'? Does it save this call, and re-display the same edit form for the same call? Or does it take you out to some other screen? Similarly, what happens if you click 'Complete Call'?
posted by chrismear 13 March | 06:38
Oh, and is the 'create new RTF' just a convenience thing (i.e. takes them straight to a 'new call' form, saving them a couple of clicks), or does it actually change state at the backend (i.e. creating a new blank timestamped record or something)?
posted by chrismear 13 March | 06:41
So, with the caveat that I don't really understand the process here, my instinct would be for something like this:

≡ Click to see image ≡

or this:

≡ Click to see image ≡
posted by chrismear 13 March | 06:51
At the moment, what happens when you click 'Apply'?

If the "Call Completed" tickbox is not ticked, then the form is redisplayed.
If a Call is completed then the form shows the completion information. (But is now required to request 1 piece of extra information)
If a call is completed (with RTF) then the form shows the completion information. (But is now required to request 2 pieces of extra information)

An RTF call is essentially a new call but with exactly the same information to be done later. An engineer creates an RTF if they need to return to site at a later date.

I think the latter of the two screens would do what I need. Now all I need to do is tie in the "Enter some extra information" functionality.
posted by seanyboy 13 March | 07:14
Having Rubber ducked this...

What?! I thought I was up on my corporate speak, but this is a new one to me. Also, if I have a spare few minutes, I'll have a think about your problem.
posted by TheDonF 13 March | 07:15
Rubber Ducking
It's not corporate speak.
posted by seanyboy 13 March | 07:35
FYI - the first thing that caught my eye was the misspelling of 'dispatch' as 'despatch'.
posted by plinth 13 March | 08:38
Perfectly acceptable variant spelling!
posted by chrismear 13 March | 08:43
Dispatch War Rocket Ajax...To Bring Back His Body!

Either spelling is good. Note: quote also contains 'Ajax' and is from 'Flash' Gordon - it's nerd-tastic!

I subscribe to the Making Passionate Users RSS feed but I'm hopelessly behind on it - my list of unread NetNewsWire posts hasn't really dropped below 1000 in the last month.
posted by TheDonF 13 March | 08:58
Flash! Flash! I love you! But we only have fourteen hours to save the Earth!
posted by Hugh Janus 13 March | 09:03
Hmmm - What's google say about this?
≡ Click to see image ≡
Dear God - What have we done.
posted by seanyboy 13 March | 09:11
The voices tell me "Thud". || Let's get started.

HOME  ||   REGISTER  ||   LOGIN