Suppose:
mainpage=nexus tid 1
foo=nexus tid 2
- is child of mainpage with min_weight 3
bar=topic tid 3
- is child of mainpage with min_weight 3
- is child of foo with min_weight 1
Right now I think pudge generates the following tree of topics for
authors to pick from:
Mainpage
Bar
Foo
Bar
The problem is that those are the same Bar. If Bar is picked with
weight 1 or 2, it is effectively only "Foo :: Bar" since it will appear
in only that nexus's skin(s). But if it's picked with weight 2 or 3, it
is both "Mainpage :: Bar" and "Foo :: Bar" since it will appear in
both (all) skin(s).
It would be nice to have a good way to represent this in the UI,
since this might be very confusing. Maybe if "Foo :: Bar" is
selected, weights 3 and 4 should not be available in the popup, but
I suspect that involves writing a lot more Javascript. Or maybe if
its weight is set to 3 or 4, we display it not as "Foo :: Bar" but as
"Mainpage :: Bar" -- but that may involve writing more Javascript
too, and that's no fun.
Maybe the only good solution is to, on Preview, echo back to the
user a proper list that is not misleading. It would also be nice to
have a simple, clear explanation of how the story will be
categorized and displayed, like:
"Story is Never Display"
"Story will appear only on the mainpage."
"Story will appear on the mainpage, linking to skin Apple, and also
in skins Apple and BSD."
"Story will appear only in skin Apple."
"Story will appear only in skins Apple and BSD."
But we'd still need a Preview for that...
Logged In: YES
user_id=3660
We had discussed changing how the topic in the select box appears
anyway, so let's include that in this discussion. Regardless, we might not
need a preview for the text description, I think we could do it in
JavaScript.
Logged In: YES
user_id=3889
I think I talked pudge out of doing this in Javascript, since it requires
running the renderTopics algorithm. So I'm still working on this.
Logged In: YES
user_id=3889
This kicks ass, thanks Tim.