 So, first question is about running Plasma Mobile Shell on your system. So, I see first question from Lo in the chat. The question is do I need to be using the Valiant Plasma Test Obsession to run Plasma Mobile Shell? No. So, no, you don't need to run Valiant Test Obsession. In fact, right now my demo will show it running inside X11 session, so no that's not necessary. So running Plasma Mobile Shell on your system is useful when you want to work on cell design or you want to work on various shell interaction patterns or application launchers or something, things like, or various bits like that. There are multiple ways to actually run Plasma Mobile on your desktop, so one thing you can do is use existing packages on your distribution. Another method is using KDE Source Build and build the packages on your system and then build the packages in your system in the prefix and then use them to run a Plasma Mobile Shell. Also, you can use the KDE Union-based ISO as well as PostMarket OS M1 image. There are various resources I have linked in this presentation. So the first is developer guide of the Plasma Mobile documentation which shows the two different methods of running KDE Union-based ISOs and also running PostMarket OS-based FEMO image. They are nicely documented in the documentation. So I won't be covering those here but still if you have any questions feel free to reach out in Plasma Mobile Matrix Room. So first I will be demoing the method of using KDE Source Build. The whole process of setting up KDE Source Build is quite long to be covered in one single session. However the Wiki page does show it, the Wiki page linked here shows the whole process. I will be showing my configuration and how it is configured on my system. So I have this KDE Source Build RCA file in my home directory. I have this KDE Tier set to OPKD, Qtier set to also OPKD. If you are using custom Qtier, you may want to set it to something where you have installed your Qt5. So you can set it to OPKD5 but I also have my Qt5 in OPKD so I have set it to this. Source directory is where you want to have all your source directories. So in my case it is a KDE Source source where I have all the repositories which are all the KDE repositories clone. Build directory is where your builds are and log directory is where you can find various logs like you can check various logs like you can check the git clone load, git installation log, build log and various operations log. So there is also this option which I use for my convenience is Ignore KDE structure. The reason I am using this is this allows me to have all the repositories in single directory which is like KDE source, KDE source and slash source. Instead of everything being according to KDE's wrapper structure which is actually not flat, I want to have proper control over how which dependencies are paired and which dependencies are not paired. So I do include dependencies false, this options so this options which are like include dependencies you can turn on if you want to let KDE source build handle all of the dependencies but since I have some dependencies installed from system packages and some dependencies build manually myself I set it to false. I have set it up to use ninja instead of make and there are CMake options which I set and make options and prefix then you can also include some configuration files to include a module so I install frameworks and got my box please. I can also set some specific CMake options for some specific repositories like for my network management I set deep build mobiles to true. Once this is false setup generally what you do is basically run KDE source build so once you run KDE source build like this it will build everything and install it to your selected locations for example in my case it's off KDE that everything is installed. I will stop this process here because this process can take long with about 135 packages so for running Plasma Mobile on your system there are two essential packages which are most important which is Plasma Nano and Plasma phone components these two packages so Plasma Nano is the basically minimal shell package based on which Plasma Mobile shell is I just to make sure that everything is in order I have run KDE source build with two argumentals like Plasma Nano and Plasma phone components and it has compiled them and installed it so the next thing is you want to run these things so for running this in your system there are some important environment variables which are Plasma underscore default shell which allows me to switch to phone shell by default that is Qtweap controls mobile is equal to true or Qtweap controls mobile is equal to one Qtweap controls underscore style is equal to Plasma and Qt underscore valent disable window decoration one and Plasma platform so Plasma platform environment variable is used for shell to shell and setting applications and various other application to see on which platform it is running there are some is supported here like desktop tablet it is here and also this this is not exclusively so you can even say Plasma platform is equal to toaster and various it's like widget explorer put filter widgets which are which can be done on let's say toaster so here we want to run plus want to filter everything which is in phone and handle devices so we export it to phone call on handle so once this environment variables are installed there is one more thing so recently Plasma workspace started to install started to allow you to install this configuration files which you which you can install in for example in your prefix and using those you can start it from STDM start lessons from STDM one of the things which the script installs is this convenience script which is called Plasma-Tel prefix it sets up some environment variables which are which are useful for running running the various programs installed inside the prefix so what I am going to do is in the terminal where I had exported the Plasma mobile related environment variables I'm going to be doing sourcing this script so it sets up those environment variables properly like you can see here it sets up up to be pin as the path now I'm going to run this command which is tbush transition queen valent I will specify some height and width so that it's a more like mobile instead of desktop actually let me remove these options for for this one so you can see how it looks so we have this queen valent x valent and then we have execute session which allows me to with basically kills the x queen valent when Plasma shell exits this helps me for easier debugging and cleaning up so I'm going to run this one and here you can see that it starts the Plasma mobile shell you can start various applications like calendary and test it out now let me add the height and width arguments so you can also see it here so with height and width argument you can see that it is now it is now looking just as the mobile and you can essentially use it as you want to as you would be using your mobile shell you can close windows and so in general this is very simple so another options which I wanted to cover was using existing packages on your distribution so there are some distributions currently I know that there is a manjaro and there is a terineon table as well as alpine Linux which packages the Plasma mobile shell on Plasma mobile shell so we will be using those packages in a similar method to run the mobile shell so okay so I have this terineon table unstable virtual machine here and I'm running it inside using KVM KVM allows me to choose the hardware acceleration so it is actually usable for testing valent based session which is requirement for running Plasma mobile so what I will be doing is I will basically install Plasma phone okay let me maximize this it's actually so installing the Plasma phone components and this will install all the dependences which are required for Plasma mobile there is one more package which I I don't really install on my own desktop but since this is virtual machine I will install it anyway so Plasma phone set things install some some mobile specific options which mobile specific options and configuration like there is this twin RC which disables the window decorations and sets the window to maximize by default also disables some some effect effects which are not optimal for mobile devices and will also disable the left and right it swipe which is actually which you can which is actually annoying on the mobile devices so once I have installed those three pack those two packages which are Plasma phone components and Plasma phone settings what I will do is I can do this in a new way there are two different ways so first is very similar to what I did earlier like I can do Plasma default shell style is over to be Plasma phone good quick controls style is over to Plasma export here this one I have it's for good so export here trail and disable window decoration but one so well what you generally can do is put this in one script file and you can just source it every time you want to actually use the Plasma mobile shell for some reason my virtual machine is broken so I'm going to just okay and after that instead of doing sourcing the environment variable sourcing the environment variable which was installed in prefix what you can do is basically just run deeper strong session when they land x well and that's weird that's weird so I don't have when back and epsilon so I did not had x11 back end which allowed me to run between well and inside x11 so I had to install that after that the height and width options to be available so so once you have so similarly you can run Plasma mobile shell which was which I did run on my actual desktop system another way of doing this is directly logging in mobile session so once you install the Plasma mobile related packages what you can do is log out of your session this actually change it to that's interesting okay so this was one of the side effect of reinstalling Plasma phone settings package it had switched our look and feel package to mobile which meant that logout window did not actually had a lockout option so that's why I had to move it out of way to actually demo how this I will actually move it back to where it was so after that you cancel like Plasma mobile violent session from from the your STDM screen and enter your password and log into your system which will start normal Plasma mobile session here you can see that it has installed the same cell package you can install various for example you can install Kirikami Gallery and and you can run Kirikami Gallery which will something is broken in my system this which is why Kirikami Gallery is not starting okay so for some reason my session packaging is broken which is why I need to manually install so you can try the Kirikami Gallery this way I see that it has got very recently new design thanks to Carson Plagg in the chat here you can use various cell functions like application drawer or our top manual drawer and things like that so back to the presentation so there is a question in chat which asks if we can set the VM to a phone size dimension so in my experience virtual machine manager can do some of this but then it's then anything which is non desktop resolution is broken in very weird ways so I would I have I haven't had many much services with it so it is in theory possible but then it is not usable at all so as for Kiri in based ISOs and using post market where is grandma images I have linked them in resources sections of slideshow I will be uploading slides later and linking them as well so you can try those using that that those two links are the one is first directly into Kareemian ISO and the second is grandma post market OS based grandma right so now that you have seen that I have shown you at least four different options so you would say that these are too many options and which options I would actually select so each options have its own its own own pro and cons like for example if you are using plasma mobile shell on your desktop system using quince well and X11 packet you can manually you can very easily iterate upon the design and you can also like you can directly deploy it from deploy the new paste version from your ID and quickly restart it so if you are working on developing the running it directly inside your system instead of running it inside what you are most saying is much is here if you want to taste not us just not just shell package but everything like for example like for example if you need to taste other shell functions then other other shell functions then you have probably the virtual machine is the better options so it really depends on which part you want to work on and how is your workflow one important thing to need not is you don't actually need the shell to test applications for example I can I can show you starting applications without shell packages it's a basically very same method I used it's a basically very same method I used for shell package of except that there are less environment variables so for example I can start with sourcing the tail prefix because my all of my applications are installed inside so basically I will be sourcing the prefix file after sourcing the prefix file what I will do is export the Qtpick controls style is equal to plasma and Qtpick controls mobile is equal to true which basically makes which basically switches to Qtpick controls to style which we are using on plasma mobile and also set tells Qtpick controls that we are now on the mobile on the mobile um after that I will basically start one of the applications which is with me so here you can see how it would behave on on for example on mobile and I can show you it on side by side that it will look like this on the desktop so here you can see that there is two different styles and two different user interactive user interaction methods so basically for testing applications you don't actually need the whole whole shell and you can test individual applications like how it would look on mobile or how it will function on mobile okay so I see a question that could we maybe have kidney on custom docker image uh so docker so docker is sometimes not actually useful for running the whole system while you can use it in my experience docker does not provide docker is designed to be used for running single applications or single program rather than running whole system so in my in my experience the docker is designed to run us not designed to run our GUI applications and also there are some problems with integration with docker so I would very much recommend using the virtual machine rather than the docker uh as for the ios show I have linked the new neon isos I should probably change website to it a point to new allocation uh there is question that are this pre-configured with basma mobile or are they like pre-configured for dialog thing so the ISO for kidney neon is pre-configured for just running plasma mobile and not exactly development environment but but it should not be hard to convert it to to actual development you can very easily enable the source uh legend source repositories and install various development packages any other questions