KR20230036670A - Web Application Development System - Google Patents

Abstract

The present invention relates to a solution interface technology for developing web applications. Disclosed are a presentation method for web applications and a system for developing web applications using the same. The present invention relates to a solution interface method for developing web applications in a web environment consisting of a client including a web browser and a web server implemented by various types of server platforms, in which the solution interface method comprises: dividing a web page constituting the web applications into a screen corresponding to a design of the web page and a handler corresponding to a programming source to implement the same as a separate file; and loading the handler according to a request of the web browser by a web plus engine executed on a client side, loading a screen corresponding to the handler, creating an html tag through mapping between the handler and the screen, and assigning an attribute to the created html tag, thereby providing the attribute to the web browser. Accordingly, since a start-up of design and programming is possible, a development period can be shortened, maintenance and repair can be easily performed, and development can be performed independently regardless of platforms of various web servers.

Description

Web Application Development System {Web Application Development System}

The present invention relates to a web interface technology as a solution for developing web applications, and in particular, to general users who access web applications through the World-Wide-Web (WWW). It is a solution that specifies how to express a page. It is a presentation method that can express a web application at the level of a desktop application through connection with a solid business logic, and a technology related to a web application development system using the same.

In general, the Internet has grown rapidly in recent years with the proliferation of computers and networks, and has developed into a worldwide sophisticated network of computer systems linked together by web pages that collectively constitute the "World Wide Web (or WWW)". . On individual PCs that wish to access the WWW, users use software commonly known as 'web browsers'. A web browser makes a connection to another computer known as a web server on the WWW, receives information from the web server, and displays it on the user's computer. The information presented to the user consists of pages implemented using a proprietary language, usually referred to as Hypertext Markup Language (HTML). Web browsers using HTML have become available for almost every computer system on the market, allowing almost anyone with access to a computer and modem to access the WWW. The rapid growth and spread of computer users accessing the WWW inevitably became the driving force leading to the remarkable development of computer hardware and software.

1 is a schematic diagram showing a presentation concept for a conventional web application, in which a web browser 11 as a client 10, a web server 20, and a database 30 are shown.

Referring to FIG. 1, the web server 20 includes at least a presentation layer 21 and a business logic layer 22. In the conventional web model, the presentation layer 21 has a screen design and a program source. It is implemented in the same file without being separated. In this conventional web model, when the browser 11 requests a web document according to the HTTP protocol, the presentation layer 21 of the web server requests the business logic 22 to process as needed, and then receives the data and HTML A web standard document composed of and CSS was created and responded to by the browser 11, and the browser 11 outputs it to the screen accordingly.

In this way, although the popularity of the WWW is rising and the technology is rapidly developing accordingly, the reality is that various incidental problems are also growing together. The problems in the current web application are examined from the user's side, the web application operator's side, and the web developer's side, respectively.

The present invention has been proposed to solve the above problems, and manages design and source as completely independent files of screen and handler according to the above invention, and components already developed by the above invention and their properties It is easy to develop and maintain by using the characteristic that the implementation of the corresponding function is completed without the developer's direct programming work through the declaration of (Attribute), and after the screen is loaded, only the necessary data of the specific part can be called and expressed again. The purpose is to provide a presentation method for web applications that can minimize screen reload and improve reaction speed and a web application development system using the same.

The structure of web applications so far is that when a user accesses a specific web application on the WWW and the user requests a specific task on the web page, the presentation layer 21 of the web server processes the business logic 22 as needed. to complete the task, receive the data, and output data to be sent to the user's web browser (including static HTML pages in which the content of the page does not change, or data that must be dynamically determined and inserted into the output data) can be done) and transmits it to the user's web browser, the web browser interprets it and displays it on the user's monitor screen. In other words, when a user's request arrives, the user has to wait until the web server completes all processing and output data is transmitted to the user's web browser.

Therefore, while the user was waiting, the connection was suddenly disconnected or the user waited for a certain amount of time, depending on the variable environment such as the speed of the network or the process of the web server.

In addition, when a data change occurs in a specific part of the currently accessed webpage according to the user's request, in order to reflect it to the web browser, conventionally, only the information of the changed part cannot be received, and the entire data such as HTML to be displayed on the screen is rediscovered. Since the transmission is received from the web server, it causes load on the web server and the network, and then the web browser reconstructs the output data received and displays it on the user's monitor, causing the screen on the monitor to flicker. had no choice but to meet

