Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
spec:dfn-patterns [2013/07/30 12:24] – Add an export section. tabatkinsspec:dfn-patterns [2013/07/31 12:38] – added token and dictmember dfn types plinss
Line 26: Line 26:
   * function (like counter() or linear-gradient())   * function (like counter() or linear-gradient())
   * selector   * selector
 +  * token
  
 There are additional categories for WebIDL definitions: There are additional categories for WebIDL definitions:
Line 33: Line 34:
   * attribute   * attribute
   * dictionary   * dictionary
 +  * dictmember
   * enum   * enum
   * const   * const
Line 56: Line 58:
   * Does it start with an @? Then it's an **at-rule**.   * Does it start with an @? Then it's an **at-rule**.
   * Is it surrounded by <>? Then it's a **type**.   * Is it surrounded by <>? Then it's a **type**.
 +  * Is it surrounded by 〈〉? Then it's a **token**.
   * Does it start with a :? Then it's a **selector**. (This is a simplistic auto-detection for pseudo-classes and pseudo-elements.)   * Does it start with a :? Then it's a **selector**. (This is a simplistic auto-detection for pseudo-classes and pseudo-elements.)
   * Does it end with ()? Then it's a **function**.   * Does it end with ()? Then it's a **function**.
Line 74: Line 77:
 |funcdef | function| |funcdef | function|
 |selectordef | selector| |selectordef | selector|
 +|tokendef | token|
 |interfacedef | interface| |interfacedef | interface|
 |methoddef | method| |methoddef | method|
 |attrdef | attribute| |attrdef | attribute|
 |dictdef | dictionary| |dictdef | dictionary|
 +|dictmemberdef | dictmember|
 |enumdef | enum| |enumdef | enum|
 |constdef | const| |constdef | const|
Line 97: Line 102:
 |funcdef- | function| |funcdef- | function|
 |selectordef- | selector| |selectordef- | selector|
 +|tokendef- | token|
 |interfacedef- | interface| |interfacedef- | interface|
 |methoddef- | method| |methoddef- | method|
 |attrdef- | attribute| |attrdef- | attribute|
 |dictdef- | dictionary| |dictdef- | dictionary|
 +|dictmemberdef- | dictmember|
 |enumdef- | enum| |enumdef- | enum|
 |constdef- | const| |constdef- | const|
Line 152: Line 159:
 If using Tab's preprocessor, you may instead use a simple ''for'' attribute on the ''<dfn>'', or a ''dfn-for'' attribute on a container.  As well, Tab's preprocessor automatically enforces the use of "for" indicators, flagging an error if they're missing.  (TODO: Rather, it will soon. Haven't coded it up quite yet.) If using Tab's preprocessor, you may instead use a simple ''for'' attribute on the ''<dfn>'', or a ''dfn-for'' attribute on a container.  As well, Tab's preprocessor automatically enforces the use of "for" indicators, flagging an error if they're missing.  (TODO: Rather, it will soon. Haven't coded it up quite yet.)
  
-==== Exporting Definitions ====+===== Exporting Definitions =====
  
 Definitions have a concept of being "exported" from a spec, which makes them available for automatic cross-referencing.  Most types of definitions are //automatically// exported, with no additional effort from you.  The only exception is "dfn" type definitions - to make these available for cross-referencing, you must add a ''data-export'' attribute to them or an ancestor. Definitions have a concept of being "exported" from a spec, which makes them available for automatic cross-referencing.  Most types of definitions are //automatically// exported, with no additional effort from you.  The only exception is "dfn" type definitions - to make these available for cross-referencing, you must add a ''data-export'' attribute to them or an ancestor.
 
spec/dfn-patterns.txt · Last modified: 2014/12/09 15:48 by 127.0.0.1
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki