KR101088842B1 - Standard for Inter-Connection and Driving System of Web-Based Widget in Smart Phone - Google Patents

Abstract

The present invention relates to a smart phone interworking standard and driving system of the web widget, the smart phone interlocking standard and driving system of the web widget, the database is stored in the XML file generated according to the WZDAPI standard and the layout generated for each device is stored Including a layout container, wherein the layout generated for each device is configured to display the same content in the same page, the smartphone interworking standard and the driving system of the web widget is selected according to the user's operation It is a smart phone interworking standard and driving system of the web widget, characterized in that the automatic conversion to the widget for the device.
According to the present invention, when the interlocking system between the web widget and the smart phone is configured, it can be used simultaneously without separate redevelopment on multiple platforms through a single development, thereby shortening the development period and converting existing produced contents as well. The advantage is that you can create rich application environments.

Description

Smartphone for web widgets {Standard for Inter-Connection and Driving System of Web-Based Widget in Smart Phone}

The present invention relates to a smart phone interworking standard and driving system of the web widget, and more particularly, to an application that provides convenience and usefulness to the user, and the contents of the web widget already made a lot of work with the application of the smart phone To a specification and a drive system.

If the mobile market has focused on hardware and network-oriented hardware competition so far, the smartphone market, which has been activated by the emergence of the iPhone / Android, is the core competitiveness of the “open platform, marketplace, application” -oriented software. I am getting it.

Currently, the commonly used method is to structure the data through XML if there is a specific content, and the external part is produced as a web widget according to the developer's preference by using HTML / JavaScript and Flash. And when producing for smartphones are being produced in the form of redeveloping the application through a separate operation.

In the existing system, since the development proceeds according to the developer's preference every time without the application specifications of the web widget and the smart phone, there is a problem that it cannot be separated and reused as a common part between the devices. In other words, all layouts and functions necessary for implementing functions other than processing basic contents as XML had to be developed separately.

In addition, there is no need to discuss the interoperability standards of this part because the demand for smartphone applications is still possible manually.

The present invention relates to an application that gives convenience and usefulness to a user in order to solve the problems of the prior art as described above, and a web widget that can interoperate with the application of a smartphone the contents of a web widget that has already been made a lot. It aims to provide smartphone interoperability standard and driving system.

In order to achieve the above object, according to a preferred embodiment of the present invention, in the smart phone interworking standard and driving system of the web widget, the XML file generated according to the WZDAPI standard is generated for each database and device is stored Including a layout container for storing the layout, the layout generated for each device is configured to display the same content in the same page, the smartphone interworking standards and the driving system of the web widgets to manipulate the generated widget According to the present invention, a smart phone interworking standard and a driving system are provided.

Here, in the above-described smart phone interworking standard and driving system of the web widget, the original XML file stored in the database is used without any conversion in converting the generated widget into a widget for another device, and the API is used on a platform of another device. According to the API conversion, the layout may be configured to perform the conversion by extracting the layout of the device designated as the conversion target according to the user's selection of the layout stored in the layout container.

In addition, the aforementioned WZDAPI standard may be configured to include a widget object including onLoad, onRefresh, onResize, and onUpdateTitle, a WZDAPI.Data object, and a WZDAPI.UI object.

Meanwhile, the aforementioned WZDAPI.UI object includes WZDAPI.UI.Drawer for controlling the widget display window, WZDAPI.UI.DropDown for controlling the widget menu, WZDAPI.UI.Pager for controlling the widget page, and WZDAPI for controlling the widget tab. It can be configured to include .UI.TabView.

On the other hand, the above-mentioned WZDAPI.Data object is a getText () that receives the content from the web address url and outputs it to the callback function in the form of a string; GetXML () which receives XML format data from address url and outputs it to callback function, getFeed () which receives RSS format data from web address url and outputs it to callback function, and request that receives data from web address url and outputs it to callback function It can be configured to include ().

As described above, there is an advantage in that one source multi-use is possible by simultaneously using the web widgets and various smartphones with one development in the smartphone interworking standard and driving system of the web widget according to the present invention.

In addition, according to the present invention, if you configure the interlocking system between the web widget and the smart phone can be used simultaneously without separate redevelopment on multiple platforms through a single development, shorten the development period as well as convert the existing produced content You can expect effects such as creating a rich application environment.

1 is a diagram illustrating a physical configuration of a smartphone interworking standard and a driving system of a web widget according to an embodiment of the present invention.
2 is a view showing a layout configuration of a web widget and a smart phone according to an embodiment of the present invention.
3 is a schematic diagram of a converting framework according to an embodiment of the present invention.
Figure 4 is a conceptual diagram showing a web widget-smartphone interworking standard according to an embodiment of the present invention.
5 is an exemplary view illustrating an installation screen of a web widget.
6 is an exemplary view showing an interlocking sample of a web widget and a smart phone according to an embodiment of the present invention.
7 is an exemplary view showing an interlocking concept of a web widget and a smart phone according to an embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the smart phone interlocking standard and driving system of the Web widget.

