This document assumes that you are familiar with the Wagn concepts of sets and views and understand the directory structure of set modules. If not, please refer to the mods+howto+get started card. We would also recommend that you begin by reviewing a few of the set modules in the mods+examples card to get an idea of how they look.
It may also be helpful to introduce yourself to the MoVE architecture that frames the set module API.
If you're in this deep, you probably know what Wagn "views" are. Things like open, closed, content, core, raw, etc. And you ...
Note that this API document at present covers only the set modules api and not the other components of Wagn mods. If you are interested in the other components, we welcome a nudge!
Presumably, one function the API offers is the ability to store/retrieve/update data about ...
I just started a major overhaul of the api card and moved all our old discussion into the card above in hopes of creating more space for new conversation.
--Ethan McCutchen.....2013-02-19 20:47:19 +0000
Thanks! Would an "upgrade" to my Wagn that consisted entirely of cards be considered a mod?
No, as I'm currently using the language (which has admitted evolved a lot), it would not. I'm using "mod" specifically for code and not for card content.
I would call what you're describing a "hand". As hinted in that blueprint, we'd like to get to the point where most Wagneers can largely ignore the vocabulary of "mods" altogether, because when you copy (install? deal?) a hand, there'd be a mechanism to pull over the requisite mods along with them.
you got an email about this, right?