Hot answers tagged lists
I suggest using option A. Since we read (and view pages) from left to right this will allow users to explore more. In option B going back seems like a weird experience, I expect people to browse through less blocks this way.
Generally, time-based lists, as you have described in your sketches, would normally flow in the standard reading direction so that the earliest item is read first and the latest, last. This also works in a vertical sense (top = earliest, bottom = latest). This can be seen in all sorts of applications such as calendars or schedules where both the vertical and ...
This should be a common and clear layout. If an editable grid of tenants is not feasible or if editing tenant info is a very common use case (usually it wouldn't be), you can drop the "Edit" column and instead have a form with tenant info at the bottom of the screen, displaying the data of the tenant selected in the grid. download bmml source – ...
I agree model + panel does not sound good. Why not continue with panels? There are many ways to do this, the one below assumes minor changes and retaining your layout. See example below. One option is to retain the directional flow of content and preserve relation to the list.
A usability study would definately give you a good answer as to what your users expect. General Assumption In most cases search should return all users regardless if they are active or not. I am assuming this because, you are searching for a profile which then you may want to modify / update / etc. One of your flows could be "find an activate a user". ...
Only top voted, non community-wiki answers of a minimum length are eligible