KR20090002032A - Executing module for playing ui plug-in in universal web browser, ui plug-in development apparatus and method thereof - Google Patents

Abstract

An execution module for executing a UI(User Interface) plugin in a universal web browser, and a device and a method for developing the UI plugin according to a WYSIWYG(what you see is what you get) mode are provided to offer the execution module executable in the universal web browser by processing each UI plugin as a component. A UI development module(310) develops a UI according to a WYSIWYG mode. A plugin development module develops a plugin corresponding to the UI(320). The plug-in development module comprises an XML(extensible Markup Language) editor defining more than of property, style, or event by using XML spec, a component editor editing a source implementing a function defined in XML by using Java scrip and Java, and a compiler compiling the Java and Java script source developed by the component editor.

Description

Execution module, GUI plug-in development apparatus and method for executing GUI plug-in in a universal web browser {Executing module for playing UI plug-in in universal web browser, UI plug-in development apparatus and method}

1 is a block diagram schematically illustrating an execution module for executing an Ajax-based application program according to an embodiment of the present invention.

2 is a view showing the configuration of the brow engine unit according to an embodiment of the present invention.

3 is a block diagram of a UI plug-in development apparatus for developing a UI and plug-in according to an embodiment of the present invention.

4 is a functional block diagram showing the configuration of a UI development module according to an embodiment of the present invention.

5 is a functional block diagram showing a plug-in development module configuration according to an embodiment of the present invention.

6 is a flowchart illustrating a method of using a UI plug-in after payment from a web server in a client terminal according to an embodiment of the present invention.

7 is a flowchart illustrating a method of using a UI plug-in processed by a DRM from a web server in a client terminal according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

100: execution module 110: application unit

120: UI plug-in unit 122: basic UI plug-in

130: browser engine unit 124: extended UI plug-in

210: Ajax engine unit 220: plug-in engine unit

230: style processing unit 240: data management unit

250: debugging unit 260: monitoring unit

270: logging unit 280: communication unit

300: UI plug-in development device 310: UI development module

320: plug-in development module

410: Wizard Division 420: Witchwick Editor

430: code completion unit 440: event generation unit

450: grammar checking unit 460: UI debugging unit

510: XML editing unit 520: component editing unit

530: compilation unit 540: plug-in debugging unit

550: deployment unit 560: license unit

The present invention relates to a UI plug-in development apparatus for developing a UI and a plug-in constituting an execution module and a UI plug-in for executing an application in a web browser.

The web-based business is evolving from the web 1.0-based value chain to the web 2.0-based Internet ecosystem. In the existing Web 1.0, users could not participate in various contents or services, but in Web 2.0, Internet services work in both directions instead of one directions.

In particular, X-Internet technology, which implements the functions of existing C / S in a browser, has been introduced in the enterprise market because of its advantages of being eXtend and executable (eXecute). I have it. In contrast, Ajax, which can be run in any browser that supports XML processing and JavaScript, is applied to various web applications based on standards-based compatibility.

Ajax (Asynchronous JavaScript and Xml) architecture, a representative technology of Web 2.0, can reduce the system load and eliminate unnecessary development effort by processing only the changed part of the HTML page and displaying it on the original page without reloading when changing the screen. .

Nevertheless, the low productivity and difficulty of maintenance due to the complexity of Ajax, the technical foundation of Web 2.0, has hindered the application of various software and applications required by the new web business.

Therefore, the UI plug-in can be modularized while maintaining the advantages of improving UI performance through asynchronous communication, reducing network traffic, separating client development, and implementing a powerful user environment such as C / S. It is necessary to provide a grammar structure.

Accordingly, the present invention has been made to solve the above-described problem, and includes a UI plug-in component-processing the user interface (UI) for each plug-in, the UI plug-in is to provide an executable module executable in a general-purpose web browser It is done.

In addition, another object of the present invention is to provide a UI plug-in development apparatus for developing the UI and plug-in constituting the UI plug-in.

Another object of the present invention is to provide a method for developing a UI plug-in in a web server connected to one or more client terminals, and a recording medium on which the method is recorded.

Other objects of the present invention will become more apparent through the preferred embodiments described below.