Due to the above limitations, in order to handle more diverse and complex tasks, it was sometimes necessary to install and use desktop application programs through the cumbersome process of new installation on the user's computer. However, this has a fundamental problem in that access itself is not possible on a computer where the corresponding desktop application program is not installed.

Web Application Operator/Company Side

As mentioned above, the structure of the web application to date, which has to receive requests from numerous users through the WWW, process all the requests in the web server, create output data for them, and respond to each user. and achieved greatness. However, as more and more users access, the problem of load on the web server has been brought about again. In order to solve this problem, various development methodologies and concepts of better computer systems were derived through efforts for new development and expansion of other systems, and hardware and software developments were made accordingly. However, this has progressed in different ways by hardware, software, computer, and platform. These essentially different hardware systems typically use completely different operating systems. Since these different hardware and software systems exist, porting to each different hardware platform for a given web application usually requires an entirely new system development effort. As a result, web applications with the same content are developed and operated for each different hardware and software platform, resulting in an unproductive situation that takes considerable time and high costs.

In the meantime, desktop applications have been developed and managed separately due to the limitations of the traditional web application structure in order to implement complex corporate tasks through the web. Because of this, it was necessary to have two types of applications, which were divided into web applications and desktop applications, depending on the task, and thus suffered various difficulties such as difficulty in maintenance and increased costs.

In addition, since the desktop application could only be used through a separate installation process on the user's computer, access itself was impossible unless the computer had the desktop application program installed. So, in order to solve this problem, efforts have been made to convert desktop applications into web applications, but the reality is that the efforts so far are not enough to convert all the complex and diverse functions of desktop applications into web applications. Therefore, an unsatisfied conversion work is being made in which a web application is developed by carefully selecting only the parts that can be converted into a web application by removing some functions of the desktop application.

Web application developer (programmer, web designer) aspect

In the current system environment in which new interfaces are configured for each new web application, developers have to relearn new programming methods and pay additional efforts and costs to operate them. Therefore, even though many web applications today are accessible through the WWW, the differences between these various web application platforms discourage web application developers from spending time learning new platform environments and how to operate them. However, there is a problem that makes them reluctant to introduce new applications.

By the way, HTML is a well-known language that can be used by most computer systems currently on the market. Also, because HTML is a fairly well-controlled and standardized language, as functions of new software applications are developed and supported by HTML, those functions may be added. However, it is rare that many web application programs on the WWW construct web pages using simple HTML due to business logic calls and database connections due to frequent requests for dynamic data information.

Therefore, in reality, web application programs are developed using a server scripting language suitable for each system platform for most web applications. For example, there are JSP (Java Server Page), ASP (Active Server Page), PHP (PHP: Hypertext Preprocessor), and the like.

The above server script language has a work structure that adds programming according to the syntax of each server script to express dynamic data of the database in conjunction with business logic on top of HTML representing static data.

In other words, in general, when a web designer creates the composition and contents of a web page in HTML, the programmer takes over this again, and additionally inputs the source into the corresponding file in each server script method to configure the connection with the business logic. . This made it possible to implement a dynamic web page change and a sleek UI (User Interface) with various contents. However, since the web designer works with the same file and the programmer receives it and works again, the implementation of design and source cannot be performed at the same time, so it takes a lot of time for development. In addition, when the development of the primary web application program is completed and the configuration of the web page is changed according to the requirements of the new user, the designer receives the file already implemented in the server script language and adds or deletes new HTML. However, due to the grammar of the server script language that web designers are not familiar with, if a web design that does not conform to the grammar of the server script language is made, the programmer must take over and modify the server script language, so it is an inefficient problem wasting time and money as a whole. this may happen

In addition, from the programmer's point of view, programming to display the response to a specific request such as a user's event or action within a web page to the web browser, various types of scripts (VB Script, JScript) or server It had to be implemented in a scripting language. As a result, a long programming time is required to implement a source for a response according to each request, and when a change in the request occurs, a source for another response must be implemented, making maintenance difficult. there is.

As such, in the conventional web model, web documents in the presentation layer are not divided into design and source, so code reuse or maintenance is difficult, and it takes a lot of time to develop new web applications.

