|Publication number||US20070061486 A1|
|Application number||US 11/222,916|
|Publication date||Mar 15, 2007|
|Filing date||Sep 9, 2005|
|Priority date||Sep 9, 2005|
|Also published as||US7509374, WO2007032884A2, WO2007032884A3|
|Publication number||11222916, 222916, US 2007/0061486 A1, US 2007/061486 A1, US 20070061486 A1, US 20070061486A1, US 2007061486 A1, US 2007061486A1, US-A1-20070061486, US-A1-2007061486, US2007/0061486A1, US2007/061486A1, US20070061486 A1, US20070061486A1, US2007061486 A1, US2007061486A1|
|Inventors||Peter Trinh, Mark Trinh, Bai Pham|
|Original Assignee||Alchemic Solutions Group, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Referenced by (35), Classifications (4), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to client-server interactions over wide-area networks, and more particularly to systems and methods for retrieving content from a web server and customizing display and functionality of the content on a client device.
Over the last two decades, the internet has grown from a discreet network of government laboratories and universities into a ubiquitous and essential tool for businesses, and an integral part of everyday life. Web sites, the building blocks of the internet, are growing at an exponential rate and have evolved from simply displaying information into interactive applications of seemingly limitless functionality. Many companies use web sites to offer services and conveniences to their customers, such as banks offering online web sites to check balances, pay bills, transfer money, etc. Other companies are entirely web-based, offering their products and services only through web sites, e.g., EBAY®, AMAZON.COM ®, YAHOO!®, GOOGLE, etc.
On approximately the same timeline, mobile devices such as personal data assistants (PDA's), hand-held computers, and cellular telephones have proliferated and are now commonplace in both the business and consumer markets. In fact, in some countries, the average person may carry two or more mobile devices. Traditionally PDA's and cell phones served only very distinct and limited functions. PDA's were mini-computers used typically as organizers for storing contact and calendar information, taking notes, etc. Cellular telephones were simply just mobile telephones. Today, the functionality and features of such devices has merged and evolved, such that multi-function mobile devices are now capable of telephone communications, e-mail, web browsing, data management, and other mobile communications and computing functions. Yet, even with the convenience of being able to browse, or surf, the internet from such prolific and portable devices, the adoption of mobile devices as a viable tool to access the internet has been limited.
One primary reason for the limited adoption of mobile devices for internet communications relates to the relatively small viewing area of mobile device phone displays. The majority of the web sites available over the internet are designed to be displayed on a computer screen of 15 inches or more, and are not effectively displayed on a the limited screen of a cell phone, for example. Moreover, the interactive features of most web sites are designed for typical computer interfaces (e.g., display, mouse and keyboard). The rich content and interactive features of many websites, therefore, can be virtually unusable on mobile devices, which generally having screens of approximately 1.5 to 2 inches and a typical 11 key number pad, along with a few navigation soft keys.
Attempts to address this problem include advances in client browser software, which try to render web pages in an acceptable manner for the small viewing area of mobile devices. Computer algorithms have been developed to try to reformat and reorganize the contents of returned web pages to fit within the given screen display. However, such computer algorithms are not capable of optimizing the entire myriad of different web pages and content available over the internet, simply because of so much variation in the layout, content and features of existing websites.
On the server side, web site developers in some cases have created separate versions of their web pages specifically designed for viewing by mobile devices. For example, YAHOO!® has a YAHOO!® Mobile site that serves WML, a markup language similar to HTML, but specific for use by mobile devices. A typical WML page includes contents and features the may be very different from the regular web page, but is designed to fit within the small display areas on mobile phones. This approach is not widely used, however, and requires that the host maintains at least separate sets of web pages, e.g., one for regular desktop browsers and one for mobile device browsers. Such approaches also limit user interaction within the context of the web browser and user interface (UI) controls of the web page. They do not provide for customization of features and provisioning of interface controls to optimize usability and functionality of the page using a particular device.
Still another attempted approach for solving this problem includes creating profiles to help transform HTML and related code from web pages into some intermediary language or code to be displayed by a mobile device. Such profiles may include, for example, information about the size of the display area as well as color and language preferences. A computer algorithm then uses the profile information along with the source information to try to display an optimal view of the page on the mobile device.
However, because web pages have so much variation in content, layout, format, and functionality, the above approach has proven unsuccessful in solving the problem of effectively displaying and interacting with such ubiquitous web content using a mobile device. In particular, creating a generic computer algorithm capable of optimally or even adequately displaying any significant fraction of the large number of web pages available over the internet is simply not feasible.
Another limitation of existing approaches for navigating web sites using a cell phone or other mobile client is the problem of navigating pages and inputting text using the limited key pad of a cell phone. WML does allow the web page designer to specify short cut keys, or keys or buttons that bind to specific links within the web page. While some input technologies such as T9Word can help simplify text input by helping to auto-complete common words as a user begins to spell them, such technologies do not fully optimize a particular interface.
Thus there remains a need in the art for systems and methods for customizing and optimizing display and functionality of web sites and related content using mobile devices.
Discussion or citation of a reference herein will not be construed as an admission that such reference is prior art to the present invention.
The present invention addresses many of the shortcomings and drawbacks found in the prior art. For example, the present invention overcomes the various limitations of browsing on the internet using a handset by providing a system and method for a user, for example a web content developer, to easily create an application that is specific to interacting with a specific website for the handset.
In some embodiments, a method of improving functionality of a client device comprises creating resource files for customizing content from one or more particular websites or third-party servers, storing the resource files on a server, downloading one or more of the resource files by the client device, downloading content from the particular websites or third-party servers, and rendering a rich user interface or application to interact with the website in accordance with the downloaded resource files.
In some embodiments, the client device is a mobile device. In particular embodiments, the client device is a cellular telephone. Software instructions including content to be rendered on a client device and instructions for rendering the content can comprise one or more of a variety of code languages, for example, HTML, WML, XML, JAVA script, Visual Basic, C, C++, and/or combinations of languages or custom languages.
The present invention supports the de-coupling of existing web applications and the device-specific user interfaces to be developed for them. In some embodiments, the present invention provides support for “scraping” data from existing web applications for redisplay. This allows, for example, development of a device-tailored user interface for an existing web application with no modification to the existing application itself.
In preferred embodiments, the present invention makes use of XML and related standards, as well as an XML-based customization coding, to simplify porting to other platforms and integration with other browser applications. The present invention can also support the ease of maintaining device specific user interfaces, and in particular can maintain such interfaces even when a web application is changed.
In some embodiments, the present invention provides support for DHTML, or when servers serve different web pages with the same URL. DHTML, or dynamic HTML, can be described as a technique for developing interactive web sites using HTML, a client side scripting language (e.g. Java script) and CCS. Some embodiments of the systems and methods of the present invention can interact with websites that contain DHTML content.
In some embodiments, the present invention provides methods for generating custom applications that related device-specific events (e.g., depression of keys, buttons, and the like) to specific application functions, thereby allowing for native integration between a web application and target device.
In some embodiments, the present invention provides methods for generating a customized web application on a client device. Such methods can comprise (a) receiving on a client device, through a user interface of the client device, a command to retrieve website content from a website hosted on a first server, e.g., a web server; (b) routing a first request from the client device to a second server, e.g. a XDUML server, or customization server, wherein the second server includes a memory storing customization code including one or more instructions for customizing features of the website for use on the client device; (c) receiving from the second server the customization code; (d) sending a second request to the first server for the website content; (e) receiving the website content; (f) customizing the website content in accordance with the one or more instructions in the customization code, thereby constructing the customized web application; and (g) operating the customized web application through the user interface of the client device.
In some embodiments the client device includes a number of widgets, which may define, for example, certain features or feature sets that may be called upon by the customization code received from the XDUML server and employed in a corresponding customized application generated on the client device. Some examples of widgets include menus, tables, buttons, checkboxes, arrows, lists, graphics, and other features that may be included in a customized application. The customization code can be XML-based and can include, for example, coded instructions identifying widgets that are to be used in a customized application and how they are to be used, instructions for laying out such widgets, and instructions for mapping corresponding web content received from the web server onto the user interface of the client device.
The present invention can be applied to work with browsers on desktop or laptop computers as well as mobile devices such as cell phones, handheld computers, tablet computers, and personal data assistants. In certain embodiments, the systems and methods of the present invention are applied to client devices having small display areas. In still other embodiments, the present invention applies to client devices having large displays, but where only a portion of the display is to be used for a particular application, e.g. a web browser or e-mail client, or where specific features of the client device are to be provisioned for customized interaction with a web page.
The invention and further developments of the invention are explained in even greater detail in the following exemplary drawings. The present invention can be better understood by reference to the following drawings, wherein like references numerals represent like elements. The drawings are merely exemplary to illustrate certain features that may be used singularly or in combination with other features and the present invention should not be limited to the embodiments shown.
Like reference numerals refer to corresponding parts throughout the several views of the drawings.
Exemplary client 12 can comprise a central processing unit 14, a user interface 16, communications circuitry 18, a memory 20, and a bus 19. Memory 20 can comprise volatile and non-volatile storage units, for example hard disk drives, random-access memory (RAM), read-only memory (ROM), flash memory and the like. In preferred embodiments, memory 20 comprises high-speed RAM for storing system control programs, data, and application programs, comprising programs and data loaded from non-volatile storage. User interface 16 preferably comprises one or more input devices, e.g., keyboard, key pad, buttons, soft keys, wheels, and the like, and a display or other output device. A network interface card or other communication circuitry 18 provides for connection to any wired or wireless communication network 40, which may include the internet and/or any other wide area network, and in particular embodiments comprises a mobile telephone network. Internal bus 19 provides for interconnection of the aforementioned elements of client device 12.
Operation of client 12 is controlled primarily by operating system 22, which is executed by central processing unit 14. Operating system 22 can be stored in system memory 20. In addition to operating system 22, in a typical implementation system memory 20 may include one or more of the following:
In some embodiments, each of the aforementioned data structures stored or accessible to system 12 are single data structures. In other embodiments, such data structures, in fact, comprise a plurality of data structures (e.g., databases, files, archives) that may or may not all be stored on client 12. For example, in some embodiments, data modules 36 comprise a plurality of structured and/or unstructured data records that are stored either on computer 12 and/or on computers that are addressable by computer 12 across the network 40.
Server 50 can also be a processor based computer system, comprising a CPU, communications circuitry 54 and a memory 56 having similar features and functions as described above with respect to client 12. Memory 56 can comprise volatile and non-volatile memory, and can include an operating system 58 a file system 60, databases 62, and various other application modules, data modules, data structures, and the like. Various other aspects, details and functions of server 50 are described in sections below.
In particular embodiments, databases 62 of server 50 can include data modules that include customization code that specific may or may not be for the various web sites and or the various devices that are supported by system 10. For example, one particular set of customization code is used to generate a customized e-mail application as shown and described with respect to
Web server 70 can be any server computer connected with the internet or network 40 and hosting web pages and/or other content that may be accessible by web browser 28. One skilled in the art will appreciate that, while only one web server 70 is shown for convenience, the present invention comprises a system for communicating with a large number of distributed servers connected with the internet 40.
As discussed in sections above, the present invention is particularly useful for optimizing display and interaction with web pages and other content stored on servers 70 over the internet 40. In some embodiments, client device 12 is configured to browse web pages stored on servers connected to the internet in a typical manner that is known and used in the art. For example, a user interacts with a web browser 28 or other application on client device 12, which may be a mobile device, cell phone, desktop device, or any other device, e.g. by clicking on a web link or inputting a uniform resource locator (“URL”), or address, using an input feature of user interface 16. The web browser 28 will send an HTTP request over the internet 40 to the web site designated by the URL. A web server 70 receives the HTTP request, processes the request, and returns HTML code over the internet 40 back to the web browser 28 on client 12. Web browser 28 and/or related applications on client 12 then renders the HTML code on a display of the user interface 16. The user can then interact with the displayed content, and the process repeats.
The above general process describes basic interactions with web pages as is generally known in the art. Embodiments of the present invention include additional features and aspects that provide customized display of web page information on client devices 12 using specialized configuration code, e.g., referred to herein as customization code, an example of which is XDUML code, from server 50. Such customization code is used by browser 28 to customize layout, mapping and functionality of particular web sites optimized for that client device 12.
Referring now to
If, in step 216, there is no customization code on the server for the corresponding URL/HTTP request, then the logic engine is notified 224, e.g., by a message or other signal from the server 50 that there is no customization code, and the remaining steps 222, 226, 228, 230 and 232 proceed as described in the general web browser example above.
In step 226, one or more web servers 70 receive the HTTP request(s) 226. Server 70 then processes the request and returns corresponding HTML code(s) back over the network 40 to logic engine 32 in step 228. If the requested URL(s) have no dependencies upon each other, the logic engine 32 may send all the requests at once. For example, in one embodiment of a customized web mail client according the present invention (e.g., as shown and described below with respect to
After receiving all the required HTML code, logic engine 32 then processes 230 any corresponding customization code along with the HTML code(s) to generate a set of display code. The display code can then be processed by the interface engine 30 in step 232 to generate a customized application having rich content and greater functionality than the corresponding web page(s) defined by the HTML code, thereby creating the “look and feel” of a rich, native-looking, client-based application with which the user can interact using interface 16. Some examples of such “native looking” applications include customized web mail applications and web search applications as described in more detail with respect to FIGS. 6 to 10B.
When the user interacts with the new application, interface engine 30, if needed, works in conjunction with logic engine 32 to retrieve further data from web server 70, or other web servers, and server 50, and to provide the data for the new application. For example, from the perspective of a user, he or she simply interacts with the new customized application as if it were a native application on the device, even though with each click, key stroke or other input function the logic engine 32 may invoke a request, e.g. and HTTP request, to fetch additional HTML or other code in the background from one or more specified URLs.
If in step 216 there is no customization code on the server for the new corresponding URL/HTTP request, then the logic engine is notified 224 and the interface engine 30 will simply revert back to the web browser mode and display the HTML code within the web browser interface until a URL is requested with a corresponding customization code.
Referring now to
Referring now to
Content mapping component 404 specifies the various content that client 12 is to retrieve in order to customize the requested web site or page. Such content may be different than the content specified by the original HTTP request by the user, and may include information from multiple web pages and/or URLs to be combined into a customized application for display by client 12. Content mapping component 404 can comprise specifications, e.g., XPATH specifications or the like, which specify where to locate the content information for the custom application. The XPATH portion of the content mapping component 404 will specify the URLs needed to obtain the content, as well as where in the resulting HTML documents the information should be obtained (e.g., scraped). As suggested above, one or more URLs can be specified by the XPATH portion, thereby allowing applications to be developed that can display information from multiple HTML documents and enabling more flexibility in designing the device-specific user interfaces. XPATH specifies a certain location in an XML DOM tree, and therefore requires that the HTML be valid XML (i.e. valid XHTML), which is not always the case; however one skilled in the art will appreciate that there are existing tools that can convert HTML into valid XML. The contents pointed to by the XPATH will then be bound to a variable for use in the widget layout 406 portion of the customization code 400.
Widget layout component 406 can specify the user interface layout along with what widgets are to be displayed. Widgets are user interface components, e.g., check boxes, buttons, or other features that may be incorporated into the customized user interface application. An example illustrating features of sample code that may be used according to the present invention is provided below in the section entitled “Example”.
For example, suppose one wanted a particular action to occur when a user pressed the “#” key on a cell phone. A code fragment for the event handler component 408 might look like this:
The context data component 410 comprises URL specific data that would aid in the interaction with the web site. Among other data, the context data 410 can include a dictionary of the most commonly used words for a given web site. Context data 410 can also supply a different set of dictionaries specific to the widget that a user is currently interacting with. This could aid the T9Word technology, for example, to more accurately predict and complete the word that the user is trying to type on the handset keys. For example, if the current input field requires a URL, then words www., .com, .net, etc. would be in the dictionary for that field. However, if the current input field requires key words to do a search, and the most commonly searched word for the week was “Food”, then “Food” would be in the dictionary for that input field. In another embodiment according to the present invention, a text input application uses recent events and tracks and ranks common search words and parameters related to such events. For example, if there has been a recent earthquake in California and a lot of recent queries in GOOGLE™ have included the words “earthquake” and “California”, then when the web browser on a cell phone browses GOOGLE™, the words earthquake and California should have a correspondingly higher priority when using the T9Word text input.
If the regular browser view is being displayed, then user interaction with the Display UI 502 will be sent to Browser Event Handler 408. If the invention's enhanced view is being displayed, then user interaction will be sent to Extended Event Handler 514.
When the user enters a text or clicks a link in the Display UI 502 which results in a URL requests, the Request Router 508 will query the XDUML Server 50 for the customization code 400.
Based upon the created render trees, the Browser Renderer 510 and the Extended Renderer 512 will use the Browser Widgets 518 and Extended Widgets 520, respectively, to create the display in the user interface. Both the Browser Widgets 518 and Extended Widgets 520 along with the Browser Event Handler 516 communicate with the Device GUI Toolkit 536 via the Application Windows Toolkit 526, for example. Application Windows Toolkit 526 is the programming interface to draw the images in the view, where as the Device GUI Toolkit is the low level code that does the actual drawing on the device. The Application Windows Toolkit 526 would be enhanced by the Extended AWT (Application Windows Toolkit) 528 so that it would be able to support the events from the Extended Event Handler 514.
The Extended Parser 504, Browser Parser 506 and Request Router 508 utilize the Web Interface Services 522 and File Services 530, which in turn communicate through native device APIs with Device OS 415 and Networking Services 534.
Referring now to
Section 704 can be defined by a widget for displaying a number of e-mail messages in a widget 710 shown as well as a total number of messages in one or more particular folders. A field 708 can be used to enter a desired message number, e.g., to jump forward to display that message or to begin the displayed list 710 with that message. Navigation through messages can be performed, for example, by pressing specific keys or navigation keys, or by a scroll wheel or other user input devices, as described in more detail in the Example section.
Section 706 is an example of column header extended widgets 520 for identifying the e-mail information shown in section 710. In this case, “Date” and “Sender” are the column headers, and the e-mails of section 710 can be sorted by date or by sender, for example by highlighting and selecting the column header using device input features such as a scroll wheel, space bar, tab key, arrow key, etc.
Section 710 is another example of an extended widget 520. It contains the list of the emails 710-1, 710-2, 710-3 . . . 710-8 that are in the currently selected mailbox (e.g., “Inbox” 714). The user can access each email directly by pressing the corresponding number, e.g., “1” for 710-1, “2” for 710-2, etc. on the keypad of the client device 12. Alternatively, the user can use scroll wheels, directional keys, etc on the device to move a cursor or selection box, and highlight the email they wish to see. Messages that not yet been opened or read can be designated, for example, using bold or colored font compared to those messages that have been read.
In one embodiment, as the user navigates from one email to the other, a small semi-transparent box 720 appears on top or bottom of the selected email. Such box 702 includes, for example, a preview of the contents of the email. Such preview information can include any desired level of detail, e.g. the subject, the first one, two or more lines from the e-mail, etc. Such underlying information can be automatically acquired from the web mail server by client for each e-mail listed in 710, for example by logic engine 32 or other components, and stored in client 12 until called for display. To view the whole email, a user can press a key, e.g., the Ok key, Select key, or any other key or device designated by the customization code. The user may also browse the other emails in their mailbox, for example, by pressing the directional keys on the key pad as shown in field 704. This action can be defined to navigate to the next 8 or X number of emails to display in the view.
Section 712 is another example of an extended widget 520 that would support advertisements. In one embodiment, this widget would appear as a pop-up box for a defined period of time. e.g., 2 seconds, 3 seconds or more, when the user first navigates to this page.
Sections 716 and 714 are yet additional examples of extended widgets 520. The Compose 716 and Inbox 714 menus can be mapped to the left and right soft keys, respectively, on the handset of device 12 as described in the “Example” herein. The customization code can include any number of widgets or features to optimize display and functionality of the content retrieved from the web server 70 on the client device 12.
Additional details regarding the widgets and features employed in the embodiment shown in
Referring now to
A top area 702 of interface page 900 can include status information such as wireless signal strength, notification icons, battery life, and the like as described above with respect to
Area 912 is designated in this example to correspond to the “Google Search” button in
Area 916 can be, for example, a menu widget that can be tied to a corresponding soft key or other input, and allows the user to select between various features of website 800. For example, in
Referring now to
As shown in
The following sample customization code provides an example illustrating some of the concepts and instructions that can be included in resource files from Server 50. In this particular example, the sample code is used for generating an exemplary web-mail application on a mobile device, e.g., such as application 700 as shown and described above with respect to
Several of the sample instructions provided in the above example will now be described in more detail.
<XDUML version=“1.0” application=“email-yahoo” device=“samsung 8100” url=“http://mail.yahoo.com”>
Headers or similar instructions such as the above statement can be used to identify or declare the type of code that follows. In this example, the above instruction includes a declaration where:
version identifies the XDUML version
application defines the application for this XDUML file
device identifies the applicable devices
url can identify the url containing the primary web page(s) that the application will customize
In one embodiment, all XDUML file include a declaration that may be similar to the above for identifying the customization code.
After the declaration, a first main component of the Example is a
The template command identifies the widget layout template. In this example, the template is for an email application that displays and provides for interaction with e-mail messages from a web-mail client, e.g., YAHOO!® Mail.
The Widget Layout instruction set defines different pages and corresponding widgets to be employed within the application template defined by
The PAGE id instruction declares a page to display, where:
id identifies the unique id of this page.
In this case, the unique id relates to the logon page of the specified web-mail client. The next PAGE id instruction, described later, provides instructions for the mailbox page that is shown after logon is completed.
<WIDGETS> <DROPDOWN id=“name” type=“edit” text=“Logon Id” location=“10,40” size=“60,10” /> <DROPDOWN id=“password” type=“edit_password” text =“Logon Password” location=“40,40” size=“60,10” /> <BUTTON id=“logon” type=“push” text=“Logon” location=“70,40” size=“50,10” /> </WIDGETS>
The above portion of the logon page code, initiated by
type specifies a more refined type for the widget.
text specifies the text to display.
location specifies a location on the device display to place the widget on the page.
size specifies the size of the widget.
<KEYBINDINGS> <KEY_NAV_UP>name</KEY_NAV_UP> <KEY_NAV_DOWN>password</KEY_NAV_DOWN> <KEY_NAV_OK>logon</KEY_NAV_OK> </KEYBINDINGS>
After logon is completed, the next page displayed by the customized application is the Mailbox Page, details for which are initiated within the
In this example, a
<COLUMN id=“date” type=“sorted” data=“normal”>Date</COLUNN> <COLUMN id=“subject” type=“sorted” data=“preview”>Subject</COLUMN>
Similarly, row designations can be used to specify rows and corresponding columns containing e-mail information for the e-mail inbox page, for example:
<ROW id=“row_1” type=“preview” font=“default” location=“default” size=“default”> <RCOLUMN id=“cell_11” name=“Date”/> <RCOLUMN id=“cell_12” name=“Subject”/> </ROW>
The row identified as row_1 includes two cells, cell_11 and cell_12, corresponding to the columns identified above and include date and sender information, respectively, for the e-mail listed in that row. See, for example, row 710-1 of
Of course, various other widgets, components and/or features can be incorporated and coded as desired. For example, a pop-up box widget such as that advertisement box 712 in
<MESSAGEBOX id=“ad” type=“popup” location=“25,60” size=“50,30” lifespan=“5” />, where:
type designates a particular type of message box widget, in this case a popup box.
location, size and lifespan define particular placement and other characteristics of the popup box.
Also, one or more
<MENU id=“action” type=“softkey” location=“0,90” size=“40,10” /> <MENU id=“folders” type=“softkey” location=“40,90” size=“40,10” />
In this example, the “action” menu can designate a menu such as 716 in
<KEYBINDINGS> <KEY_1>row_1</KEY_1> <KEY_2>row_2</KEY_2> <KEY_3>row_3</KEY_3> <KEY_NAV_LEFT>pagelist</KEY_NAV_LEFT> <KEY_NAV_RIGHT>pagelist</KEY_NAV_RIGHT> <KEY_SOFT_LEFT>action</KEY_SOFT_LEFT> <KEY_SOFT_RIGHT>folders</KEY_SOFT_RIGHT> <KEY_POUND>script_spam</KEY_POUND> <KEY_0>script_move</KEY_0> <KEY_STAR>script_delete</KEY_STAR> </KEYBINDINGS>
Other keys can be bound to different elements or functions, such as the left and right soft keys being bound to the action and folders menus as shown in the sample code and described above with respect to
One skilled in the art will appreciate that various other widgets, features scripts, and the like may be bound or linked to any desired input keys, soft keys, scroll wheels, or other user input devices of interface 16.
<CONTENTMAPPING> <MAPPING type=“text” src=“c:\usernames.cache” dst=“name.values” /> <MAPPING type=“text” src=“c:\password.cache” dst=“password.values” /> <MAPPING type=“text” src=“[xpath to the text]” dst=“pagelist.value” /> <MAPPING type=“table” src=“[xpath to table]” dst=“emails”> <COLUMNMAP src=“[relative xpath to date column]” dst=“date.values” /> <COLUMNMAP src=“[relative xpath to subject column]” dst=“subject.values” /> <COLUMNMAP src=“[relative xpath to subject column]/[relative xpath to email data]” dst=“sender.preview” /> </MAPPING> </CONTENTMAPPING>
type tells what type of mapping to make.
text means that it just takes the text value from the source as is and makes no changes.
table specifies that this is a table mapping and will map the web page table to the application's table widget. When the type is table, the system may require further XML text to specify the column mapping, for example using the
src specifies the source of the data, which can be from a local cache or a XPATH to the web page, for example. The XPATH can be a complete path or a relative path.
dst specifies the destination widget to place the data.
By default, each widget can have a Values property that is set by such default mapping. The code can specify the desired property of the widget to be set, for example by using a “.” (period) specification. For example, the command sender.preview sets the preview property of the sender widget.
The above example of the
The present invention can be implemented as a computer program product that comprises a computer program mechanism embedded in a computer readable storage medium. For instance, the computer program product could contain the program modules shown in
Many modifications and variations of this invention can be made without departing from its spirit and scope, as will be apparent to those skilled in the art. The specific embodiments described herein are offered by way of example only, and the invention is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled.
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7818686 *||Sep 4, 2008||Oct 19, 2010||International Business Machines Corporation||System and method for accelerated web page navigation using keyboard accelerators in a data processing system|
|US7952607 *||Apr 28, 2006||May 31, 2011||Avaya Inc.||Method and apparatus for efficient presentation of content over a network to a visually impaired user|
|US8104044||Jul 31, 2007||Jan 24, 2012||Amazon Technologies, Inc.||System and method for client-side widget communication|
|US8375358||Jan 30, 2008||Feb 12, 2013||International Business Machines Corporation||Automatically generating rest clients from rest resources|
|US8504913 *||Jun 8, 2007||Aug 6, 2013||Apple Inc.||Client-side components|
|US8635287 *||Jul 8, 2008||Jan 21, 2014||Google Inc.||Systems and methods for supporting downloadable applications on a portable client device|
|US8706803 *||Sep 24, 2010||Apr 22, 2014||Imdb.Com, Inc.||Client-side generation of preliminary version of network page|
|US8713536 *||Jun 11, 2009||Apr 29, 2014||Webtrends, Inc.||Method and system for constructing a customized web analytics application|
|US8756271||Jun 17, 2010||Jun 17, 2014||Pekka Aarne REHTIJÄRVI||Providing a customized application to a user terminal|
|US8826260||Jan 11, 2011||Sep 2, 2014||Intuit Inc.||Customization of mobile-application delivery|
|US8949361||Mar 17, 2014||Feb 3, 2015||Google Inc.||Methods for truncating attachments for mobile devices|
|US9008464||Jun 16, 2009||Apr 14, 2015||University-Industry Cooperation Group Of Kyung Hee University||Media data customization|
|US9021383 *||Dec 13, 2011||Apr 28, 2015||Lenovo (Singapore) Pte. Ltd.||Browsing between mobile and non-mobile web sites|
|US9026905 *||Dec 17, 2010||May 5, 2015||Facebook, Inc.||Customization of mobile applications using web-based technology|
|US9064028||Apr 3, 2008||Jun 23, 2015||The Hong Kong University Of Science And Technology||Custom rendering of webpages on mobile devices|
|US20070067305 *||Nov 29, 2005||Mar 22, 2007||Stephen Ives||Display of search results on mobile device browser with background process|
|US20080288582 *||Feb 19, 2008||Nov 20, 2008||Sms.Ac||Systems and methods for passing application pods between multiple social network service environments|
|US20080307299 *||Jun 8, 2007||Dec 11, 2008||Apple Inc.||Client-side components|
|US20100318976 *||Jun 11, 2009||Dec 16, 2010||Webtrends, Inc.||Method and system for constructing a customized web analytics application|
|US20110154374 *||Dec 16, 2010||Jun 23, 2011||Electronics And Telecommunications Research Institute||Apparatus and method for managing customized application|
|US20120011446 *||Jan 12, 2012||Mtld Top Level Domain Limited||Generating user interfaces|
|US20120144290 *||Jun 7, 2012||Adobe Systems Incorporated||Integrated Native HTML Rendering|
|US20120159308 *||Dec 17, 2010||Jun 21, 2012||Erick Tseng||Customization of Mobile Applications Using Web-Based Technology|
|US20130024766 *||Jan 24, 2013||Infosys Limited||System and method of context aware adaption of content for a mobile device|
|US20130097687 *||Apr 18, 2013||Open Text S.A.||System and method for secure content sharing and synchronization|
|US20130152009 *||Jun 13, 2013||Neal Robert Caliendo, JR.||Browsing Between Mobile and Non-Mobile Web Sites|
|US20130174050 *||Dec 18, 2012||Jul 4, 2013||Nokia Corporation||Method and apparatus for downloading third party content within the same web page context|
|US20140366014 *||Apr 3, 2014||Dec 11, 2014||Bmc Software Acquisition, L.L.C.||System and method for automated customization of applications|
|US20150019991 *||Jul 9, 2013||Jan 15, 2015||Tail-f Systems AB||Customizable graphical user interface for network management|
|US20150149582 *||Nov 25, 2013||May 28, 2015||International Business Machines Corporation||Sending mobile applications to mobile devices from personal computers|
|US20150149596 *||Jun 11, 2014||May 28, 2015||International Business Machines Corporation||Sending mobile applications to mobile devices from personal computers|
|WO2009042243A1 *||Feb 20, 2008||Apr 2, 2009||Andrew Ballester||Systems and methods for passing application pods between multiple social network service environments|
|WO2010146241A1 *||Jun 16, 2010||Dec 23, 2010||Rehtijaervi Pekka Aarne||Providing a customized application to a user terminal|
|WO2010147365A1 *||Jun 15, 2010||Dec 23, 2010||University-Industry Cooperation Group Of Kyung Hee University||Media data customization|
|WO2012096683A1 *||Apr 5, 2011||Jul 19, 2012||Intuit Inc.||Customization of mobile-application delivery|
|Sep 9, 2005||AS||Assignment|
Owner name: ALCHEMIC SOLUTIONS GROUP, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TRINH, PETER L.;TRINH, MARK L.;PHAM, BAI;REEL/FRAME:016972/0335
Effective date: 20050908
|Sep 14, 2006||AS||Assignment|
Owner name: MOBOPIA CORP., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCHEMIC SOLUTIONS GROUP, INC.;REEL/FRAME:018300/0875
Effective date: 20060907
|Dec 29, 2008||AS||Assignment|
Owner name: ALCHEMIC SOLUTIONS GROUP, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOBOPIA, CORP.;REEL/FRAME:022037/0245
Effective date: 20081014
|Jul 13, 2012||FPAY||Fee payment|
Year of fee payment: 4