KR101730070B1 - Method for providing webpage in SaaS ENVIRONMENT, Computer program for the same, and Recording medium storing computer program for the same - Google Patents

Abstract

The present invention relates to a web page service method in a SaaS environment, a computer program therefor, and a recording medium therefor.
According to an aspect of the present invention, there is provided a method for providing a generating means necessary for generating a web page from a web page server to a client and a rendering means required for providing a web page through a network, It manages Web page elements to include meta information files, template files, unit view files, and static view files as physical elements for creating web pages, including widgets, components, elements, handlers and interactions. An editor provided in the web page server generates a page, a master, and a widget template file based on the request information input from the client, and the parser provided in the web page server parses the page, master, and widget template file And stores the previously stored unit view file A page or a master and a widget static view file are generated by using at least one component as a component. When rendering a web page, the web page server requests a page or a master corresponding to the requested web page based on the web page information requested from the client A Web page service method in a SaaS environment configured to render a widget static view file to provide a web page is disclosed.

Description

TECHNICAL FIELD [0001] The present invention relates to a web page service method in a SaaS environment, a computer program for the web page service method, a storage medium storing the same,

The present invention relates to a web page service method in a SaaS environment, a computer program for the web page service method, and a recording medium, and more particularly, to a SaaS environment in which a generating means necessary for generating a web page and a rendering means necessary for providing a web page are provided in a SaaS environment, To a web page service method in a SaaS environment configured to be able to implement a flexible web page in response to various device environments, a computer program therefor, and a recording medium therefor.

Recently, due to the development of the computer industry and the telecommunication industry and the dissemination of Internet private lines, the number of websites of enterprises and individuals has been increasing exponentially. A home page is a file produced in HTML (Hyper Text Markup Language), and is generally referred to as an image medium that is stored in a server and displayed through a browser accessed through the web. One homepage is generally configured to include one or more pages and to be capable of page conversion by a user operation or a command of the server, and each page configured to perform such conversion is generally referred to as a web page.

A typical homepage is largely composed of a program part for implementing various functions such as a page name, a menu, a graphic part, a flash part, and a member login, a board, a product search, and a shopping cart. When design coding is passed on to the programmer, the programmer must program the design coding to produce the homepage.

As a result, the costs (salaries) paid to professional staff such as web designers and web programmers related to the homepage production are considerable. In addition, frequent movements of professional staff such as web designers and web programmers are causing serious disruption to the sales and profits of agencies. This also puts a heavy burden on the users who have requested the agent to make the homepage.

Accordingly, conventionally, a portal service provider such as Hihome, Freechal, Me2u2, Daum, and Naver provides a homepage creation / management wizard function for homepage creation / management in order to easily create a homepage by users themselves.

Nevertheless, users need to prepare various contents, images and contents for home page creation and management and manage them directly or through a web hosting company. Therefore, it takes a long time to produce the homepage, There is a problem that additional cost is required to store and manage a lot of information in a hosting company's account.

As such, it is not easy for ordinary Internet users who do not have the expertise or experience to make homepages to produce homepages, so they are commissioned by a company specialized in homepage production.

At this time, the cost of production of the homepage is determined according to the components of the homepage. The cost required for the basic construction work, the time required for the content usage fee, and the fee for the content usage are small. It is taking a procedural time.

Because it takes such a lot of time and cost, it is sometimes burdensome to open a homepage in a private business or a small business site. In some cases, even after opening a homepage, when an Internet user visits the homepage, And it is difficult to carry out continuous updating.

In consideration of the above problems, some attempts have been made to provide a homepage providing service in a SaaS environment. However, there is still a limit to providing a high quality service that can provide a homepage by organically connecting a desktop environment and a mobile environment .

Korean Registered Patent No. 10-1275871 (registered on June 11, 2013)

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and it is an object of the present invention to provide a SaaS environment in which a generating means necessary for generating a web page and a rendering means necessary for providing a web page are provided, A computer program for the web page service method in a SaaS environment configured to be able to be implemented, and a recording medium therefor.