According to an aspect of the present invention for achieving the above object, the present invention is an execution module for executing an application program in a web browser, the UI plug-in component processing a user interface (UI) for each plug-in A UI plug-in including: wherein the UI plug-in is executable in a universal web browser; And a browser engine unit for disposing the UI plug-in and performing communication with a web server.

In addition, the UI plug-in may include at least one of a basic UI plug-in, an extended UI plug-in generated by modifying the UI plug-in or recombining the UI plug-ins, and a combination thereof.

The basic UI plug-in and the extended UI plug-in may include an input, an output, a textarea, a secret, a button, a check box, a radio, and a selection box. (Select Box), file upload, image, table, line, dot, shape, grid, chart, menu ), Toolbar, treeview, tab, calendar, browser component, active-X wrapper, edit masking, progress bar bar, a color picker, a modal window, and combinations thereof.

The browser engine unit may include an ajax engine unit supporting an abstraction layer to be executed in the general-purpose web browser; And a plug-in engine unit configured to execute and manage the UI plug-in.

In addition, the Ajax engine unit may abstractly provide XMLHTTP and support encryption / decryption of data.

The browser engine unit may further include a communication unit for performing communication with the web server in an asynchronous manner.

The browser engine unit may further include a data manager that provides an application program interface for processing data required for the communication.

The browser engine unit may further include a style processor configured to process style information of a program executed on the web browser.

In addition, the browser engine unit may further include a logging unit for leaving a log in a program executed in the web browser.

The browser engine unit may further include a debugging unit integrated with a debugger of the web browser to check a bug of the application program while executing the application program.

In addition, the browser engine unit may further include a monitoring unit for monitoring the state of the platform.

According to another aspect of the present invention, the present invention provides a UI plug-in development device for developing a UI and plug-in, UI development module for developing the UI according to the WYSIWYG method; And a plug-in development module for developing the plug-in corresponding to the UI, wherein the UI plug-in is a component processing of the UI corresponding to each plug-in, and the UI plug-in can be executed in a general-purpose web browser. UI plug-in development device.

The UI plug-in may be at least one of a basic UI plug-in, an extended UI plug-in generated by modifying the UI plug-in, or recombining the UI plug-ins, and a combination thereof.

The basic UI plug-in and the extended UI plug-in may include an input, an output, a textarea, a secret, a button, a check box, a radio, and a selection box. (Select Box), file upload, image, table, line, dot, shape, grid, chart, menu ), Toolbar, treeview, tab, calendar, browser component, active-X wrapper, edit masking, progress bar bar, a color picker, a modal window, and combinations thereof.

In addition, the UI development module includes a Wikiwick editing unit for developing a program by placing the UI on the screen using a mouse and keyboard; Code auto-completion unit for automatically searching for and inputting an inputtable API and variable names; And an event generator that provides a JavaScript editing screen to implement an event handler.

In addition, the UI development module may further include a UI wizard for generating a template-based screen.

In addition, the UI development module may further include a grammar check unit for verifying whether or not an error of the grammar for the JavaScript.

In addition, the UI development module may further include a UI debugging unit that provides a debugger integrated with a web browser.

The plug-in development module may further include an XML editing unit defining at least one of an attribute, a style, or an event using a standardized XML specification; A component editing unit which edits a source that implements a function defined in XML using JavaScript and Java; And a compiling unit for compiling Java and JavaScript sources developed by the component editing unit.

The plug-in development module may further include a plug-in debugging unit configured to check a bug of the application program while executing the application program by being integrated with a debugger of the web browser.

In addition, the plug-in development module may include a deployment unit for deploying a plug-in; And a license unit managing a license.

According to another aspect of the present invention, the present invention provides a method for developing a UI plug-in in a web server connected to one or more client terminals, the method comprising: registering K basic UI plug-ins with the web server (K is a natural number); And registering an extension UI plug-in input from the client terminal, wherein the extension UI plug-in modifies the basic UI plug-in or another extension UI plug-in, or the base UI plug-in, another extension UI plug-in, and a combination thereof. It relates to a method for using a UI plug-in, characterized in that generated by recombining one or more of the.

In addition, the basic UI plug-in and the extended UI plug-in may be executable in a general-purpose web browser.

