edit_html permission removed at 0.10
false
<-->
Home Recent
Request an Invitation Sign in
Page Feature

What are Forms?

 

Forms are patterns of content. Every day we encounter lots of formatted information: weather forecasts include temperature, cloudiness, humidity and so on; sports cards include a player's various statistics. Restaurant menus, user profile pages, tax documents and nutrition labels each have their own pattern of what information is included, and how it is laid out. Whenever you want to organize sets of information, these patterns help you compare and contrast information visually, and to notice missing information.

 

Wagn lets you create forms (they are simply cards of course), and to apply a form to many cards, so that when you have a set of cards that are about the same kind of thing, you can be sure they will all contain the same information, in the same layout.

 

Type forms apply to cards of a particular cardtype. For example, the type form associated with the Recipe cardtype is applied to every Recipe card, so that each Recipe shows how many people it serves, a list of ingredients, how to prepare the dish, etc.

 

The other kind of form is a right form, so-called because it applies to all cards that have a given card name as the right-most part of their name. For example, the right form connected to serves is applied to every card that ends with +serves — Carnitas+serves, Dahl+serves, etc., in this case simply ensuring that each of those cards contains a number.



Page

Forms are, like everything else in Wagn, cards. Specifically, they are plus cards whose right-most part is either *tform — for type forms, or *rform — for right forms.

To create a type form, join a cardtype card to *tform. For example, the form for all Recipe cards is Recipe+*tform.

To create a right form, join any simple card to *rform. For example, the right form for all cards ending in "+serves" is serves+*rform.

 

Building a Type Form


Building type forms relies heavily on plus cards and inclusions, so make sure you understand them first before giving this a try. When you're creating a form for creating common content and layout, for each piece of information you want on the form, you'll add a relative inclusion. Often you'll also have some text to label it. For example, part of Recipe+*tform looks like this:

Serves: {{+serves}}

 

{{+ingredients|open}}

 

Preparation

 

{{+preparation}}

Note that the layout and styling you apply to text and to inclusions will affect the cards the form applies to.

 

Forms Can be Soft or Hard

 

By default, new forms are soft, which means that cards they apply to only draw their initial content from the form, but can be edited later. You'll almost always want type forms to be hard, meaning that the cards the form applies to are not editable — when you edit them you are actually editing just the inclusions in them. You can change a form's soft/hardness whenever you're editing a form, with these buttons just above the edit box (note that this will only appear after you have created the card, and are editing it again):

Building a Right Form

 

Type forms and right forms have all of the same capabilities. That said, the most typical usage is as described above for type forms, while right forms are often used simply to set the card's cardtype. To make it so that every recipe's +serves card will contain a number, you would create serves+*rform, set it to be cardtype Number, not enter any content in it, and leave it as a soft form.



Page

Here's the whole Recipe type form:

Page

Preparation time: {{+preparation time}}

Serves: {{+serves}}

 

{{+ingredients|open}}

 

Preparation

 

{{+preparation}}

 


Tags: {{+taglist}}

 

Comments

 

{{+discussion|closed}}

It includes plus cards for information relevant to any recipe: preparation and cook time, number served, ingredients, etc. When a user edits a recipe, Wagn offers to edit those plus cards (or create them if they don't exist yet). Here are all of the Recipe cards — open some up and edit them to see how the form works in action:

Preparation time: 10 minutes Serves: 4   Pork Water Salt Lime  

Preparation

  Put the pork in a pan and cover (barely) with water.  Sprinkle liberally with salt.  Cook on medium flame until the liquid is reduced to ...  
Tags:  

Comments

 
Preparation time: 30 minutes Serves: 4   Tortilla Tomatos Chile Chicken (optional) Cheese Cream  

Preparation

 
  • Place the tortillas in a pan with oil until they are really crunchy
  • Prepare the salsa (placing tomato in a pan with oil, onion and chile)
...  
Tags:  

Comments

 
Preparation time: 5 minutes Serves: 6   1 cup red lentils 2 cups water 1 tablespoon cumin powder 1 tablespoon coriander powder 1 teaspoon turmeric ...  

Preparation

   
Tags:  

Comments

 



Page
  • Custom edit instructions can be created to show up next to relative inclusions when they're being created or edited
  • Whenever you edit a card controlled by a hard form, there's a link to the form itself at the top of the card — just click on the word "form" in "Formatted by a form card."
  • If you only want to edit one item on a hard-formatted card, you can double click in that text and only that card will be opened for editing.
  • Permissions on a card will be set by a form that applies to the card. However, while a hard form permanently determines a card's content and cardtype, the card's permissions are always editable later.
  • In general, when a type form and a right form would apply to a given card, the right form takes precedence.


Tickets relevant to formatting:
documenting , medium , John Abbe Issue or Question Instead of creating card-specific forms, we just want to add another way to edit that shows edit boxes for each inclusion. Solution Tags: Example of the bug, or an example the question relates to Discussion User stories open , medium , +assigned to Issue or Question Solution When you add a hard form to card(s) that already exist and have content, offer to copy the current content to a relative inclusion card ... Tags: Example of the bug, or an example the question relates to Discussion User stories open , medium , +assigned to Issue or Question +issue Solution +solution Tags: Related tab Options tab Wagn 1.0 formatting upgrade formatting Example of the bug, or an example the question relates to Discussion User stories open , high , +assigned to Issue or Question I'm using svn trunk, r694. I cannot seem to set the a +*rform to Hard, which prevents my having plus cards that are Searches. In ... Solution Tags: Example of the bug, or an example the question relates to Discussion User stories open , high , +assigned to Issue or Question type form (coaching session on nurture wagn) created with no permissions --Lewis Hoffman.....Sun Dec 09 20:38:15 PST 2007 Soft form should be applied whether ... Solution Tags: Example of the bug, or an example the question relates to Discussion User stories open , medium , +assigned to Issue or Question +issue Solution +solution Tags: formatting Example of the bug, or an example the question relates to On John Abbe go down to How to reach me. I can't figure out how to get rid of the vertical space between ... Discussion User stories open , medium , +assigned to Issue or Question +issue Solution +solution Tags: Pointer formatting Connectipedia show help text on new cards Example of the bug, or an example the question relates to Discussion User stories open , medium , +assigned to Issue or Question +issue Solution *limit+*tform (soft) = blank but cardtype Number   Code such that if you plus a Pointer card to *limit, then you can't add more items ... Tags: Example of the bug, or an example the question relates to Discussion User stories open , medium , +assigned to Issue or Question +issue Solution +solution Tags: formatting design Connectipedia Example of the bug, or an example the question relates to Discussion User stories open , high , +assigned to Issue or Question +issue Solution Set cardtype to "type:", "|cardtype|" in relative inclusion's +*options. No menu.   Once we make specifying a parameter twice in a search work, ... Tags: Example of the bug, or an example the question relates to Discussion User stories open , high , Issue or Question For cards that are included in content or raw view:   A way - besides double-clicking - to edit them. (Comes up when the included ... Solution add page icon? √Add ability to edit name and cardtype when editing an included card not in card/line/open/closed view. √When you double-click on an ... Tags: Example of the bug, or an example the question relates to Discussion User stories open , medium , +assigned to Issue or Question Open Money wants menus. We also want check boxes, radio buttons... The list of cards would be specified by +*options. Solution +solution Tags: Example of the bug, or an example the question relates to Discussion User stories documenting , medium , John Abbe Issue or Question A way to specify view for items returned by Searches and Pointers. Clearer/easier view:-related syntax Solution Deprecate view:card and view:line in favor of view:open and view:closed. Also, make the "view:" optional - i.e., interpret |open, |closed, etc. the same as |view:open, ... Tags: Example of the bug, or an example the question relates to Discussion User stories

Add +discussion