From 333a8e9c84f31d1b8765441c33dc5cac67d46868 Mon Sep 17 00:00:00 2001 From: aleteoryx Date: Mon, 7 Oct 2024 17:45:10 -0400 Subject: [PATCH] fallback handling --- proto/tabbde.xml | 80 ++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 78 insertions(+), 2 deletions(-) diff --git a/proto/tabbde.xml b/proto/tabbde.xml index 3565a43..05c4537 100644 --- a/proto/tabbde.xml +++ b/proto/tabbde.xml @@ -7,10 +7,43 @@ A better way to use the computer. - + + + 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. + + + + + + This is what any renderer uses to advertise to the WM. Slugs + must be globally unique, and attempting to reregister one + should error. + + + + + + + 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. + + + + + 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. + + - + @@ -18,7 +51,50 @@ + + + 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. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- 2.45.2