Pattern Cards

(Note that when they were implemented, "patterns" got renamed to "sets".)

 

The "pattern cards" idea aims to address a number of evolving wagn challenges that stem from different ways in which we want to manipulate (format, regulate via permissions, cue editing with instructions, layouts, etc) cards that adhere to certain patterns of name and type.

 

A "Pattern" defines a group of cards to which settings may be attached.    "Pattern" is actually not a new cardtype, but it is defined ...

Needs

  • We are increasingly finding our permissioning system meeting significant limits.  For example:
    • you can set global permissions determining who can change
...

Solution

  We propose to abstract the idea of a "pattern" out from these separate problems -- conceptually, in card structure, and ...

I've done a little work on a first stab at how it might look to interact with patterns on a per-card basis.  The following is ...

Use cases

The two most common use case for patterns are:
  1. we have a card and need to know a pattern-based setting.
...

  1. how do we want to pull off step #1 in Pattern Cards+implementation?  So far we've stopped short of picking an implementation route.
...

Based on the outline in WADL, I am reworking the DSL part, I'll leave the original below and we can delete it when ...

BP = Before Patterns.  AP = After Patterns (or Anno Patterni) italics = name is significant / recognized by code  

Type forms

BP: ...

 

 

 

I wiped the discussion here because it was mostly about implementation of an earlier version of the solution.  It's all in "Changes", of course.  
I ...

 

Also see:

try it

 

wagneers

intro

videos

features

syntax

weekly calls

ideas

 

twitter

mailing list

 

developers

roadmap

next release

tickets

pack API

REST API

one-pager

 

github

mailing list

 

wagn.org

recent

todo