185 reputation
18
bio website
location
age
visits member for 3 years, 2 months
seen 10 hours ago

Aug
2
awarded  Popular Question
Apr
5
awarded  Notable Question
Jul
9
comment if a screen has unsaved changes - if the user switched to a different view, should he be prompted to save (otherwise changes will be lost)?
Thanks for the useful reply. What would you say should happen when editing is possible in only one of the views? say only the table, while the graphical view shows different kind of information about the entities? Say, only the relations between entities but not their textual properties.
Jul
8
asked if a screen has unsaved changes - if the user switched to a different view, should he be prompted to save (otherwise changes will be lost)?
Apr
18
awarded  Popular Question
Sep
1
awarded  Commentator
Sep
1
comment How to display a distinction between actions which affect the 'real world' vs. actions that affect only the information in the application?
This would have been a good option if only the minority of actions required 'publish', yet this is the other way around...as most actions affect the real world, i don't want the users to have to take an extra 'publish' step in each of these
Sep
1
accepted How to display a distinction between actions which affect the 'real world' vs. actions that affect only the information in the application?
Sep
1
comment How to display a distinction between actions which affect the 'real world' vs. actions that affect only the information in the application?
Sadly no...this is part of a technical limitation and so it's the way it must be...
Sep
1
comment How to display a distinction between actions which affect the 'real world' vs. actions that affect only the information in the application?
This is a good option, yet any such graphical distinction requires text anyway, as this is a very specific difference, which has no commonly associated graphical appearance (such as grey for disabled). So I decided to go with using a different icon on the 'commit' button for such actions, and the explanation will appear on the button tooltip.
Aug
25
comment How to search using tags - know any good examples?
I like this approach. How would you present the results - in a flat list or within a hierarchy? if the latter approach is used, then one item can be found under more than one tag/category - so should it be presented several times or just once?
Aug
24
asked How to search using tags - know any good examples?
Jul
31
comment How to display a distinction between actions which affect the 'real world' vs. actions that affect only the information in the application?
That would work for buttons maybe, but in some cases these are text fields. Maybe the buttons to save these can look different...
Jul
24
awarded  Supporter
Jul
24
comment How to mark required (and optional) fields in a form where some fields are NOT editable?
I'm showing read only as well as editable data because they are all properties of the entity, all related to each other (content-wise), and are all part of the same task flow of problem solving (it's difficult to predict when the users will need which piece of information). Also some of the editable fields are not always edited - sometimes the user will just want to read the information and not necessarily edit it.
Jul
24
comment How to mark required (and optional) fields in a form where some fields are NOT editable?
I also considered using the 'optional' instead of the asterisk for mandatory, but it's also important to be consistent across different forms in the application: for some forms, the optional was the exception and for other it was half-half..so for the sake of consistency (and familiarity), I went with the asterisk approach. Since these are not sign up but property forms, even of some information is optional it should still be there for users who want to fill it.
Jul
24
awarded  Scholar
Jul
24
accepted How to mark required (and optional) fields in a form where some fields are NOT editable?
Jul
24
comment How to mark required (and optional) fields in a form where some fields are NOT editable?
I completely agree - read only fields should look like text only - without any input field. What I was concerned about was that this would not be clear enough to the users in terms of whether they whole mandatory/optional distinction even applies to them (it doesn't). From all the answers here it seems like it should be appropriate to use the regular markings for mandatory (asterisk) and optional. If I come across some relevant results on user testing on this I'll post it...Thanks again!
Jul
24
comment How to display a distinction between actions which affect the 'real world' vs. actions that affect only the information in the application?
That would be very helpful - thanks!