Felly, rydym wedi bod ni yn gweld i wefbapt ganwethaf a thisai bod yn gwneud i'r fath o'r cyflwyno. Rwy'n cael ei wneud i'r wneud i wefbapt, ond mae'n gweithio ar y gwnaeth. Felly, maen nhw'n gwneud i wefbapt yn cael ei wneud i wefbapt. So, first of all, what is a web app? Well, we in the group have to find a web app as something that a package or a group of packages that has access to a HGPP, or a server, or applications that run on a server, so you also include things like a server and various Apache modules which are still essentially web apps. Our aim in the team web apps company is to produce a standards document which we hope to integrate into policy as a way of a best practice procedure for how to package a web app that's secure, portable, allows upgrades at the moment because nothing does. We also introduce packaging manual, how best to do this, with examples, and help for applications. So, one-term goals, quite simply, is to have all packages combined. This is very important because if we don't have all packages combined then there will still be security issues and we need us to look at security issues in web apps in particular. Basically, if we get all packages combined, it's a lot less work for us. It should be a policy, best practice, so whenever anyone packages into a web app, then they refer to the documentation we've written. And, as I mentioned earlier, the help for applications. So, they should be easy hooks into maintainers scripts so that people will be able to install and register web apps easily. Current issues with web apps include problems being compliant with the FHS, peer-to-pea libraries at the moment don't really have any standards to follow. As you mentioned, this isn't in order of priority or anything, but it's just a general list which we brought up together. Database interaction. So, does a web app register with a database? How does it do that? What happens if the database is on a different box? What about if the database is offline? And, dealing with a web server? Does it need to, for example, register a module with a web server? And, which web server? So, move on first to the FHS. Most web applications have a single folder in school. Now, this is done by upstream, so it's very, very easy for the NJZ. Just copy all the files in here to a web-accessible directory, and everything works. But then that causes no answer problems for us. Conflict files and included libraries are normally within the single folder, so it's part of the web route. This obviously has security issues. If you have a file within the web route, the web server can access it, and it makes it a lot harder to attack a box if it's outside. The same for included libraries. You don't want some functions being public that are available. Again, template files, for example, skins, plugins or whatever. The admit local administrator will or may want to change those. If it's all within the web route, when it gets to upgrade time, it's going to cause an absolute nightmare. The other problem with web apps at the moment is that many of them use hardcoded paths, so they, which also instantly search about layout of the file system, expect things to be in user-level, for example. They expect things to slash SRV to exist. I mean, they're all hardcoded all over the place. Even this day, simply a bug in that application is built. Package for the bin? I mean, do we really need quality to say, don't write buggy apps? Yes, ideally, because the amount of ones that don't write buggy apps. But that's the quality that should be something that we do anyway. There's a lot of gray areas. We have to tell people what a bug is. Exactly. If you don't have a policy, how do you know if that's exactly a bug? What is a bug? Depending on anything in user local, for a database package, it's a bug. We don't need any policy about these things, don't write buggy codes. I'm just saying that we are kind of expanding the scope of this document to a point where it might not fit into general technical policy. Best practices might be the best re-corpers towards the developers reference. I didn't mean to call the big into the trend. I just wanted to raise the point that we might be overreaching the error. The first and foremost role is to make a best package of the document. After that is stabilized and solidified, and we have people actually adhering to it, and the tools are in place to help them. Best practices you can't force people to adhere to. I think we need to separate one of these two things. There has to be policy that packages must follow, and that has to be fairly minimal, and you don't define how people do things. You define what must be done. The piece about things not being accessible under the web server rule, that's a good policy. Some of the other things are a little bit more fluffy. If you could separate these out and perverse them, this part of the document is going to go into the developers reference and best practices that application ought to follow. And this part, if you don't follow this, your package goes out of testing and will not be released, because that is what going into policy means. Not all of these things would mean that things should be thrown out of the web. So if we can start off thinking about what you've got in your web app thrown out of the web, and what else is good practice that should be in the developers reference in Devian or any other help of packages that will come up with it. Yes, and in fact we have sent emails to Devian policy on multiple occasions asking for comment on this. Unfortunately, Devian policy, you're far better off if you come up with something, and then ask people to critique it, then you're asking for guidance that you're trying to do. That's what this has been about. Sorry that I didn't comment earlier, but this is my feedback as well. Certainly any time anyone has any questions or comments, they're more than welcome. This is sort of the end so we can move this on. Sorry where was I? Yes, another potential problem that web apps have is using persistent caches. They can have need files just within the web route because they don't know where anything else is. So potential solutions would be strict FHS compliance. Conflict files go in etc. Caches don't hang around where the hell you want to put it or anywhere you want to put it. And we've got quite a large section of policy of basically, well sorry, we're calling it policy now. Sorry, quite a large portion of the web apps best practice document. On where to put folders, what permissions they should be, which we should probably put into best practice, and items like that. What I'd like to see is according to my truth tales, and I can see a lot of variance in making that. We're going to put these things under, something under far and something new to share. Well also as soon as we truth the web apps can be a work. Yes, we could say the same about many other applications. It's still out to create the directory that's in line with something. Yes, our policy should make it easy to assume this. Ok, that's definitely the point is, if we have a policy stating precisely where the files go and the FHS go, then we have a script to help to create the FHS route afterwards. So this problem does not go away, but we have a solution for it. Ok, we're just going to briefly touch on the HV boundaries, because we haven't gone very far with it at the moment. People are generally creating the HV boundaries in the same way, but no one's really sure what it's got to do. So we are doing a short section of the HV boundaries on how to name PHP packages, which is a large one, because there is PHP somewhere in the module name, PHP in the number module name, or PHP in the module name, and there isn't really any co-gill or anything like that. Also we hope to deal with how PHP boundaries register themselves with PHP. For this, there is a, what we call in policy, best practice on how to create PHP library packages and PHP modules. That's very much in the other stage. We've got the fundamentals, but not much more. There's lots of to do with that. There's also recently been a DHMake PHP package. Now that contains DHMake Pair and DHMake Teckle, which can be used to pull packages straight from Teckle Pair, which are PHP's equivalent of C-Panel, for example, and can pull packages from there. Problems with database integration, with a web app. Top there is the URL for the DB app policy, which was written quite some time ago, I think, really now. Problems include offline copy. What do you do if the web server is offline when you come to install a great package? Normally with a web app, it would just fail completely. Now, that may not be the best case for a DB app package. We want to be able to handle that with the use of the unit. Use of permissions would be an example of a administrator may not want the web server to have grant access, create access on the database. The administrator may not want the web server to have access on the database to create a database, just to read and write an update. Are we talking mostly about PHP-based web apps? Because some of these things, not seem to apply to only web apps, I wasn't using Ruby on Rails. They have different set of problems for their root, but it's very tightly integrated with the database. Most of the time, they don't go under the web root, they just redirect using empty access to go somewhere outside. I was just wondering if there is somebody on the web app team who is familiar with Ruby on Rails, and can represent the Ruby community while this document is being created. I'm not sure at the moment. And all the parallels are also the turbogears. You know, the vital number is popular and developed, right? Which also has its own clerks. We'll try to design this to be as agnostic as possible. So it's not very ready to create a web server. Maybe we should extend the invitations to the package maintainer of the Rails package. Because even though I'm dabbled with Rails, I'm definitely not an expert. And maybe the Rails package maintainer should be invited. See now, Sean tried to get some package maintainers involved, but we didn't really get them. At one point, we sent emails out to various programming language package maintainers and web server databases for package maintainers. That was some time ago. Someone came back to us that was doing it. I guess it could be a little longer. Traditionally, what works best is writing a draft as you understand it, sending it as a proposal for policy and then having all those package maintainers coming in screaming. Can we have one more step, please, before you send me forward to policy? Just send something to the Rails slides. I know that you have tried them once, but if you could please just... It's not just the Rails guys, it's the Flone guys, it's the Mason guys, it's the... Just send it, grab the constituency and send me an email before moving on to policy.  You have to see the proposal ready to go. Regarding Rails, it seems like Rails isn't a web app, it's a framework. So you can use Rails to create any sort of thread that you want. That seems like it's not an issue with the package maintainer and that stuff. It feels like it's more of an issue with Rails in general. I think you should get the Rails package you're in here to see. The primary purpose of Rails is to write a web app. Yeah, I know. And so the specific web apps written with Rails, Ruby has this thing. They have this thing about convention, not configuration. So you'll find that most web apps written on Rails are going to form the de facto conventions. So if you can get the Rails people to have input and maybe add on sections which are specific for web apps written for Rails, we might come out with a bit of a problem. And I'm sure the thing applies to no one then. The other packages that you mentioned that I have no idea about. Yeah, so we're trying to be as agnostic as possible. Fortunately, most of these problems on PHP packages, basically, because they have happened to be reversed with... Upgrades are a problem with database integration, because very often it's the case that upgrades between different package versions also due to the fact that it's quite heavy and they can fail as well. And I do a video synchronisation of languages as well. Some languages are sensible and maintain double-edged version information and some languages expect the database to look like this before it starts and to look like them and thems and don't you? Yeah, some of these added users, permissions again, what happens if you have multiple databases that you want to configure this with, what some parts here, some parts there, it's all a bit heavy. Now for this we have a solution like the DB conflict common package. It's already in unstable and edge, I believe. It's being used. It's a framework that basically register an application for databases and provide you, obviously, a great table to update it. You can do various things like that. That's a very specific... Two more packages. Yeah. That's the variant for database. Is there a documentation for DB apps? Yes. I have looked on the web page, there was a green system, so if you like this. The documentation has been... How long ago was this with the release? A few months. Well, the documentation should be updated on time. It could be updated on time. We'll talk more about the actual documentation now. Okay, now the other problem is how does web update on the web server? First, which web server? There's 16 in DB apps, hopefully, not counting the duration. So, you also have, instead of, say, just a passion, you've got a passion SSL, a passion code, and then a passion 2. Not counting the 16 separate projects which we have to deal with so now. Registering involves making content accessible. Possibly, we started a web server group, David, and how should the web app deal with this? Should it deal with postings? Should it just drop things in a conflict directory? Also, we have problems with v-hosting, which basically means virtual hosting. You have multiple URLs, a point of assembly to code, and creating different conflicts for the web servers and indeed the applications themselves within that. Another problem is that there's many applications used and work-based config created to them. So, your login would get to installed or whatever and you're putting all your details there. Now, that would be suboptimal for Debian, I believe, simply due to the way that you want something just running and you could have a long interactive front-end and you don't want to actually go to a URL and put in all your details there. Now, the solution for this one is the web apps form package. This is almost finished. For this bit, I'll hand over the check to you, Sean, to talk to you about this and see how it's the best process you've made in it. Okay. Yeah, let's go over both of these in abstract. I'll show you actually in use and practice. These have been my pet projects in maybe a year or two. From a very abstract perspective, the goals are for these packages to work by consolidating code. Anyone who's looked at more than two or three web applications that actually try to do any kind of automatic configuration will notice that there's very significant amounts of code that are duplicated. Within all of this duplicated code are bugs. Unfortunately, the bugs are not duplicated. They're all unique to each specific package. Often, the features provided by these packages, automated assistance, are not fully developed in addition to being bugged. Sometimes they're not fully developed. Sometimes they're not fully flexible. Sometimes they do things that they really, really ought not to do like editing the configuration files of other packages, taking kind of the restarting servers, et cetera. The goal of these two packages is to consolidate the code that all of these packages would use into a single framework. Consolidate the translations of the DevConf templates so that there's a single set of DevConf templates that all of these packages can use so that the poor translators don't have to basically translate what's essentially the same message but just a plenty of different in 70, 80, 90 different packages and instead, they can translate one set of DevConf templates which then will automatically propagate to all the packages that use these frameworks. And then ideally, it will also consolidate all the bugs so that the bugs that do occur are in one place and when they're fixed, they're fixed for all the packages that use this framework. They work by providing hooks for the maintainerscripts. So, basically, in each maintainerscript, the package will insert a couple of lines that basically source a shell script library and call function that will then do what needs to be done at that stage in the installation. And then, often, a problem with developing all these features and providing these tiny little hooks is often one package will need to do something slightly different than another package. So, there are certain features that are overriding just by setting a few variables before you call the function that does what it does. Obviously, no automatic system will be feature-complete for everyone's needs but the idea is to be as flexible as possible for all the conceivable needs that we can figure out. The design principles of these is to provide consistent policy-compliant behavior that adheres to certainly, first and foremost, to the existing data policy but also to the best practices, documents that we've been drafting up for the web applications and gateway service. Another design principle is that the packages should only have to insert a very minimal amount of code into their maintainerscripts which will reduce the theoretical possibility that six months from now we've realized that, oh no, we really need them to say something else in their maintainerscript.  It also makes it easier for the package. Obviously, a lot of people, if you provide a half of these resistance that's really easy for them to follow that, accomplishes what they want. A lot of people will end up doing that. Another design principle is that the local admin should always have the ability to opt out of any assistance that we provide because it's quite possible that they know something we don't and we shouldn't try to be too helpful because often you can end up with some pretty bad problems when they happen. So, another fundamental design principle is that we're trying to be as fast as possible to both the packager who's packaging the application as well as the local administrator who's installing the application. Okay, so the package is in action. So, included in both the db2fig common package and the web apps common package, there's an example of sub directory. If you install the package, it's a user shared doc db2fig common slash example is the same thing for web apps and you can build these source packages and install them to see how they work. You can look at the source package to see how they actually do what they do. I guess at this point I'll actually show you how it's shared. Now, it's there. It's there. So, how do these do? Use an extra. It's okay. You can click on the camera also. Just run extra. Repeat. Have extra. This laptop's a little slow, doesn't like... ...confrigunder鼱r ar ymysg wneud atriacol Samsung. Rhwng am y dydd ymlaen i'r parwys. Felly y gallwn yng ngynghwm ar y salogau. Yn y tîm ymweliadau, gan ystod o'i cyntaf Llywodraeth... ...yna'r perwyr yma? Mae'r ffordd mae'n rôl ystod... Mae'n hoffa. Mae ymddirwr trafodaeth ar y hiphwil, pan mae'r ddau hostrach mae'r hydrach. Ond ychydig yma... ..es yw chyrhaf i'r hoffa'r perwylliant yma? First and foremost, it asks, do you want assistance? You can say no and then it will pretend it was never there, but then it wouldn't be a great example. So in this case, you're presented with your past, what virtual host would you like to configure this for? Global is just the default, whatever your default server is, so I'll use that. Then it will ask, what's the name of the subdirectory under which you want this website to be available? You can provide a nested subdirectory. In this case, you can provide an empty name in which case it will actually be the document group of that virtual host. In this case, it will just stay for the default, which is the package name. Then it will ask about what web servers you want to configure. So let's actually do this without a warning. Now it's asking, this application uses a database, so would you like assistance in the centre of the database? Sure. It's a MySQL application, so it's asking MySQL specific questions. How do you want to connect to your MySQL server? You select a unique socket, it's going to try to talk to the MySQL server a little bit more. If you select TCPIP, you'll get options about connecting to remote servers. The administrative user group password is TCPIP. We've got a MySQL user name that defaults to being based off of the package name. You enter a password for the user, then the name of the database for the application you create again is based off of the package name by default. Then you need to reload some servers. Here's your chance to avoid doing that if you want. Now it's configured with web servers, setting up the database, and it's done. Now I'm going to go over to Firefox and it's set up. I've just had some stuff in there. It's a simple PHP page that does some database queries so you can actually see what the database is set up. That's the package in action. There's also another package which shows an experimental feature supporting setting up multiple instances at all. I guess everything's experimental at this point. An extra experimental feature which shows it supporting multiple instances installed at the same time. So you can use the same installation, you can use the same package and configure it so that it can be accessible for multiple directories with different configurations and different databases. So if you were, say, someone providing web mail to different organizations, you could install the same web mail package under different locations and use the same package to set the configurations and set the databases. I won't bother actually showing that in action because I think we're going to take a little bit more time than expected. But I do want to show you basically just how this works. So I'm here in the source package for what we just saw. First of all, the text and the questions. I think they really, really need some usability work because they couldn't be understandable in short lines. You have to really read into it to understand them. And the second one about multicosting, usually web service providers, they could have thousands of clients and they could have hundreds of web apps. And that user scenario, they want to install the package once and not have it activated in post install. And instead they want to activate and configure the package. Then you just say no and it puts that? Yes. Wait. They want to configure, activate or deactivate packages to specific users, to specific records afterwards. That would be perfect example of using the same interface that you have to hear or direct command by interface. Asking the same questions but as a separate executable that you run afterwards after the package is installed. But they've got a thousand users and they want to take one active package and use a number 55. If we install it for everybody, all thousand, but we only want to configure a number 55, you don't want to go to the active executable and try to configure all thousand users all at once. So if you had something in a script that used DevCon post installation to ask the same questions and tap into whatever instance I've already been providing, I think you might fall the fall of doing this thing if you're using DevCon for the registry in any answer. But you're not. No, I'm just looking at everything as I was looking. Well, one of the sort of items on my mention to do with this is possibly exporting some of this functionality to command line programs. But first and foremost, it's going to be scripted. It's going to be scripted. Yeah, it's going to be. But you get working in this score instance and use and see what the problems are as it grows around. Right. And you try to do the whole thing and you can finish. The primary design goal is to tie this as closely as possible with the actual package installation process so that when somebody actually installs a package, they don't actually have to know about any arcane command line programs that my system uses. They don't have to know about. Ideally, they don't even have to know a whole lot about the use and resins of Apache or my simple or postgres configuration. They can just install the package. It configures it to the web server. It sets up the database. Remove the package. It reconfigures it to the web server. Remove the database. Reconfigure the package. You can change the settings for how it's installed on the server.  You can actually just do that by reconfiguring the package. But all that asks questions for all the three user costs. It will, if you like, after we've gone through everything, I can actually show you what I have in place right now with the multiple host support. It's a tiny bit buggy right now, but it actually works enough that I can actually show you how power works. You basically present it with a list of contributing instances and you can deselect from that list and it will remove them where you can say how much you think you're doing. And it will then only ask you questions for that instance. But is that the reconfiguration then? Yes. Quite fit the definition of the difficulty reconfigure then, because you're supposed to get the same question, the same process like you were just installing the package for the first time. Oh boy, I see what you're saying. Well, basically what happens is it precedes all the depth-configuration questions with the information that is stored in the configuration files on the system. And you could, sorry? I'm so excited. If you reconfigure the package and didn't provide any additional information, no changes would be made to the system. So it would be ideal. If you chose to remove an instance, it would then remove the instance because it was specifically told it to you. If you chose to add an instance, it would add an instance because it was specifically told it to you. But if you say reconfigured it with a non-interactive front-end, there would be no difference at all. The idea is to make it behave as much in line with the package installation process as possible so that it's consistent here and won't drive administrators crazy by being confident with the same questions over and over.  I understand it. It does not on me that the two applications you have talked about are mostly dealing with installation and dealing with how to integrate with a web server and the database. I think that these are useful beyond just web apps. I have got things that need to talk to web servers and need to talk to databases and they are not. There is no reason to introduce DB Conflict common for that. It is a separate application. DB Conflict common is different from web applications. Maybe we should advertise it. Well, in fact, there are a few applications that use DB Conflict that are not web applications. If I wanted to take pieces of these applications that you created, but I don't really want to talk to either web servers or databases and just like the way you ask a question and presenting me with lists of examples. I'm thinking of AC Linux actually. I've got a lot of AC Linux policies. They're confronted so that administrators can choose the policy and I see what everything that I need. If I just need to throw the web server in the database, I'll give it a throw. It's like DB Conflict, it's AC Linux. So, can I take bits and pieces of these two applications and use it for a long time? No, it's too chaos. I'm not sure exactly. You have written a lot of utility functions that deal with their point of deal with gathering information from the disk. And presenting the user with choice. You figure out how many web servers I installed. I need to figure out how many policies are currently present on the system. You say if you want to talk to web server A or web server B, you want to... This way, where do you want to place your things? For me, I can obey you because in strict policy, you want just a base on the extended version. And that I do get by using a derivative. You've got utility functions that other people can use. Maybe you should update DevCon for that. I think quite your time. If you want to update app dealings, that's fine. It's not the instant. Yeah, it's only cheddar cheese and wine afterwards. How many applications have already used DB Conflict as compared to the already available? 21. I just looked right here. In the very small font, I typed it to WC. Yeah, but compared to the many that we have in Davion... Compared to the what? How many applications we have using DB configuration in Davion already? I would say that DB Conflict is actually a fairly young package. I've been working on it for some time, but I don't think it's been generally useful, stable and helpful package, except maybe in the past year. I haven't been going out my way trying to badger people to using it because I've been quite busy with basically talking with people who are coming to me saying, I want to use this, but I need this extra feature. So when I work, I think about it, and then in most cases I provide that feature so that they can actually do it. I've been so busy with that I haven't bothered to reach out and try and bring anyone in. I was actually surprised to find out that there were 20 more people. When I was asked me a couple of days ago, how many were you using? I was like, oh maybe six or seven or something like that. I went and looked right here and said, oh wow. I actually have done two of them, but I see that not many people are using that, so maybe you need to sponsor that between me. I was in the middle of this. It's one of the reasons that it's bought. It's one of the reasons to make policy draft for using it. So more comments are coming in and more specific people are looking at it. This is a constantly evolving process. One of the things with policy is that there is a chicken to make thing. You can't just write down something in stone and say, oh it's policy and I expect people to start following it.  You've come a good start in that approach. We also map with the draft. The idea is that all of these are developed in parallel. When we come up with a draft that says, this is the way we think things ought to be, then we come up with a code so that people can do those things the way we think they ought to be done. They sort of feed back into each other because sometimes you realize, oh we missed, oh we need to consider this one thing or maybe we were too short-sighted to this other thing. So they feed back into each other a lot. I think this is the ideal way to get things fast-drafted in policy. Yes. Okay, well, are we... Okay, so now in the road head, basically where things are and where we're going with things, yeah, like Nils said, you can take comms out on this table. It's a natural, you know, it doesn't do any arcing bugs. It will be a natural when it's released. It's used by about 20 packages. Web Apps Common is more of an alpha-state project. Because my own personal resources are limited, I started out very centrally focused on deep version of Common because it was much narrower in scope and something that, as I, as a near mortal, started off in scratch to do. And then what I learned from that, I applied to the Web Apps Common package and that's really where the real work is happening right now. And so, yeah, we'll probably sometime after DevComp will be going into experimental and asking people to just try it out to let us know. I'm trying to say, packages has never been in Devian before. They've no point in going into experimental. They're not going to break anybody. They're just going to be using the new packages and just put it straight into the set. There's no reason. If any current packages want to use this, then they should go into experimental. My fear is that we may end up making some drastic change to this kind of behavior. This is unstable. Yeah, well, my personal method of operations, I don't put stuff in that table unless I feel like it sign off on the job like that. I feel like it should go into unstable because people, you know, you don't want people to go into experimental just because they want less for example. Yeah, and you're not going to damage the existing system. You're not going to impact current users and the people who are writing the application based on what they're developing and they know what they will get when they're running set. The problem is, when you start putting packages to where it's coming to and all the packages maintenance start writing the packages to where it's coming and where it's coming, ends up not being released into Edge. Why not? Well, I'm here, but it's not depending on whether they're packages. Sorry? It's not depending on whether they're packages getting released into Edge. That's the problem. All the version that's currently unstable, the version that's currently Edge do you know any serious ones in the package? Do you know there's anything that will cause data loss for anybody? Not data loss, but there are... Well, I feel it's this is why I say it's... I feel it's mirroring the point where I should present it to the world. It's not quite there yet. This is your package, your decision, but my advice is unless you've understand there are people who need the exposure to this will get especially if you guys want to post this into policy before release Edge. No, I don't know. You don't want the Web Apps policy to be Edge's policy? It would be nice, but I'm not sure the timeline is with us. Yes, from what I've seen I think you guys are far enough ahead. No, probably not. A policy in this way to play at least for Web Apps policy it could make it the deep-in-config common policy. My piece, but also quite questionable because it is not much to understand. Yeah, and not only do we have to have it prepared and presented and agreed upon but then we have to go find all the packages that are doing it and get them fixed. No, this is... It will come in as a recommendation. It doesn't come in as a must. The only packages that choose to use Web Apps common and the deep-in-config common will be policy. You know, policies for packages that choose to use those tools. No, no, no, no. No, no, no. If I'm writing a Web application where do I dump my files? Where do I dump my dash? Where do I put anything? Can you use it a little bit? Whether I put anything to use a local order in the world of WWW that's policy. How is the public press reference? You can get that to the public press reference. That's what's very important. And using the packages currently really long needed. People should be using packages correctly without being hit on the head with the developer's reference. In any case, it would be better if we did this. Yeah, it would be better if we did this. I think the train said and I would think that you guys have a decent chance of getting at least at the recommendation moving into itch. Actually having that on the developer's reference, we don't have already. I've seen it dropped and I think that it would be good to have that on the developer's reference because there's people making Web applications that don't have it too. It's a total mess right now. You said to yourself that it's a mess out there. Something, any guideline is better than that. Any package is better than the mess we have and what you have until October to get all those nasty bugs that will really slow it down. This might be better. OK. Is there a report? Thank you. What next? It's glass zero. This is what we've done up to the present moment in time. We've got this draft currently in practice. Or policy or whatever you want to call it. Is there a next match at the moment? I think you have some policies that you can take it out. Yeah. But Web app's common package which is more or less right now. You can't do the common package but it's already there. We've got this best practice at BHB and not the database which John know not much about. He's actually slightly used now which is good. What we've got to do next is work, well basically on this policy try and get this integrated try and get more people using it and talk to the people who are known and raised and so on. It's trying to get input and try and get these things. Actually if you can get them to be part of the team and you can't post them today but if you can extend them in invitation to have a seat at the table that might any of you may have played it before but I think at this point you'll be able to find more positive response than you did before. So you've got the Web app's common package and you can't become a package without these years of work not only because it makes the package do the right thing but it's also easier. It's much, much easier than having to sort this all out yourself and it also provides a much more standard base for all these packages so now I'm in a blue pot and its database handling is completely handled. And brought to you? Yeah, it sort of works. But if we people usually can't become a package it's going to work and it will work in a standard way so let's do it if they really can't become As we said, the least though is edge plus one If we can get it into edge that's great. That'd be brilliant. It won't be a must rule. It will be a condition in edge. Edge plus one is when we say that we are going to get it going out. So thank you. We would like basically edge plus one for all packages from my dream as long term girls all packages to be compliant everything works and this whole problem which we have at the moment is all nice and clean and sorted out. Does anyone have any comments for anything? We're very in the policy because the policy just stayed where it put things and cleaned things up as hard as the file system or is the policy going to try and enforce people who package web apps to use dvd content content. No, that's looking at the virus. You're only talking about policy but maybe there's obvious references to other things. Men, if I could say that you put packages and thinking in this or something. They'll have their own database in methods, upgrading methods that come from upstream. Which is certainly something we want to preserve. We don't have four seconds. Actor records for example that grades users in the back end. Actor records is totally different unless we can if you have got some kind of a configuration plug-in interface to do the config being actually able to configure grades that actor records based on what they use next but that is something I don't know how modular it is. What language is it that we need? What language? There are all shell scripts in very big shell scripts. In which case it should be possible to load specific things like this is loaded from the script so you can compile the database back end but it doesn't work to any of the normal and none of the military of talking to databases. Do they run under the day? Do they run under Gash? I'm Does Gash support local? The local key word? I'm a bash this. Is this the one thing that it doesn't you know what I'm saying? Is this the one thing that it doesn't support local but then some of the others do? I don't think it's perfect if in the exercise extension. But there is a way for it. You can already use bash It's the first thing. I was just wondering about you. Music is the same language. You should talk about why you need key. There is one thing that I would like to bring up. You said that all this was done by thinking about policy. Edge is going to ship with cylinders on the system and targeted policy installed. Maybe you can turn it on if I can spin down my policy by its level. You guys have come up with a decent pattern for how web application should be present on the disk and the pattern for how this should be. I think we can also come up with a security pattern for Edge on this one which can be part of the document and then the developer applications can create an application which does this you get a default policy. Which goes in there. It means there is a policy generation for web applications. That's right. Complete based automation. I'm doing some of this already in order to be testing for it. It won't require much to do the automatic policy generation. We need to do automatic policy generation for the internet because otherwise we are never going to be able to code 15,000 packages. The truth is web apps are not yet. So it has a version repository. The main list is getting on web apps and a list of them at all. If you go to webapps-com.alib. It's got the drafts on there at the moment. It's got the one which we have for web apps. It's got the PHP 1 and it's got the what. I think it has the dark condition on the actual web apps. Do with DB content comment stuff is people aren't doing it at all. It's not still there. So please join with it help us. We're not speaking already. At the moment it did start a while ago. There's lots of activity and then we've kept on doing work in other people. It's the first ups and downs. I know where you're coming from. We're done with people on the web apps. It's me and James. We've had really good input before. Now again we do get people coming to the web apps and say what should I do? Do you want them at this? Try and do that. Most of us have helped point out errors in all of the drafts. So any help you can give us? It would be great. We just want to start with you. Thank you everybody. Thank you very much for coming home. Thank you.


