Luna/gui/wind/Client.h

#pragma once
#include "IPC.h"
#include "Window.h"
#include <os/IPC.h>

constexpr i16 HAS_NOT_YET_PLEDGED = -1;
constexpr i16 EMPTY_PLEDGE = 0;

struct Client
{
    OwnedPtr<os::IPC::ClientConnection> conn;
    Vector<Window*> windows;
    const bool privileged { false };
    bool should_be_disconnected { false };
    i16 pledges = 0;

    bool update_pledges(i16 pledges);
    bool check_pledge(i16 pledge);

    Client(OwnedPtr<os::IPC::ClientConnection>&& client, i16 pledges);
};
wind: Handle CreateWindow IPC messages 2023-08-14 18:15:29 +02:00			`#pragma once`
libos+wind+apps: Make IPC code object-oriented and add functionality for properly receiving messages This functionality previously had to be repeated across all server programs using the IPC API. 2024-02-03 19:16:39 +01:00			`#include "IPC.h"`
wind: Handle CreateWindow IPC messages 2023-08-14 18:15:29 +02:00			`#include "Window.h"`
libos+wind+apps: Make IPC code object-oriented and add functionality for properly receiving messages This functionality previously had to be repeated across all server programs using the IPC API. 2024-02-03 19:16:39 +01:00			`#include <os/IPC.h>`
wind: Handle CreateWindow IPC messages 2023-08-14 18:15:29 +02:00
wind+libui: Add "pledge" functionality to access special features for system programs This segments privileges more, making it so that any app connecting to wsys.sock can't just always access every single advanced feature in wind if they don't need to. Of course, apps have to restrict themselves, which is why only privileged apps have access to this feature in the first place. Normal apps' pledges are all empty and can't be changed. An example: taskbar uses the "ExtendedLayers" pledge to move its window to the background, but relinquishes it afterwards, and doesn't need any other advanced feature for now. If a pledge-capable app tries to use a pledge-protected function without having pledged anything, it can't. Pledges are mandatory if you want to access certain functionality, unlike the kernel's pledges which make every syscall available if you don't use pledge(). 2024-12-13 23:47:53 +01:00			`constexpr i16 HAS_NOT_YET_PLEDGED = -1;`
			`constexpr i16 EMPTY_PLEDGE = 0;`

wind: Handle CreateWindow IPC messages 2023-08-14 18:15:29 +02:00			`struct Client`
			`{`
libos+wind+apps: Make IPC code object-oriented and add functionality for properly receiving messages This functionality previously had to be repeated across all server programs using the IPC API. 2024-02-03 19:16:39 +01:00			`OwnedPtr<os::IPC::ClientConnection> conn;`
wind: Handle CreateWindow IPC messages 2023-08-14 18:15:29 +02:00			`Vector<Window*> windows;`
wind: Add a second unix socket for privileged clients which need to be in a different group 2024-02-01 21:57:40 +01:00			`const bool privileged { false };`
wind+libui+taskbar: Add a request for setting special window attributes This lets the taskbar window stay unfocused even when it's clicked. 2024-02-04 13:35:50 +01:00			`bool should_be_disconnected { false };`
wind+libui: Add "pledge" functionality to access special features for system programs This segments privileges more, making it so that any app connecting to wsys.sock can't just always access every single advanced feature in wind if they don't need to. Of course, apps have to restrict themselves, which is why only privileged apps have access to this feature in the first place. Normal apps' pledges are all empty and can't be changed. An example: taskbar uses the "ExtendedLayers" pledge to move its window to the background, but relinquishes it afterwards, and doesn't need any other advanced feature for now. If a pledge-capable app tries to use a pledge-protected function without having pledged anything, it can't. Pledges are mandatory if you want to access certain functionality, unlike the kernel's pledges which make every syscall available if you don't use pledge(). 2024-12-13 23:47:53 +01:00			`i16 pledges = 0;`

			`bool update_pledges(i16 pledges);`
			`bool check_pledge(i16 pledge);`
wind: Fix client references being out-of-date in windows when disconnecting other clients Classic "keeping a pointer to an element inside a vector after the vector is updated" bug, ah yes. 2023-08-16 20:02:54 +02:00
wind+libui: Add "pledge" functionality to access special features for system programs This segments privileges more, making it so that any app connecting to wsys.sock can't just always access every single advanced feature in wind if they don't need to. Of course, apps have to restrict themselves, which is why only privileged apps have access to this feature in the first place. Normal apps' pledges are all empty and can't be changed. An example: taskbar uses the "ExtendedLayers" pledge to move its window to the background, but relinquishes it afterwards, and doesn't need any other advanced feature for now. If a pledge-capable app tries to use a pledge-protected function without having pledged anything, it can't. Pledges are mandatory if you want to access certain functionality, unlike the kernel's pledges which make every syscall available if you don't use pledge(). 2024-12-13 23:47:53 +01:00			`Client(OwnedPtr<os::IPC::ClientConnection>&& client, i16 pledges);`
wind: Handle CreateWindow IPC messages 2023-08-14 18:15:29 +02:00			`};`