Updated 062 Add your own JCB packages to the JCB Communty Directory (markdown)

Amigo 2019-09-26 12:03:44 +02:00
parent a246f36f96
commit d3ab27f263
1 changed files with 5 additions and 3 deletions

@ -12,7 +12,7 @@ I want to demonstrate the way to add JCB packages to the Community Directory. Th
[00:01:17](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m17s)
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. <<<<<<
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
@ -24,13 +24,15 @@ The import feature has the same functionality. If for instance we would import
[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 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.<<<<<<<<<<<<
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
[00:05:06](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m06s)
I'm going to illustrate it by doing what you need to do, demonstrating it to you. I'm not going to teach you how to do this in a more thorough way. You need to go and study GitHub and Git specifically to be able to manage this. What will happen is anyone who wants to add a package, must start by forking the repository. Once it's been forked, they need to clone it down to their the developing environment where they have JCB. Or to where they can move a JCB Package. Because at the end of the day they need to add their package which they want to contribute to their forked version [00:05:53](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m53s) of this JCB Community Packages. Once they have done all that and pushed up the changes to their repository, they'll make a pull request to add the change into the Community Version of this repository. Hope that all makes sense to you. You'll get the URL (Clone or Download) [00:06:14](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m14s) on your own repository, copy that and then you'll go to your developing environment. Hopefully it will be Linux because you need to run a hash.sh script. It needs to be a hash environment. You could run it in a VM where ever you want, just get it going.
I am going to illustrate what you need to do, demonstrating it to you. You need to go and study GitHub and Git specifically to be able to manage this. What will happen is anyone who wants to add a package, must start by forking the repository.<<<<<<<<<<<
Once it has been forked, they need to clone it down to their the developing environment where they have JCB. Or to where they can move a JCB Package. Because at the end of the day they need to add their package which they want to contribute to their forked version [00:05:53](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m53s) of this JCB Community Packages. Once they have done all that and pushed up the changes to their repository, they'll make a pull request to add the change into the Community Version of this repository. Hope that all makes sense to you. You'll get the URL (Clone or Download) [00:06:14](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m14s) on your own repository, copy that and then you'll go to your developing environment. Hopefully it will be Linux because you need to run a hash.sh script. It needs to be a hash environment. You could run it in a VM where ever you want, just get it going.
### Open A Terminal - Cloning The Repository