Hello, everybody, I'm EvilRabbit. We're here staring at the next round of ESDA starting line in my ESDA E36, the next all the racing, Mazda Racing Tourist Drift E36. We're going to Irwindale as well for the next round of ESDA. So we're going to go full send here in some practice before this round this weekend. To make sure you guys follow me and also share me the knowledge found in the description box below. Let's get our lights on. So there was a lot of requests about bringing the pedal cam back. So what better time than to bring it back for the final round of ESDA and upcoming videos and stuff like that. So we're here on Irwindale. This Irwindale has that inner, second inner bank area, which is not like this year's FD1s, but it was like last year's. So we're going to go full send. See what we can do. We're on a base tune. Not sure how the base tune is going to do. Let's give it kind of a little sloppy entry. So we are on the public ESDA server so that we can get the correct amount of heat and everything with temperatures and everything like that for the round. Bring it in on the center clip. That zone is very interesting to get into, but not a bad run. We are, like I said, since we're in the public lobby for ESDA, we'll go back and exit out and take a look at the replays after the fact, after we get a couple runs in. So I think I need to stay in force gear though for that final outer zone because I was kind of bouncing around and throw a little bit too much. So we have to do some clutch kick stabs and get it in there. So let's see if we can get better entry in here. That would have been a restart with the restart cone. Trying to limit my left foot braking on the wall. They were using a lot of left foot braking to keep their cars up on the wall, but those cars are super gripped up. Quick e-bank grab there in the diesel zone. We may have started a little bit sooner than the actual diesel zone. All right, so we can stay in force. That was actually not that bad of a run. So that was two runs in succession with no heating up of tires or anything like that. So we're gonna do two more runs. We're gonna heat up the tires initially before the first run because the second run felt definitely way better. Irmondale is definitely a track that either you are on it or you're off it and it could either be good or bad depending on how you are. So let's do a little heat cycle of these tires. Keeps that helps us in our first run. So for qualifying, we're probably gonna be doing two runs of outgoing into pits because I didn't like how that felt on that second run. So now we get a little bit of heat in our tires. We're gonna try and stay high on the bank. Like I said, we'll go take a look at the replays after this, but the base tune does feel pretty good. That's a really aggressive flicking. I do like how much grip the car does have with heated tires. So that's something we may have to actually do. And that was overall not too bad. Bring it in on the inner clip. This and out in that diesel zone. That was probably a little bit slow of a transition. Probably should have transitioned that a lot faster. That is the zone I'm still getting used to because I have never run this version of Irmondale. I've always run the one like the final round this year where you end after that inner clip. So one more run. We do have hot tires after a heat cycle and then a full run. So we'll see where we're at on this run. Oh, too much of a flick. That was way too much of a flick. We're gonna probably reset that run. That was a little bit too much on the handbrake, a little bit too much on a quick stab of the brake. We're gonna try and do this flick entry without doing too much grab of the handbrake to initiate. Massage the brakes a little bit to get up to the wall. I think we are pretty close to that outer wall. Oh, that's not gonna be good. I don't think the second run on tires is going to be the greatest. We kind of are already out of tread. So we're gonna do one more cold run. And then we'll go take a look at the replays from the outside and see exactly where we were on track. I'm bouncing a little bit to my fender. Seeing where we are on track in relation to the walls and stuff like that. Nope, that's gonna be a wall. So I think we're gonna go take a look at those replays. So we switch to the replays. All right, so this is the first run of the set that we were running. Take a look at a couple of different camera angles. The E36 definitely looking super nice. So we were kind of mid to high on that first outer bank in that first run. We did manage to get all the way into that zone though. That was pretty decent. Having to change our cameras a lot for the actual replays. So we're gonna run this and see where we're at. And we'll click over to 10 to see that inner bank. So this was on the first run with warm tires. About mid to high bank again. I think we can get a lot closer. On that inner bank though, we are on the second outer zone. We were pretty nice on that wall. I feel like we're actually getting that final zone pretty well. So we need to work on working our way up in the first outer zone to this camera's lake. That's not gonna be a good camera view. This one might, we might be able to actually see where we are. Okay yeah, we're deep in the zone that time. We're almost the entirety of that. Pretty decent on there. Good hard transition and nice and deep on that outer zone too. Tagging that and then going into that zone we were pretty much in there. So that run was the better of all of them so far. And that was after heat cycling the tires a little bit. So we may be having to do some heat cycles in the tires in order to get a qualifying run but we need to manage to see how the tire wear is really going with running, having to run back to back runs in actual tandem if we do make it into the 32. Let's see where we are on this one. It's always good to digress these runs from outside perspective. That one we threw way too hard. Then we went and reset it. I think this one we also sent a little bit too much. We were nice and deep in the wall there though. I think we sent this into way too hard on that transition and looped that one. And then this one we ended up in the wall. So overall first runs on this, not too shabby. Gonna do some tuning, fine tuning of the actual tune of the car to see how where we're at. Oof, it's a hard hit. Fine tune to see where we're really at and do some more testing before qualifying. So make sure you follow me on all social media on what you found in the description box below. Appreciate you guys coming back for another episode. I'm EvilRabbit. I'll see you guys on the track.