According to an aspect of the present invention, there is provided a method of providing rendering means necessary for generating a web page and a rendering means necessary for providing a web page from a web page server to a client through a network, It is a logical element for creation. It contains pages and masters, widgets, components, elements, handlers, and interactions. Web pages are created to include meta information files and template files, unit view files, When the web page element is generated, an editor provided in the web page server generates a page, a master, and a widget template file based on the request information inputted from the client, and the parser provided in the web page server transmits the page Or master, analyze the widget by parsing the template file And a unit for generating a static view file of a page or a master and a widget using at least one of the previously stored unit view files as a constituent element in accordance with the web page information, Disclosed is a web page service method in a SaaS environment configured to render a web page corresponding to a requested web page by rendering a master or widget static view file.

Preferably, the page and the master are managed in the form of the template file or the static view file, and the widget manages in the form of the template file, the static view file, and the unit view file, and the component, element, handler, The meta information file or the unit view file.

Preferably, the page, the master, and the widget include at least one of the component, the element, the handler, and the interaction.

Preferably, the widget is a functional element constituting the page, and the component is a UI (user interface) element constituting the page or the widget, and the element is an element representing an HTML (Hypertext Markup Language) element .

Preferably, the handler is an element for processing data or logic in the web page server.

Preferably, the interaction is an element that defines a screen flow processing action in the page or the widget.

Preferably, the template file is an intermediate file for creating the static view file, and the unit view file is a view file of the component or element or a JS (JavaScript) file constituting the interaction, And the template file is a file converted through the parser and output upon page rendering.

Preferably, the meta information file is a file that defines basic information of a web page component.

Preferably, the meta information file and the template file are managed in an XML file format, and the unit view file and the static view file are managed in a file format of VM / CSS / JS (Velocity Template / Cascading Style Sheet / JavaScript) .

Preferably, the parser includes a configuration file defining a processing method of a parser, a file conversion program element performing a file conversion process according to the setting file, and a variable processing program element processing a variable value in a file conversion operation, The file conversion program reads the configuration file, invokes the variable processing program, and returns a variable processing result value to convert the page, master, and widget template file into a page or a master corresponding to each template file , And a widget static view file.

Preferably, the conversion process for the page or the master template file parses the template file requested to be converted, parses the setting file, and stores the widget template file and the file defined in the template file, Extracts the variable processing object from the intermediate template data, calls the variable processing program, returns the variable processing result value, and outputs the static processing result to the static view And generating the static view file through a process of generating file data.

According to another aspect of the present invention, a computer program stored in a medium for executing a web page service method in SaaS environment in combination with hardware is disclosed.

According to another aspect of the present invention, there is provided a computer-readable recording medium having recorded thereon a computer program for executing a method of servicing a web page in a SaaS environment in a computer.

The present invention provides an advantage that SaaS environment provides a generating means necessary for generating a web page and a rendering means necessary for providing a web page, and a flexible web page can be implemented in various device environments.

1 is a system configuration diagram for providing a web page service method in a SaaS environment according to an embodiment of the present invention;
2 is a diagram illustrating a page creation process in a web page service method in a SaaS environment according to an embodiment of the present invention;
3 is a diagram illustrating a page editing process in a web page service method in a SaaS environment according to an embodiment of the present invention;
4 is a diagram illustrating a widget generating process in a web page service method in a SaaS environment according to an embodiment of the present invention;
5 is a diagram illustrating a widget editing process in a web page service method in a SaaS environment according to an embodiment of the present invention;
6 is a diagram illustrating a logical structure of a web page in a web page service method in a SaaS environment according to an embodiment of the present invention;
FIG. 7 is a diagram illustrating the concept of each element of a logical structure of a web page in a web page service method in a SaaS environment according to an embodiment of the present invention;
8 is a diagram illustrating the types of elements of a logical structure of a web page in a web page service method in a SaaS environment according to an embodiment of the present invention;
FIG. 9 is a diagram illustrating a physical structure (file structure) of a web page in a web page service method in a SaaS environment according to an embodiment of the present invention;
FIG. 10 is a diagram illustrating the concept and file format of each element of a physical structure of a web page in a method of providing a web page in a SaaS environment according to an embodiment of the present invention; FIG.
11 is a diagram illustrating a correlation between elements of a logical structure of a web page and elements of a physical structure in a web page service method in a SaaS environment according to an embodiment of the present invention;
FIG. 12 is a diagram illustrating a mutual relation between each element of a logical structure of a web page and each element of a physical structure and a file format thereof in a web page service method in a SaaS environment according to an embodiment of the present invention;
13 is a diagram illustrating a process of generating a static view file in a web page service method in a SaaS environment according to an embodiment of the present invention;
14 is a flowchart illustrating a parser process for generating a static view file in a web page service method in a SaaS environment according to an embodiment of the present invention;
15 is a diagram illustrating a process of parsing a static view file in a web page service method in a SaaS environment according to an embodiment of the present invention in more detail;
16 is a diagram illustrating a page rendering process in a web page service method in a SaaS environment according to an embodiment of the present invention.

