Template:Domsub: Difference between revisions
Jump to navigation
Jump to search
Category:Article initialization templates |
catg sort |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
#Edit the page; replace "foo" with the name of the subsystem. Make any other edits and save the page. | #Edit the page; replace "foo" with the name of the subsystem. Make any other edits and save the page. | ||
This is what this template produces: | This is what this template produces: | ||
</noinclude>'''Summary:''' The '''foo subsystem''' manages the resolution of [[URI]]s based on various URI schemes and filename extensions. | </noinclude>'''Summary:''' The '''foo subsystem''' manages the resolution of [[URI]]s based on various URI schemes and filename extensions. | ||
| Line 37: | Line 37: | ||
* ''other?'' | * ''other?'' | ||
<includeonly>[[Category:DOM project|Foo subsystem]]</includeonly> | <includeonly>[[Category:DOM project|Foo subsystem]]</includeonly><noinclude>[[Category:User templates|{{PAGENAME}}]]</noinclude> | ||
Latest revision as of 22:06, 4 March 2009
This template is most likely obsolete.
This template is intended for use by engineer creating DOM subsystem description pages.
USAGE:
- Go to a new blank page--preferably by adding the article's name as a link in the COLLADA DOM user guide article and then clicking that link.
- In the new blank page, type: {{subst:domsub}}
- Save the page; this fills in the outline and sample text.
- Edit the page; replace "foo" with the name of the subsystem. Make any other edits and save the page.
This is what this template produces: Summary: The foo subsystem manages the resolution of URIs based on various URI schemes and filename extensions.
Purpose
- Anything more detailed about its purpose
Text here...
Default behavior
- What kinds of default behavior does this subsystem exhibit and in what circumstances? Can you change the default?
By default, this subsystem resolves only COLLADA documents, whether internal or external references...
More text here...
How it works
- How does this subsystem operate?
Each blah blah blah
Foo example
- Describe an example use of the foo subsystem
Related classes and functions
- DOM foo class: summary text here, e.g.: An interface to inherit from for creating resolvers.
- other?