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

Updated 004 General Planning (markdown)

Amigo 2019-05-17 12:07:56 +02:00
parent 0282020554
commit 70d9166dbf
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
004-General-Planning.md

@ -24,6 +24,12 @@ The way to add a view to a component is different from the way to create a view.
If you start building a component, you might feel lost if you do not know where you are going. [00:16:48](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h16m48s) This will help you know if you need to set up these views. You need to add these fields to those views. (This kind of information and knowing how to construct it this is something that you need to know before hand.) You can always add more fields and more views. [00:17:23](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h17m23s) Component Builder cannot decide that for you. You have to create all of these fields before you can add them into a view. This line are seen as a view although when it's compiled, it will represent two views. It is in Component Builder's component back end views. It's seen as one view. [00:17:50](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h17m50s)
These fields will need to be created before they can be added to this view. The nice thing is the name field which you can create once and reuse three times. The hits are already added by default so you don't need to add hits field. [00:18:17](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h18m17s) The default fields are showing you which fields you don't need to add but are added dynamically. To each back end view there is a custom back end view. The purpose is that it doesn't directly relate to a single database. That gives you the option of pulling from multiple databases. Modelling the data and displaying it, it is a quick overview on how to get started with a component. [00:18:57](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h18m57s)
These fields will need to be created before they can be added to this view. The nice thing is the name field which you can create once and reuse three times. The hits are already added by default so you don't need to add hits field. [00:18:17](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h18m17s) The default fields are showing you which fields you don't need to add but are added dynamically. To each back end view there is a custom back end view. The purpose is that it doesn't directly relate to a single database. This gives you the option of pulling from multiple databases. Modelling the data and displaying it, it is a quick overview on how to get started with a component. [00:18:57](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h18m57s)
We will be starting at fields. It seems turned around. You might feel we must start at the component, and then build the views, and then build the fields! [00:19:24](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h19m24s) You can after having created the Component, you can click your own admin views. The first thing you need to create is the admin views. Click new and create an admin view. Again it is just like with the component, you are able to set the bare bone information. I usually start at the bottom, and work my way up. [00:20:02](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h20m02s) I usually start with creating all the fields. I will basically Collapse this, and create all these fields. When I see there are duplicate Fields, I will remove them, because I know we used them. I will create Fields, that I know are unique. Then when I come to certain Fields, like these are custom fields. [00:20:42](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h20m42s) These I won't create initially. These are the custom fields. These are custom fields. I won't create them initially. I would also separate the custom field. How do I know it's a custom field? Because the Preacher is. I want to pull IDs from the Preacher view. Mark those custom Fields again, I would like to have this field basically link to that Name. A list of these names. [00:21:45](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h21m45s) The same for the series. I would like to link to that value. In Joomla you can create what is known as custom fields. Component Builder makes provision for you to do so. This is what I would call an advanced field. We will look at advanced custom fields after we've looked at creating Normal fields and creating actually back end views. [00:22:15](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h22m15s) Because only then will you understand the implementation of this custom Field. Since it will be linking to back end views value. It is not just linking to a bunch of values, it is linking directly to this back end views value called Name, and so we can't really create it until we know how this is going to look. That is why we will be looking at that after I possibly explain this again. Just to let you know where we are going. Building a Component needs these kind of things [00:22:51](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h22m51s) t0 be thought through and sort of mapped out. Some of us might not need to write it down, some of us do. Depends on who you are. To me that doesn't really matter even if you have these things in your head. As long as you come to Component Builder at least knowing partially what you want to achieve and what you want to build. That means you can do a lot of paper planning and do a lot of structuring of your component long before actually getting to Component Builder itself. That is what this [00:23:33](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h23m33s) short tutorial was trying to illustrate. If you haven't done this, you might get lost and not know where you are heading when you start mapping the Fields, and the views, and the things in Component Builder itself. The next tutorials we will start looking at Field types, and look at how to use field types to create fields. [00:23:56](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h23m56s) Slowly we will be progressing to eventually ending up with having this Component fully functional and working. We will be illustrating all of these Fields as they relate to this back end views that are linked to Database tables. Hopefully that will give a good enough insight and [00:24:22](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h24m22s) understanding of how all this should be done
We will be starting at fields. It seems turned around. You might feel we must start at the component, and then build the views, and then build the fields. [00:19:24](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h19m24s) After having created the component, you can click your own admin views. The first thing you need to create is the admin views. Click new and create an admin view. Again it is just like with the component; you are able to set the bare bone information. I usually start at the bottom, and work my way up. [00:20:02](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h20m02s) I usually start with creating all the fields. When I see that there are duplicate fields, I will remove them because I know that we had used them. I will create fields which I know to be unique. When I come to certain fields I won't create them initially, like these custom fields. [00:20:42](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h20m42s) I would separate the custom fields. How do I know it's a custom field? Because the preacher is. I want to pull IDs from the Preacher view and mark those custom fields again. I want this field to link to that name; a list of those names. [00:21:45](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h21m45s) The same goes for the series.
In Joomla you can create what is known as custom fields. Component Builder makes provision for you to do so. This is what I would call an advanced field. We will look at advanced custom fields after we've looked at creating normal fields and creating actual back end views. [00:22:15](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h22m15s) Only then will you understand the implementation of this custom field since it will be linking to back end views value. It is not just linking to a bunch of values, it is linking directly to this back end views value called name, so we can't really create it until we know how this is going to look. That is why we will be looking at that after I explain this again.
Building a component needs these kind of things [00:22:51](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h22m51s) to be thought through and mapped out. Some of us might not need to write it down, some of us do. You must come to Component Builder at least knowing partially what you want to achieve and what you want to build. That means you can do a lot of paper planning and do a lot of structuring of your component long before actually getting to Component Builder itself. That is what this [00:23:33](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h23m33s) tutorial was trying to illustrate. If you haven't done this, you might get lost and not know where you are heading when you start mapping the fields, the views, and the things in Component Builder itself.
In the next tutorials we will start looking at field types, and how to use field types to create fields. [00:23:56](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h23m56s) We will be progressing to eventually ending up with having this component fully functional and working. We will be illustrating all of these fields as they relate to this back end views that are linked to database tables. Hopefully that will give a good enough insight and [00:24:22](https://www.youtube.com/watch?v=gEgwiVNj6N0&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h24m22s) understanding of how all this should be done.