In addition, selecting a UI plug-in to be downloaded by the client terminal; Connecting the client terminal to a payment server for payment of the selected UI plug-in; Calculating an amount of the UI plug-in downloaded from the client terminal using the payment server; And downloading the paid UI plug-in from the web server.

In addition, DRM processing the UI plug-in; Allowing the UI plug-in to be distributed to one or more client terminals without making a payment; If the client terminal detects that a play command for the UI plug-in in an unpaid state is generated, controlling the UI plug-in providing server to perform a payment procedure for the UI plug-in; When the payment is completed, storing payment information including a UI plug-in identifier for identifying the paid UI plug-in and a user identifier for identifying the user; And authenticating the paid UI plug-in with reference to the payment information, wherein the authenticated UI plug-in may be played on the client terminal.

According to another aspect of the present invention, the present invention provides a method for developing a UI plug-in in a web server connected to one or more client terminals, the method comprising: registering K basic UI plug-ins with the web server (K is a natural number); And a program executing the step of registering the extended UI plug-in input from the client terminal, recorded on a readable recording medium, wherein the extended UI plug-in modifies the basic UI plug-in or another extended UI plug-in, It is generated by recombining one or more of the other extended UI plug-ins and combinations thereof, wherein the basic UI plug-in and the extended UI plug-in are executable in a general-purpose web browser.

The client terminal may further include downloading the UI plug-in from the web server.

In addition, the client terminal is connected to the payment server to pay the amount; And calculating the amount of the UI plug-in downloaded from the client terminal by using the payment server.

In addition, DRM processing the UI plug-in; Allowing the UI plug-in to be distributed to one or more client terminals without making a payment; If the client terminal detects that a play command for the UI plug-in in an unpaid state is generated, controlling the UI plug-in providing server to perform a payment procedure for the UI plug-in; When the payment is completed, storing payment information including a UI plug-in identifier for identifying the paid UI plug-in and a user identifier for identifying the user; And authenticating the paid UI plug-in with reference to the payment information, wherein the authenticated UI plug-in may be played on the client terminal.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not 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 the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that no other component exists in the middle.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination 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. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, and in describing the present invention with reference to the accompanying drawings, the same or corresponding components are given the same reference numerals regardless of the reference numerals. Duplicate explanations will be omitted.

1 is a block diagram schematically illustrating an execution module for executing an Ajax-based application program according to an embodiment of the present invention.

Referring to FIG. 1, the execution module according to the present embodiment may include an application program, a UI plug-in unit, and a browser engine unit.

The application program unit is a web 2.0 based application, that is, an Ajax based application, and may correspond to a program that executes a UI plug-in.

The UI plug-in unit 120 may include UI plug-ins in which a user interface (“UI”) is processed for each plug-in.

Here, the user interface (UI) refers to a part of a program in which a user and a software program interact with each other to exchange information between the user and the computer. The UI includes a command-line interface for operating a program by a user inputting a command through a keyboard, a menu-driven interface for operating a command by menu selection, and a photoelectric pen and mouse. And a graphical user interface (GUI) using a positioning tool, such as a control ball or a joystick, to operate a graphics display program.

Also, plug-ins are programs that can be easily installed and used as part of the web, and are automatically recognized by the browser, and their functions are integrated into the main file that is currently appearing. In addition, since the plug-in according to the present embodiment is implemented through the object-oriented technology, the user can change to another form as needed.

In this embodiment, the UI plug-in refers to a component composed of a plug-in and a corresponding UI. The plug-in program is written for each UI function, and the UI plug-in is matched for each plug-in. In other words, it can be referred to as a breakdown by function.

In addition, in the present embodiment, the UI plug-in generated by combining n UI plug-ins may be viewed as one UI plug-in. For example, a combination of separate UI plug-ins having chart and tab functions may be classified into one UI plug-in.

In this case, the UI plug-ins can be operated and reused individually, so that a new type of UI plug-in can be developed by combining components.

Reflecting this, the UI plug-in unit according to the present embodiment may include at least one of a basic UI plug-in, an extended UI plug-in 124 generated by modifying the UI plug-in or recombining the UI plug-ins, and a combination thereof.

Here, the "basic UI plug-in 122" may be referred to as a UI plug-in on which an extension UI plug-in 124 can be generated by modification or recombination, such as a UI plug-in provided by an operator of a web site.

