MMOframework
Why AI Playground Libraries Documentation Search Agency
FR EN
MMOframework · made by Hydra Agency Documentation · MCP
The search an agent runs

Search the documentation

Every document of every library, and their agent skills, searched by the MCP server's own search_documentation: a match holds every word, on one line or on 3 lines in a row.

11 matches, the best first

  1. php/js/JHSParser.md mmo.doc · line 130 method MMO\doc\js\JHSParser::readSlots
  2. php/js/JHSParser.md mmo.doc · line 156 method MMO\doc\js\JHSParser::taggedDescriptions — Read a `@tag name - description` family into a `name => description` map -- the shape `@attr`, `@css` and `@slot` share (@see \MMO\client\JHSCompiler::extractJSDoc, which reads the very same tags).
  3. php/js/JHSParser.md mmo.doc · line 56 | ƒ | 🔐 | [`readSlots($source)`](#jhsparser-readslots) | |
  4. php/js/JHSParser.md mmo.doc · line 58 | ƒ | 🔐 | [`taggedDescriptions($comment, $tag)`](#jhsparser-taggeddescriptions) | Read a `@tag name - description` family into a `name => description` map -- the shape `@attr`, `@css` and `@slot` share ([`JHSCompiler::extractJSDoc`](../../../../client/docs/php/JHSCompiler.md#jhscompiler-extractjsdoc), which reads the very same tags). |
  5. php/js/JHSParser.md mmo.doc · line 159 `@slot` share ([`JHSCompiler::extractJSDoc`](../../../../client/docs/php/JHSCompiler.md#jhscompiler-extractjsdoc), which reads the very same tags).
  6. js/layouts/mmo-boarding.md mmo.client · line 24 | **Source** | [`../../../src/customElements/layouts/mmo-boarding.jhs:1`](../../../src/customElements/layouts/mmo-boarding.jhs) | Items are slotted children distributed into columns via their `data-column-id` attribute.
  7. js/layouts/mmo-tabs.md mmo.client · line 24 | **Source** | [`../../../src/customElements/layouts/mmo-tabs.jhs:1`](../../../src/customElements/layouts/mmo-tabs.jhs) | The tabs and the panes are both slotted: a tab carries `target-id`, the pane it shows carries that
  8. js/tools/mmo-specimen.md mmo.client · line 24 | **Source** | [`../../../src/customElements/tools/mmo-specimen.jhs:1`](../../../src/customElements/tools/mmo-specimen.jhs) | The example is the element's own light dom, shown through a `<slot>` -- so it is painted by the
  9. js/layouts/mmo-app.md mmo.client · line 880 ```jhs MMO.app.showNotification('success', MMO.core.dom.createElement('span', {slot: 'title'}, 'Saved'), file.name)
  10. js/tools/mmo-element-doc.md mmo.client · line 26 Every element compiled by `MMO\client\JHSCompiler` carries its own documentation: `documentation()` returns what its jsdoc declared (`@attr`, `@css`, `@slot`, methods, getters) and its shadow root
  11. mmo-client/references/examples.md mmo.client · agent skill · line 101 **Notes:** `<slot></slot>` inside `#text` lets callers write `<mmo-progress value="0.5">Uploading…</mmo-progress>` and have the light-DOM text land there. `<div id="content">`/`<div id="percent">` are plain static markup (no bindings needed — the setter drives them imperatively via `queryShadow`), which is a legitimate pattern for anything that needs more control than declarative `{path}` binding gives you. The `<style>` is plain Simple CSS with no `lang`: `@use lib::surface($radius.sm)` gives `#content` the same ground, hairline and radius as every card of the design system, and every value is a token (`$space.xs`, `$color.brand`, `$z.base`), so the bar follows the dark theme and a client's reskin with no code of its own. ## 2. Element with `<for>` + `<if>/<else>` — `src/customElements/inputs/mmo-radio.jhs` (excerpt)

Connect your agent