network profile
| bio | website | elstensoftware.com |
|---|---|---|
| location | London, UK | |
| age | ||
| visits | member for | 2 years |
| seen | May 14 at 16:46 | |
| stats | profile views | 4 |
Programmer of bliss.
|
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. |
|
Jun 20 |
comment |
For large hierarchies - checkbox tree or 'guided tree construction' I kinda like this. Here are the reasons I started with a tree view: (1) possible to navigate to find the appropriate genre (2) if an album has a genre that is not 'allowed', the software chooses the first parent that is allowed. I wanted the model of (2) to be represented in the UI. Maybe it's not important? Maybe the communication of genre parenting in breadcrumbs is enough? |
|
Jun 17 |
awarded | Supporter |
|
Jun 17 |
comment |
For large hierarchies - checkbox tree or 'guided tree construction' Thanks for the extra detail. I just added the clarification that either tree must support adding arbitrary user-entered nodes/leaves. For example, select 'Rock' and add '70s Rock'. It should possibly also allow some movement of a sub tree elsewhere, for instance via copy/paste or d'n'd. |
|
Jun 17 |
revised |
For large hierarchies - checkbox tree or 'guided tree construction' Clarification that the tree should support arbitrary added/removed nodes |
|
Jun 17 |
comment |
For large hierarchies - checkbox tree or 'guided tree construction' Agree this can always be an issue. I'm trying to make sure the UI represents the internal model. Are you saying users may expect a flatter/folksonomy approach? |
|
Jun 17 |
awarded | Editor |
|
Jun 17 |
revised |
For large hierarchies - checkbox tree or 'guided tree construction' Added a disadvantage to the alternative - lots of clicking when adding lots of nodes |
|
Jun 17 |
comment |
For large hierarchies - checkbox tree or 'guided tree construction' Thanks, but what are the reasons for going with a checkbox tree? Familiarity? Clumsiness of the alternative? |
|
Jun 16 |
awarded | Student |
|
Jun 16 |
asked | For large hierarchies - checkbox tree or 'guided tree construction' |