In addition, the "extended UI plug-in 124" may be a new UI plug-in generated by modifying the basic UI plug-in 122 or another extended UI plug-in 124. In addition, the "extended UI plug-in 124" may also be viewed as an extended UI plug-in 124, which is a UI plug-in created by combining one or more basic UI plug-ins 122 or extended UI plug-ins 124.

The basic UI plug-in 122 and the extended UI plug-in 124 are, for example, input, textarea, secrets for entering passwords, secrets, buttons for event handling, checkboxes ( checkboxes, radios, select boxes, file uploads that support various parts, images, tables, output and lines, dots ) And a form component and an output component function, which are essential for composing a screen such as a shape formed of a basic figure, a connection line, and the like, may be included.

In addition, in addition to the above components, the basic UI plug-in 122 and the extended UI plug-in 124 provide an extension component that can play a role of supporting a program identically to the existing C / S or X-Internet. It may include.

For example, a chart that can be expressed in various forms such as a grid, a bar, a pie, a line chart for inputting and outputting tens of thousands of large amounts of data, and a menu capable of controlling authority (menu), permission-controlled toolbar, tree-view tree view, tab to divide complex screens, calendar element linked with holiday data, etc. It may include the function of.

In addition, the basic UI plug-in 122 and the extended UI plug-in 124 include a browser component that displays an existing HTML page, an active-X wrapper, and a creator that controls Active-X as a plug-in. Edit masking in conjunction with Formatter and Validator, Progress bar to show progress, Color Picker to select various colors, Modal It may include a function such as a modal window supporting a window.

The browser engine 130 serves as an execution environment for starting a web 2.0 based application program, which will be described later in FIG. 2.

2 is a view showing the configuration of the brow engine unit according to an embodiment of the present invention.

Referring to FIG. 2, the browser engine unit 130 according to the present embodiment is an execution environment for starting a web 2.0 based application program, and includes the Ajax engine unit 210, the plug-in engine unit 220, and the style processing unit 230. It may be configured to include a data management unit 240, debugging unit 250, monitoring unit 260, logging unit 270 and communication unit 280.

Ajax engine unit 210 is a standard technology that can be executed in various general-purpose browsers such as Internet Explorer, Firefox, Safari, Opera, etc. by combining JavaScript and XMLHTTP technology. Based on RIA (Rich Internet Application) is implemented and provided. To this end, the Ajax engine unit 210 may provide an abstraction layer abstracting XMLHTTP so that the plug-in engine unit 220, the style processing unit 230, and the communication unit 280 may operate independently of the browser.

In addition, the Ajax engine unit 210 may support association, encryption, and decryption with a data encryption solution for security. Specifically, it may support PKI based encryption and signature used for connecting to financial institutions, and support SSL for secure communication.

In addition, the Ajax engine unit 210 may support development of various applications by supporting a common library that supports cookie and session processing.

The plug-in engine unit 220 is an engine for executing and managing a plug-in which is a basic unit of the UI plug-in. The plug-in engine unit 220 may determine a screen layout, arrange plug-ins, and manage a lifecycle of each plug-in.

In addition, the plug-in engine unit 220 may provide a function of storing and setting state information of the plug-in to support a configuration of a dynamic web application faithful to the user's experience. In particular, since the plug-in engine unit 220 according to the present embodiment can support all plug-ins implementing the standard plug-in specification provided by the platform, plug-in development by various users can be performed, thereby improving the development productivity of the program. have.

The style processing unit 230 may serve to process style information of a program executed on a web browser, which may include a UI style and a skin manager function.

Here, the UI style supports standard CSS to apply a consistent and diverse design, and further supports an expandable stylesheet according to the plug-in to support various designs according to the UI plug-in.

If the UI style is to apply a style sheet to the unit program, the skin manager is a module that can support the design and formatting of the entire web program. Designers designing web applications can provide services by transforming pages of the same content into completely different UIs by creating skins of various designs.

The data manager 240 may provide XML, JSON (JavaScript Object Notation) API (Application Program Interface) for processing various types of data required by the communication unit 280. Through such an API, the execution module 100 according to the present embodiment can easily use such data by a developer of an application program without knowledge of a complicated API such as a separate SOAP XML or JSON protocol.

