~aleteoryx/TabbDE

ref: 57bce9111f70b9b479283c66f61037bc04c49b1e TabbDE/proto/tabbde.xml -rw-r--r-- 4.8 KiB
57bce911 — aleteoryx scheme requests 2 months ago 
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134

<?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="A better way to use the computer">
    A better way to use the computer.</description>

  <interface name="tde_wm_base" version="1">
    <request name="register_scheme">
      <description summary="Used by all scheme handlers.">
        This is what a program wishing to handle a specific scheme
        uses to inform the WM that it will do so. Only one of these may
        exist for any scheme, in all clients. Creating a new one
        for a given scheme invalidates all others.</description>
      <arg name="id" type="new_id" interface="tde_scheme" />
      <arg name="scheme" type="string" />
    </request>
    <request name="register_renderer">
      <description summary="Used by all renderers.">
        This is what any renderer uses to advertise to the WM. Slugs
        must be globally unique, and attempting to reregister one
        should error.</description>
      <arg name="id" type="new_id" interface="tde_renderer" />
      <arg name="slug" type="string" />
    </request>

    <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="tde_fallback" />
    </request>
    <request name="register_system">
      <description summary="May contain settings, debug info, etc.">
        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
        system:// handler, and the WM should expect this to happen at
        early boot.</description>
      <arg name="id" type="new_id" interface="tde_system" />
    </request>
  </interface>

  <interface name="tde_scheme" version="1">
    <event name="read_request">
      <arg name="response" type="new_id" interface="tde_response" />
      <arg name="url" type="string" />
      <arg name="metadata" type="string" />
    </event>
    <event name="write_request">
      <arg name="response" type="new_id" interface="tde_response" />
      <arg name="url" type="string" />
      <arg name="metadata" type="string" />
      <arg name="data" type="fd" />
    </event>

    <event name="superceded" type="destructor" />
  </interface>

  <interface name="tde_renderer" version="1">
    
  </interface>

  <interface name="tde_response" version="1">
    <request name="surface" type="destructor">
      <arg name="page" type="new_id" interface="tde_page" />
      <arg name="surface" type="object" interface="wl_surface" />
    </request>
    <request name="data" type="destructor">
      <arg name="page" type="new_id" interface="tde_page" />
      <arg name="mime_type" type="string" />
      <arg name="metadata" type="string" />
      <arg name="data" type="fd" />
    </request>
    <request name="error" type="destructor">
      <arg name="page" type="new_id" interface="tde_page" />
      <arg name="title" type="string" />
      <arg name="message" type="string" />
    </request>
  </interface>

  <interface name="tde_page" version="1">
    
  </interface>

  <interface name="tde_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>

  <interface name="tde_system" version="1">
    
  </interface>

  <interface name="tde_surface" version="1">
    
  </interface>

  <interface name="tde_window" version="1">
    
  </interface>

  <interface name="tde_tab" version="1">
    
  </interface>
</protocol>