WEBVTT

00:00.000 --> 00:20.000
We know start just in time.

00:20.000 --> 00:23.000
Hello, I am Erin.

00:23.000 --> 00:30.000
You can see here and this is my first time I'm giving a talk.

00:30.000 --> 00:38.000
So let's begin talking.

00:38.000 --> 00:42.000
Do you want to talk about Wyland composers?

00:42.000 --> 00:46.000
So here you can, I'm Erin.

00:46.000 --> 00:48.000
I work.

00:48.000 --> 00:51.000
It doesn't make you can see my work.

00:51.000 --> 00:54.000
Get up if you want to see stuff.

00:54.000 --> 00:58.000
There is source code related to this talk on there as well.

00:58.000 --> 01:05.000
If you want to stalk me the website where you can text me probably.

01:05.000 --> 01:07.000
So let's begin.

01:07.000 --> 01:09.000
I have to say this claimer.

01:09.000 --> 01:11.000
I will be talking about Wyland.

01:11.000 --> 01:15.000
I'm not paid by IBM or Red Hat to chill it.

01:15.000 --> 01:19.000
I also do not use any narrative AI.

01:19.000 --> 01:21.000
So you will see that.

01:21.000 --> 01:23.000
Graphic design is my passion.

01:23.000 --> 01:25.000
And no license.

01:25.000 --> 01:27.000
Let's see.

01:27.000 --> 01:29.000
Okay.

01:29.000 --> 01:35.000
Okay.

01:35.000 --> 01:41.000
Long time ago before probably I was even born.

01:41.000 --> 01:45.000
There was only X ever on the next.

01:45.000 --> 01:49.000
Even before X11 X3 86.

01:49.000 --> 01:51.000
And you had this.

01:51.000 --> 01:53.000
One big X11 server.

01:53.000 --> 01:55.000
You had to.

01:55.000 --> 01:59.000
You used OST one.

01:59.000 --> 02:01.000
More that.

02:01.000 --> 02:02.000
Take your shaman art application,

02:02.000 --> 02:05.000
communicate it and use it stay.

02:05.000 --> 02:09.000
Un Hugh.

02:09.000 --> 02:11.000
But what you from the file.

02:11.000 --> 02:13.000
Top team.

02:13.000 --> 02:15.000
15.

02:15.000 --> 02:23.000
And you were starting on the set.

02:23.000 --> 02:26.480
There were a lot of restructuring done.

02:26.480 --> 02:34.760
We have now in the kernel DRM responsible for rendering stuff.

02:34.760 --> 02:38.440
You have a major project implementing graphics APIs.

02:38.440 --> 02:42.920
Programs can use cameras for modes setting.

02:42.920 --> 02:49.560
So you have to have a kernel for events,

02:49.560 --> 02:51.880
excel and so to use that.

02:51.880 --> 02:54.680
But yeah, you still have the separate window manager

02:54.680 --> 02:56.320
compositor application thing running.

02:56.320 --> 02:59.800
We have the one big Excel 11 server, which

02:59.800 --> 03:02.520
is designed from the 80s.

03:02.520 --> 03:03.880
I've read.

03:03.880 --> 03:08.120
Does anyone know the handbook for Unix Hs?

03:08.120 --> 03:12.840
Yeah, even then, Excel was criticized.

03:12.840 --> 03:14.280
So nothing new.

03:14.280 --> 03:19.080
But then we got this island.

03:19.080 --> 03:24.600
And yeah, one compositor is not one well-in-compositor.

03:24.600 --> 03:26.600
Just the arrow between the well-in-compositor

03:26.600 --> 03:30.440
and application is the island.

03:30.440 --> 03:32.840
This is probably our normal desktop stack,

03:32.840 --> 03:36.440
is the desktop stack I run on this computer.

03:36.440 --> 03:41.080
But as we will see later, you don't have to run it in this way.

03:41.080 --> 03:43.720
So we eliminated all the separate components.

