YOU NEED TO UNDERSTAND About Code Generators for Quick Web Development
As a web developer, one thing that helps me to quickly develop web applications is to use a common application framework that is flexible and robust. Additionally, I like to use code generators to create code for custom applications I build for my customer. My most powerful code generators, create code for interacting with the local database focused on my website.
Normally, it is bad practice to repeat code when doing development. However, there are certain instances when this is often beneficial and assist in creating dynamic web applications. Right here, we will discuss some of the many applications that I have found useful and how you can apply them to your own business.
One way I enforce code reuse is to apply object-oriented design. For my information access layer I create an abstract school which contains the common functionality. Next, I create derived courses which implement the precise methods which are needed for the entity style (usually a database table).
These derived classes have distinct fields which represent the areas defined for the table. They also contain mappings for the principal keys, any related fields which are retrieved from relevant tables, and custom options for querying the database. The idea is that all the database phone calls are encapsulated in the data access layer classes.
These derived classes have sufficient similarities between one another that it made sense for all of us to create a code generator to generate these files from the database schema.
How exactly to Generate Code in Your Intranet
On our intranet, we have the code generated connected right to our database supervision scripts. When an administrator is usually viewing a table schema, they have a button on underneath of the screen to generate the code for the data access layer. When the user presses this press button, the code is promptly generated and an individual can click anywhere on the code to select the code block and backup it to the clipboard.
The process of generating code is remarkably simple. We basically retrieve the schema from the database and from that we define all the macros which are needed to substitute right into a program code template. These macros include items like the script name, database table label, primary key fields, public areas, private fields, and a generated class name.
The code is outcome to the display as pre-formatted text. Below that is a web form where in fact the user may tweak the macro values that were generated. After making modifications to these values, they are able to click a submit button which regenerates the code utilizing the custom macro values. Needless to say this step is optional. An individual may simply choose to copy each of the program program code and paste it in their program code editor and continue making adjustments that way.
In my website administration panel, I’ve a lot of pages which are built for managing database tables. I have an extremely capable library which handles all the heavy lifting for paging through a table of records, creating a new record, editing and deleting an archive. That is an object-oriented class that requires a variable number of parameters.
To produce a new administration area, I just need to instantiate this class, define all the required properties, and then call a way called “Process”. The resulting record is usually no more than 25 lines of code. Creating these data doesn’t take lengthy when done yourself. However, I knew that creating a code generator for these server-area scripts would save us lots of time.
Again, the main element to accomplishing this objective was to first read the database schema for a desk to get all of the field definitions. From these definitions, it might be a simple matter to create the code from a preexisting script template. I simply define macros for all of the properties I need to substitute in the template. Because the desk schema is read, I build these properties which are later substituted into the template.
When generating code, it is important to keep in mind the way the script will likely be used. In my own data access layer scripts, I know they are usually two directories beneath the website root. For this reason, I know that any relative links have to go up two levels to get to the site root.
Another important area to take into account is form validation. There are specific constraints you can place on a web web form to limit the volume of characters a user enters right into a text field. You can also make Boolean fields display as radio control keys labeled “Yes” and “No”. Date fields can display using a specialized date picker.
Other special data fields could be displayed based on the field name. For example, fields containing the word “Password” can be displayed as password fields. I take advantage of fields with the label “created” and “modified” to monitor whenever a record has been changed. Areas that have the text “email” could possibly be validated to ensure they contain a valid email address. Also, fields that have the text “postalcode” could be tested for legitimate postal codes.
I try to build my code generator so it’s as smart as can be. The thinking behind this is that the developer can simply remove extra code that was added if they find too much validation has been done or the incorrect type is performed. The more work you can save for the developer, the higher off you will be in the long run.