The present invention may be embodied in many other forms without departing from its spirit or essential characteristics. Accordingly, the embodiments of the present invention are to be considered in all respects as merely illustrative and not restrictive.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms.

The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, .

On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise.

In the present application, the terms "comprises", "having", "having", and the like are intended to specify the presence of stated features, integers, steps, operations, components, Steps, operations, elements, components, or combinations of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings, wherein like or corresponding elements are denoted by the same reference numerals, and a duplicate description thereof will be omitted.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

The web page service method in the SaaS environment of the present embodiment provides the SaaS environment with the generating means necessary for generating the web page and the rendering means necessary for providing the web page and is configured to be capable of implementing a flexible web page in various device environments .

1 is a system configuration diagram for providing a web page service method in a SaaS environment according to an embodiment of the present invention.

The web page service method in the SaaS environment of the present embodiment provides a generating means necessary for generating a web page and a rendering means necessary for providing a web page from the web page server 200 to the client 300 through the network 10. The manager client 100 is further interlocked with the web page server 200 so that the server management related to the web page service provision of the present embodiment can be performed.

The web page server 200 of the present embodiment includes a controller system 210 that controls and manages events for providing a web page creation service and a web page rendering service at the request of the client 300, A service system 220 for providing a web page creation service and a web page rendering service under the control of the service system 220 and various file management functions necessary for a web page creation service and a web page rendering service in cooperation with the service system 220 A DBMS 240 that manages a DB relating to a web page creation element such as a page and a widget in cooperation with the service system 220 and a DBMS 240 that manages a page configuration / And a local DB 250 for managing information.

The service system 220 provides overall functions for a web page creation service and a web page rendering service, and provides functions such as a page editor, a widget editor, and a parser.

The client 300 of the present embodiment accesses the web page server 200 via the network 10 (Internet, mobile communication network, etc.) and receives the generating means necessary for generating the web page, or provides the rendering means necessary for providing the web page It can be understood as a receiving client, and can include a user client using a rendered web page. Such a client 300 may be implemented in the form of conventional computing means (e.g., PC, tablet computer), mobile terminal, or the like.

FIG. 6 is a diagram illustrating a logical structure of a web page in a web page service method in a SaaS environment according to an embodiment of the present invention. FIG. 7 is a diagram illustrating a web page service method in a SaaS environment according to an embodiment of the present invention. FIG. 8 is a diagram illustrating the types of elements of a logical structure of a web page in a method of providing a web page in a SaaS environment according to an embodiment of the present invention, and FIG. 9 (File structure) in a web page service method in a SaaS environment according to an embodiment of the present invention. FIG. 10 is a diagram illustrating a web page service method in a SaaS environment according to an embodiment of the present invention FIG. 11 is a diagram illustrating a concept of each element of a physical structure of a web page and a file format in the SaaS environment according to an embodiment of the present invention. FIG. 12 is a diagram illustrating a correlation between each element of a logical structure of a web page and each element of a physical structure in a web page service method of FIG. 12; and FIG. 12 is a diagram illustrating a web page service method in a SaaS environment according to an embodiment of the present invention. And also shows the mutual relationship between each element of the logical structure and each element of the physical structure and the file format thereof.

In this embodiment, a logical element for generating a web page includes a page and a master, a widget, a component, an element, a handler, and an interaction. The meta information file and the template file, the unit view file, Manage Web page elements to include view files.

The page and the master are managed in the form of the template file or the static view file and the widget is managed in the form of the template file, the static view file and the unit view file, and the component, element, handler, File or unit view file.