Hello and welcome to Connecting Hawaii Business on ThinkTech Hawaii. My name is Kathleen Lee, owner of Kathleen Lee Consulting, and I am your host for this program. We are currently live-streamed on ThinkTechHawaii.com as well as on ThinkTech's Facebook and YouTube pages. And for all our viewers out there, if you would like to send us questions during the show, you could email us at questions at ThinkTechHawaii.com. Before today, I am very pleased to have on the show one of my friends. Her name is Tricia Fatui and she is the Executive Director of Donor Development for the Hawaii market for March of Dimes. Welcome to the show, Tricia. Thanks for being on. Thank you for having me. I'm so excited to be here. Of course. So let's launch into this, Tricia. Tell our viewers about yourself. Well, Alohaan, thank you again, Kathleen, for asking me to be here today. I'm Tricia Fatui, Executive Director of Donor Development with March of Dimes Hawaii. I had the pleasure of working with Kathleen when I was previously at the Chamber of Commerce Hawaii as Associate Vice President of Events and Engagement. And in my role at March of Dimes, I oversee all of our programs, our events, and advocacy initiatives for the state of Hawaii. And so I kind of fell into this line of work of fundraising. I always loved event planning. I started event planning when I was in college and I just loved it. And then when I joined the Queen's Health System back in 2012, I was working in the Philanthropy Department as a special events coordinator, and I just fell in love with fundraising events and the idea of being able to raise money to help people. And I kind of came up with the motto of saving the world one party at a time. And so it's really like my philosophy on fundraising. I think that's wonderful. And I'm glad that I met you through the Chamber of Commerce as well. And I knew you were really active in that. So I was very excited to learn that you had gone into the non-profit world. So before you go into how you got into your current position, could you give us a brief background of the March of Dimes? What is your mission statement? March of Dimes leads the fight for, sorry, the fight for, gosh, I just went blank. You threw me off in the talking point here, fight for the health of all moms and babies. And then so we tailor that to all moms and babies in the state of Hawaii. Sorry about that, Tricia. Thank you. Thank you for all the long. So let's go into it. Why did you decide to take on your current position? I know you've been doing very well in everything that you've endeavored. And I've seen you do that from the time that I've known you. So why the March of Dimes? It's a very intense mission. It's a very meaningful one. So let's go into that. Thank you. Yeah. Leaving the chamber was a very difficult decision. I just loved working for the chamber and helping and supporting our business community. But last year March of Dimes had approached me to join their mission to fight for the health of all moms and babies. And I just couldn't say no. I am a working mom. I do have two teenagers and last year the pandemic was just so difficult for all of us moms across the nation, you know, and we all had to pivot our work life and we had to pivot our kids' school life and maintain everyone's health and safety. And so it was just a lot of added stress on to already being a working mom was stressful. And then I also had a miscarriage last year. And so having a miscarriage in the middle of the pandemic, it was just it was a very difficult season. And so when I had the opportunity to join March of Dimes, it was an opportunity to turn my pain into purpose and to serve our community and to help boys, moms that have also had a rough couple of years. I love that. Let's pull up the first slide. So people will have an idea of the mission of the March of Dimes, which Trisha had already mentioned earlier. And I know you wanted to talk about preterm birth. So let's go into that. And for our think tech folks, let's show the next three slides. Yeah, thank you so much, Kathleen, for once again inviting me here and to think tech, you know, just for the opportunity to share a little bit more about March of Dimes and one of the topics that I wanted to share with everybody today was about prematurity. So we can go to the next slide. One out of 10 babies are actually born preterm in in the US and also in Hawaii. And so when you think about it, you know, you're like, one out of 10 doesn't seem that impactful, but it really is. We think about some of the other issue, you know, other issues that affect children nationwide, you know, one in 500 babies have diabetes or children have diabetes. One in 285 have cancer. One in 59 have like a was it sorry. There you go. Autism spectrum disorder and one out of 10.  And so last year and we can go to the next slide. Last year, Hawaii actually received a report card grade of a D for having healthy babies. And so it was just shocking to think that Hawaii is one of the health the best places to raise a family, but it's not necessary. The best place to like to birth a child. And so there's, you know, we're so passionate about our families here. It's like there's got to be more that we can do just to make sure that babies are born healthy and have the best possible start. And so we can go to the next slide. So some people think like, OK, what's the big deal about having a premature baby? And the problem is that babies born premature. They don't have enough time to develop in the womb. And so if they don't have enough time to develop in the womb, then it leads to long term health issues. So premature is the leading cause of baby death. It is a leading cause of development delays such as, I think, you know, with the heart, with the lung, with the brain and even stomach issues. And some of the long term health issues include asthma, cerebral palsy, mental retardation, visual and hearing impairment for health and growth and learning disabilities. You know, in Hawaii has a high, has a lot of people that have asthma issues. Hawaii has a lot of people that have, you know, special education needs. We have a huge special education, you know, here in our DOEs. And so I actually have a girlfriend that's a special education teacher. And she says that, you know, when she really drills down, some of her students are were actually premature babies. They are like, oh, OK, that, you know, that makes sense. When you have a premature baby, it's also increased risk of ADHD and increased risk of sudden infant death syndrome. And so the list goes on and on. And you don't realize that all these things could happen, you know, once you have a baby that's born too early. And so we can go to the next slide. So the cost of having a premature baby is even more staggering. So the societal cost of Hawaii is about $94 million a year. And so when you break that down to like local businesses. So in Hawaii, we have such great health care, right? Like all the if you work 20 hours or more, you have health care. And so for a local business, when they provide health care for their employees, if their employee has a healthy baby, then the employer cost is about $8,000 a year. But if the employer, if the same employee has a healthy as it has a premature baby, then the cost of the business is $65,000 a year. So there's definitely an invested interest for businesses, you know, for the community, for everybody to make sure that one, we have healthy babies because it helps us financially, but also it helps us set up our society for the future so that our people and our community are helping. Tricia, just if you can go over that real quick, because that's a that's a huge difference between having like a preterm baby and like a healthy baby. So where are the costs coming from? Is it mostly through medical bills or? Yeah, a lot of it is medical because when a baby is born premature, a lot of times they have to stay in the NICU for a certain amount of time before they can be discharged from the hospital. So like the average stay in the NICU is about six weeks. But some babies are in the NICU for six months or up to a year. So that's all the daily hospital costs of being in the hospital. Then you have all the specialized care, the medicine, the equipment, the nurses. And then it's also lost lost productivity for the for the parents, right? Because now the parents are leaving their work to be at the hospital for long, you know, term, long times to be with the baby by the bedside. So it's a little bit combination of both as a high cost, you know, of hospital care, education and then also the lack of productivity. And thank you for pointing that out to so people, especially, you know, the businesses and employers out there are aware of it. Wanted to share a story or, you know, talk about neighbor island families and how preterm births affect them. So could you go into that, Trisha? Yeah, if you want to bring up the next slide as well. And so also for neighbor island families like this, the disparities are even more shocking. So, you know, we all know that on Oahu, we have the wonderful hospital Coppulani Medical Center. It is only level three hospital for mom and baby care across the state. So families on the neighbor island, if they do have a high risk pregnancy or have an emergency delivery and it's a preterm, then they have to fly over to Oahu for that care. So there's no place on the neighbor islands for them to get that care. And so there are some babies, so if you say you live on the big island and you have a high risk pregnancy, some families are moving to Oahu for the last three months so that they can be close to the hospital.  They have a hospital, you know, physician shortage. And so you might end up not getting the care that you need so that baby is healthy and that mom is healthy. So there's more complications that arise. So there was a story about a couple of years ago that one mom had a C-section and there was complications with that C-section and she ended up leading to death because there was there was a shortage of blood supply on the big island. So it's crazy to think that in this day and age with all of our technology and all of our advances that we still have moms that are losing their lives, delivering birth because of lack of resources. And so, you know, we're just like all hands on deck. You know, I know COVID is huge right now, but at the same time, we can't forget about our moms and babies and just the basics of being able to have a healthy baby. Thank you for bringing that to our attention, Tricia, because I didn't even know that. So we are going to go on break, but when we come back, I would love for you to talk about how March of Dines is helping in advocacy for mothers and babies and upcoming programs or initiatives that you guys have. So yeah, stay tuned. We'll be on break. We'll be right back. State of clean energy. I think that Hawaii. Hawaii, the state of clean energy is about following the many clean energy initiative in Hawaii. Hawaii, the state of clean energy, appears weekly on Think Tech Hawaii at 4 p.m. on Wednesday. Thank you so much for watching our show. We'll see you then. Aloha. Welcome back to Connecting Hawaii Business on Think Tech Hawaii. My name is Kathleen Lee, and our guest for today is Tricia Fatui. She is the executive director for donor development for the Hawaii market for March of Dines. And March of Dines does they do advocacy for healthy mothers and babies. Tricia, I hope I got that right. Healthy mothers and babies. So the last time that we the last that we laugh, Tricia had talked about how free term birth affect people not only in Oahu, but on the neighbor islands as well and how it affects the businesses. So Tricia, let's delve into what March of Dines is doing as far as initiatives and programs go. Yeah, thank you. Thank you, Kathleen, for for being here again. If we would like to put that, yes, thank you for the slide. And so, like I said earlier, that all of these issues has really inspired our local office to to make a difference for our families and to put together some new programs to increase positive outcomes for moms and babies. And so since February, we have launched a whole bunch of new programs. So one of them is our COVID webinar series. So last month, we held our first one and it was really targeted on just providing awareness and education about the COVID vaccine for pregnant moms, for breastfeeding moms and talking about the safety and explaining all the information. So it was a big success. And so we are moving forward to doing additional webinars. September, October, November, and December. And we're just focused on educating moms of all demographics, working moms, staying at home moms, ethnic backgrounds statewide, just so they understand the benefits and the risks of COVID and the vaccine so they can make well informed decisions. The topics include the vaccine, prematurity, infant loss and the future motherhood. So more information, you can visit us on Facebook, March of Dines Hawaii for more information on that. Also in 2022, we're going to launch our education and series and support groups. And so we're going to do monthly support groups for working moms and new moms and postpartum and also doing education classes, such as becoming a mom, childbirth and pregnancy classes and more. And so one of the additional things we launched was our WIP board. So this is a group of young women leaders who want to help and get involved. We also launched that, Tricia, I did. Surprise, surprise, I launched a young professionals board. And I did recruit some Chamber of Commerce young professionals to join the WIP board. So we're all in this together. Very awesome. And you're one of the four members for that. Yes. So if you know of any young women that would like to join or men, they can be dads as well. We have the young professionals board. OK. And then we also have our NICU family support program, which supports Kapilani Hospital and their NICU. And it provides education for families, education for staff and then also support for parents. So when a baby is in the NICU, the baby is the patient and the parent is just kind of like a visitor. So all the care goes towards the baby. But the parent, you know, baby is helpless, so the parent has to be there. So we have a NICU family support coordinator that helps with the parents, provide emotional support, education. And then we're also launching to turn that NICU family support coordinator into a neighbor island patient navigator so that when families do travel from a walk from neighbor islands to Oahu, they have a patient navigator that can help them navigate. OK, where in the hospital? This is a huge hospital. Where am I supposed to go?  You know, all those different things. So we're really excited about that. We're also working for the Big Island specifically to increase quality of prenatal care for families on the Big Island with potentially a mobile health ban. And so it'll be a mobile health ban and we want to make it special for Big Island families or for Big Island because it is so rural and we're planning to have like big monster trucks and like a grill so it can go off roading in the dirt roads and really help those families that, you know, maybe have transportation issues or that just live in very rural settings. And let's see what else we're doing. So I have a ton of things up there. What do you think? I think you so you already went over the neighbor island initiatives. What about the Storks Nest program and our partnering with the Am I Home program? You can go ahead. So Storks Nest is a program that March of Dimes has nationally and it's to it's to like motivate women to go to their prenatal care appointments. And it's a shopping card program.  Once they fill out that card, then there's a closet that they can shop and they can get, you know, baby blankets, diapers. So it's fun like who doesn't love a shopping program. And so this one, the Storks Nest, we are partnering with Tripler Hospital and a local sorority here, Zeta Phi Beta, and we want to help military families because military families, you think living on an island, having a baby is hard. But living on an island away from your friends and family and your whole entire support group is even harder. So we're working on doing that for military families. I'm really excited. And then lastly, the My Home program.  So we've been helping them with a diaper drive with donating used clothes, gently used clothing for those families. So we're super excited just to partner with more community partners and just, you know, serve and love the community more. Thanks, Tricia, that those are a lot of programs. And I'm glad that you are keeping busy and, you know, with every single program, there is a like a purpose to it. So I hope that the community knows about that when when they watch this and just like everyone else, whether it's a business or a nonprofit or even as individuals, I know you run into some challenges. So what are some of those challenges that you have encountered so far? You know, our biggest challenge is COVID. It just won't go away. It's a fundraising challenge because we were having to pivot our fundraising events, which funds all of these programs and initiatives. So we're supposed to have our annual Gala this November and we're tentatively pushing it back, postponing it to spring of next year. You know, with the the mayor's orders that came out this week, that was really unfortunate. You know, obviously, everyone's health and safety is number one. And then also it's a challenge for our mamas, you know, like when you're pregnant and you have to go to your doctor's office, now the doctor's offices are changing the visitor role.   So I'm just not going to go to the doctors. And now moms are not getting the prenatal care that they need, which snowballs and like, OK, they might have premature birth, they might have birth defects. So we really want COVID to go away so that we can help help our families. Well, so how can people with the viewers that are out there and the community members that are tuning in, how can they help out? We would greatly appreciate the community support to follow us on Facebook at March of Dimes, Hawaii and also to visit our website, marchofdimes.org. We have lots of free resources and information and also encourage if you know anyone that's pregnant, encourage them to go to the doctors to know their rights, take the time off of work, you know, and make it a priority to get their doctor visits. We also would greatly appreciate volunteering. So volunteer on our young professionals board. We did launch a Neighbor Islands Council as well. So if you live or work on the Neighbor Islands or interested in joining volunteer as guest speakers for our webinar series or even volunteering in our office, you know, we're a small team. We only have about three people in our office. So we do have lots of like filing and organizing projects. So if anyone's interested and then also obviously a donation, you know, donating a gift of your time, talent or treasure, will definitely help us to go a long way. Thanks, Trisha, and we have a couple more minutes. So I want to tie this back into why you are doing this. Why is this work meaningful to you? You know, I think going back to just my personal experience as being a working mom and the challenges that we face and having a miscarriage last year. And I love I wasn't I'm not originally from Hawaii, you know, I'm from California and but I have spent majority of my adulthood in Hawaii and I just love this community. So much and I love our families and we just want to make sure that families have the best possible starts to a successful future. You know, living in Hawaii is one of the most beautiful places in the world to live, but it does present a lot of challenges. We all know how expensive housing is, you know, the job opportunities. You know, there's a lot of challenges that living on an island presents. And so if we have unhealthy babies on top of that, then makes our society even harder to to succeed. And so we just want to make sure that babies have the best possible start and that are healthy. And so that our community community can continue to grow and thrive. You know, and I obviously have a best interest. I have two teenagers. So one day they're going to be parents and just want to make sure that we have great doctors and physicians and technology and systems so that I have I can have healthy grand babies. That's like, wait, that's way too crazy, even say that right now. I'm like, no, my son's 15. So I do not want to think about grand babies for at least 20 years to think about the future. Is there anything else that you would like to add? I just want to say, thank you, Kathleen. Thank you so much for your friendship and for this opportunity just to get our message out there to the masses. And I just I just really appreciate you on this time. Awesome. Let's pull up that last slide. If people would like to get a hold of you, Tricia Petui, how do they go out and doing that? You can email me at pfetuiatmarchofdimes.org or you can visit our website at www.marchofdimes.org. Thank you, Tricia again. And I am grateful for you, for, you know, educating reviewers and for your friendship as well and for coming on the show, even though we had some technical difficulties in the beginning. I appreciate you for that. And thank you to the folks at Things at Kauai as well and to J. Fidel for making shows like this possible. We had Michael helping us out today. So thank you, Michael. And thank you, everyone, for joining us today. Until next time, aloha.