In addition, the data manager 240 converts data such as numbers, dates, currencies, social security numbers, and telephone numbers by providing a formatter and a validator for providing input value verification or conversion functions necessary for data processing. Function and verification of required input values can be provided. In particular, the required input item verification function can be used in various forms beyond simply input verification by providing an extended API, and can be combined with a skin manager to provide a screen display function when an error occurs.

In addition, the data manager 240 may provide a function that can be immediately displayed on the screen without generating XML through data buffering.

The logging unit 270 may provide an API and a console so that a developer who develops an application program may log a program executed in a web browser. In addition, when transferred to the operating environment, only by setting environment variables, a log level management framework may be provided to prevent generation of such logs.

The debugging unit 250 may provide a debugger integrated with a debugger of a browser so as to check a bug of an application while executing the program in a test environment. This allows developers to easily debug complex Web 2.0 applications by taking advantage of features such as breakpoints and various watchers that can be paused when a program reaches a specific place to eliminate defects and wait for user input. can do.

The monitoring unit 260 performs a role of providing a monitor that can monitor various states of the engine. For example, the monitoring unit 260 cleans up the memory for the XMLHTTP state, the communication data monitor, the encryption / decryption module information, the object information, the memory space information, and the garbage collection through a monitor console. Information can be monitored.

The communication unit 280 may support XMLHTTP, a core module of the Ajax architecture for interacting with a server. In particular, WSDL, SOAP to support SOA by abstracting XMLHTTP, REST mainly used in mash-up through open API, Servlet / PHP / ASP interworking of POST method for JSON connection, and non-standard XML communication Interworking modules such as XML-RPC, support for PKI-based encryption and signatures used to connect to financial institutions such as banks, insurance companies, and securities firms, and an extension API for other non-standard plain text communication. Can be provided.

 As described above, according to the present embodiment, through an engine of which browser compatibility is guaranteed, an interoperable page that operates in an operating system (OS) other than Internet Explorer or another browser can be easily implemented. In addition, it is possible to implement RIA environment superior to X-Internet functionally only with standard browser, so that it is easy to develop web software by supporting web environment as platform.

3 is a block diagram of a UI plug-in development apparatus for developing a UI and plug-in according to an embodiment of the present invention.

Referring to FIG. 3, the UI plug-in development device 300 may include a UI development module 310 and a plug-in development module 320.

The UI development module 310 is a tool for easily developing a Web 2.0 program running on a platform. The UI development module 310 may develop a program in a WYSIWYG method such as 4GL tools such as Visual Basic and Delphi. .

In addition, the plug-in development module 320 is a tool for supporting the easy development of the plug-in constituting the UI plug-in.

As described above, the UI plug-in may include a UI and a plug-in program. The UI plug-in may process the UI corresponding to each plug-in.

Hereinafter, the UI development module 310 and the plug-in development module 320 will be described in detail.

4 is a functional block diagram showing the configuration of a UI development module according to an embodiment of the present invention.

Referring to FIG. 4, the UI development module 310 includes a wizard unit 410, a Wiziwick editor 420, a code completion unit 430, an event generator 440, a grammar checker 450, and a UI debugging unit 460. It may be configured to include).

The wizard unit 410 is a template-based screen generation tool used when developing a standardized program. The wizard 410 generates a standardized page such as an input, an output, and an inquiry page for a single table in a wizard manner. Developing a program using this wizard method can achieve remarkable development productivity by eliminating the repetitive and unnecessary work required when generating the wizard. This can be especially useful when you are developing an application with a large number of formatted pages.

The Wiegwick editing unit 420 develops a program by placing a UI defined in advance on the screen using a mouse and a keyboard as a Widgwick-type UI development tool. Using the Wizwick-style development tool, you can easily create an environment in which developers and designers can collaborate to increase the development productivity of web applications. In addition, the developed screen is saved as an XML file conforming to the XForms 1.1 standard, and the program is executed using this file on the platform.

The code completion unit 430 provides a function of automatically searching for and inputting an inputtable API and a variable name to facilitate development during JavaScript programming or XML programming. In addition, help for the function and function is provided on the same screen so that the necessary information can be easily obtained.

The event generator 440 provides a JavaScript editing screen to implement an event handler coupled with an XForms event. It also provides a mapping feature that allows you to combine predefined Actions and XForms events.

