Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a core/requirements module. #88

Merged
merged 1 commit into from Oct 17, 2012
Merged

Add a core/requirements module. #88

merged 1 commit into from Oct 17, 2012

Conversation

tobie
Copy link
Member

@tobie tobie commented Oct 17, 2012

This module does two things:

  1. It finds and marks all requirements. These are elements with class "req".
    When a requirement is found, it is reported using the "req" event. This
    can be used by a containing shell to extract them.
    Requirements are automatically numbered.
  2. It allows referencing requirements by their ID simply using an empty <a>
    element with its href pointing to the requirement it should be referencing
    and a class of "reqRef".

<p>This use cases implies the following requirements:
<a href="#foo" class=reqRef></a>, <a href="#bar" class=reqRef></a>.</p>

[…]

<p id="foo" class=req>It MUST be possible to do foo.</p>

<p id="bar" class=req>It MUST be possible to do bar.</p>

Will yeld:

This use cases implies the following requirements:
<a href="#foo" class=req>Req. 1</a>, <a href="#bar" class=req>Req. 2</a>.</p>

[…]

<p id="foo" class=req><a href="#foo" class=req>Req. 1</a>: It MUST be possible to do foo.</p>

<p id="bar" class=req><a href="#bar" class=req>Req. 2</a>: It MUST be possible to do bar.</p>

This module does two things:

1.  It finds and marks all requirements. These are elements with class "req".
    When a requirement is found, it is reported using the "req" event. This
    can be used by a containing shell to extract them.
    Requirements are automatically numbered.

2.  It allows referencing requirements by their ID simply using an empty <a>
    element with its href pointing to the requirement it should be referencing
    and a class of "reqRef".

                           * * *

    <p>This use cases implies the following requirements:
    <a href="#foo" class=reqRef></a>, <a href="#bar" class=reqRef></a>.</p>
    
    […]
    
    <p id="foo" class=req>It MUST be possible to do foo.</p>

    <p id="bar" class=req>It MUST be possible to do bar.</p>

Will yeld:

    This use cases implies the following requirements:
    <a href="#foo" class=req>Req. 1</a>, <a href="#bar" class=req>Req. 2</a>.</p>
    
    […]
    
    <p id="foo" class=req><a href="#foo" class=req>Req. 1</a>: It MUST be possible to do foo.</p>

    <p id="bar" class=req><a href="#bar" class=req>Req. 2</a>: It MUST be possible to do bar.</p>
darobin added a commit that referenced this pull request Oct 17, 2012
Add a core/requirements module.
@darobin darobin merged commit 7cc8574 into w3c:develop Oct 17, 2012
shikhar-scs pushed a commit to shikhar-scs/respec that referenced this pull request Feb 19, 2018
shikhar-scs pushed a commit to shikhar-scs/respec that referenced this pull request Feb 19, 2018
shikhar-scs pushed a commit to shikhar-scs/respec that referenced this pull request Feb 19, 2018
Voronoi overlays for single line charts made the mouse-overing slightly
awkward, this makes rects the default for single line charts and
voronoi the default for multi-line ones.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants