Updated 004 General Planning (markdown)

004-General-Planning.md

@@ -8,4 +8,6 @@ By illustrating what is the best convention of implementation, Component Builder
 
 When Sermon Distributor is going to be build, [00:02:20](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m20s) back end views need to be set up, because we want these features inside of the component. That is the sermons. We have a list view of [00:02:33](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m33s) the sermons as well as an editing view of the sermons. They share a common database table [00:02:51](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m51s) although they represent two views: a list view and an edit view. [00:03:27](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m27s) The editable view is in relation to the back end connection of the database itself. The back end usually forms the connection to the database. The front end is more dynamic. These things will take quite a lot of explanation if you are new to coding, PHP, JavaScript and CSS.  [00:04:21](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m21s)
 
-The site views and custom back end views are mostly the same kind of implementation, both drawing their data from the Dynamic Get feature in Component Builder. Think of these three as working as a team, while the back end views stand as the database for these. You need to set these up first. Add them to all the necessary fields which will then mapped the database [00:05:16](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m16s) columns, which then through the Dynamic Get connect to formulate a data model. Which can be reused in your custom back end and in your site views.  Back end views are very tightly connected to database structures, even if you look at Component Builder itself, you have what is called components, and if you open one, it has fields in it. If you want to go to the database, [00:06:02](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m02s) and open Component Builder, components table, if you click on structure you would see the fields there. All these names [00:06:31](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m31s) are actually mapping directly into the database, add licence. These names are alphabetical. It directly maps to the database and it is in a way editing the database through this view. When it comes to the Components, your back end views are all being limited to this kind of structure, and is not a limitation on Component Builders behalf. It is the way Joomla [00:07:13](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m13s) wants to implement it by doing it this way. Your class, your model, your controllers and everything else behave correctly because of that implementation. It is a major limitation but that is the Joomla API's implementation. If you want to go beyond that kind of infrastructure you must probably need to look at another way of using Component Builder. We only implemented it that way so that your back end views directed maps to the database. We know that from time to time there is back end views that do not have their own Database, but rather takes saved information in the database. Either from other third-party components or even your own component, because we know that you would like to take that information and remodel it into a spreadsheet. [00:08:17](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m17s) Or into a chart or any other kind of way we added this custom back end views, which behaves on the same Dynamics as the site views. We are trying to give you best of both worlds. First being that strong tightening manage data sets, which relates directly to the view and the list view and so forth. At the same time the option of adding a custom back end view, which can be dynamic and you can do custom scripting in it.[00:09:08](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m08s) First you need to know your back end views and then any possible custom views that combines back end view. In the future we haven't done so yet. Possibly takes Statistics and Sermons and Preachers and Series, because these Statistics are taking only the downloads, where as Preachers has in them a field called hits. And Sermons also have a field called hits. When someone opens one, downloading isn't necessarily so does series's. [00:09:55](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m55s) But statistics only counts the downloads of the sermons, we could possibly add an extra custom back end view called; Analysis. Then in Analysis we can use the Dynamic Get Option to get data from all through those tables. [00:10:29](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m29s) These tables; Preacher table, series table. Let us shortened it by removing statisctics, and then do modelling. [00:11:15](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m15s)Nitty Modelling the data possibly end up with a whole new Data structure which we can place into a table, or into a chart. In that view which means that it is now dynamic, and no longer directly connected to the Database. [00:11:38](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m38s) These above views won't have an edit view, it will be a single view. Displaying rows of analysis data. From multiple back end Database tables. And this Can also be done on the front of the site. [00:11:59](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m59s) We can put this whole Get Feature under get and we can give it a name and call it the Analysis Get. [00:12:17](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m17s) Get Analysis, We could call it Line truncated
+The site views and custom back end views are mostly the same kind of implementation, both drawing their data from the Dynamic Get feature in Component Builder. Think of these three as working as a team, while the back end views stand as the database for these. You need to set these up first. Add them to all the necessary fields that will then be mapped to the database [00:05:16](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m16s) columns, which then through the Dynamic Get connect to formulate a data model. This can be reused in your custom back end and in your site views.
+
+Back end views are very tightly connected to database structures. If you look at Component Builder itself, you have what is called components, and if you open one, it has fields in it. If you want to go to the database, [00:06:02](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m02s) and open Component Builder, components table, if you click on structure you would see the fields there. All these names [00:06:31](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m31s) are actually mapping directly into the database, add licence. These names are alphabetical. It directly maps to the database and it is in a way editing the database through this view. When it comes to the Components, your back end views are all being limited to this kind of structure, and is not a limitation on Component Builders behalf. It is the way Joomla [00:07:13](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m13s) wants to implement it by doing it this way. Your class, your model, your controllers and everything else behave correctly because of that implementation. It is a major limitation but that is the Joomla API's implementation. If you want to go beyond that kind of infrastructure you must probably need to look at another way of using Component Builder. We only implemented it that way so that your back end views directed maps to the database. We know that from time to time there is back end views that do not have their own Database, but rather takes saved information in the database. Either from other third-party components or even your own component, because we know that you would like to take that information and remodel it into a spreadsheet. [00:08:17](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m17s) Or into a chart or any other kind of way we added this custom back end views, which behaves on the same Dynamics as the site views. We are trying to give you best of both worlds. First being that strong tightening manage data sets, which relates directly to the view and the list view and so forth. At the same time the option of adding a custom back end view, which can be dynamic and you can do custom scripting in it.[00:09:08](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m08s) First you need to know your back end views and then any possible custom views that combines back end view. In the future we haven't done so yet. Possibly takes Statistics and Sermons and Preachers and Series, because these Statistics are taking only the downloads, where as Preachers has in them a field called hits. And Sermons also have a field called hits. When someone opens one, downloading isn't necessarily so does series's. [00:09:55](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m55s) But statistics only counts the downloads of the sermons, we could possibly add an extra custom back end view called; Analysis. Then in Analysis we can use the Dynamic Get Option to get data from all through those tables. [00:10:29](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m29s) These tables; Preacher table, series table. Let us shortened it by removing statisctics, and then do modelling. [00:11:15](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m15s)Nitty Modelling the data possibly end up with a whole new Data structure which we can place into a table, or into a chart. In that view which means that it is now dynamic, and no longer directly connected to the Database. [00:11:38](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m38s) These above views won't have an edit view, it will be a single view. Displaying rows of analysis data. From multiple back end Database tables. And this Can also be done on the front of the site. [00:11:59](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m59s) We can put this whole Get Feature under get and we can give it a name and call it the Analysis Get. [00:12:17](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m17s) Get Analysis, We could call it that and the analysis view used to get analysis. To get the data and then takes that data and displays it on a page and the same can be done [00:12:37](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m37s) to the front. The same Dynamic Get can be use in the front again. That is how Component Builder works. If you are not looking at the fields itself, the fields is a discussion on its own, but this which I have typed out are very basic and alimentary. It is what you need to know before coming to Component Builder. You need to know what you want to achieve. [00:13:05](https://wwLine truncated