vorticity Wrote:I will note that you have to do a db request for every single link anyway, to determine whether it's a red link or blue link.
What.
That strikes me as the sort of function that begs for some sort of consolidated lookup table. (As does the addition being suggested here, in my mind.)
Although I'm a bit wary of just using the Laconic entry and calling it good. A lot of the ones I see strike me as going for comedy through abbreviating things as much as possible. (And ones for series are usually even worse.) Not really ideal for the purpose at hand.
(snip stuff)
Quote:Unless someone has a concern about this sort of structure.
Sounds pretty good, although I've got my doubts about using Laconic entries as summaries. Enough doubts that the level of redundancy I'm engaging in at the moment feels sadly inadequate.
Well, there are a couple other things. As an example, take Love Tropes, because it has examples of both the things I'm thinking of, and not just because I'm a Love Freak. For the most part, it's a list. But there's also a bit of introductory text, and links at the side to other related indices. I think both of these are good things, and think it'd be a good idea to have a way to do those and have the auto-generated list get stuck in the appropriate place.
On the other side, there's things like the line for "Love Triangle" having the subtropes for specific types of love triangles listed under it. This also strikes me as good. I'm thinking this could be done by an expansion of the tag syntax - have a format for "In this list, as a child to this other entry".
Quote:So far as the Tropes namespace -- I've thought about that one too, but I'm not sure what the advantage of it is. Leave the root namespace empty except for redirects? It certainly can't be done automatically, given the massive amount of junk in Main/ currently, so a decision on this can wait. What we can do is tag trope pages with "trope". I'm not against it, but right now, I can't think of any arguments in favor of it.
Well, there's something that occurred to me, but that I'm not sure is really a great idea or not. (Or even technologically feasible.) But I kind of don't like the way things seem to end up working with redirects and stuff right now. And then I thought, if there wasn't anything that lived in the root namespace, combined with summaries that can be pulled at need... you could automate the whole thing. If someone requests "/FortAwesome", and there's only one page named that, then it just redirects there, but if there's more than one, it automatically generates a disambiguation page asking if you want the anime Fort Awesome, the unrelated novel Fort Awesome, or the trope about suddenly being put in charge of an awesome fort.
nylor: I don't really like any arrangement for changing trope names that doesn't include a discussion process. For one thing, there's some reasons for keeping certain names that may not correlate with popularity among the people likely to be doing the voting.
-Morgan. Did I mention that a lot of Laconic entries don't make good summaries?