Updated 5. Field Types: 11 23 2018 Work in progress (markdown)

5.-Field-Types:-11-23-2018-Work-in-progress.md

@@ -31,8 +31,8 @@ There is a name which is called type And a value for checkbox and it must be set
 You see that it shows you examples of how that XML line should look right see Now Yeah In the Field area where you created to field Basically gave the few the name this is just for the system The name used here is the one that is important That should be the correct name the label This name is just that you when you add it to your view You know this is what we used to identify it Weston explain adding it to the view In more detail This diet data type and things were also explain we only go into more depth around What a field is and how to build one I'm simply now looking at few pipes and showing you how the changes that you've made in field type Effects I feel that you would build with that type So here is that Detail that was in field type Member on change And it tells you What is mandatory in what is optional but that's basically because I placed it in the description right I mean let's be country close to go back to that field type And then take on property And we'll see that I added optional and mandatory To the description So that I can know is this option or mandatory Yes you could Possibly argued that I should have done it from here and that it's not true don't be necessary to add it there But you know this is that this The settings here is used when we compile the component Where is this Here is used for you You know what this field attribute is all about And maybe as weak Continue to develop this component I might Make it changed to that But I wouldn't make such a change that it affects anything that already exists Dramatically and anyway Ok so let's go back to a field
 
 + [17:43](https://youtu.be/OhLzvThDXls?list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=17m43s) **XML string within compilier** _How XML string is build and compilied within component builder._
-The way the compiler works it is doesn't really grab the string and just put it into the XML In fact if I show you how a string looks that the compiler is built Wrong window Let's go to the string that the compiler is built Assessment type You see that it is completely reformatted The label is turned into a translatable string So it's been done done with the description It also tells you where in the compiler if well we'll still look at that because this might Sometimes show and sometimes you can Tweak Your Your component that it doesn't show it But it tells you Europe in which line in the Compiler it was built and also in which file which is very nice I think those of you that are developers will appreciate this feature from tremendously I also tells you the fuel type so Obviously as you can see it as we scroll through this You can see that Component builder really goes way out of its way to Reconstruct That That field It is not using This directly It in fact Grabs That area And that To determine that this is a Text Field So it actually is really dependent on that part Which is up dude name come now And That part there So the opening Exclamation and the closing one And the value in between those is what is used So if you prefer by accident drop off this Or that it will still work perfectly
+The way the compiler works it is doesn't really grab the string and just put it into the XML. In fact, if I show you how a string looks that the compiler is built, the assessment type, you see that it is completely reformatted. The label is turned into a translatable string. It's been done done with the description. It also tells you where in the compiler. We'll still look at that because this might show sometimes and you can use apply a JCB Tweak to your component so it doesn't show it. But it tells you which line in the compiler it was built on and also in what file which is very nice. I think those of you that are developers will appreciate this feature tremendously. It also tells you the field type and you can see it as we scroll through it. You can see that Component builder really goes way out of its way to reconstruct that field. It is not using this directly. In fact, it parses an area to determine of it is a text field. So, it is dependent on that part which is up dude name come now and that part there. The opening exclamation and the closing one and the value in between them is what is used. If you prefer or by accident drop off this or that it will still work perfectly
 
-These are really the only Things that are Really need it And part of what I am Hoping to achieve eventually is that this becomes just input Fields Like These And yet I'm wondering if I should go that way The fact that they all in one big text area Leaves us with a lot of room and freedom 2/2 really adjusted easily without major Complications And any case if you start a new field which we'll look at later It populates this with the demo demo data and the demo data Is actually values that you said When you create a fuel type You see Here it is the demo is this Value or example That is placed here It's from these values that region is in if you create a new text field It grabs these values as the values which you can then Adjust to your purpose Of you you know Implementation for that specific field at that moment If you leave it blank it will also build it without any value Between those two Estimation marks Ok That is looking at fuel types 
+These are really the only things needed to understand for using field types. Eventually these may become input fields in one big text area that leaves us with a lot of room and freedom. They are really adjusted easily without major complications and in any case if you start a new field, which we'll look at later, it populates this with the demo data and the demo data is actually values that you added when you created the field type. You see in the demo it is this value from the example that is placed here. It's from these values that the region is in if you create a new text field. It grabs these values as the values which you can then adjust to your purpose. If you you know implementation for that specific field at that moment and if you leave it blank it will also build it without any value between those two estimation marks that is looking at field types. 
 
-Most field types have been set up for you and you hardly ever would need to come here except fro a deeper understanding of how filed types work and how Joomla! and JCB implement them. You do not need to change things unless you wish to. You may be interested in my next tutorial on how to use field types in fields.
+Most field types have been set up for you and you hardly ever would need to come here except for a deeper understanding of how field types work and how Joomla! and JCB implement them. You do not need to change things unless you wish to. You may be interested in my next tutorial on how to use field types in fields.