joomla/Component-Builder
joomla/Component-Builder
39
23
Fork 11
Code Issues 81 Pull Requests Projects 4 Wiki Activity

Updated 066 The new fields Area to make things easier (markdown)

Amigo 2019-10-01 08:12:12 +02:00
parent 07b9317cef
commit a47f4fba75
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
066-The-new-fields-Area-to-make-things-easier.md

@ -11,20 +11,16 @@ I would like to explain a little bit more about all the changes that had been ma
[00:00:46](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m46s) [00:00:46](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m46s)
Just a quick recap of how it used to look. If we go to an older install of JCB and open a field. If the Alias is opened, we would see that it has this XML field definition area. In the past it was very easy to leave out, maybe leaving out anything by accident, change something and then it breaks. We had lot of freedom and as developers I am sure this did not feel in anyway to be a problem. Whatever you have selected we build the XML for you and you could just adapt it as you please.[00:01:33](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m33s) Since we are trying to make JCB more stable and eventually much more user friendly. This new feature was suggested from within the team. Therefore the decision was made to add it. Just a quick recap of how it used to look. If we go to an older install of JCB and open a field. If the Alias is opened, we would see that it has this XML field definition area. In the past it was very easy to leave out, maybe leaving out anything by accident, change something and then it breaks. We had a lot of freedom and as developers, I am sure this did not feel in any way to be a problem. Whatever you have selected we build the XML for you and you could just adapt it as you please. [00:01:33](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m33s) Since we are trying to make JCB more stable and eventually much more user-friendly. This new feature was suggested by the team. Therefore the decision was made to add it.
### Removed The XML Definition Area Replaced It with Sub-form ### Removed The XML Definition Area Replaced It with Sub-form
[00:01:55](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m55s) [00:01:55](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m55s)
What had been done? We removed this XML definition and we have replaced it with a sub-form.<<<<<<< :) What had been done? We removed this XML definition and we have replaced it with a sub-form. We've moved the database values to its own tabs. We also moved the field information to its own tab. We added a lot of structures and tools to the page. Let's show you that. Version 2.7.5 [00:02:28](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m28s) which is the stable release of this change. If we open that same Alias which we did just now, you will see it looks like this now(see video). You have a sub-form, with those values in a sub-form layout. You have a lot of new information. It also has the Database in its own tab. The Type Info is still available and you can still come and [00:02:58](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m58s) review. The new option still gives you the ability to add those fields which are not already on the page. You could still say I want to add 'size'. We still load the description of the field on the page in the default value, which you can then change. Except when it tells you that it must be text. We have not yet [00:03:31](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m31s) blocked this field from being changed or being removed, though it is mandatory. If you do leave it out on compiling, the component we will detect that it is mandatory. If you did not add value, it will fall back to its default value. [00:03:59](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m59s) That is how it currently behaves. I wouldn't develop it in that way, best practice is to put in the value and make sure that is correct. That is the new Field area. There have been some hiccups and [00:04:23](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m23s) bugs which we have ironed out the predominantly all those we know about. We also added this new option, we have not fully released some of the features but there is this option which is going to separate if you use the custom Field currently. It adds the PHP in the rows which [00:04:50](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m50s) is a little tedious if you want to change this to keep track of the open braces.<<<<<<<<<<
We've moved the database values to its own tabs. We also moved the field information to its own tab. We add a lot of more structures and tools to the page. I'm very sure you are going to be very glad to see the things we've done. Let's show you that. Version 2.7.5 [00:02:28](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m28s) which is the stable release of this change. You'll see that if we open that same Alias which we did just now, you will see it looks like this now(see video). You have a sub-form, having those values in a sub-form layout. You have a lot of new information. It also have the Database in its own tab. The Type Info is still available and you can still come and [00:02:58](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m58s) review. The reality is the new option still gives you the ability to select, other on add of those fields which are not already on the page. You could still say I want to add size. We still load the description of the field on the page in the default value, which you can then change. Except when it tells you that it must be text. We have not yet [00:03:31](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m31s) blocked this field from being changed or being removed, though it's mandatory. There's still a level of caution required, you could still break it although, no you can't really break it whatever is mandatory. If you do leave it out on compiling, the component. We will detect that it's mandatory. If you didn't add a value, It will fall back to its default value. [00:03:59](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m59s) That's how it currently behaves. I wouldn't develop it on that way, best practice is to put in the value and make sure that is correct. That's the new Field area. We've put a lot of work into this and there has been some hiccups and [00:04:23](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m23s) bugs which we have ironed out the predominantly all those we know about. We also added this new option, we haven't fully release some of the features but there is this option which is going to separate if you use the custom Field currently. It adds the PHP in the rows which [00:04:50](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m50s) is a little tedious if you want to change this to keep track of the open braces, and all that in this way is little challenging.
### New Implemetation For Custom Fields and Custom User ### New Implemetation For Custom Fields and Custom User
@ -56,4 +52,4 @@ The other option which is also available. It is the Display option. We'll still
Last but not least, Validate. Not all fields have the property to validate the value. There are Validation Rules. You can add a validation to this field, if that property is not available in the field type, which you have selected. If it is, we would suggest that you add it to the properties at the top. It says that, if you have a validation set as a field property, this extra property will not be needed because you can just use that one. [00:09:33](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m33s) Last but not least, Validate. Not all fields have the property to validate the value. There are Validation Rules. You can add a validation to this field, if that property is not available in the field type, which you have selected. If it is, we would suggest that you add it to the properties at the top. It says that, if you have a validation set as a field property, this extra property will not be needed because you can just use that one. [00:09:33](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m33s)
That was a quick demonstration of the new field area. We trust that it will be as easy and as comfortable as we hoped it would be. Trust that this change would not frustrate you, but be great. Because of the reason, for example one of the unforeseen [00:10:00](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m00s) outcomes, as if you have a field like this which already has all its values. You are thinking on changing it and you say, let me just check how will the text look. You can change it and it really adds all your text value with its defaults. If you say no I want to go back, you can click back, and lo and behold your old values [00:10:25](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m25s) are again been added to the page. The values that were there originally. That is even true if you were to remove a specific property. Then you want to add it back, it adds the original value back, was what we intended because by accident [00:10:48](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m48s) you might remove it and want to just put it back. It should be as easy as that. You could still go to Type Info to see what could be the default values and adapt them. It's not like you don't have access to the default values, it's just that we want to [00:11:10](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m10s) recover your current saved value for you. Whenever you add another field which isn't already here, this drop down list only shows the fields that are not already on the page. You won't end up adding fields properties the second time. It has become much more easier to build fields and its properties [00:11:39](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m39s) as before. You really had to navigate through some of the complexities of dealing with an XML set of values. Which maybe some of you don't even know exactly what's going on. Those of you that do, I mean it's not like you're losing any advantage with the new implementation, [00:12:02](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m02s) you are still targeting that value with any value you want. It's still as easy as clicking a plus and selecting a value and adding it. I do hope that all of you will be as excited about this change as we are . We are now at the point where making JCB easy-to-use is also a priority. That was a quick demonstration of the new field area. We trust that it will be as easy and as comfortable as we hoped it would be. Trust that this change would not frustrate you, but be great. Because of the reason, for example one of the unforeseen [00:10:00](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m00s) outcomes, as if you have a field like this which already has all its values. You are thinking on changing it and you say, let me just check how will the text look. You can change it and it really adds all your text value with its defaults. If you say no I want to go back, you can click back, and lo and behold your old values [00:10:25](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m25s) are again been added to the page. The values that were there originally. That is even true if you were to remove a specific property. Then you want to add it back, it adds the original value back, was what we intended because by accident [00:10:48](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m48s) you might remove it and want to just put it back. It should be as easy as that. You could still go to Type Info to see what could be the default values and adapt them. It's not like you don't have access to the default values, it's just that we want to [00:11:10](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m10s) recover your current saved value for you. Whenever you add another field which isn't already here, this drop down list only shows the fields that are not already on the page. You won't end up adding fields properties the second time. It has become much more easier to build fields and its properties [00:11:39](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m39s) as before. You really had to navigate through some of the complexities of dealing with an XML set of values. Which maybe some of you don't even know exactly what's going on. Those of you that do, I mean it's not like you're losing any advantage with the new implementation, [00:12:02](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m02s) you are still targeting that value with any value you want. It's still as easy as clicking a plus and selecting a value and adding it. I do hope that all of you will be as excited about this change as we are . We are now at the point where making JCB easy-to-use is also a priority.