As described above, according to the present invention, the handler corresponding to the program source of the web application constituting the screen and the screen corresponding to the design of the screen are divided and managed, thereby facilitating the development of new web applications and reducing maintenance. It is convenient, and the load of the server can be reduced by processing the function responsible for the user interface (UI) on the client side, and minimizing screen reload by applying the latest web standards such as AJAX It provides an effect that can reduce the elegant screen composition and load time.

In addition, by adding additional functions to the existing web application model that accesses software applications on the WWW, it provides easy and elegant web page configuration and fast response speed to general users, and a groundbreaking change in the existing development method for software developers (programmers and designers). It is not dependent on different development languages for web application program development, and provides programmers and designers with an independent working environment through complete separation of design and source files to improve development productivity and provide ease of maintenance.

It also allows software developers to adopt standard access protocols, allowing developers to provide support for any computer system capable of using an HTML-aware browser.

In addition, the present invention provides an independent environment that is not dependent on different platforms to develop the corresponding web application to the operator and operating organization of the corresponding web application, so that web application programs having the same contents as the number of different platforms can be developed in different ways. Since it can be used for each platform as a single web application according to the invention without the need to make it for each platform, even small operators and operating organizations can provide an open path to access a large market through the effect of reducing cost and development period. can

The present invention is not limited to the above embodiments, and it is obvious that many modifications are possible by those skilled in the art within the technical idea to which the present invention belongs.

In order to achieve the above object, the method of the present invention is a method for providing a web application in a client-web server structure, wherein the web plus engine running on the client communicates with the web plus engine according to the request of the web browser. A first step of creating a document; a second step of the web server providing a handler when the web plus engine requests a handler for the corresponding screen; a third step of providing, by the web server, a corresponding screen when the web plus engine requests a screen to be used for a corresponding handler; a fourth step in which the web plus engine responds to the web browser using the handler and the screen; a fifth step of, when an event occurs and data is requested, the web plus engine requests data from the web server, and the web server executes a predetermined business logic and returns the resulting data as an xml file; and a sixth step of the web plus engine parsing the xml file and providing an html file including updated data to the web browser.

In addition, in order to achieve the above object, the system of the present invention, in a web environment having a client-server structure, includes a web browser running on the client; Upon initial access, it is loaded from the server to the client side, and after requesting a handler and a screen of the corresponding screen to the server according to the request of the web browser, the handler configured in xml is parsed and mapped with the screen (Mapping) Interprets the information to generate a basic html document to be output to the web browser and outputs it to the web browser, and if new data is needed according to the event, it communicates with the server in a synchronous/asynchronous manner to receive xml data and send it to the web. a web plus engine that updates html information output to the browser and outputs the updated html information to the web browser; a presentation unit that is executed in the server and manages documents by classifying them into handlers and screens and provides handlers and screens according to a request of the web plus engine; and a data controller that is executed in the server and provides a connection with business logic that processes a specific service according to a request of the presentation unit and provides a result.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Figure 2 is a schematic diagram showing a presentation concept for a web application according to the present invention, Figure 3 is a detailed configuration diagram of the presentation layer shown in Figure 2, Figure 4 is the operation of the web plus engine shown in Figure 2 It is a flow chart showing the procedure.

As shown in FIG. 2, an environment for implementing a web application according to the present invention consists of a client 100 and a web server 200 structure. The client 100 is composed of a normal web browser 110 and the web plus engine 120 according to the present invention, and the web server 200 sends a web document to a handler 213 corresponding to a program source according to the present invention. The presentation layer 210 and the normal business logic 220 provided by dividing into the screen 214 corresponding to the screen design and the screen design It means logic). The business logic 220 is connected to the database management system (DBMS) 300 or other resources 300 such as CRM/ERP and LDAP according to the nature of the application, processes the service required by the application, and presents the result It is provided to the presentation layer 210. When the client 100 accesses the web server 200 to which the present invention is applied, the web plus engine 120 is initially automatically loaded and executed on the client side.

In addition, as shown in FIG. 3, the presentation layer 210 according to the present invention is composed of a web plus viewer manager 211, a web plus data controller 212, and a tool unit 215, and a web plus viewer manager ( 211) connects the screen 214, which is an element of the screen of the web application, and the element of the logic of the web application, and the handler 21 that controls the screen by connecting data.

3) consists of The handler 213 includes the data set 213-1, the transfer 213-2, the config 213-3, and the built-in function 213-2.

