From a246f36f960a6513332bef958f5ed1952fb684c6 Mon Sep 17 00:00:00 2001 From: Amigo <49749100+aamigo@users.noreply.github.com> Date: Thu, 26 Sep 2019 11:58:09 +0200 Subject: [PATCH] Updated 062 Add your own JCB packages to the JCB Communty Directory (markdown) --- ...your-own-JCB-packages-to-the-JCB-Communty-Directory.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/062-Add-your-own-JCB-packages-to-the-JCB-Communty-Directory.md b/062-Add-your-own-JCB-packages-to-the-JCB-Communty-Directory.md index 35d8fde..7730227 100644 --- a/062-Add-your-own-JCB-packages-to-the-JCB-Communty-Directory.md +++ b/062-Add-your-own-JCB-packages-to-the-JCB-Communty-Directory.md @@ -6,25 +6,25 @@ [00:00:00](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m00s) (Click on these time links to see Youtube video) -I want to demonstrate the way to add JCB packages to the Community Directory. The moment if you go to Import JCB Packages, there is now a new tab called Community Packages. We would like to encourage all of you to start sharing packages. The main focus or purpose for it would become, to be a quick start for developing Components. [00:00:28](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m28s) It could serve as a back up for yourself to easily pull on old packages that you've developed. To maybe have a specific feature, for example linking your Joomla users into your component. I know have some components that does that. I often want to reuse that. [00:00:52](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m52s) You can now with this new idea be able to import that component over and over without merging it with the old version, but creating a new component, including fields and everything else. That is a way you will be able to quickly start a new project. You don't need to do all that over again and again. +I want to demonstrate the way to add JCB packages to the Community Directory. The moment if you go to Import JCB Packages, there is now a new tab called Community Packages. We would like to encourage all of you to start sharing packages. The main focus or purpose for it would become, to be a quick start for developing Components. [00:00:28](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m28s) It could serve as a back up for yourself to easily pull on old packages that you have developed. To maybe have a specific feature, for example linking your Joomla users into your component. I know have some components that does that. I often want to reuse that. [00:00:52](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m52s) You can now with this new idea be able to import that component over and over without merging it with the old version, but creating a new component, including fields and everything else. That is a way you will be able to quickly start a new project. You do not need to do all that over again. ### The Clone Feature [00:01:17](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m17s) -It's sort of similar as the Clone feature that now has become available. The JCB components now have a Clone feature. You could select a component and you can clone it. In cloning it creates a exact copy of the component, but not linked to the components. Even did Admin Views. You will see it creates a new Admin View. [00:01:44](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m44s) The same goes for the fields. You can create a whole new set of fields, specifically for this component. You will see it have the same Suffix (EO). That is the Clone feature. +It is sort of similar as the Clone feature that now has become available. The JCB components now have a Clone feature. You could select a component and you can clone it. In cloning it creates a exact copy of the component, but not linked to the components. Even did Admin Views. You will see that it creates a new Admin View. [00:01:44](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m44s) The same goes for the fields. You can create a whole new set of fields, specifically for this component. You will see it have the same Suffix (EO). That is the Clone feature. <<<<<< ### The Import Feature - Merge Yes Or No [00:02:00](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m00s) -The import feature has the same functionality. If I was to go and say let's import the Demo component, then once we have the component from GitHub, we will see that it has this Merge option Yes or No. Remember we already have the Demo component, and it is exactly the same component, but I don't want it to update this one, [00:02:33](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m33s) I want it to bring it in as a new component, and then I will tick this to No. It does give you a little explanation and tells you the validation rules, Field types, snippet, languages, and language strings. These things will still be merged, that simply is unavoidable. If you want to see what happens under the hood, click on continue. What it will do now, [00:03:03](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m03s) it will give you a whole lot of information of the import. And also whatever files it moved. It created a new component. It didn't update the old one. That is a very nice option, because you can quickly start with this component without affecting this one. Now you'll see that even the admin view is dislocated, it's not the same admin View. The same again with the fields. If we look at the fields, you'll see it also has the (Ra) [00:03:36](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m36s) Suffix to it. This name doesn't anywhere appear in the compiled version of the components, it's all system names. This (Ra) will just be for your own to know that this field belongs to this component and so on. That is what the new JCB Package Import option is been improved to manage. +The import feature has the same functionality. If for instance we would import the Demo component, then once we have the component from GitHub, we will see that it has this Merge option 'Yes' or 'No'. Remember we already have the Demo component, and it is exactly the same component, but I do not want it to update this one, [00:02:33](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m33s) I want it to bring it in as a new component, and then I will tick this to 'No'. It does give you a little explanation and tells you the validation rules, Field types, snippet, languages, and language strings. These things will still be merged, that simply is unavoidable. If you want to see what happens under the hood, click on 'Continue'. [00:03:03](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m03s) It will give you a whole lot of information of the import and also whatever files it moved. It created a new component. It did not update the old one. That is a very nice option, because you can quickly start with this component without affecting this one. Now you will see that even the Admin View is dislocated, it is not the same Admin View. The same again with the fields. If we look at the fields, you will see it also has the (Ra) Suffix to it.[00:03:36](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m36s) This name does not appear anywhere in the compiled version of the components, it is all system names. This (Ra) will just be for you to know that this field belongs to this component and so on. That is what the new JCB Package Import option has been improved to manage. ### Community Option - Sharing [00:04:01](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m01s) -Now with the community option you can do what we want to call share. Like I've been doing, sharing many information with all of you, components, tools. The idea that all of you would have this attitude of giving back to the community and the other option is that if you want to distribute a package, at the same time, maybe get some marketing, this is also going to be doing that. [00:04:33](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m33s) Let me illustrate to you the process of getting a package into the Community Packages. We are going to use GitHub. This repository, JCB community Packages, this is the URL vdm-io/JCB-Community-Packages. [00:04:57](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m57s) You will need to fork this package. I'm not going to teach you how to use GitHub, neither how to use Git. +Now with the community option you can do what we call 'Share'. Like I have been doing, sharing many information with all of you, components, tools. The idea that all of you would have this attitude of giving back to the community and the other option is that if you want to distribute a package, at the same time, maybe get some marketing, this is also going to be doing that. [00:04:33](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m33s) Let me illustrate to you the process of getting a package into the Community Packages. We are going to use GitHub. This repository, JCB community Packages, this is the URL vdm-io/JCB-Community-Packages. [00:04:57](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m57s) You will need to fork this package. I am not going to teach you how to use GitHub, neither how to use Git.<<<<<<<<<<<< ### Demonstration - When Adding A Package Must Start Forking The Repository