Deleted "allow name collision when creating new cards".

Also shifted solution from below to above the card interface, so that it will be visible on card creation links of content-formatted cardtypes (e.g. http://www.wagn.org/new/Ticket ).

I like this as a default solution and would like not to hard code it. Thoughts about how to represent it in cards?

  --Ethan McCutchen.....Thu May 13 16:35:26 -0700 2010

not clear - what do you want represented in cards? The text, something general about cards going above below _main, ... ?

  --John Abbe.....Thu May 13 19:21:15 -0700 2010

from a broad perspective, I want to start moving more and more system messages, like "a card by that name already exists...." into cards. I think there's a ticket about that somewhere, but in any case it's central to our strategy of internationalization. I don't think we're expecting to do much of any hard-coding of translation.

more specifically to this issue, I'm a little hesitant to hard-code anything using closed view into wagn, as some wagns that are on the cms end of the spectrum seem to stray away from the closed/open thing.

we may end up hard-coding in the very short term because we'd have to do some magic to make it recognized which card is meant to be closed, but I just wanted to think about our long term (not hard-coded) solution.

  --Ethan McCutchen.....Fri May 14 00:32:42 -0700 2010

Heh, i was just thinking the other day about starting to collect those messages somewhere. The ticket in question is move cue text to editable cards.

  --John Abbe.....Fri May 14 01:44:06 -0700 2010