Updated Home (markdown)
parent
53199c3f41
commit
38bbd7f5a8
2
Home.md
2
Home.md
@ -17,7 +17,7 @@ For example, open a view and read through the script. If you use NetBeans you ca
|
||||
|
||||
Developers familiar with let’s say the Google API have an advantage with understanding how JCB works. They will immediately see the JCB application is implementing the Joomla! API repeatedly. I am not in the habit of reinventing things and as such I'm trying to stay as close to Joomla! coding conventions as possible. As I become aware of better ways to implement it, I would like to enhance what is already written and also employ it in what has not been coded yet. I am open to better ways of doing something already implemented or ideas for code I am in the process of developing. Please communicate that to me. I will gladly do what is necessary to change the code and implement your suggestion.
|
||||
|
||||
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 is 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.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user