Local Prototyping & Content

If you wish to prototype intercooler interfaces locally, with no server, or if you wish to avoid server round trips for certain elements, you can take advantage of the prototyping system built into intercooler:

• Demarcate a section of HTML to be ignored by intercooler by applying the ic-ignore class to it. No content will be processed in this section, so you can use intercooler attributes without risk of triggering things like polling, event support, etc.
• Within this section, you can create elements with unique ID's that hold the prototype HTML content you want swapped in via an intercooler request.
• In your active UI, you can refer to these elements using a fragment identifier corresponding to the element's ID.
• You can use ic-local-* attributes to return status codes or custom intercooler headers to more fully simulate server requests.
• Depending on where you are in development, you may want to hide the ic-ignore section, to better visually simulate your UX.

Using this technique, you can build prototype or local-content UX with no Javascript whatsoever!

      <div ic-on-error="alert('oh no!')">
        <div class="btn btn-default" ic-get-from="#hello_world">Click me</div>
        <div class="btn btn-default" ic-get-from="#error_example">Don't Click me</div>
      </div>


      <hr>
      <h3>HTML For Responses:</h3>

      <div class="ic-ignore panel">

        <div id="hello_world">
          Hello, world
        </div>

        <div id="error_example" ic-local-status="500 Server Error">
          Goodbye, world
        </div>
      </div>