So, you fixed your middle click controls, but you don't understand the rest of the menu. Not a problem. Big thanks to everyone who left extra comments and messages with some other important hot keys. Some of my favorite ones you guys shared were if you hold right click, you can move around with WASD, and use Q to move down, and E to move up. Also if you hold shift, you can select multiple objects at the same time. If you press spacebar, you can cycle through the gizmo modes. You can hide all the gizmos with G, and control tilde lets you flip-flop between local and world rotation. Now again, thanks for sharing the new information, it was super useful. So if you watched the last tutorial, you should have a fairly good understanding how to control the viewport. However, there are three other important main parts of Unreal's menu, and the first one we'll talk about in this video is up here. Here you can press the green arrow to play your game. You can also press alt P, you can pause the game by clicking this, and while paused you can click this to progress the game one frame at a time. You can press escape or click here to stop the game, and at any point if you want to mess with the game as a developer god, you can press F8 or click here.  There are some dots you can click on to give you some more options to look through, but we'll get into those later. You will see the platforms your game has available to you, and before we go any further I just want you to know that you don't need to know every option in every menu. It'll help, but the way I'm going into this series is we're going to introduce you to the most important things first, and as the other things start to become more relevant on your journey in learning Unreal, that is when we'll go into the specifics. But for now, just to give you a basic outline of where things are in the menu, you can save your scene at any time by clicking the floppy on the left, but all of the most important modes in Unreal are going to be in this thing right here. The default is the selection mode, which will feel familiar if you're coming from Unity, but you also have landscape, foliage, mesh, modeling, fracture, brush, and animation modes that you can use to do a lot of really cool stuff that I'll definitely be showing you later. Next to that we have the second most important menu, which is the add to project button, which is where you will go anytime you want to grab any asset that you need from Unreal's massive library. Quixel Bridge contains all the 3D assets you should ever really need for environments and materials, and it's completely free. The marketplace is where you go if you can't find what you're looking for in Quixel Bridge. The content browser is like the asset browser in Unity. You can also find basic actors, lights, shapes, cinematic materials, visual effects, areas, classes, and the actor panel. Next to that you have your blueprints menu, which is where you go when you want to create commands for your game, and next to that you have your sequence menu options. So that is the upper area of Unreal's menu. If you join me next video we will talk about the Outliner menu, what it is, and why it's so useful. And meanwhile, I hope that helps and as always, I hope you have a fantastic day and I'll see you around.