network profile
| bio | website | |
|---|---|---|
| location | Vienna, Austria | |
| age | ||
| visits | member for | 1 year, 9 months |
| seen | May 15 at 11:24 | |
| stats | profile views | 5 |
|
Jan 31 |
comment |
Layout question regarding “Select existing record or create new one” pattern thx. good comments. I agree on what you said about the tabs. I think they might confuse the user more than they help (proably also easy to oversee). Going with option 2 allows me to show directly the create form interface when the user doesn't have any existing records to choose from and skipping the select existing record alltogether. Do you know of any existing sites that implement something like that? I only found this: desdag.blogspot.de/2012/06/progressive-disclosure.html and this: sixrevisions.com/user-interface/… |
|
Jan 29 |
comment |
Layout question regarding “Select existing record or create new one” pattern Yes, that was actually the third option I was considering. I will try both Tab Panel and split view approach and see how it looks. |
|
Jan 29 |
comment |
Layout question regarding “Select existing record or create new one” pattern Example for fluid/liquid layout for fullscreen: twitter.github.com/bootstrap/examples/fluid.html |
|
Jan 29 |
comment |
Layout question regarding “Select existing record or create new one” pattern Thx for the feedback and the links. Regarding liquid vs fixed layout: This is a web-application with a lot of charts and visualizations where it makes sense to use the available screen estate. I don't think that a fixed layout is necessarily the best thing for these kinds of web-apps (they are most suitable for descriptive web-sites). For example gmail, google analaytics and other web-apps make use of the entire screen. I can use fixed width for text blocks and combine this with responsive/fluid layouts. For example I can have 4 cards in a row in widescreen and only 1 for a mobile view. |
|
Jan 29 |
asked | Layout question regarding “Select existing record or create new one” pattern |
|
Aug 30 |
comment |
master/detail view blank state/detail view when nothing is selected Thanks for the good suggestions (i.e. circle placeholder for the PieChart, etc). For example Basecamp uses "cartoonish/painted" placeholders for blank space (public.basecamp.com/1679267/projects/178-bcx-blank-slates/…). |
|
Aug 30 |
comment |
master/detail view blank state/detail view when nothing is selected Ok you might be right in that specific use case. Maybe it makes sense to select a default value and display everything initially. However I am more interested in how this "ask the user to select something to display more info" blank space part can be solved regardless of this specific use case. |
|
Aug 30 |
comment |
master/detail view blank state/detail view when nothing is selected Thanks for the feedback and the links. Actually I have another use case which is exactly what you show in your Axure mockup. So I think you understand the question. I was also looking for some real life examples that can provide inspiration on how to style/design this blank space, but unfortunately I couldn't find any good ones. I already saw the examples in ui-patterns before but they are more about creating initial content rather than asking the user to select something to get more info. |
|
Aug 30 |
awarded | Supporter |
|
Aug 29 |
comment |
master/detail view blank state/detail view when nothing is selected Because there is no good default "Category". If I set it to a random one most users will probably not bother thinking about choosing the correct Category and create entries with a wrong Category. Although not entirely the same thing as in my use case in Gmail they also have a blank space/state when you initially open your inbox. Once you chose a mail it will update the detail view with the content. |
|
Aug 29 |
asked | master/detail view blank state/detail view when nothing is selected |
|
Jul 25 |
awarded | Student |
|
Jul 25 |
asked | UI for Access Control List (ACL) |