03:43.720 --> 03:47.160
There's the big x-server with the old Arcane APIs,

03:47.160 --> 03:51.880
and just you think this?

03:51.880 --> 03:59.560
So first of all, desktop step on embedded.

03:59.560 --> 04:03.720
Like I said before, I work a tourist.

04:03.720 --> 04:06.520
We do open source routers.

04:06.520 --> 04:09.720
And we have a new one.

04:09.720 --> 04:11.960
There is a display.

04:11.960 --> 04:12.840
There is a depart.

04:12.840 --> 04:15.000
You can use for navigation.

04:15.000 --> 04:16.040
It's just arrow keys.

04:16.040 --> 04:18.920
And by the way, the back button from the left,

04:18.920 --> 04:22.440
like if you look on the front is F1 key.

04:22.440 --> 04:25.720
And it runs a tourist OS, which is,

04:25.720 --> 04:27.080
this is then based on OpenWRT.

04:27.080 --> 04:30.680
And on OpenWRT, there are in-many things related

04:30.680 --> 04:33.720
to a GUI.

04:33.720 --> 04:37.560
Actually, they have a repository with GUI stuff.

04:37.560 --> 04:41.400
But both of the things are outdated or missing.

04:42.360 --> 04:44.840
I think the wild protocols are like six years old.

04:44.840 --> 04:47.800
I couldn't even run a terminal on it.

04:47.800 --> 04:51.240
And there is also no proper user thing.

04:51.240 --> 04:54.840
There is a lip you have zero, and you can look at the repo

04:54.840 --> 04:59.320
if you laugh conspiracy theories about system D.

04:59.320 --> 05:02.280
There is, like, under reach me, a nice way to explain,

05:02.280 --> 05:04.280
explaining that you def was created in this way.

05:04.280 --> 05:08.600
So it's hard for people to use and some vendor locking and stuff.

05:08.680 --> 05:11.320
It's kind of fun.

05:11.320 --> 05:16.760
So when I went to Saudi working at a tourist,

05:16.760 --> 05:19.160
it's quite recent.

05:19.160 --> 05:22.280
It under half a year ago.

05:22.280 --> 05:25.880
I go to task with working for the display control thing.

05:25.880 --> 05:28.680
And we have a graphical application.

05:28.680 --> 05:31.000
It's using the slint to rust.

05:31.000 --> 05:36.680
We fry, and it uses directly DRM for rendering.

05:36.760 --> 05:41.240
One thing, the back end is bugged, or at least was at a time.

05:41.240 --> 05:45.640
And it really, really ate all the CPU stickers.

05:45.640 --> 05:51.400
And also, we wanted to implement an easterack in a form of a little mini game.

05:51.400 --> 05:56.680
That was an issue, because implementing in the GUI application of slint,

05:56.680 --> 06:01.720
something which isn't made of the basic components is painful.

06:01.720 --> 06:04.760
Also, for conference in Proachlinux days,

06:04.760 --> 06:08.680
we wanted to demo a doom, because can it run doom.

06:08.680 --> 06:17.320
And all the things, and as we are friendly towards user customization,

06:17.320 --> 06:23.560
we wanted a nice way for users to actually run their own programs on the display.

06:23.560 --> 06:28.200
And doing that with DRM is painful.

06:28.200 --> 06:30.840
You have to use a GUI tool kit, which supports that thing.

06:30.840 --> 06:34.200
If you want to use that, an application switching is literal hell.

06:34.280 --> 06:37.880
So I was like, I will make a violent compositor.

06:40.440 --> 06:44.280
So the control program for the screen is called PicoCurs.

06:44.280 --> 06:48.120
So I named PicoCurs.

06:48.120 --> 06:50.920
It's just like over a thousand lines of rust.

06:50.920 --> 06:56.120
It uses the smithy library, and it's pretty lightweight.

06:56.120 --> 07:00.440
It currently supports running only one window, like one window,

07:00.440 --> 07:02.920
but it will just stack them on top of each other.

