Thank you for joining me for this video using modules. For Sirboy University, I'm Bob Cusick. The whole concept of modules in Sirboy is to promote code reuse so that you don't have to recreate the same types of methods over and over and over again in every single solution. Models are solutions themselves so they can contain anything, global variables, global methods, forms, relations, valuests, media, and they can even contain other modules. More on that in just a minute. To create a module, you just create a normal solution. And then over here in the properties for the solution type, rather than normal, you would choose module. Now you don't have to choose module for a solution to be used as a module within other solutions. Changing the solution type to module will suppress it from the open dialog and it will suppress it from the web client open dialog. But you can use any solution as a module in any other solution. So I've set up a simple module here. It's very straightforward. I've set up a couple of global methods when it gets the current date and one that gets the current form context. And I've created a couple of variables. Company ID, contact ID, the security group and the security user IDs. And I've also created some valuests. There's a simple yes no valuest. And a yes no valuest that returns an integer of one for yes and zero for no. And I've put in a bunch of media files. These are little icons. A module is a great place to store graphics. That way you're not having all of these icons all over the place. And if you want to add icons or change icons, you can go ahead and do that in one place in one module. And then all of your other solutions that use that module will be instantly updated. If you're doing a SAS application or you're doing a piece of commercial software, it's a lot easier to replace a single module that has media that change rather than redoing the whole solution or re uploading the whole solution just because you change a couple of graphics. So now we have our sample module. And I now want to include it into my main solution. So I have a solution here called SU modules. Close this up. And inside of my modules solution, there are no globals. There are no variables. There are no valuests. And there's no media at all. So now I want to go ahead and I want to add my module to the solution. It's very simple and straightforward. Simply open up your all solutions, right-click and say add as module. When you do that, if you notice, there's an SICon and it has an M there telling you that this solution is a module and it's now active. So in my main solution, if you notice down here on the modules, I have my sample module. And if I expand this node, it has all of the normal objects you would expect. Here's my global methods. Here's my global variables. Here's my valuests and my media. Now the cool thing about Servoy is that you can modify these valuests, even though it's being used as a module. So I can double-click it. And here I can edit my valuests. In my main solution, I have a single form. It's called customers. So I'm going to open this up. I'm going to right-click and say open and form designer. And as you can see, it's a very simple form. But I wanted to show you how you can use these objects that are stored in the module, but use them in your main solution. So the first thing that we're going to take a look at is the media. So I'm going to click on my button. And I'm going to come over here to the image media. And I'm going to double-click. And now this dialog box is going to show me that I have a bunch of media. I'm going to turn on Preview so you can see them. So I can go down this list and see all of the icons that I have available. Now notice that after the name of each one, in brackets, it says, SU sample module. This tells you that the media is not stored in this particular solution, but it's stored instead inside of a module. So let's add this control pause to this button. So I'm going to say, OK, and there you go. There's the icon. Now here's another example. Here I have a combo box that is on a form variable that I've created. And I want to attach a valueless to it. But remember, I don't have any valueless in the native solution. I only have valueless in my module. So if I double-click valueless here, again, it shows me the mod yes, no, and the mod yes, no integer coming from the sample module. I'm going to click this one, click OK. Now when I click save, and we open it up in client, we'll see I get the yes, no valueless that's coming from the module. I also have my icon here on my button. Now there is something that you have to keep in mind that's absolutely critical when you use modules. And that's your naming conventions. Because when servoy loads up the SU modules solution, it will load up this sample module as well. And as far as servoy is concerned, this hierarchy is flat. That means that any valueless, global methods, relations, forms, media, whatever is in this sample module, it thinks that it was created natively inside the SU module solution. So there's no difference internally to servoy, whether you use a module or you create them natively inside of the solution itself. But it does make a big difference in naming conventions, because you have to have absolutely unique names for forms, valueless, global variables, global methods, and your media. If you don't, then you'll get an error, and you won't be able to include the module. So I'm going to go up here to my SVY core, and that's also a module. I'm going to click Add as Module. And now it's asking me what is the parent solution? Because I can add the module to my module, or I can add it to this parent solution, which is SU modules. So I'll add it to the parent solution. And now here I have two modules. I have my sample module and my servoy core. Now my servoy core could also contain other modules. And if it did, they would all show up here underneath this module's list. Inside of servoy core, there's forms. There's also globals. There's variables. So what's really cool now is I have the benefit of all of these objects and all of these things that I can reuse in my parent solution called SU modules. I don't have to recode all of that stuff. It just happens for me automatically. Remember that modules are recursive. So you can have modules that are in modules, in modules, in modules. And they don't have to be anything special. Any servoy solution can be a module to any other servoy solution. As long as you've got a good naming convention, modules are definitely the way to go for code reuse. Thanks for watching.