A "hand" being any arbitrary list of cards.
Put a link in the Options tab of every Pointer which you can click on and Wagn offers you to download a hand file.
On the Config page of every Wagn is a link you click on and it asks for a hand file to be uploaded. You upload one of those files, and it adds those cards to the Wagn. (need to protect against denial-of-service issues here)
We could also maintain a bunch of hand files on wagn.org and have links on a Config page that let you import one of those files into your Wagn.
By the time we get to this, there won't be an Options tab. Does this belong in a settings tab? What other pieces of functionality are similar enough that they should be integrated? RSS? import/export? Is this basically a subset of broader import/export functionality we need to design? Should this be done as a view so it's easier to share hand files?
Probably a separate conversation, but we should also think about what it would take so we could do a complete "structure dump" of a wagn. Meaning you could go to a wagn (at least an open one) and click "copy my structure" and get everything you need to start a new wagn from scratch, but without all the content.
The last bit is tricky — which cards are structure and which are content?
All star cards is a start, but not enough. E.g., the choices specified by *options are part of structure (and their +description label). Hm, and *options' choices are structure only in some cases (e.g. often not when input=list). Even if we do end up requiring some human maintenance of the list of structure cards, having some logic that provides a good first pass is probably well worthwhile.
--John Abbe.....Thu Dec 16 12:13:22 -0800 2010
Yes, this feels like a subset of import/export function generally.
--John Abbe.....Thu Dec 16 12:13:53 -0800 2010
If it's a view, then you can get a hand with a URL to a Pointer or Search card that ends something like this?
--John Abbe.....Thu Dec 16 12:15:54 -0800 2010
yep. I'm starting to think for some extensions (.css, .txt), it should automatically do no layout and give you the right view. maybe this should also apply to .hand?
--Ethan McCutchen.....Thu Dec 16 12:43:26 -0800 2010
This is tricky, because when people upload files, they sometimes name the card after the file. More generally it feels like a big step I would want to think about before diving into.
--John Abbe.....Thu Dec 16 13:47:38 -0800 2010
there would definitely be a lot of work, but fwiw, rails has a bunch of extension handling built in (which we use for .rss), our standard urls wipe out the periods from cardnames (see Wagn 1.05), and we are in a place of needing simpler urls now for things like css. I don't want to jump into it too fast, but we have more actually user pressure for this stuff than for hands, arguably.
--Ethan McCutchen.....Thu Dec 16 13:53:47 -0800 2010
I'm closing this and moving discussion over to the blueprint: Hands of Cards
--Ethan McCutchen.....2013-02-25 17:02:32 +0000