07:02.920 --> 07:06.280
You can easily switch them, which I would like to fix at some point.

07:07.880 --> 07:11.480
Currently, currently, we just run one program on it.

07:11.480 --> 07:14.040
It's an easter egg, but you can 41.

07:15.400 --> 07:19.880
And so I have to probably say that we make a gaming router.

07:24.760 --> 07:26.760
This is a pretty general purpose compositor still.

07:27.480 --> 07:33.640
So we can look at more domain specific use cases.

07:36.520 --> 07:37.400
Do you notice computer?

07:39.400 --> 07:43.160
Me and the friend we went to a store, like when I saw all stuff,

07:43.160 --> 07:45.720
and I saw this computer, it's really pretty.

07:45.720 --> 07:50.680
So I bought it home, installed a Camaro Linux on it.

07:50.680 --> 07:55.400
It supports a filter to be power PC, and unlike Debian, the support is actually working.

07:56.840 --> 08:00.280
The last time I tried Debian, installing network manager,

08:00.280 --> 08:04.040
I wanted to uninstall system D, and the carnal as well.

08:05.080 --> 08:05.880
It was kind of fun.

08:05.880 --> 08:11.480
And it runs, it has the ATA rage 128 Pro GPUs,

08:12.120 --> 08:13.240
ATP advanced graphic pot.

08:14.200 --> 08:18.200
And I found out that there is no really Debian driver in the carnal for it.

08:18.200 --> 08:19.720
I just have the frame buffer device.

08:21.000 --> 08:25.320
I could use the Debian driver for the open firmware frame buffer,

08:25.320 --> 08:28.040
but it wasn't doing well.

08:28.040 --> 08:32.440
So I was like, yeah, okay, I again use this midi library,

08:32.440 --> 08:34.200
and just write a compositor.

08:34.840 --> 08:39.160
And the nice thing about Wellen is very easy compositor-nesting.

08:39.160 --> 08:42.040
You just implement your compositor with a violin as a back end.

08:44.440 --> 08:48.840
So I wrote it, it's not complete yet.

08:48.840 --> 08:53.080
I had some issues with 32-bit atomics on the platform.

08:53.240 --> 08:57.400
But yeah, and I can run an optional inside it.

08:57.400 --> 08:59.560
Note that I want to run a good optional on that computer.

09:03.160 --> 09:06.120
So, for example, there is a WAPAP.

09:08.120 --> 09:11.320
Anyone here uses Excel the forwarding over SSH.

09:13.160 --> 09:17.240
Yeah, the fun thing is, many people say, oh, we don't have a violin.

09:17.240 --> 09:18.680
We can't do Excel the forwarding.

09:18.760 --> 09:23.880
Like, we would have to copy the entire frame buffer to a computer.

09:23.880 --> 09:27.560
Okay, you do that mostly with Excel then as well,

09:27.560 --> 09:32.360
because maybe accept X-term and all the OG X software.

09:33.080 --> 09:37.160
As far as I know, all the GUI frameworks we nowadays use,

09:37.160 --> 09:40.600
still just take a frame buffer, and render their things themselves.

09:40.600 --> 09:42.200
So you have to do it anyways.

09:42.200 --> 09:45.640
So there is a WAPAPAP which forwards violin messages,

09:46.600 --> 09:47.960
series of buffers.

09:47.960 --> 09:53.080
We use it with development because I have the router lying on the desk.

09:53.080 --> 09:55.960
I wrote a really cursed script for a cross-compiling it.

09:57.960 --> 10:02.440
And then it just runs over SSH, and I have on my screen can interact with it.

10:03.560 --> 10:08.280
Sadly, as I don't think I managed to get FFM,

10:08.280 --> 10:11.640
they're running on it well, so it's a really slow.

10:13.480 --> 10:15.080
Okay, so next thing.

10:15.880 --> 10:19.720
When I first started programming,

10:19.720 --> 10:22.760
I went to a programming course,

10:22.760 --> 10:25.080
and we were using bold and delf-y.

10:25.080 --> 10:28.280
And it had a nice thing for a GUI design.

10:28.280 --> 10:32.040
When I then went to using things at Linux,

10:32.040 --> 10:34.600
for a GDK2 and GDK3,

10:34.600 --> 10:37.720
there were graphic designers, you can just click here, stuff in.

10:37.720 --> 10:43.080
But when GDK4 came, it was not very well done.

10:43.720 --> 10:48.360
And we had this project called Kambalash.

10:48.360 --> 10:49.640
I don't know how to read it, sorry.

10:51.080 --> 10:55.960
And I was kind of surprised that it renders the UI file.

10:55.960 --> 10:57.160
You made it.

10:57.160 --> 11:01.240
But just running a one-composator as a GDK widget, using a casilda.

11:02.680 --> 11:06.280
So you can embed violin in your programming, say, if you want.

11:06.440 --> 11:12.440
And so, laughing from this category,

11:12.440 --> 11:19.240
I recently read on foreign eggs that I don't know who proposed that

11:19.240 --> 11:22.440
to have an option to switch kernel virtual terminal,

11:22.440 --> 11:24.040
like on runtime.

11:24.040 --> 11:27.240
That's fedora in the next release was to use KMS,

11:27.240 --> 11:32.120
a con, instead of BT102 emulated by the Linux hurdle.

11:32.520 --> 11:38.680
Well, there were plans for that, like, I don't know,

11:38.680 --> 11:41.960
read these milling 13 years ago.

11:41.960 --> 11:43.720
And there were many proposals how to do it.

11:43.720 --> 11:49.880
And one of them was running a quantum compositor as the root thing.

11:49.880 --> 11:53.160
If you study the violin docs, there are actually some entries

11:53.160 --> 11:56.520
about certain called assistant compositor.

11:56.520 --> 11:59.880
It was funny I've never found anything else about it,

11:59.880 --> 12:04.680
except on the valent, I don't know, specification page,

12:04.680 --> 12:10.040
where you could then deprecate the VITs entirely,

12:10.040 --> 12:14.440
and just use the violin compositor if you just want to have a console.

12:14.440 --> 12:19.880
You can just add a no-food, like we do on the OmniaNG.

12:19.880 --> 12:25.240
If you run from the menu application, which requires a console,

12:25.240 --> 12:28.520
it's setting for it, it's supposed to food.

12:28.520 --> 12:31.560
I'm old, well, that's pretend.

12:31.560 --> 12:35.560
And you can add all you have the valent compositor

12:35.560 --> 12:39.800
nesting, and you could run your normal session compositor inside it.

12:39.800 --> 12:43.320
I wouldn't recommend it nowadays, because both compositors

12:43.320 --> 12:51.560
are really designed to run on your student directly.

12:51.640 --> 12:56.040
And the valent backends are, most of our development.

12:56.040 --> 12:59.640
And also, it would require having a violin compositor

12:59.640 --> 13:03.080
for the entire system, which just a lot of stuff.

13:03.080 --> 13:11.960
So the idea really didn't get well, but yeah, we can see an example of that.

13:11.960 --> 13:17.400
So no, I just have to wait to just slide a little bit,

13:17.400 --> 13:19.240
press well.

13:19.240 --> 13:22.760
Again, we can look at how we can implement one.

13:22.760 --> 13:27.560
Anyone here tried to make a violin compositor?

13:27.560 --> 13:31.960
Yeah, so yeah, several options.

13:31.960 --> 13:37.480
If we do not want to make it completely ourselves,

13:37.480 --> 13:42.920
actually, I know a person who went to make some valent library, which

13:42.920 --> 13:44.760
I don't know pre-allocated some buffers.

13:44.760 --> 13:51.960
And then except for that needed, like for the new client and stuff,

13:51.960 --> 13:53.960
I tried to minimize that.

13:53.960 --> 13:55.320
I don't know how the project went.

13:55.320 --> 13:58.920
But yeah, I used Smithy, written in Rust,

