We want these cards — which return content determined by code, as virtual cards — to be overridden by an actual card by their respective names if such a card is created.
We may want to solve this by implementing all of their functionality with regular cards (*search would present an interesting challenge here).
Note however that expose deck metadata in cards and expose card metadata in cards seem likely to introduce new coded virtual cards.
Why would we want to enable overriding of *recent_changes or *search? —John
the time I wanted to do it was when I wanted to change the default view.
Let's knock this down to low until we're sure we don't just want to make them real cards. (done)
--Ethan McCutchen.....Thu Mar 05 10:44:11 -0800 2009
+discussed in support tickets
+relevant user stories