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

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

Amigo 2019-09-28 18:38:47 +02:00
parent d3227baf89
commit 2ef9e9a8a6
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -5,19 +5,26 @@
[00:00:08](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m08s)
(Click on these time links to see Youtube video)
I would like to explain a little bit more about all the changes we've made to the field area. The field area is really the foundation of most of your component. It is what causes many of the behavior and concepts which you might have in your views that are all based on the field. The field area was a difficult place to change and it is still in progress. The interface most probably won't change much, [00:00:38](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m38s) just little tweaks here and there. The back-end of how we deal with the data, we're certainly going to continue improving that.
I would like to explain a little bit more about all the changes that had been made to the field area. The field area is really the foundation a great part of your component. It is what causes many of the behavior and concepts which is in your views. The field area had been a difficult area to change and it is still in progress. The interface most probably will not change much, [00:00:38](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m38s) just little tweaks here and there. The back-end of how we deal with the data will certainly be improved.
### A Quick Recap how It used To Look
[00:00:46](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m46s)
I just want to give you a quick recap of how it used to look. If we go to an older install of JCB, open a field. If we open the Alias, 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'm sure this didn't feel in anyway to be a problem. Whatever you have selected we build the XML for you and you could just adapt [00:01:33](https://www.youtube.com/watch?v=26x_Sc8jbp8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m33s) it as you please. Since we are trying to make JCB more stable and eventually much more user friendly. This new feature was suggested from inside of the team. We decided 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 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.
### What Did We Do? - 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)
What did we do? 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 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.
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 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