Examples
Each page is one pattern. It says what the pattern does, shows the HTML with its ypy-* attributes, shows what the
server answers (an HTML fragment, a status, the headers) and, for the twelve first ones, runs the pattern on the page
itself.
Read the demos
-
The demos are real. Each one sends requests to this site, which answers with HTML fragments, and YPY swaps them into the page. Nothing is simulated in the browser.
-
What you change is kept for you alone, in a cookie that lasts an hour. No other visitor sees it, and there is no database.
-
The server side is described, not coded. Any server that answers an HTML fragment works, in any language. The Docs page lists what a server has to know.
What every example assumes
-
The script. Every example needs the core:
<script src="https://cdn.jsdelivr.net/gh/ypy-develop/[email protected]/dist/ypy.min.js"></script>The same file is also served at
https://cdn.ypy.dev/[email protected]/ypy.min.js. When an example needs an extension, it names it. Theypy.maxbuild already includes most of them. -
The default swap. Without
ypy-swap, the response is morphed into the target: its children are updated in place (innerMorph). The examples that replace the element itself sayypy-swap="outerHTML". -
Attributes are not inherited, unless they end in
:inherited. Writeypy-targetandypy-swapon the element that makes the request. See Attribute inheritance. -
Answers are fragments with
Vary: YPY-Request, so a cache never hands one to a visitor who asked for a page. -
CSRF. A
POST,PUTorDELETEneeds a CSRF token. A form carries it in a hidden_tokenfield; a button that is not in a form sends it as theX-CSRF-Tokenheader withypy-headers. See CSRF. -
No script of yours. The approach is to start from links and forms that work and let YPY make them faster.
The patterns
| Example | What it shows | Demo | Extension needed |
|---|---|---|---|
| Click to edit | Swap a read-only block for a form, and back | yes | none |
| Bulk update | One form of checkboxes, one answer that updates the table and a message | yes | none |
| Click to load | A Load more button that adds rows and moves itself | yes | none |
| Delete row | Confirm, delete on the server, remove the row | yes | none |
| Edit row | A table row that becomes inputs and back | yes | none |
| Lazy loading | Load a slow part after the page, at load or when seen | yes | ypy-lazy, optional |
| Inline validation | Check a field on the server when the user leaves it | yes | ypy-validate, optional |
| Infinite scroll | The last row asks for the next page when it appears | yes | none |
| Active search | Search while typing, with a delay | yes | none |
| Progress bar | Follow a long job by asking for its progress | yes | ypy-poll, optional |
| Dependent selects | A second select that fills from the first | yes | none |
| Tabs | Load one panel at a time and mark the current tab | yes | none |
| Animations | Fade and slide content in and out with CSS classes | no | none |
| File upload | Send a file with a progress bar | no | ypy-upload, optional |
| Preserve file inputs | Keep the chosen file when a form comes back with errors | no | none |
| Reset user input | Clear a form after a successful submit | no | none |
| Confirm and prompt | Ask the user before a request, or for a typed answer | no | ypy-prompt, for the prompt |
| Dialogs with layers | Modal, drawer and popup content loaded from the server | no | ypy-layers |
| Keyboard shortcuts | Start a request from a key press | no | none |
| Drag and drop sort | Reorder a list by hand and save the order | no | ypy-sort |
| Updating other content | One response that changes several places | no | none |
| Session expired | Send the user to sign in when a request is refused | no | none |
| Live updates | The server pushes changes to the page | no | ypy-sse |
| Optimistic UI | Show the result before the server answers, and undo it on failure | no | ypy-optimistic |
| Polling | Ask again every few seconds, and stop when the server says so | no | ypy-poll, optional |
An extension marked optional improves a pattern that already works with the core alone.
Where next
- Docs: the long page that goes through every part in order.
- Reference: attributes, headers, events and settings in tables.
- Extensions: the optional scripts named in the table above.