The grammar checker 450 compensates for the difficulty of checking grammatical errors at the time of development, which is a disadvantage of JavaScript, an interpreter language, and the development tool automatically generates grammar for JavaScript that conforms to the ECMA-262 standard. It provides a JavaScript Parser function that verifies it. It also provides a variety of features, such as extracting useful information from a JavaScript parser and tracking the interrelationships between programs.

The UI debugging unit 460 provides a debugger integrated with a web browser to test while executing the developed application. The UI debugging unit 460 provides functions such as breakpoints and various watchers to easily catch bugs in the program.

5 is a functional block diagram illustrating a plug-in development module configuration according to an embodiment of the present invention.

Referring to FIG. 5, the plug-in development module 320 includes an XML editing unit 510, a component editing unit 520, a compiling unit 530, a plug-in debugging unit 540, a deploying unit 550, and a license unit 560. It may be configured to include.

The XML editor 510 may define an attribute, a style, an event, etc. using a standardized XML specification. In order to do this standardization, predefined XML Schema and XML Editor are provided to make it easy to write XML conforming to the standard.

The component editor 520 is a source editor that actually implements various functions defined in the plug-in XML. It is divided into Java module used in platform and Java module used in UI development tool, and each module can be easily implemented by using predefined plug-in parent component.

Compiler 530 is a tool that can compile Java and JavaScript source developed in the component editor 520 and correct the grammatical error.

The plug-in debugging unit 540 is a debugger for testing while executing the developed plug-in. The debugger for the JavaScript part of the plug-in extends the debugger of the existing Wikiwick UI development tool, and the debugger for the Java part to be integrated into the UI development tool extends Java's standard debugger.

The deployment unit 550 is a tool for distributing the tested plug-in, and the license unit 560 is a tool for applying a license policy and managing a license.

6 is a flowchart illustrating a method of using a UI plug-in after payment from a web server in a client terminal according to an embodiment of the present invention.

Referring to FIG. 6, in step 610, an operator of a web server may first register K basic UI plug-ins 122 on the web site by uploading K (K is a natural number) to the server.

In operation 620, the user of the client terminal may select a UI plug-in to be downloaded, and in operation 630, the web server may calculate the amount of the UI plug-in and inquire of the client terminal whether to pay for the UI plug-in.

Thereafter, in step 620, the client terminal may download the basic UI plug-in 122 registered through the web site operated by the web server. In this case, the web site may authenticate whether the client terminal has permission to download the UI plug-in by login or other forms.

As described above, the UI plug-in downloaded from the client terminal may be referred to as a basic UI plug-in 122. That is, when the UI plug-in first provided by the web server and the extension UI plug-in 124 modified by another client terminal using the UI plug-in are uploaded to the web site again, this is a basic UI plug-in for another client terminal. 122).

In operation 630, the client terminal may generate another extension UI plug-in 124 by downloading another basic UI plug-in 122 from the web server, modifying the downloaded basic UI plug-in 122, or recombining the plurality of UI plug-ins. .

In this case, the basic UI plug-in 122 and the extended UI plug-in 124 may be executable in a general-purpose web browser. This may be possible, for example, when running a UI plug-in using the aforementioned AX Engine.

In operation 640, the client terminal may upload and register the extension UI plug-in 124 on a web site operated by a web server. In this case, the client terminal may add a step of authenticating the authority from the operator of the web server in order to upload to the web site.

According to the present embodiment, by matching the UI with the plug-in for each function and classifying them into components, a third party can freely reuse them and further recombine to develop a new UI plug-in.

7 is a flowchart illustrating a method of using a DRM-processed UI plug-in from a web server in a client terminal according to an embodiment of the present invention.

In the embodiment of FIG. 7, unlike FIG. 6, a method of allowing a distribution of an unpaid UI plug-in, such as a download, and then allowing the execution of the UI plug-in after payment is illustrated.

In operation 710, the web server may maintain a database of DRM-processed UI plug-ins. In this embodiment, since the web server only permits distribution of the unpaid UI plug-in and does not allow execution of the unpaid UI plug-in, DRM processing for the UI plug-in registered in the web site will be essential.