13:58.920 --> 14:04.120
it used for nearly cosmic or RP comp.

14:04.120 --> 14:06.200
It's pretty easy to use.

14:06.200 --> 14:11.960
So you can create a compositor object and just implement traits,

14:11.960 --> 14:18.440
or to which implement the protocol and kind of works.

14:18.440 --> 14:23.640
Then you have probably one of the, all the ones,

14:23.640 --> 14:26.920
WL routes, originally made for a sway.

14:26.920 --> 14:31.880
This is in C, and it's also used in the Casilla, in the widget,

14:31.880 --> 14:34.040
or a fock.

14:34.040 --> 14:37.600
Anyone here uses osmarched osmarched osmarched osmarched osmarched

14:37.680 --> 14:41.120
generally links, just with desktop Linux and phone,

14:41.120 --> 14:44.160
just compositor use in a flash.

14:44.160 --> 14:50.560
Or one of the OG ones, the Western reference implementation for that.

14:50.560 --> 14:55.520
It's, I think also, it's nice if you want to do some more.

14:55.520 --> 14:58.000
Like you want a compositor, which is kind of done,

14:58.000 --> 15:01.120
and you just want to have some your own logic on top of that.

15:01.120 --> 15:04.880
So I had that it's also used in embedded stuff.

15:05.840 --> 15:10.640
Remember the canonical thing that kind of like it was like,

15:10.640 --> 15:13.840
oh yeah, let's remember how would it use a space?

15:13.840 --> 15:17.040
We will make our own graphics on protocol.

15:17.040 --> 15:20.320
We will make our own desktop environment, which

15:20.320 --> 15:26.560
didn't really go well, they made this by protocol called mere.

15:26.560 --> 15:29.360
I think I tried it once.

15:29.360 --> 15:34.480
Really, that was useful, but they turned it into violent compositor now.

15:34.560 --> 15:38.080
Use in miracle and mirror way, and for my head,

15:38.080 --> 15:40.240
it's more like a complete product.

15:40.240 --> 15:42.960
You just implement some policies.

15:42.960 --> 15:46.560
So probably a developed experience should be more close to

15:46.560 --> 15:48.800
making specific window managers for violent,

15:48.800 --> 15:52.000
than just making their own compositor from the scratch.

15:55.760 --> 16:00.000
And for what to say about the core, about a violent protocol

16:00.000 --> 16:03.840
on the embedded, what's nice about that is,

16:03.920 --> 16:08.560
we have just these protocols, which are the Correlan.

16:08.560 --> 16:11.680
That's what makes the base of violent.

16:11.680 --> 16:14.080
It's not really much.

16:15.360 --> 16:19.680
Nesting compositor, I did it was like 649 of rust.

16:21.920 --> 16:25.440
You don't have to when you make embedded things to use it directly.

16:25.440 --> 16:27.520
You can just shove a little violent compositor,

16:27.520 --> 16:28.800
which is just one thing you need.

16:29.680 --> 16:32.080
You don't need to run entire excel, have on it.

16:33.040 --> 16:36.240
And I don't think there is like packaging for OpenWR

16:36.240 --> 16:39.920
to have X11, and I am not going to make it.

16:41.760 --> 16:44.480
For sure, this was pretty much.

16:45.440 --> 16:48.080
Easier thing, but if you want to run something on it,

16:48.080 --> 16:49.840
most applications just won't work.

16:49.840 --> 16:51.840
Like for terminal requires some extensions.

16:54.560 --> 16:59.040
So, we also have some extra extensions,

16:59.040 --> 17:04.240
like the Excel, which implements the notion of window wing and stuff.

17:05.040 --> 17:07.040
We've deprecated a WL shell one.

17:08.480 --> 17:10.160
Then you have extensions like session lock.

17:12.880 --> 17:18.960
Everom managed to use some lock external lock program for a violent session

17:19.760 --> 17:26.000
when it crashes, and some compositors just like show dark red.

