Updated 010 Component Settings (markdown)

Amigo 2019-06-10 16:23:09 +02:00
parent 870d427d01
commit 1edb043550

@ -66,4 +66,6 @@ If you're a developer you would know that inside of your component, you have a p
If you are a developer, always keep the concepts of conventions logical, repetitive and scalable. Here is one that I have added for instance. In the global area go to 'preachers'. It is this field here, 'Display - Table - Grid - List' and in the code, if preacher_display = 1, then show the table. [00:25:59](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h25m59s) If preacher_display = 2, then show the grid. If non is selected then show the list. [00:26:21](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h26m21s) I'm not asking does the global have this or that, I'm just calling the field directly, because Joomla gets that initial data and sorts it out for you. I've tested it and made sure that my explanation is correct. The same goes when it comes to 'colors'. (See video.) [00:26:55](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h26m55s) Component builder makes it easy to implement these kind of things which otherwise would take time to write and then make sure it's the same inside of the XML folder menu, etc. Component Builder does all of this out of the config file with a convention that relates to the actual front end. [00:27:26](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m26s)
Possibly it might be ideal for us to [00:27:48](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m48s) stop here with the component and go look at setting up a custom admin view or setting up a site view.The ideal will be to first deal with some of this component features and finish that [00:28:12](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h28m12s) and as soon as we've finished it, we'll go into the custom area of your front-end development and custom admin development and then we'll be relating back to what we have discussed as we continue. So I've now looked at the setting tab and try to cover as much of this area as poosible. I have not mentioned much about 'MySQL' tweak. This is a very advanced feature and [00:28:44](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h28m44s) You're able to exclude dummy data through this area so that if you have different versions you will through this 'MySQL' tweak be able to exclude certain information.It is a little bit advanced and in many case are not going to be used. It's only when you start having multiple versions of the same extension and you are marketing them at different prices and want to be able to [00:29:17](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h29m17s) from within component builder just export the different versions then you start using this feature and I think we possibly deal with it with when we start looking at more advanced implementations. We'll start in the next run with scripts
It might be better for us to stop here with the component and look at setting up a custom admin view or setting up a site view. [00:27:48](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m48s) The ideal will be first to deal with some of these component features. As soon as we've finished it, go into the custom area of your front-end development and custom admin development and relate back to what we have discussed as we continue. [00:28:12](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h28m12s)
I've now looked at the setting tab and had tried to cover as much of this area as possible. I haven't mentioned much about the 'MySQL' tweak. This is an advanced feature. [00:28:44](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h28m44s) You'll be able to exclude dummy data through this area so that if you have different versions this 'MySQL' tweak will be able to exclude certain information. It won't be used in many cases. It's only when you start having multiple versions of the same extension and you are marketing them at different prices that you want to be able, from within component builder, to export the different versions. [00:29:17](https://www.youtube.com/watch?v=V2WkTjNFjvo&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h29m17s) I think we can deal with it when we start looking at more advanced implementations.