Updated 070 How to change the License Template in JCB (markdown)

Amigo 2019-10-03 11:03:34 +02:00
parent f6094ddd45
commit f6cf0e3ced

@ -11,25 +11,25 @@ I would like to talk to you about changing the licence template For your compone
[00:00:57](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m57s)
Now let me show you how that works. First of all It must be done when the Joomla Component Builder is already installed on your website. I have a website Joomla Mount. In administrator, components, com_componentbuilder. There is a folder called compiler [00:01:21](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m21s) and in it there is 5 txt files. Going back to the component, there is 5 files. I see it's also using the HTML. That one will not come out right. These ones with the .txt's, the one that you would select, any one of those to be the template that you are going to use.
Now let me show you how that works. First of all, It must be done when the Joomla Component Builder is already installed on your website. I have a website Joomla Mount. In administrator, components, com_componentbuilder. There is a folder called compiler [00:01:21](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m21s) and in it, there are 5 txt files. Going back to the component, there are 5 files. I see it's also using the HTML. That one will not turn out right. These ones with the .txt's, the one that you would select, any one of those to be the template that you are going to use.
### Changing The Templates
[00:01:50](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m50s)
If you are using one of the existing templates and change it, then with the next update your changes will be overwritten. You want to do it in a way that preserved your changes. The way you do that is you go back to the compiler area and then select [00:02:13](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m13s) select the default one. And maybe you don't like this(see video). You want to take that out. Maybe you don't want to support or show that you use JCB. Take that out. I really don't mind. I'm a supporter of open-source that [00:02:36](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m36s) I don't mind you changing anything except @copyright and @license, that I want you to leave. These placeholders are being replaced by the settings of your component. [00:02:58](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m58s) You could still tweak this, but do it in the component. But leave the license and copyright notice that people can know how to use your program. Having said all that, you should realize that a lot of the code between all the components that JCB built are more or less the same. It's little names here and there. That's really the only thing you are copyrighting. [00:03:26](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m26s) Just keep that in mind. You're not copyrighting every little line, you are copyrighting the changes. The idea of how built is already been copyrighted either by Joomla or by JCB. Keep that in the back of your head. You are copyrighting the changes you've made and that which you have done. When someone uses your component they won't think about it that way. I don't mind and I don't think [00:04:00](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m00s) anyone would because we are an open source community. If you do change your program to a proprietary software, you might have to look at what would be the implication. I think there's a possibility that some areas cannot be made proprietary, because of the Open Source license already is on JCB [00:04:28](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m28s) and on everything that it has done. I'm not sure I'm not a lawyer. I don't know how all that works out. I want to give many people so much freedom and I'm not going to check people up. Someone else may, there is places that might feel obligated to do so. I want to be busy with code. Writing programs. [00:04:58](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m58s)
If you are using one of the existing templates and change it, then with the next update your changes will be overwritten. You want to do it in a way that preserves your changes. The way you do that is you go back to the compiler area and then select [00:02:13](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m13s) select the default one. And maybe you don't like this(see video). You want to take that out. Maybe you don't want to support or show that you use JCB. Take that out. I really don't mind. I'm a supporter of open-source that [00:02:36](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m36s) I don't mind you changing anything except `@copyright` and `@license`, that I want you to leave. These placeholders are being replaced by the settings of your component. [00:02:58](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m58s) You could still tweak this, but do it in the component. But leave the license and copyright notice that people can know how to use your program. Having said all that, you should realize that a lot of the code between all the components that JCB built is more or less the same. It's little names here and there. That's really the only thing you are copyrighting. [00:03:26](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m26s) Just keep that in mind. You're not copyrighting every little line, you are copyrighting the changes. The idea of how builds is already been copyrighted either by Joomla or by JCB. Keep that in the back of your head. You are copyrighting the changes you've made and that which you have done. When someone uses your component they won't think about it that way. I don't mind and I don't think [00:04:00](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m00s) anyone would because we are an open-source community. If you do change your program to proprietary software, you might have to look at what would be the implication. I think there's a possibility that some areas cannot be made proprietary, because of the Open Source license already is on JCB [00:04:28](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m28s) and on everything that it has done. I'm not sure I'm not a lawyer. I don't know how all that works out. I want to give many people so much freedom and I'm not going to check people up. Someone else may, there are places that might feel obligated to do so. I want to be busy with code. Writing programs. [00:04:58](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m58s)
This is how you change the template more or less.
### Placeholders - Helper, Compiler, Infusion
[00:05:00](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m00s)
You could leave things in. You can check between them, you will see the way to know what is all the placeholders that are available, is to go to the helper, compiler. It's that infusion one. You should look at the infusion. You will see the COMPANYNAME , CREATIONDATE, BUILDDATE, AUTHOR, AUTHOREMIAL, AUTHORWEBSITE, COPYRIGHT, LICENSE, VERSION, ACTUALVERSION, Component_names, SHORT_DESCRIPTION, DESCRIPTION, COMP_IMAGES_TYPE, ACCESS_SECTION, most of these aesthetic content placeholders could be used. Some of them won't make sense, like custom helper [00:06:01](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m01s) script. It's going to add the custom helper script in that lines. It's not going to come out right. These placeholders are really from where the content is being updated in the file. You'll see it is the same. This is a new method we are using to put it in the >hhh, ###. The CREATIONDATE is the one it [00:06:31](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m31s) gets from the infusion which is found in helper, compiler. You can check out these and use any of those as you like. The point is it's best to leave this in. At least tell people who did it, that someone can be blamed. If you save now, it'll still work. The default template will be updated.
You could leave things in. You can check between them, you will see the way to know what is all the placeholders that are available, is to go to the helper, compiler. It's that infusion is one. You should look at the infusion. You will see the `COMPANYNAME , CREATIONDATE, BUILDDATE, AUTHOR, AUTHOREMIAL, AUTHORWEBSITE, COPYRIGHT, LICENSE, VERSION, ACTUALVERSION, Component_names, SHORT_DESCRIPTION, DESCRIPTION, COMP_IMAGES_TYPE, ACCESS_SECTION,` most of these static content placeholders could be used. Some of them won't make sense, like custom helper [00:06:01](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m01s) script. It's going to add the custom helper script in that lines. It's not going to turn out right. These placeholders are really from where the content is being updated in the file. You'll see it is the same. This is a new method we are using to put it in the >hhh, ###. The `CREATIONDATE` is the one it [00:06:31](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m31s) gets from the infusion which is found in helper, compiler. You can check out these and use any of those as you like. The point is it's best to leave this in. At least tell people who did it, that someone can be blamed. If you save now, it'll still work. The default template will be updated.
### Suggestion - Save As... - Give Your Name - Save - New File
[00:07:03](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m03s)
But the problem is if we are going to release a new update for JCB and you install that update, it is going to override this. What we would suggest is by saying Save As... Give it your name, I'm going to say default_q.txt. Save now and we have a new file. We can go back to JCB. [00:07:32](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m32s) Refresh the component area, we'll see that there it is the new template. If I save and compile this component, it will use the new template. Let me show you that. In the code we go down to sermon distributor, we open any of its files. And that's how it's current template looks like (see video). [00:08:03](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m03s) There is the current template all the way down to there. Let's compile and see. It'll update every file across the spectrum. We are going to say Sermon Distributor and compile, install it. Let's go check out our template. If we scroll up we will see it have the new [00:08:36](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m36s) template and it is being used, no longer the old one. It's the same file, but it refreshed it in the background.
But the problem is if we are going to release a new update for JCB and you install that update, it is going to override this. What we would suggest is by saying Save As... Give it your name, I'm going to say `default_q.txt`. Save now and we have a new file. We can go back to JCB. [00:07:32](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m32s) Refresh the component area, we'll see that there it is the new template. If I save and compile this component, it will use the new template. Let me show you that. In the code we go down to sermon distributor, we open any of its files. And that's how it's current template looks like (see video). [00:08:03](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m03s) There is the current template all the way down to there. Let's compile and see. It'll update every file across the spectrum. We are going to say Sermon Distributor and compile and install it. Let's go check out our template. If we scroll up we will see it have the new [00:08:36](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m36s) template and it is being used, no longer the old one. It's the same file, but it refreshed it in the background.
That how it works. Easy To change the license and that's really means you can make it a small or is big as you like. Any shape and size. Just keep in mind that you need to escape it and unescape it. [00:09:02](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m02s) Because otherwise it will mess up the code. That is how you can change the license template. Make a wise decisions and how you deal with this area. I don't want to say much more and put restraints up, because I know that the initial desire was to give everybody as much freedom as they need.
That how it works. Easy To change the license and that really means you can make it a small or is big as you like, any shape and size. Just keep in mind that you need to escape it and unescape it [00:09:02](https://www.youtube.com/watch?v=AveBf6YZzmo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m02s) because otherwise, it will mess up the code. That is how you can change the license template. Make wise decisions and how you deal with this area. I don't want to say much more and put restraints up, because the initial desire was to give everybody as much freedom as they need.