17:26.160 --> 17:29.760
Something, it's implemented way, then when you lock a session,

17:29.760 --> 17:32.560
the one compositor itself should be locked.

17:32.560 --> 17:36.800
So, when you lock crashes, it should not unlock your session.

17:36.800 --> 17:38.160
But it's very unfortunate.

17:40.560 --> 17:43.200
You also have extensions like Linux, the MABF,

17:43.200 --> 17:48.800
for making a buffer for memory access with your, for example.

17:48.800 --> 17:52.320
Graphics devices, and a controversial,

17:52.320 --> 17:56.320
ex-digit decoration manager, which doesn't implement,

17:56.880 --> 17:59.920
I think it's one of the few who do not implement it.

18:01.920 --> 18:04.960
I mean, I had the code basis with Cursed for that,

18:05.680 --> 18:08.320
or compositor specifically like Lair Shell,

18:10.240 --> 18:15.360
which loves you to make things like panels, background,

18:15.360 --> 18:16.560
using external programs.

18:18.400 --> 18:22.160
We implement in a PCom per decoration manager,

18:22.240 --> 18:24.880
but what it all does is a telling the program.

18:24.880 --> 18:26.960
Here we are, I will draw several side decorations,

18:26.960 --> 18:28.960
and just not proceeding not doing it.

18:28.960 --> 18:33.200
Because you probably do not want to waste space

18:33.200 --> 18:36.320
on the little screen decoration of the window.

18:36.320 --> 18:42.320
Okay, so here you can see you can pick any back and view.

18:42.320 --> 18:45.760
I actually want to put out, because, again, it's just a protocol.

18:46.960 --> 18:48.320
You have to do some presenting, like,

18:48.320 --> 18:51.120
allocate in buffers, we just use, I think,

18:51.120 --> 18:52.880
at least in the library called Dumbuffers,

18:52.880 --> 18:55.120
because we do not have a GPU on the router.

18:56.400 --> 18:59.360
You can do rendering, using, yeah, again, anything,

19:00.560 --> 19:02.720
maybe someone could do direct access, that will be funny.

19:03.920 --> 19:08.720
We use a pixelan, or just to solve to renderization,

19:09.680 --> 19:13.200
input management, and an ocean of seed.

19:13.840 --> 19:17.360
When you have, like, some keyboard to display at the devices,

19:17.440 --> 19:18.640
which was actually one of the problems

19:18.640 --> 19:21.440
of the system composers, because, while on,

19:21.440 --> 19:24.240
can work with, like, screen keyboard mouse,

19:24.240 --> 19:26.400
but, what about audio device?

19:27.120 --> 19:30.960
That's managed in, such a seed management thing,

19:30.960 --> 19:34.080
like log in D, but, it's not.

19:34.800 --> 19:38.480
So, I hope I wasn't too quick, but,

19:38.480 --> 19:41.040
who's 25 minutes, so now we have time for questions.

19:47.360 --> 19:49.360
Thank you.

20:18.000 --> 20:20.000
Oh, you have to answer.

20:20.000 --> 20:22.000
Yeah, of course.

20:24.000 --> 20:26.000
Your question?

20:28.000 --> 20:30.000
Yes, can you hear me?

20:30.000 --> 20:32.000
Yes, I can.

20:32.000 --> 20:37.440
One question I have is, we have a lacking sufficient replacement

20:37.440 --> 20:41.440
for XRDP, which implements something, like,

20:41.440 --> 20:44.080
multi-seed remote terminal server.

20:44.640 --> 20:47.280
Is a compositor thinkable that could implement that?

20:47.280 --> 20:50.480
I didn't hear you, how can you please be a little louder, I?

20:50.480 --> 20:55.280
Um, multi-seed remote terminal server, running on a headless machine,

20:55.280 --> 20:58.880
what kind of compositor would be thinkable to implement this?

21:00.880 --> 21:02.880
Um, multi-seed things.

21:02.880 --> 21:06.400
I mean, I wanted to do some fun with multi-seed,

