joomla/Component-Builder
joomla
/
Component-Builder
38
19
Fork 11
Code Issues 53 Pull Requests Projects 3 Releases Wiki Activity

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

Amigo 2019-09-26 14:29:14 +02:00
parent d3ab27f263
commit d9427ebe25
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
062-Add-your-own-JCB-packages-to-the-JCB-Communty-Directory.md

@ -32,13 +32,15 @@ Now with the community option you can do what we call 'Share'. Like I have been
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.
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 of this JCB Community Packages.[00:05:53](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m53s) Once they have done all that and pushed up the changes to their repository, they will make a pull request to add the change into the Community Version of this repository. Hope that all makes sense to you. You will 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 will 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
[00:06:36](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m36s)
I'm going to open a terminal. In the terminal I'm simply going to clone this repository. Once it's finished cloning, we are going to change it to that directory. If we list out the items, you will see that it is exactly the same as what we have here on GitHub. It is in literally the same information. [00:07:13](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m13s) It is a folder on your computer. We will then need to go to JCB, extract the package you want to share, and simply place it into this folder. Run this hash.sh script. We are in our JCB program [00:07:39](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m39s) and I want to share this question and answers component. I want to ask that you won't share things that do not work. If you still busy developing the thing then it is not time to share it yet. When it's ready and you know that it works, that means you've compiled it and tested it, and you know it stable, then you want to share it. It doesn't need to be a big component, it could have just one view. It doesn't matter, but it needs to be something other than already what exist. No more new demo components, [00:08:15](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m15s) it need to be something else. Please always check that if you want to contribute something, let it be something that's already there. If there is already one, and you want to improve it, sure then you can do that. You can pull it in, make it better and make it pull request to improve it. Know that we will have to be able to test it, if you're using a key, [00:08:42](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m42s) you can't contribute it without a key back. If someone places a package in the Community and it has a key, then it lockout everybody else, because then only they can improve it. [00:08:59](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m59s) As soon as they take the key away, then everybody else can improve it because there is no key and it doesn't matter. We all can check it out.
I am going to open a terminal. In the terminal I am simply going to clone this repository. Once it is finished cloning, we are going to change it to that directory. If we list out the items, you will see that it is exactly the same as what we have here on GitHub. It is in literally the same information. [00:07:13](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m13s) It is a folder on your computer. We will then need to go to JCB, extract the package you want to share, and simply place it into this folder.<<<<<<<<<<<
Run this hash.sh script. We are in our JCB program [00:07:39](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m39s) and I want to share this question and answers component. I want to ask that you won't share things that do not work. If you still busy developing the thing then it is not time to share it yet. When it's ready and you know that it works, that means you've compiled it and tested it, and you know it stable, then you want to share it. It doesn't need to be a big component, it could have just one view. It doesn't matter, but it needs to be something other than already what exist. No more new demo components, [00:08:15](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m15s) it need to be something else. Please always check that if you want to contribute something, let it be something that's already there. If there is already one, and you want to improve it, sure then you can do that. You can pull it in, make it better and make it pull request to improve it. Know that we will have to be able to test it, if you're using a key, [00:08:42](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m42s) you can't contribute it without a key back. If someone places a package in the Community and it has a key, then it lockout everybody else, because then only they can improve it. [00:08:59](https://www.youtube.com/watch?v=8FplwKKa708&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m59s) As soon as they take the key away, then everybody else can improve it because there is no key and it doesn't matter. We all can check it out.
### Helps Get Projects Going Quite Quickly