joomla/Component-Builder
joomla/Component-Builder
39
23
Fork 11
Code Issues 80 Pull Requests Projects 4 Wiki Activity

Updated Home (markdown)

Joseph Geller 2018-09-15 21:20:23 -05:00
parent 38bbd7f5a8
commit 0e31681d96
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Home.md

@ -9,7 +9,7 @@ The [list of videos](https://www.youtube.com/playlist?list=PLQRGFI8XZ_wtGvPQZWBf
# [Intro](https://youtu.be/9evJkBTnKxE?list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE?list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE) # [Intro](https://youtu.be/9evJkBTnKxE?list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE?list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE)
+ Basic introduction + Basic introduction
Joomla! Component Builder (hereafter known as JCB) was built for those who know the PHP programming language. If you don't know PHP, there are some great places to learn it. One of the few I would recommend is http://www.lynda.com and you can go to their website and search for PHP. You will find many courses that should get you on your way. If you don't know CSS, JavaScript, and HTML then you definitely need to go visit this website and ones similar to it and get that knowledge. JCB was not created for those who have no development skills. Joomla! Component Builder (hereafter known as JCB) was built for those who know the PHP programming language. If you don't know PHP, there are some great places to learn it. One of the few I would recommend is [Lynda.com] (https://www.lynda.com/) and you can go to the website and search for PHP. You will find many courses that should get you on your way. If you don't know CSS, JavaScript, and HTML then you definitely need to go visit this website and ones similar to it and get that knowledge. JCB was not created for those who have no development skills.
I developed JCB for myself as a Joomla! Component developer to easily and quickly get the bulk of the code common to most Joomla! Components so I could focus on the custom code which goes beyond the norm. If you don't have an understanding of the Joomla! API, you will be at a disadvantage. It's not that difficult to get this knowledge, but you do need to be able to read PHP and build a Joomla! web site. Understanding the Joomla API requires an understanding of Object Oriented Programming (OOP) and the classes, methods and properties in the Joomla! core. A good way to do this is to build a Joomla! web site without any installed extensions. Then, look at its directory, folders and files. Become familiar with the many models, views and controllers (MVC) within the directory structure. I developed JCB for myself as a Joomla! Component developer to easily and quickly get the bulk of the code common to most Joomla! Components so I could focus on the custom code which goes beyond the norm. If you don't have an understanding of the Joomla! API, you will be at a disadvantage. It's not that difficult to get this knowledge, but you do need to be able to read PHP and build a Joomla! web site. Understanding the Joomla API requires an understanding of Object Oriented Programming (OOP) and the classes, methods and properties in the Joomla! core. A good way to do this is to build a Joomla! web site without any installed extensions. Then, look at its directory, folders and files. Become familiar with the many models, views and controllers (MVC) within the directory structure.
@ -19,7 +19,7 @@ Developers familiar with let’s say the Google API have an advantage with under
I have and continue to do the bulk of the work developing JCB. If it’s not a serious issue with JCB requiring my involvement and instead is an issue within your component builds you must be willing to get your hands dirty. If you built something and it doesn't work you need to debug it. The best way to do this is to build a local sandbox environment as I do. I have PHP, MySQL and Joomla. If I was to open a browser I would type in local followed by VDM as an example. I have a few sites here and they are what we will be working in throughout this manual. One being developed is this Bowler component. Other sites are on the server so I use a small script on my server to change to another site let's say Builder.VDM which is another site that’s loading some of the best displays that I'm working on. So, I add an administrator to that, open the backend and log in to run in a sandbox environment. What are the advantages? I have and continue to do the bulk of the work developing JCB. If it’s not a serious issue with JCB requiring my involvement and instead is an issue within your component builds you must be willing to get your hands dirty. If you built something and it doesn't work you need to debug it. The best way to do this is to build a local sandbox environment as I do. I have PHP, MySQL and Joomla. If I was to open a browser I would type in local followed by VDM as an example. I have a few sites here and they are what we will be working in throughout this manual. One being developed is this Bowler component. Other sites are on the server so I use a small script on my server to change to another site let's say Builder.VDM which is another site that’s loading some of the best displays that I'm working on. So, I add an administrator to that, open the backend and log in to run in a sandbox environment. What are the advantages?
Not being exposed to the Internet is one advantage. Those of you that already have a sandbox environment are familiar with all these advantages but for those of you who don't, you can work offline most of the time plus add some things like XDEBUG and other scripts which help you debug your application very easily. Why is online development not a good solution? It is time consuming and difficult to build an online server and expensive; it's much easier and less costly to develop offline. If you don't know how to do that please visit [Lynda.com](https://www.lynda.com/) and look at a course called Up and Running with Linux for PHP Developers by John Peck.[Linux for PHP Developers by John Peck](https://www.lynda.com/Linux-tutorials/Linux-PHP-Developers/587676-2.html?srchtrk=index%3a1%0alinktypeid%3a2%0aq%3aUp+and+Running+with+Linux+for+PHP+Developers%0apage%3a1%0as) This is an excellent course to get your own local developing environment set up. I Don't know if this URL is going to be helpful, but Up and Running with Apache for Linux PHP developers which I watched many moons ago has been very helpful to get my initial sandbox set up and ones after that. It will probably be beneficial for you to read also. You'll find you get better as you find better ways, but it's a good place to start. Not being exposed to the Internet is one advantage. Those of you that already have a sandbox environment are familiar with all these advantages but for those of you who don't, you can work offline most of the time plus add some things like XDEBUG and other scripts which help you debug your application very easily. Why is online development not a good solution? It is time consuming and difficult to build an online server and expensive; it's much easier and less costly to develop offline. If you don't know how to do that please visit [Lynda.com](https://www.lynda.com/) and look at a course called [Linux for PHP Developers by John Peck](https://www.lynda.com/Linux-tutorials/Linux-PHP-Developers/587676-2.html?srchtrk=index%3a1%0alinktypeid%3a2%0aq%3aUp+and+Running+with+Linux+for+PHP+Developers%0apage%3a1%0as) This is an excellent course to get your own local developing environment set up. I Don't know if this URL is going to be helpful, but Up and Running with Apache for Linux PHP developers which I watched many moons ago has been very helpful to get my initial sandbox set up and ones after that. It will probably be beneficial for you to read also. You'll find you get better as you find better ways, but it's a good place to start.
The best place for functions to be functional is offline. If you're going to develop online, please realize there may be security risks, especially when you've compiled an application. It places it in your temporary folder, which can be accessed from anywhere. Anyone can access your temporary folder on your server or your website. You can delete the application from there immediately with a button which I'll show you later but it unsafe. The purpose of the application was to create a development environment where you can safely explore all aspects of the environment you have installed. So, I would still suggest you develop offline. The best place for functions to be functional is offline. If you're going to develop online, please realize there may be security risks, especially when you've compiled an application. It places it in your temporary folder, which can be accessed from anywhere. Anyone can access your temporary folder on your server or your website. You can delete the application from there immediately with a button which I'll show you later but it unsafe. The purpose of the application was to create a development environment where you can safely explore all aspects of the environment you have installed. So, I would still suggest you develop offline.