Here, DRM (Digital Rights Management) refers to digital rights management, and may be a technology and service that protects the rights and interests of providers by preventing unauthorized use of digital content. Although the DRM is specified in the present embodiment, all the techniques for encrypting digital content so that only authorized users execute the content can be included in the present invention.

When the download request for the DRM-processed UI plug-in is received from the client terminal, the web server may transmit the UI plug-in to the client terminal at the request of the user regardless of whether or not the UI plug-in selected by the user of the client terminal is paid. .

In this case, whether a predetermined UI plug-in is a payment state or an unpaid state to a specific user may include, for example, an information database unit (not shown) corresponding to a payment server maintained in a web server or a payment server included in a web server. It can be determined by referring to payment information for each user and UI plug-in stored through.

In addition, the user may download and store the DRM-processed UI plug-in transmitted from the web server, or may transmit the same to another medium such as another client terminal.

Subsequently, if a playback command for the unpaid UI plug-in downloaded to the client terminal is input in step 730, the client terminal first accesses a web server and inquires whether payment for the corresponding UI plug-in has been performed. Can be.

The web server may determine that the corresponding UI plug-in is in an unpaid state by referring to the payment information stored in the payment information database and the like, and provide a payment procedure to the user in step 760 to enable payment.

When the payment is completed, in step 760, the client terminal may perform an authentication procedure for the UI plug-in in the payment state to perform the execution command of the user, and then execute the DRM-processed UI plug-in in the authentication state.

The method of the present invention as described above may be implemented in a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.).

The present invention is not limited to the above embodiments, and many variations are possible by those skilled in the art within the spirit of the present invention.

As described above, according to the present invention, the plug-in includes UI plug-ins in which a user interface (UI) is processed for each plug-in, and the UI plug-in may provide an execution module executable in a general-purpose web browser.

In addition, according to the present invention there is an effect that can provide a UI plug-in development apparatus for developing the UI and plug-in constituting the UI plug-in.

In addition, the present invention can provide a method for developing a UI plug-in in a web server connected to one or more client terminals and a recording medium on which the method is recorded.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art that various modifications of the present invention without departing from the spirit and scope of the invention described in the claims below And can be changed.

Claims (29)