4), Ajax-based component library (213-5) is included, and the WebPlus Data Controller (212) is connected to the business logic (220) to relay data to be displayed on the corresponding web page It is divided into an XML Manager (212-1) and a Data Mapping (212-2) that play a role. The tool unit 215 performing auxiliary functions processes handler automatic completion and logging.

Referring to FIG. 3, a screen 214 inserts an HTML tag for UI expression, defines an ID having information mapped to a handler, and allows the screen to be reused in other handlers. . These screens can accommodate files in any serverscript language format such as html, jsp, asp, php, etc.

The handler 213 is implemented in XML and defines screen UI components as XML elements, defines ID and XPATH for mapping with screens and data binding, and defines elements for automated function implementation. Attributes and built-in functions (213-4) are used, and corresponding handlers and screens can be reused using inheritance and inclusion relationships. This handler (213) consists of Dataset (213-1), Transfer (213-2), Config (213-3), built-in function function (213-4), and Ajax-based component library (213-5). As the logic of the web application being formed, it connects the screen 214 and data and controls the screen 214 to perform practical functions. The component library (213-4) includes UI CONTROLS, UI COMPONENT, DATA MANAGE, BEHAVIORS, TOOLS, etc. UI CONTROLS provides organic control properties between UI components, UI COMPONENT provides a rich screen interface, and DATA MANAGE provides efficient data synchronization management and desynchronization and data transmission. BEHAVIORS provides optimized reload and simple URL movement.

For example, when a conventional web page in which design and program are not separated as shown in Table 1 below is divided into design and handler according to the present invention, the handler is shown in Table 2 below and the screen is shown in Table 3 below.

Table 1 below is an example of a web page in which design and program are not separated.

The XML Manager 212-1 receives data configured in xml form from the client 100, parses the corresponding xml, delivers it to the Data Mapping unit 212-2, and Mapping) (212-2) plays a role in generating and delivering XML-type data to the client.

The data mapping unit 212-2 connects with the business logic 220 and serves as a data interface with the business logic 220 to transfer the received data to the XML manager 212-1. carry out

And the web plus engine 120 is implemented in JavaScript and performs the procedure shown in FIG. 4 to call the handler 213 and the screen 214 according to the request of the browser 110 and the handler 213 ) is parsed, and an html file of the corresponding object mapped to the screen 214 and ID information is generated and provided, and connection communication with the web server 200 communicates with HTTP and xmlHttpRequest. That is, the webplus engine 120 has a function of configuring one window in which the webplus engine is loaded according to the request of the web browser 110, and one window performs a pop-up without the need to reload the webplus engine A function to enable use in all screens, including functions to load and parse an environment setting file that defines common elements for implementing screens and functions to set information such as global variables and sessions, and an environment to implement screens and functions. A function to call a handler that is defined directly through a setting file or URL, a function to call screen files defined in the handler and draw them in each location of the set window, and a controller described in the called handler to display data information (XPATH) and screen classification A function that divides by (ID) and parses element and property information, a function that maps handler controller tag and screen controller tag ID to create basic information for connection with the screen object, and controller tag property of handler A function that automatically implements various screen functions with only the declared property information, which was previously implemented by developers directly. Event handlers are used through handler script tags, and data are provided through built-in functions and user-defined scripts when events occur. Provide functions such as call, screen transition, pop-up, and message notification, function that enables implementation of various user-added functions, function that imports and reuses duplicated screens and functions from handler as handler and screen are completely separated, And it handles the function of reloading only the desired data according to the handler's controller tag classification.

Referring to FIG. 4 , when a client 100 attempts an initial access to a corresponding web application of a web server 200 to which the present invention is applied, the web plus engine 120 from the web server 200 sends the client 100 is loaded into the browser 110 of (S401, S402). Thereafter, the web plus engine 120 generates a common document when there is an HTTP request from the browser 110 (S403). As shown in FIG. 6, the common document is a basic screen composition to be commonly used consisting of a top, a body, and a bottom. The top corresponds to the head portion of the entire screen, and the body corresponds to the main screen. This is the part that shows the contents of the screen, and the bottom is the lower part of the entire screen.

Next, the start-config.xml and message.xml files are read, the basic environment to be executed of the web application is set, and the handler 213 that controls the screen is called (S404). The start-config.xml file controls the basic environment of the corresponding web application, and the message.xml file contains the contents of an alert window to be shown to the client 100 when a specific event occurs in the corresponding web page. A guideline is defined.