21:06.400 --> 21:09.520
writing my own compositor to implement multi-seed stuff.

21:10.160 --> 21:13.280
Because, like, one of the annoying things you can do on Windows,

21:13.280 --> 21:16.880
not annoying nice things, you can do in Windows, but it's annoying,

21:16.880 --> 21:19.120
it doesn't, one Linux is, is a session hand-off,

21:19.120 --> 21:21.760
like, you can just move the session to RDP.

21:21.760 --> 21:24.160
Yeah, so, um, yeah, uh, I don't think there are any things for that,

21:24.160 --> 21:26.160
at least right now.

21:26.160 --> 21:29.680
The most mature support is for, um,

21:29.680 --> 21:34.400
I don't think there are any things for that, at least right now.

21:34.400 --> 21:37.600
The most mature support is for,

21:37.680 --> 21:41.040
the most mature support is for RDP stuff is GNOME,

21:41.040 --> 21:45.440
which you can actually get a login and start a new session,

21:45.440 --> 21:46.880
but you can just not do one session.

21:46.880 --> 21:49.840
So, if you want to log in as your user, you have to kill it.

21:51.360 --> 21:56.480
That's, uh, not a nice one, and, uh, I hope in the future we actually get some support.

21:56.480 --> 21:59.280
Is one of the things the system level compositor would solve for a nice?

22:02.560 --> 22:04.480
Okay, any more questions?

22:05.120 --> 22:06.640
Yeah.

22:07.840 --> 22:09.520
Okay, right before.

22:11.520 --> 22:14.480
You mentioned small devices, right?

22:14.480 --> 22:16.400
Like, like, those emited routers.

22:17.760 --> 22:23.440
What would you recommend for, like, Raspberry Pi zero class of device,

22:23.440 --> 22:26.720
with some, uh, SPI small display?

22:28.080 --> 22:32.800
And it should be like single, single screen application, single window application,

22:32.880 --> 22:33.920
like on a small screen.

22:33.920 --> 22:35.440
That would start automatically.

22:36.160 --> 22:37.440
I don't need any login.

22:37.440 --> 22:38.880
I don't need to authenticate the user.

22:38.880 --> 22:44.560
I just need to basically start a small device and display some application,

22:44.560 --> 22:45.920
and take input from the user.

22:46.960 --> 22:48.960
What kind of setup would you recommend?

22:49.680 --> 22:51.760
Set up in terms of, uh,

22:54.400 --> 22:58.480
in way, well, and basically, how to set, how to build this application?

22:59.040 --> 23:06.640
Well, what we do, at least on our routers, you can, by the way, look at the demo, we have a stand here.

23:08.080 --> 23:09.040
You can play doing with it.

23:10.080 --> 23:12.000
Well, we just run a system.

23:12.000 --> 23:13.040
There is an inscript.

23:13.040 --> 23:14.160
It runs the compositor.

23:15.760 --> 23:17.360
Well, which libraries?

23:17.360 --> 23:20.880
Because I, I checked basically what is available, and it's,

23:20.880 --> 23:25.520
and it also is that, like, a dozen of different names, which are completely not telling.

23:26.480 --> 23:28.240
Well, depends.

23:28.240 --> 23:30.320
So we don't look our own one called, uh, peak comp.

23:30.320 --> 23:31.040
It's open source.

23:31.040 --> 23:31.840
You can use it.

23:31.840 --> 23:33.120
It should be fine.

23:33.120 --> 23:38.320
There are also things like cage, which also implement similar things for

23:39.440 --> 23:41.440
kiosk, like deployments.

23:42.240 --> 23:43.120
That could also work.

23:43.840 --> 23:47.600
But, uh, could we probably sit somewhere together and actually

23:47.600 --> 23:49.200
exchange some contacts?

23:49.200 --> 23:51.600
Because it's difficult to talk.

23:51.600 --> 23:54.160
Any more questions or, uh,

23:55.520 --> 23:57.520
uh,