An executable module that runs an application in a web browser, A UI plug-in including a UI plug-in that processes a user interface (UI) for each plug-in, wherein the UI plug-in is executable in a general-purpose web browser; And An execution module including a browser engine unit configured to arrange the UI plug-in and perform communication with a web server. The method of claim 1, The UI plug-in unit And at least one of a basic UI plug-in, an extended UI plug-in generated by modifying the UI plug-in, or recombining the UI plug-ins, and a combination thereof. The method of claim 2, The basic UI plug-in and the extended UI plug-in Input, output, textarea, secret, button, check box, radio, select box, file upload ), Image, table, line, dot, shape, grid, chart, menu, toolbar, tree view ( treeview, tab, calendar, browser component, active-X wrapper, edit masking, progress bar, color picker, An executable module comprising at least one of a modal window and a combination thereof. The method of claim 1, The browser engine unit An ajax engine unit supporting an abstraction layer to be executable in the general-purpose web browser; And And a plug-in engine unit configured to execute and manage the UI plug-in. The method of claim 1, And the Ajax engine unit abstractly provides XMLHTTP and supports encryption / decryption of data. The method of claim 1, The browser engine unit Execution module, characterized in that it further comprises a communication unit for performing communication in asynchronous manner with the web server. The method of claim 5, The browser engine unit And a data manager configured to provide an application program interface for processing data necessary for the communication. The method of claim 1, The browser engine unit And a style processor configured to process style information of a program executed on the web browser. The method of claim 1, The browser engine unit Execution module, characterized in that it further comprises a logging unit for leaving a log in the program running in the web browser. The method of claim 1, The browser engine unit And a debugging unit integrated with a debugger of the web browser and checking a bug of the application while executing the application. The method of claim 1, The browser engine unit Execution module, characterized in that it further comprises a monitoring unit for monitoring the status of the platform. In the UI plug-in development device for developing the UI and plug-in to configure the UI plug-in, A UI development module for developing the UI according to a WYSIWYG scheme; And Including a plug-in development module for developing the plug-in corresponding to the UI, The UI plug-in is a component of the UI corresponding to each plug-in, The UI plug-in development apparatus, characterized in that which can be executed in a general-purpose web browser. The method of claim 12, The UI plug-in Basic UI plug-in, UI plug-in development device, characterized in that it is generated by modifying or recombining them. The method of claim 13, The basic UI plug-in and the extended UI plug-in Input, output, textarea, secret, button, checkbox, radio, select box, file upload ), Image, table, line, dot, shape, grid, chart, menu, toolbar, tree view ( treeview, tab, calendar, browser component, active-X wrapper, edit masking, progress bar, color picker, Apparatus for developing a UI plug-in, characterized in that it comprises one or more of a modal window and a combination thereof. The method of claim 12, The UI development module Wywickwick editing unit for developing a program by placing the UI on the screen using a mouse and keyboard; Code auto-completion unit for automatically searching for and inputting an inputtable API and variable names; And The UI plug-in development device further comprising an event generator for providing a JavaScript editing screen to implement an event handler. The method of claim 12, The UI development module UI plug-in development apparatus further comprises a UI wizard for generating a template-based screen. The method of claim 12, The UI development module UI plug-in development device further comprises a grammar check unit for verifying whether the syntax error for JavaScript. The method of claim 12, The UI development module UI plug-in development device further comprises a UI debugging unit for providing a debugger (Debugger) integrated with a web browser. The method of claim 12, The plug-in development module An XML editing unit that defines one or more of an attribute, style or event using a standardized XML specification; A component editing unit which edits a source that implements a function defined in XML using JavaScript and Java; And UI plug-in development apparatus further comprises a compilation unit for compiling Java and JavaScript source developed in the component editing unit. The method of claim 12, The plug-in development module And a plug-in debugging unit integrated with a debugger of the web browser and checking a bug of the application while executing the application. The method of claim 12, The plug-in development module A deployment unit to deploy a plug-in; And UI plug-in development device further comprises a license (license) for managing the license. In the method of using the UI plug-in in a web server connected to one or more client terminals, Registering K basic UI plug-ins in a database of the web server; And Registering the extended UI plug-in input from the client terminal, The extended UI plug-in is generated by modifying or recombining the basic UI plug-in or another extended UI plug-in. The method of claim 22, And the basic UI plug-in and the extended UI plug-in are executable in a universal web browser. The method of claim 22, Connecting the client terminal to a payment server for payment of the UI plug-in selected from the client terminal; Calculating an amount of the UI plug-in downloaded from the client terminal using the payment server; And The client terminal further comprises the step of downloading the paid UI plug-in from the web server. The method of claim 22, DRM processing the UI plug-in; Allowing the UI plug-in to be distributed to one or more client terminals without making a payment; If the client terminal detects that a play command for the UI plug-in in an unpaid state is generated, controlling the UI plug-in providing server to perform a payment procedure for the UI plug-in; When the payment is completed, storing payment information including a UI plug-in identifier for identifying the paid UI plug-in and a user identifier for identifying the user; And And authenticating the paid UI plug-in with reference to the payment information, wherein the authenticated UI plug-in can be played on the client terminal. On a web server connected to one or more client terminals, Registering K basic UI plug-ins in a database of the web server; And A program for executing the step of registering the extended UI plug-in input from the client terminal is recorded in a readable recording medium, The extended UI plug-in modifies the basic UI plug-in or another extended UI plug-in, Generated by recombining one or more of the base UI plug-in, other extended UI plug-ins, and combinations thereof, And the basic UI plug-in and the extended UI plug-in are executable in a universal web browser. The method of claim 26, The client terminal further comprises the step of downloading the UI plug-in from the web server. The method of claim 27, Connecting the client terminal to a payment server for payment; And And calculating the amount of the UI plug-in downloaded from the client terminal by using the payment server. The method of claim 26, DRM processing the UI plug-in; Allowing the UI plug-in to be distributed to one or more client terminals without making a payment; If the client terminal detects that a play command for the UI plug-in in an unpaid state is generated, controlling the UI plug-in providing server to perform a payment procedure for the UI plug-in; When the payment is completed, storing payment information including a UI plug-in identifier for identifying the paid UI plug-in and a user identifier for identifying the user; And And authenticating the paid UI plug-in with reference to the payment information, wherein the authenticated UI plug-in can be played on the client terminal.

Images