Subsequently or in the case of non-initial access, the information described in the called handler 213 is parsed (S405). At this time, it can be reused in common by importing other handlers. Subsequently, the screen 214 file defined in the handler 213 is called and the corresponding screen 214 is included in the body of the common document (S406). Accordingly, the screen can be reused. Next, by mapping a tag with the same ID of the handler tag and screen tag,

This html tag is generated (S407). Looking at this in more detail, it is as follows.

a) The web plus engine analyzes the id information of the handler's element tag.

b) The web plus engine searches for the same id in the tag id of the screen with the id information found in step a).

c) The web plus engine creates the mapping information found through steps a) and b) as basic tags in html.

d) Cycle back to step a) to map the corresponding handler and screen.

For example, as shown in Table 3 below, if the id is "sch_value", the html basic tag is created from the mapping between the handler and the screen as shown in Table 4 below.

Subsequently, the handler 213 interprets the defined attributes, events, and actions of the xml elements, and additionally sets the attributes and scripts of the basic html tags generated in the previous step (S408). Looking at this in more detail, it is as follows.

1) Webplus engine searches object information related to event and action of element tag of handler or interprets each described attribute information.

2) Based on the attribute information described in the element tag of the handler, the webplus engine adds the html attribute of the object with the same id as the handler and the screen, and additionally writes scripts related to events and actions based on the information found in step 1. all.

3) Cycle back to step 1) and execute again.

For example, when an html tag is generated as shown in Table 4 above, attributes are assigned as shown in Table 5 below from the handler and screen.

Then, the body part of the common document is output to the browser, and screens corresponding to the top and bottom are called and output to the browser (S409 and S410).

Subsequently, the entire operating procedure between the web browser and the web server in the web application system according to the present invention configured as described above will be described with reference to FIG. 5.

Referring to FIG. 5 , when the client-side browser 110 requests, the web plus engine 120 creates a common document (S1, S2). As described above, the common document is a configuration of a commonly used base screen consisting of a top, a body, and a bottom.

Subsequently, when the web plus engine 120 requests the handler of the corresponding screen from the web server 200 through xmlHttpRequest, the web server 200 provides the handler 213, and when requesting the screen to be used for the handler 213, the screen 214 ) is delivered (S3 to S6). At this time, the presentation layer 210 of the web server is a handler 213 corresponding to the program source and a screen corresponding to the design, rather than a form in which the design and source are combined in one file according to the previous web application model form according to the present invention. It is managed as an independent file separated by (214).

Subsequently, the web plus engine 120 generates HTML output data based on parsing and mapping information of the handler 213 and the screen 214 and responds to the web browser 110 (S7 and S8).

When an event occurs and data is requested, the Webplus engine 120 requests data to the XML Manager 212-1 of the web server using xmlHttpRequest, and the XML Manager 212-1 of the web server performs xml parsing. After performing Data Mapping (212-

2) VO (Value Object), model (Model), and list (List) form data are delivered, and accordingly Data Mapping (212-

2) calls the business logic and requests corresponding processing (S9 to S12).

The business logic 220 processes the requirements through the resource 300 such as a database management system according to the nature of the application required, then transfers the resulting data to the Data Mapping 212-2, and the Data Mapping 212 -2) delivers the data information in the form of VO (Value Object), Model, and List to the XML Manager (212-1) again (S13 to S15).

And XML Manager (212-1) generates VO (Value Object), Model, and List type data provided by Data Mapping (212-2) as XML, and then converts them to Web Plus Engine (120). In response, the web plus engine 120 parses the received xml information and converts it into html information for updating the browser 110 to update a part of the screen of the browser 110 (S16 to S19).

As such, in the web application model according to the present invention, the web plus engine receives a request from a browser and forwards it to the web server, and generates an html file for the browser using the handler and screen received from the web server. That is, the present invention balances the roles between the client and the server by processing all user interface (UI) tasks that create a screen that is displayed to the user through a web browser in the client's web plus engine, and the server processes only business logic and data. Distributed in an efficient manner to ensure efficient use of resources.

Claims (8)