According to the present embodiment, since the physical elements can be managed correspondingly in various device environments, it is possible to implement a flexible web page corresponding to each device environment.

Preferably, the page or master and the widget include at least one of the component, the element, the handler, and the interaction.

The correspondence between the logical elements and the physical elements of such a web page element and the hierarchical structure of each element can be understood by way of example with reference to FIGS. 6 and 11, and an example of a preferred file format is exemplarily shown in FIG. 12 Can be understood.

In this embodiment, a page can be understood as a basic element for constituting a web page.

The master can be understood as a layout in which the elements of the page are set in advance. For example, the page may be set to have a separate layout according to individual page characteristics at the request of the client, or may have a layout by selectively applying a preset page master. When a master is applied, the user can be provided with a more uniform and convenient page structure. To this end, a separate user UI for application of the master may be provided.

For reference, the module illustrated in FIG. 8 can be understood as an element of a user function view that is implemented by a page or a master. For example, the module illustrated in FIG. 8 can be a board, a membership, a cafe, .

In the present embodiment, the widget is a functional element constituting the page. For example, widgets such as a login widget, a post extracting widget, and a banner widget may be managed.

The component is a user interface (UI) element constituting the page or the widget. For example, components such as a calendar, a counter, a grid, and a map may be managed.

The element is an element representing an HTML (Hypertext Markup Language) element. For example, elements such as audio, bookmarks, button images, and check boxes can be managed.

In addition, the handler is an element for processing data or logic in the web page server, and the interaction is an element for defining a screen flow processing action in the page or the widget. For example, a handler receives an HTTP request from a client, processes the request, and returns the result to the request or JSON format.

The concept of these web page logical elements may be understood by way of example in FIG. 7, and various forms actually managed may be understood by way of example with reference to FIG.

In the present embodiment, the template file is an intermediate file for creating the static view file, and the unit view file is a view file of the component or element or a JS (JavaScript) file constituting the interaction, An information file is a file that defines the basic information of a web page component.

The static view file is a file in which the template file is converted through a parser and is output at the time of page rendering.

In a preferred embodiment, the meta information file and the template file are managed in an XML file format, and the unit view file and the static view file are managed by any of VM / CSS / JS (Velocity Template / Cascading Style Sheet / JavaScript) Manage in one file format.

The relationship of these web page physical elements can be understood through FIG. 9, and the concept of physical elements and the file format can be exemplarily understood through FIG.

FIG. 2 is a diagram illustrating a page creation process in a web page service method in a SaaS environment according to an embodiment of the present invention. FIG. 3 is a flowchart illustrating a page editing process in a web page service method in a SaaS environment according to an embodiment of the present invention. Fig.

In the web page service method of the present embodiment, when a web page element is created, an editor provided in the web page server generates a page, a master, and a widget template file based on the request information input from the client, The parser parses the page, master, and widget template file, and generates a page, a master, and a widget static view file using at least one of the unit view files previously stored according to the analysis result as a component.

For example, the above process can be executed as shown in Table 1 below, and a detailed description of the work process will be described later.

sequence of the work Work process Explanation One Create template file Created when editing directly or saving editors 2 Syntax analysis Parser parses template files (eg, XML) and converts them to JSON results 3 Converting View Files Convert parsing results and unit view files into static view file data 4 Create View File Generate converted files according to static file generation rules

Referring to FIG. 2, the page creation process will be described in more detail.

When the page basic information is inputted through the page editor provided by the web page server of the present embodiment, a new page is created, and the page master is set and stored as the page DB information of the DBMS.

After the page component is added, the widget screen rendering and / or component screen rendering, element screen rendering, and handler addition process are performed according to the additional contents, and the additional contents are stored as page configuration / setting information in the local DB. To this end, in the file system, a widget unit view file, a component unit view file, and an element unit view file are read out.

In the page editing process, editing contents are stored as page configuration / setting information in the local DB through the process of position movement / size adjustment, page component addition / deletion, and interaction addition / deletion.

Thereafter, when a page component setting value is inputted through a page editor, a page information DB is generated, and a page template file is created in the file system. The page component setting value is stored as page configuration / setting information in the local DB, and the page information DB is stored as the page DB information of the DBMS.

