I’m trying to show a master-detail view, where each cell in the master table (the one on the left) represents a list.
When Clicking a cell, the list is opened in the right panel.
The table and the list have pagination.
My pro…

^{download bmml source – Wireframes created with Balsamiq Mockups}

Context:

• Desktop web app
• Wizard (multi-page form) with three steps
  • Appears in modal dialog
• First step has only one control: tree selector
  • Tree does not fit on screen
• Two buttons at the bottom of the form: [Next>] and [Cancel]

Since the tree does not fit in the screen, would it be better to:

a) scroll the entire page – as a consequence you won’t see the buttons on the form without scrolling – OR –

b) scroll the control and always keep the buttons on screen?

There’s a debate between a colleague and myself. He prefers a) using the argument “people scroll” — there are several articles online arguing for the point. However, I feel that 1) scrolling is more suited for web pages (consuming content) rather than web apps and 2) in this particular case showing all the content at once (including buttons) makes the UI more understandable at a glance. Design choice a) makes the user wonder what lies below the fold.

Opinions?

Let’s say we can display exact and approximate points on a map. Approximate points have a constant distance from an exact point. Which means they lie on the circle described by this distance, where the distance is the radius …

I have previously been using 4 fields for the credit card number, splitting up each set of 4 numbers to make it easier to enter.

I am now thinking about having one field, which inserts spaces after every set of numbers inste…

I am in the process of updating an app I have, at the moment if the device is not a tablet it will force the orientation to horizontal mode because the information displayed wouldn’t fit on phones (something never really sat …