First, the present invention does not develop according to the developer's propensity when producing an application for a web widget or a smart phone, and divides the parts such as “Title / Tab / Content / Paging” as the basis and modifies each of them, thereby making it a Web widget. It is characterized in that it is configured to be recycled by creating a container that can be used even in smartphones.

Furthermore, the present invention provides the definition of additional modules such as “Search / External Link / Thumbnail / Additional Description” and “Various View Modes” to provide smart widgets interoperability with web widgets that can be easily developed. It is meant to provide a system.

1 is a diagram illustrating a physical configuration of a smartphone interworking standard and a driving system of a web widget according to an embodiment of the present invention. As shown in FIG. 1, the smartphone interworking standard and the driving system of the web widget according to the preferred embodiment of the present invention may include a database 100 and a layout container 110.

The present invention can be thought of as divided into the "database" portion 100 and the "layout" portion 110 as shown in Figure 1, the database is a common format that can be used in the web and mobile and also TV / navigation using XML The layout part refers to a container for displaying various forms such as web widgets or smartphones based on a given database. That is, the database is an XML syntax that can be used universally regardless of the type of device, and the layout refers to a screen layout that can be expressed differently through the display unit of the device according to the type of device. Therefore, the XML syntax stored in the database can be used irrespective of the type of device, and the layouts stored in the layout part are stored for each device and used for the interworking standard and the driving system according to the present invention.

2 is a diagram illustrating a layout configuration of a web widget and a smart phone according to an exemplary embodiment of the present invention. As shown in FIG. 2, the present invention is configured to be identically configured for web widgets and smartphone layouts, and to be utilized simultaneously in web widgets and smartphones. Here, the design or everything is not made identical, but the container is developed and provided with a design and configuration suitable for each web widget / smartphone.

