163 reputation
8
bio website elstensoftware.com
location London, UK
age
visits member for 3 years, 5 months
seen Jul 7 at 10:36

Programmer of bliss.


Nov
19
awarded  Nice Question
Sep
24
awarded  Autobiographer
Apr
16
comment Enforcing mutual exclusivity in multiple constrained choices
See my response to @Andrew Leach 's idea for a development of this...
Apr
16
comment Enforcing mutual exclusivity in multiple constrained choices
Your "Select..." made me think - what if the affordance to add a row was a drop down button labelled "Add case rule" (this is a 'case rule') with drop down values being album name, artist name etc. When one is selected, a row is added with the choice as a label as suggested in @user3011961 's post. This reduces the complexity of the UI because it becomes two stage with fewer options at each stage (can't remember what the Design of Everyday Things says about this... but it's in there IIRC). The obvious drawback is you can't change the field name... but would you want to? It can still be deleted
Apr
15
comment Enforcing mutual exclusivity in multiple constrained choices
Yes, this is pretty much what I'm doing now. It just began to feel a bit "icky" as more rows were added. Should adding more rows be disallowed for example? Doesn't appear to be the case in your example. There is also the option of attaching semantics to multiple settings for the same value - e.g. ANDing or ORing the meaning together...
Apr
15
comment Enforcing mutual exclusivity in multiple constrained choices
What if there are fifty labels? Five-hundred (potentially changing to an auto complete drop down here)?
Apr
15
awarded  Commentator
Apr
15
comment Enforcing mutual exclusivity in multiple constrained choices
Broadly I agree in this case but I'm also interested in the analogy of boiler plate v free form editing. Most IDEs for example allow you to make mistakes and mark those mistakes, rather than not allowing you to make mistakes. Others enforce boiler plate. Personally I prefer the free form approach to the boiler plate approach... but maybe it depends on the skill level of the user.
Apr
15
comment Enforcing mutual exclusivity in multiple constrained choices
Sorry, I wasn't clear so I have edited the question. They cannot be labels because each row is optional.
Apr
15
revised Enforcing mutual exclusivity in multiple constrained choices
added 132 characters in body
Apr
15
asked Enforcing mutual exclusivity in multiple constrained choices
Jan
8
awarded  Popular Question
Jul
4
awarded  Scholar
Jul
4
accepted For large hierarchies - checkbox tree or 'guided tree construction'
Jun
24
comment For large hierarchies - checkbox tree or 'guided tree construction'
Agree bulk operations need to be thought about, but don't need 'add all children' yet I don't think.
Jun
24
comment For large hierarchies - checkbox tree or 'guided tree construction'
The topmost drowndown can be ignored, it just enables the list in a progressive disclosure style (the default is 'ignore genres' or something like that).
Jun
24
comment For large hierarchies - checkbox tree or 'guided tree construction'
The add button next to the search box is to allow arbitrary genres to be added, a little like autocomplete. I don't plan on conveying subgenres for now, but might add a browse by hierarchy using Miller Columns.
Jun
22
comment For large hierarchies - checkbox tree or 'guided tree construction'
I added a mockup of what I'm thinking it might look like. Feel free to agree/disagree and let me know if I'm not following. Right now, I'm not sure if there is a need for the breadcrumbs/hierarchy at all after all. Maybe an additional 'add by browsing' option, in addition to 'add by search', could use this.
Jun
22
revised For large hierarchies - checkbox tree or 'guided tree construction'
Adding another alternative - list building
Jun
20
comment For large hierarchies - checkbox tree or 'guided tree construction'
Thanks Alex. I'm beginning to come around to the flatter style. Please see @agib's answer below.