simple pattern settings



aka Pattern cards round 1


See Pattern Cards and


Proposed name changes:

  • Pattern -> Panel -> Set
  • Setting -> Knob -> Setting
  • Setting Value -> Setting -> Value (this one isn't a cardtype, just a label)
  • *edit -> *edit help, edit prompt (or edit cue)
  • *new -> *add help, new prompt (or new cue)
  • *default -> *all
  • *self -> *solo -> *self
  • *type cards (Search) -> *is type -> *type (rename *type to "*type subtab")
  • (tag pattern) -> *on right -> *right
  • (type + right pattern) -> *type plus right

(note, I've done some mock-up work for layout of Pattern and Knob cards.  Both list relevant settings. - efm)




Feature: Pattern settings

  In order to control settings in an efficient way

  As a Wagneer

  I want to be able to control settings for patterns of cards



    Given I log in as Joe User


  Scenario: default setting and plus card override

    Given I create card "*default+*new" with content "say something spicy"

    And I create Pattern card "plus color" with content "{"right": "color"}"

    And I create Phrase card "plus color+*new" with content "If colorblind, leave blank"

    When I go to new card named "Test"

    Then I should see "spicy"

    When I go to new card name "Test+color"

    Then I should see "colorblind"



By "spicy" and "colorblind", you mean the longer content phrases containing those words (respectively)? Otherwise I don't get it. But wait, I still don't, why does "Test+fruit" match the "plus color" pattern?

  --Gerry Gleason.....Mon Nov 09 13:30:04 -0800 2009

fruit is meant to be "color". the "I should see" thing is looking to match that content is present (not that it's the whole phrase). so yeah, spicy and colorblind are meant to match the longer content phrases, as you said.

  --Ethan McCutchen.....Mon Nov 09 13:56:17 -0800 2009

updated the feature.

  --Lewis Hoffman.....Tue Nov 10 09:33:25 -0800 2009

Woke up this morning thinking how we don't have a good name for a "setting value" (eg 4) and that it should be called the "setting". My best thought was that we should use "knob" (eg *table of contents) to mean what we're currently calling "setting". But Pattern and knob don't really go well together, so I started thinking, what if Patterns were Panels? The double meaning of "panel" as thing-full-of-knob and group-of-pros makes it interesting.

  --Ethan McCutchen.....Mon Nov 23 13:23:03 -0800 2009

set interface still lacks:

1. sets that haven't been created yet

2. friendly set names

3. in-place adding

  --Ethan McCutchen.....Mon Dec 07 19:47:54 -0800 2009

may also want new tform for Settings cards?

  --Ethan McCutchen.....Mon Dec 07 19:54:42 -0800 2009

Interesting - i don't see a Setting+*tform, but it looks like you did something similar in code. However, it's showing up inconsistently. On all of the setting cards have some kind of automated content (though in closed view most of them seem to be over-recursing). On Setting, only *thanks and *table of contents show the automated content when opened (and *thanks doesn't show it in line view).


I'm working on input on the coded-form for Settings cards...

  --John Abbe.....Sun Dec 20 18:14:18 -0800 2009

(nothing i'm imagining so far would imho be worth holding up the release)

  --John Abbe.....Mon Dec 21 05:02:29 -0800 2009

Settings show the help text from +*edit_help, so i changed phraseology like "this set" to "the set". E.g.*accountable

  --John Abbe.....Tue Dec 22 07:12:28 -0800 2009

*add help (which i'm guessing works now given it got added to English) doesn't appear in settings subtabs.

  --John Abbe.....Tue Dec 22 07:37:04 -0800 2009 or (probly all cardtypes) - in Options/settings, clicking on any of the "Add User+|etc.|" links does nothing (not even connecting to server...)

  --John Abbe.....Tue Dec 22 08:35:18 -0800 2009

1. I see all the settings as formatted on Setting. Might have been a caching issue before?

2. *add help is intentionally removed from the subtabs as are *autoname and *thanks -- you don't usually want to set add help for existing cards :) We may want to change this at some point to give easier access to changing those settings on other sets, but for now this seemed less confusing.

  --Ethan McCutchen.....Tue Dec 22 08:42:33 -0800 2009

Wouldn't hold up 1.3 for this, but my questions and suggested chunking/order for the settings subtab (for both the card itself, and the cardtype-based settings shown on cardtype cards):


Re-ordering the bits there from least to most geeky:


table of contents


add help

edit help








For now doing alphabetical on subtab.  Will change cardtype to match.  It's a search, not a hard-coding, so the chunking would be much harder.  Can discuss as Idea if you want. -efm


Several settings are not listed on subtabs, was this on purpose?:




*thanks is only relevant to cardtypes but doesn't yet appear on them.


No it isn't, and yes it does :) It's implemented like any setting, so if you set it on a +*right set it will apply to those cards.   It doesn't appear on any card itself, because those cards have already been created, but it appears on the cardtype set.


All the Pointer-related ones (*autoname, *input, *options, *option label) don't appear anywhere.


Autoname isn't particularly pointer related, and its exclusion is intentional (see above). 


And the pointer related ones show up on....wait for it... Pointers!  Remember, a card's subtab is for configuring that card.


  --John Abbe.....Tue Dec 22 08:47:40 -0800 2009