This question is locked. New answers and comments are not allowed.
Could we imagine to have php back end code generation about getters and setters ? Around a ui builder development, it would boost productivity.
A brief sum-up of the idea :
For example an input element (like a textbox) could have a property "datasend" (don't care about the name) which is a listbox where we can select an action element present into the form (for example a button).
So the button in this example knows all input elements linked to him and we would be able to generate the code on the mobile side to push these values on the back end and we would also be able to generate the php back end code to receive these values.
Same principle with elements having a property "datareceive" in order for them to retrieve values populated by the server.
It's just a general description to explain the process without structure or optimisation ideas in it. One example among others is that we could look as convenient for an element pushed on the backend (or retrieving a server data value) to map its variable name to another variable name on the backend we would have to specify.
I see this as a tremendous added value in productivity, saving time, avoiding errors, making developer's life much easier and so implying less ask for support in forum :) and it's also an additional interest for those who use code generation from a db on the backend (with the help of frameworks or tools).
Having both side of code generation, they benefit of developing an application in no time.
A brief sum-up of the idea :
For example an input element (like a textbox) could have a property "datasend" (don't care about the name) which is a listbox where we can select an action element present into the form (for example a button).
So the button in this example knows all input elements linked to him and we would be able to generate the code on the mobile side to push these values on the back end and we would also be able to generate the php back end code to receive these values.
Same principle with elements having a property "datareceive" in order for them to retrieve values populated by the server.
It's just a general description to explain the process without structure or optimisation ideas in it. One example among others is that we could look as convenient for an element pushed on the backend (or retrieving a server data value) to map its variable name to another variable name on the backend we would have to specify.
I see this as a tremendous added value in productivity, saving time, avoiding errors, making developer's life much easier and so implying less ask for support in forum :) and it's also an additional interest for those who use code generation from a db on the backend (with the help of frameworks or tools).
Having both side of code generation, they benefit of developing an application in no time.
2 Answers, 1 is accepted
0
Hello Alexandre,
Iva Koevska
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
Thank you for tremendous energy and enthusiasm to make Icenium better! I see you're already making use of our Feedback Portal, where you have also put this suggestion out in the open.
For anyone who's interested in the progress of this idea, you can vote about it and keep track of it here.
Iva Koevska
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
Kynao
Top achievements
Rank 1
Rank 1
answered on 30 Oct 2013, 10:09 AM
Thanks you Iva,
It's because i eat bulgarian chocolate :)
It's because i eat bulgarian chocolate :)