Through the parser, the template file is read, the page transformation rules are applied to generate the page static view file data, and the pages generated by the page editor are converted to the page static view file through the static view file data. .

When a page component conversion rule is applied, a widget unit view file, a component unit view file, an element unit view file, and an interaction JS file are read and used.

With reference to FIG. 3, the page editing process will be described in more detail.

Through the page editor provided by the web page server of the present embodiment, the page template file is read out and the page component screen rendering is performed. The page template file is read from the file system.

To do this, widget screen rendering and / or component screen rendering, element screen rendering, interaction information output, handler information output, and page editing are performed. To this end, in the file system, a widget unit view file, a component unit view file, and an element unit view file are read out.

FIG. 4 is a diagram illustrating a widget generating process in a web page service method in a SaaS environment according to an embodiment of the present invention. FIG. 5 is a flowchart illustrating a widget editing process in a web page service method in a SaaS environment according to an embodiment of the present invention. Fig.

The widget creation process will be described in more detail with reference to FIG.

Widget basic information is input through the widget editor provided by the web page server of the present embodiment, and widget basic information is stored as widget configuration / setting information in the local DB.

When the widget component is added, the component screen rendering and / or element screen rendering and handler addition process are performed according to the addition, and the additional contents are stored as widget configuration / setting information in the local DB. To this end, in the file system, a component unit view file and an element unit view file are read out.

Thereafter, in the editing process of the widget, edit contents are stored as widget configuration / setting information in the local DB through the process of location movement / size adjustment, widget component addition / deletion, and interaction addition / deletion.

Thereafter, when the widget component setting value is input through the widget editor, the widget component setting value is stored as widget configuration / setting information in the local DB.

When widget coverage is selected, widget information DB is stored as widget DB information of DBMS, and widget template file is created in file system.

Through the parser, the template file is read out, the conversion rule for each widget component is applied, and widget static view file data is generated, and widget static view file is created in the widget editor and file system accordingly.

When a transformation rule is applied to a widget component, a component unit view file, an element unit view file, and an interaction JS file are read and used.

With reference to FIG. 5, the widget editing process will be described in more detail.

Through the widget editor provided by the web page server of the present embodiment, a widget template file is selected and read out, and a widget component screen rendering is performed. The widget template file is read from the file system.

To do this, component screen rendering and / or element screen rendering, interaction information output, handler information output, and widget editing are performed. To this end, in the file system, a component unit view file and an element unit view file are read out.

FIG. 13 is a diagram illustrating a process of generating a static view file in a web page service method in a SaaS environment according to an embodiment of the present invention. FIG. FIG. 15 is a diagram illustrating a process of parsing a parser for generating a static view file according to an embodiment of the present invention. FIG. 15 is a diagram illustrating a parser for generating a static view file in a method for rendering a web page in a SaaS environment according to an embodiment of the present invention. FIG. 5 is a diagram showing the processing procedure in more detail.

The parser of the present embodiment can be understood as an independent program that is responsible for converting a page / master / widget template file into a respective static view file.

In the present embodiment, the parser includes a configuration file that defines a processing method of a parser, a file conversion program element that performs file conversion processing according to the setting file, and a variable processing program element that processes variable values in a file conversion operation The file conversion program reads the configuration file, invokes the variable processing program, and returns a variable processing result value to convert the page, master, or widget template file into a page corresponding to each template file Or master, widget static view file. The construction and execution process of such a parser can be understood from FIG. 13 and FIG.

Referring to FIG. 15, a process of a parser for generating a static view file for a page or a master template file will be described in more detail.

First, when a template file conversion is requested, the parser parses the template file requested to be converted and parses the configuration file. To this end, in the file system, the page / master / widget template file is read out and the parser configuration file is read out.

Next, the parser reads the widget template file, the component file, and the file defined in the template file requested to be converted in the element file, and combines the read setting values from the setting file to generate the intermediate template data. To this end, in the file system, a widget unit view file, a component unit view file, and an element unit view file are read out.

Next, the parser extracts the variable processing object from the intermediate template data, calls the variable processing program, returns the variable processing result value, generates static view file data, and creates and stores the static view file in the file system .

The widget static view file is also created in the same or similar manner as the above process.