In a solution interface method for developing a web application in a web environment consisting of a client equipped with a web browser and a web server implemented with various types of server platforms,
The web pages on the web server are divided into screens corresponding to designs and handlers corresponding to programs, and implemented as separate files;
The webplus engine running on the client side calls the handler according to the request of the web browser, calls a screen corresponding to the handler, maps the handler and the screen, generates an html tag, and then sets the attribute by giving it to the web browser
A presentation method for a web application, characterized in that design and program are simultaneously developed to shorten development period and facilitate maintenance, and to be developed independently regardless of the platform of the web server. In the method for providing a web application in a client-web server structure,
A first step of generating a common document according to a request of a web browser by a web plus engine executed in the client;
a second step in which the web server provides a handler when the web plus engine requests a handler for a corresponding screen;
a third step of providing, by the web server, a corresponding screen when the web plus engine requests a screen to be used for a corresponding handler;
a fourth step of the web plus engine parsing the handler and using the mapping with the screen to create html to respond to the web browser and output it to the web browser;
a fifth step of, when an event occurs and data is requested, the web plus engine requests data from the web server, and the web server executes a predetermined business logic and returns the resulting data as an xml file; and
and a sixth step of the web plus engine parsing the xml file and providing an html file including updated data to the web browser. The method of claim 2, wherein the fifth step
When the web plus engine requests data from the xml manager of the web server, the xml manager requests the corresponding data through data mapping after parsing xml, and the data mapping calls business logic to provide the resulting data. A presentation method for web applications, characterized in that the data is transmitted to an xml manager, and the xml manager generates the resulting data as an xml file. In a web environment consisting of a client and a web server,
loading a web plus engine from the web server if the client's access is an initial access; generating, by the web plus engine, a common document according to a request of a web browser;
Calling a handler for controlling the first screen by reading a configuration file by the web plus engine; Parsing element information described in a handler called by the web plus engine; calling the screen file defined in the handler by the web plus engine;
generating a basic html tag of the object by the web plus engine parsing the handler and mapping the ID of the handler tag and the screen tag; and a step in which the web plus engine interprets an attribute defined in an element of the handler and sets the attribute in the basic html generated in the previous step. A web environment having a client-server structure, comprising: a web browser running on the client;
Upon initial access, it is loaded from the server to the client, and according to the request of the web browser, a handler and a screen of the corresponding screen are requested from the server, html output data is generated through parsing and mapping, and provided to the web browser, If new data is required according to an event, a web plus engine communicates with the server in a synchronous/asynchronous manner, receives xml data, adds html information, and transmits it to the web browser; and
A web application development system comprising a presentation unit that is executed in the server and manages documents by classifying them into handlers and screens and provides handlers and screens according to a request of the web plus engine. The method of claim 5, wherein the presentation unit
A web plus viewer manager consisting of a screen, which is an element of a screen of a web application, and a handler that connects data to the screen and controls the screen as an element of the logic of the web application;
In order to deliver the data requested by the client, the xml information received from the webplus engine is parsed and transmitted to the Data Mapping unit, and the data received from the Data Mapping unit is generated as xml information to the client It is characterized in that it is composed of a web plus data controller consisting of an XML manager that transmits data to the XML manager and the data mapping unit that connects the business logic to find corresponding data and transmits the data to the XML manager. application development system. 7. The method of claim 6, wherein the handler
A web application development system characterized by including Dataset, Transfer, Config, built-in function, and Ajax-based component library. The method of claim 5, wherein the web plus engine is implemented in JavaScript
A function of configuring one window in which the Web Plus engine is loaded according to the request of the web browser;
a function allowing the one window to be used on all screens including pop-ups without the need to reload the webplus engine;
A function to set information such as global variables and sessions by loading and parsing an environment setting file that defines common elements for implementing screens and functions;
Ability to call handlers defined directly through configuration files or URLs to implement screens and functions; a function of calling the screen files defined in the handler and drawing them at the location of each set window;
a function of dividing the controller described in the called handler by data information (XPATH) and screen classification (ID) and parsing element and attribute information;
a function of mapping the ID of the controller tag of the handler and the ID of the screen controller tag, and generating basic information by connecting the corresponding screen object;
A function that automatically implements various screen functions only with the property information declared by the developer through the controller tag property of the handler; An event handler is used through the script tag of the handler, and when an event occurs Provide functions such as data call, screen transition, pop-up, and message notification through built-in functions and user-defined scripts, and functions that enable implementation of various user-added functions;
a function of importing and reusing overlapping screens and functions from the handler as the handler and the screen are completely separated; and
The web application development system characterized in that it performs a function of reloading only desired data according to the controller tag classification of the handler.