Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When selecting a tag for a parent topic, pre-fill same tag for child topics #8

Open
O-kasso opened this issue Jan 9, 2017 · 2 comments

Comments

@O-kasso
Copy link

O-kasso commented Jan 9, 2017

If I want to tag all of the subtopics in a parent topic with the same tag (Don't Know it / Know it / etc), I have to check each one individually. Checking only the parent category suffices, but there are scenarios where this causes pain:

I might "know" everything in a topic except for 1 or 2 subtopics. When this happens I must tag each subtopic with "Know it", and then tag that 1 subtopic as "Don't know it"

screen shot 2017-01-09 at 2 04 11 am

@davidgilbertson
Copy link
Owner

I have two options when it comes to score inheritance (that I can think of).

Option 1 - be loose

Let people propagate any of the four scores down to all descendants. If someone misses out on discovering something because they thought they knew all the pseudo classes (or whatever it might be) but do not actually know of :empty or the new :left and :right selectors, it's not my job to stop them.
UI for this will be hard (for mobile) - there's not much room to work with for each row.

Option 2 - be strict

Allow "don't know it" and "don't care" to be propagated down to all children.
Don't allow this for "know it" and "know of it".
This is logical but still opinionated.

Thinking about this now, if you "Don't care" or "Don't know" about CSS Filter effects, that logically applies to all children so I can propagate those scores down without asking. So option 2 is actually a zero-UI solution.

While I'm generally not a fan of software telling me what to do, I think option 2 wins here just for the simplicity of it.

Thoughts?

@O-kasso
Copy link
Author

O-kasso commented Jan 13, 2017

Both options sound like improvements to me. Option 1 pretty closely mirrors the behaviour of the nested folder checklist UI in Windows. Option 2 is a little more forgiving however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants