<?xml version="1.0" encoding="UTF-8"?>
<protocol name="tabbde">
  <copyright>This file is in the Public Domain, and the author
             waives all legal rights to it.</copyright>

  <description summary="TabbDE core">
    This protocol contains features core to the way the tabbed desktop
    environment (TabbDE) functions.</description>

  <interface name="urish_wm_base" version="1">
    <request name="register_fallback">
      <description summary="Used to handle unknown schemes and MIMEs">
        This shouldn't be used by any applications, it's a core part of
        the finished DE. Only one application may register itself as a
        fallback handler, and the WM should expect this to happen at
        early boot.</description>
      <arg name="id" type="new_id" interface="tabbde_fallback" />
    </request>
  </interface>

  <interface name="urish_fallback" version="1">
    <description summary="Internal method for fixing unknown types.">
      The fallback interface exists so that the DE can ask the user for
      what to do when encountering an unknown scheme or MIME type. Each
      event corresponds to some missing mapping. The fallback handler
      should prompt the user for input or otherwise find a handler for
      the given mapping, update the config files, and then send back a
      resolve event. If, for whatever reason, this is impossible, the
      fallback handler should send back a reject event.</description>

    <event name="scheme">
      <arg name="serial" type="uint" />
      <arg name="scheme" type="string" />
    </event>
    <event name="renderer">
      <arg name="serial" type="uint" />
      <arg name="slug" type="string" />
    </event>
    <event name="mime_mapping">
      <arg name="serial" type="uint" />
      <arg name="mime" type="string" />
    </event>

    <request name="resolve">
      <arg name="serial" type="uint" />
    </request>
    <request name="reject">
      <arg name="serial" type="uint" />
    </request>
  </interface>
</protocol>