Ticket
+status
+priority
+commit
+issues
Inclusions can specify type for cards that don't exist yet, e.g.:
When you click on the resulting "ADD +NEW CARD" the card is preset to Pointer cardtype, but if you do multi-edit (because it's hard-formatted, or by clicking the Edit...inclusions subtab) it's Basic.
(someone clicked Edit on Connectipedia's User form and ran into this)
Are there other situations in which the inclusion type-setting won't be applied that we might want it to?
keep specifiable relative content for plus cards in mind at least while coding this
--John Abbe.....Tue Apr 28 13:34:50 -0700 2009
very simple to fix. no real new structure.
--Ethan McCutchen.....Thu Apr 30 11:05:34 -0700 2009
Was unsure about prioritizing inclusion syntax over rform, but makes sense. rform specifies default in all cases, inclusion syntax overrides it in certain cases.
--John Abbe.....Thu Apr 30 11:24:22 -0700 2009
Want to document this feature in general in structure and nesting.
--John Abbe.....Thu Apr 30 11:25:26 -0700 2009