That is, as shown in FIG. 2 according to an embodiment of the present invention, the layout of the web widget 200 is titled 202, tab 1 204, tab 2 206, content 208, paging ( When configured as 210, the layout 220 of the smartphone is also configured to provide a title 222, tab 1 224, tab 2 226, content 228, and paging 230. Here, the layout itself may be variously modified as necessary, and it should be clearly understood that the gist of the present invention is not the layout itself, but the layout of the web widget and the layout of the smart phone.

In addition, although the configuration of the layout (that is, the configuration of the portion in which the respective content is displayed in the web widget or the widget for the smartphone displayed on the screen) is the same itself, the design of the layout may be configured differently for each device. . This point will be described later with reference to FIG. 7.

3 is a schematic diagram of a converting framework according to an embodiment of the present invention. In FIG. 3, the left side 300 shows an execution screen of the web widget, and the right side 310 shows a screen on which the widget is executed on the smartphone after being converted into a widget for a smartphone through a converting framework process. It is a schematic diagram shown.

As shown in FIG. 3, the web widget and the widget for a smartphone have a layout having the same configuration for each page, and are configured to express the same content. In the process of converting framework, the XML file is used as the original file used in the web widget, and the widget API for the web widget is automatically converted into the corresponding API according to the platform adopted in the selected smartphone. .

4 is a conceptual diagram illustrating a web widget-smartphone interworking standard according to an embodiment of the present invention.

The present invention is based on the WZDAPI standard, which is the only domestic API standard used in the development of the existing web widgets, and constitutes a container including a standard that can be linked in the same way in smartphones, such as iPhone, Android.

As shown in FIG. 4, UI parts such as Open / Close, DropDown, Tab, and Paging implemented in the web widget are configured for each individual device and using getText, getXml, request, etc. of the WZDAPI.Data object. Information such as XML can be used. (See Tables 1-5)

Tables 1 to 4 are tables showing WZDAPI.UI objects among WZDAPIs, and Table 5 is WZDAPI.Data objects.

A. WZDAPI.UI.Drawer

-Method

Kinds Explanation show () Change to expanded state. hide () Change to closed state. toggle () Changes to collapsed state when collapsed and collapsed state when expanded. setMainContent (DOMElement el) Set the main screen content. setSubContent (DOMElement el) Set the secondary screen content.

N. WZDAPI.UI.DropDown

-Method

Kinds Explanation addMenu (String id, {text: String}) Add a menu with a text string. selectMenu (String id) Select the menu. setWidth (Number width) Set the menu width. appendTo (DOMElement el) Attaches the tab control as the last child of el.

C. WZDAPI.UI.Pager

-Method

Kinds Explanation setMaxPageNumber (Number num) Set the total number of pages. selectPage (Number pageNo) Select a page. appendTo (DOMElment el) Attach the page control as the last child of el

D. WZDAPI.UI.TabView

-Method

Kinds Explanation WZDAPI.UI.TabView (Number type) Specifies the tab format. (Currently TYPE1, TYPE2 available) addTab (String id, {text: String, content: DOMElement}) Add a tab. selectTab (String id) Select a tab. appendTo (DOMElement el) Attaches the tab control as the last child of el. getTabContent (String id) Returns the tab content corresponding to the tab ID. getCurrentTabContent () Returns the current tab content. setTheme (Number theme) Specify a theme that matches the tab format.

WZDAPI.Data object of WZDAPI Kinds Explanation getText (String url, Function callback, Function onfailure) It takes the content from the web address url and passes it to the callback function as a string. getJson (String url, Function callback, Function onfailure) It receives JSON data from web address url and passes it to callback function.
If the data is not in the correct JSON format, the callback will not be called. getXml (String url, Function callback, Function onfailure) It receives XML data from web address url and passes it to callback function.
If the data is not in the correct XML format, the callback will not be called. getFeed (String url, Function callback, Function onfailure) It receives RSS data from web address url and passes it to callback function.
The structure of the data you pass is described below. request (String url, Object opts) It receives the data from the web address url and passes it to the callback function.
opts is like the options structure that the Ajax.Request class of the Prototype library accepts as its second argument.

5 is an exemplary view showing an installation screen of the web widget, Figure 6 is an exemplary view showing an interlocking sample of the web widget and the smart phone according to an embodiment of the present invention. Web widgets that can be installed in blogs / sites of the type shown in FIG. 5 are also implemented in the prototype form so that they can be implemented in the same configuration as in FIG.

7 is an exemplary diagram illustrating an interlocking concept of a web widget and a smart phone according to an exemplary embodiment of the present invention.

'Data (Contents)' shown at the top of FIG. 7 refers to content to be displayed on the screen, and 'Scheme (Semantics)' refers to a display unit (box) of a layout in which the corresponding content is displayed. In addition, at the bottom of FIG. 7, embodiments of a layout displayed for each device type are illustrated. As illustrated, the layout of the layout displayed on the screen for each device is differently designed according to the characteristics of the devices, but the configuration itself of the box displaying the content displayed on the screen is the same. That is, the layout is configured to display 'Title', 'Subtitle', and 'Comment' on the same page of the widget in four kinds of devices, and design the size of the box and the typeface / size of the content displayed in the box. It can be seen that the device itself is configured for each device according to the characteristics of the device. As described above, such content is stored in a database according to the present invention, and the layout for each device is stored and utilized in a layout container.

Therefore, for example, when the widget for device type 1 is configured to display "Foo" in "Title", "Bar" in "Subtitle", and "Baz" in "Comment" as shown in FIG. By changing the device type of the configured widgets, conversion to widgets for each device can be easily performed.

It will be apparent to those skilled in the relevant art that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims. The appended claims are to be considered as falling within the scope of the following claims.

100: database 110: layout container

Claims (5)

In the smart phone driving system of the web widget,
It includes a database in which XML files generated according to the WZDAPI specification are stored and a layout container in which layouts generated by devices are stored.
The layout generated for each device is configured to display the same content within the same page.
The smart phone driving system of the web widget automatically converts the generated widget into a widget for the selected device according to the user's operation,
The WZDAPI standard includes a widget object including onLoad, onRefresh, onResize, and onUpdateTitle, a WZDAPI.Data object, and a WZDAPI.UI object.
The method of claim 1,
The smart phone driving system of the web widget in converting the generated widget into a widget for other devices, the original XML file stored in the database is used without any conversion, the API is converted to an API according to the platform of the other device, The layout is a smart phone driving system of the web widget, characterized in that for performing the conversion by extracting the layout of the device designated as the conversion target from the layout stored in the layout container according to the user's selection.
delete The method of claim 1,
The WZDAPI.UI object is a WZDAPI.UI.Drawer for controlling a widget display window, WZDAPI.UI.DropDown for controlling a widget menu, WZDAPI.UI.Pager for controlling a widget page, and WZDAPI.UI for controlling a widget tab. Smartphone operating system of the web widget, comprising a TabView.
The method of claim 1,
The WZDAPI.Data object receives the contents from the web address url and outputs it to the callback function in the form of a string, and getJson () receiving the JSON format data from the web address url and outputting it to the callback function and XML from the web address url. It includes getXML () to receive data from the web address url and getFeed () to receive the RSS data from the web address url, and to callback function to get the data from the web address url and to the callback function. Smartphone operating system of the web widget.

Images