16 is a diagram illustrating a page rendering process in a web page service method in a SaaS environment according to an embodiment of the present invention.

In the web page service method of the present embodiment, when a web page is rendered, a web page server renders a page, a master, and a widget static view file corresponding to the requested web page based on the web page information requested by the client, .

Referring to FIG. 16, the process of providing page rendering will be described in more detail.

When the page URL request is input from the client, the controller system calls the page controller.

Then, the service system inquires the site common information, the page master information inquiry, the page information inquiry, the handler execution, and the page view are determined. To this end, the information of the page master DB and the page DB is read out from the DBMS.

After that, the controller system performs page response rendering to the client through page view rendering. Page view When rendering, the page static view file is read from the file system.

Embodiments of the present invention include a computer readable medium having recorded thereon a program for performing various computer-implemented operations. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The media may be those specially designed and constructed for the present invention or may be those known to those skilled in the computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs, DVDs, USB drives, self-optical media such as floppy disks, And a hardware device specifically configured to store and execute program instructions such as flash memory and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like.

It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. It will be possible.

100: Administrator Client
200: Web page server
300: Client

Claims (13)

There is provided a method for providing a generating means necessary for generating a web page from a web page server to a client via a network and a rendering means necessary for providing a web page,
It is a logical element for web page creation. It includes pages and masters, widgets, components, elements, handlers, and interactions. It also includes meta information files and template files, unit view files and static view files as physical elements for web page creation. Manage Web page elements,
At the time of creating a web page element, an editor provided in the web page server generates a page, a master, and a widget template file based on the request information inputted from the client, and the parser provided in the web page server transmits the page, Parses the file, generates a page, a master, and a widget static view file using at least one of the unit view files previously stored according to the analysis result as a component,
In rendering a web page, a web page server provides a web page by rendering a page or a master or a widget static view file corresponding to the requested web page based on the web page information requested from the client,
The page and the master are managed in the form of the template file or the static view file,
The widget manages the template file, the static view file, and the unit view file,
Wherein the component, the element, the handler, and the interaction are managed in the form of the meta information file or the unit view file.
delete The method according to claim 1,
The page or master, widget,
Wherein the at least one element comprises at least one of the component, the element, the handler, and the interaction.
The method according to claim 1,
Wherein the widget is a functional element constituting the page,
The component is a user interface (UI) element that constitutes the page or widget,
Wherein the element is an element representing an HTML (Hypertext Markup Language) element.
The method according to claim 1,
Wherein the handler is an element for processing data or logic in the web page server.
The method according to claim 1,
Wherein the interaction is an element that defines a screen flow processing action in the page or the widget.
The method according to claim 1,
The template file is an intermediate file for creating the static view file,
Wherein the unit view file is a view file of the component or element or a JS (JavaScript) file constituting the interaction,
Wherein the static view file is a file converted by the parser through the template file, and is output during page rendering.
8. The method of claim 7,
Wherein the meta information file is a file that defines basic information of a web page component.
9. The method of claim 8,
The meta information file and the template file are managed in an XML file format,
Wherein the unit view file and the static view file are managed in a file format of any one of a VM / CSS / JS (Velocity Template / Cascading Style Sheet / JavaScript) format.
The method according to claim 1,
The parser,
A file conversion program element for performing a file conversion process according to the setting file; and a variable process program element for processing a variable value in a file conversion operation,
The file conversion program reads the configuration file, calls the variable processing program, and returns a variable processing result value,
And converting the page, master, and widget template file into a page, a master, and a widget static view file corresponding to the respective template files.
11. The method of claim 10,
The conversion process for a page or a master template file may include:
Parses the template file requested to be converted and parses the configuration file,
Reads out a widget template file, a component file, and a file defined in the template file requested to be converted among the element files, and combines the set values read from the setting file to generate intermediate template data,
Wherein the static view file is generated by extracting a variable processing object from the intermediate template data, calling the variable processing program, and returning a variable processing result value to generate static view file data. Web page service method.
13. A computer program stored on a recording medium for executing a web page service method in a SaaS environment according to any one of claims 1 to 11 in combination with hardware.
A computer-readable recording medium on which a computer program for executing a web page service method in a SaaS environment according to any one of claims 1 to 11 is recorded.

Images