EP2614435A1

EP2614435A1 - Method for producing an application which is capable of being executed on a digital terminal which has a touch-sensitive screen, and apparatus

Info

Publication number: EP2614435A1
Application number: EP11767912.6A
Authority: EP
Inventors: Walter Benzig; Bernhard HOCHSTÄTTER; Sebastian Werner
Original assignee: Deutsche Telekom AG
Current assignee: Deutsche Telekom AG
Priority date: 2010-09-10
Filing date: 2011-09-09
Publication date: 2013-07-17
Also published as: WO2012031768A1

Abstract

The present invention relates to a method for producing an application which is capable of being executed on a digital terminal which has a touch-sensitive screen, wherein a code for the application is transferred, at least in part, from a server device to the digital terminal, wherein the transfer of the code for the application is initiated, at least in part, by user interaction, characterized in that the method comprises the following steps: - a model code which can be used for multiple types of the digital terminal is created for the application and - the code for the application is produced on the basis of the model code. In addition, the invention relates to an apparatus for producing an application which is capable of being executed on a digital terminal which has a touch-sensitive screen, and to the code for an application.

Description

METHOD FOR PRODUCING A DIGITAL END DEVICE EMITTING ON A TOUCH-SENSITIVE SCREEN LIVE-EFFICIENT APPLICATION AND DEVICE

description

State of the art

The present invention relates to a method for generating a running on a touch-sensitive screen digital terminal running application. Moreover, the present invention relates to a device for

Generating a running on a touch screen digital terminal running application and the code of such an application.

Due to the growing prevalence of wireless networks nowadays an ever-increasing number of wireless devices are in use. These digital devices or digital terminals include mobile phones, Personal Digital Assistants (PDAs) capable of wireless communication, two-way pagers, and the like. As the availability of wireless devices has increased, the usefulness of software applications running on such digital devices or digital terminals has increased. For example, the wireless device may include an application that retrieves a weather report for a list of preferred cities, or an application that allows a user to purchase groceries. These software applications leverage the ability of the wireless data transmission network to provide users with timely and useful services, often in addition to voice communications.

However, the development of software applications remains a difficult and time consuming task given the plethora of different types of devices, the limited resources of some digital terminals and the complexity of delivering large amounts of data to the digital terminals.

[0003] Currently, the digital terminals are configured to communicate with web services via Internet-based browsers and / or native applications. The advantage of the browsers is that they can be set up to operate on a cross-platform basis for a variety of different digital terminals. Browser applications are efficient tools for designing platform-independent applications. Accordingly, different runtime environments - regardless of the platform - run the same application. On the other hand, native applications are being developed for a particular platform of wireless devices, allowing a relatively optimized application program for a runtime environment running on that platform. However, a platform-dependent application introduces several obstacles, including the need to develop multiple versions of the same application. In addition, application developers need programming languages such as Java and C ++ to build such native applications.

Disclosure of the invention

The invention has for its object to provide a method and apparatus for generating a on a touch-sensitive screen having digital terminal running application in which at least some of the above-mentioned disadvantages are mitigated or eliminated.

This object is achieved by a method for generating a running on a touch-sensitive screen digital terminal running application, wherein a code of the application is at least partially transmitted from a server device to the digital terminal, wherein the transmission of the code of the application at least partially triggered by user interaction, the method comprising the steps of:

Creating a model code of the application usable for a plurality of types of the digital terminal and

Generate the code of the application based on the model code.

The device according to the invention has the advantage that it can be used for a plurality of different types of digital terminals (or also from different platforms of digital terminals, for example terminals which are operated by means of an Android operating system or by means of a Windows operating system be operated or the like), the programming effort for the production of an application can be significantly reduced in any case that not for each type of digital device (or for each platform about different operating systems) a completely new or specially created programming is required, but that at least parts of the generated program code of the application for multiple types of digital

Terminals (or for multiple platforms) can be used. In this case, according to the present invention, a "model code" is produced, which in any case is universal in that, in any case, without further human interaction for code manipulation Application is possible with several types of digital terminals. The program code of the application actually used for a specific type of digital terminal (or for a specific digital terminal) is referred to in the context of the present invention as the "code of the application". It is possible according to the present invention according to a first alternative embodiment that this code of the application is identical or quasi-identical to the model code. In this case, the code of the application, if necessary, also code parts that is not processed in the specific digital device or can be. In this (first) case, "generating the code of the application based on the model code" means that essentially one copy of the

Model codes are generated or generated. According to a second alternative

However, according to an embodiment of the present invention, it is also possible that the code of the application is not identical (and also not quasi-identical) to the model code, but is essentially freed from any code parts pertaining to such types of digital terminals (or platforms) for such digital terminals) that do not correspond to the particular digital terminal for which the "code of the application" is to be generated based on the model code. In this case, the code of the application either does not have any code parts which can not or will not be processed in the specific digital terminal, or at least the code of the application has fewer code parts which are not processed or processed in the particular digital terminal can. In this (second) case, "generating the code of the application based on the model code" means that at least parts of the

Program codes that relate to types of terminals that do not correspond to the specific terminal to be removed. It is according to the present invention

For example, it is provided that such multiplatform-capable code parts are present in the model code, for example in the form of conditional statements (so-called IF statements (or "case statements") or so-called CASE statements (or so-called case distinctions)).

According to the invention it is preferred that the model code for the plurality of types of digital terminal is platform independent.

According to the invention it is further preferred that the code of the application is a hypertext markup language (HTML) code.

It is further particularly preferred if the creation of the model code usable for the plurality of types of the digital terminal of the application

Developer is used, which has no touch-sensitive screen. According to the invention, it is further preferred that the application has at least a first possible view and a second possible view, wherein the first and second views correspond to different view modes of the application, wherein the first possible view by means of a first uniform source indicator (URL , Uniform

Resource Locator) and wherein the second possible view by means of a second

uniform source locator (URL, Uniform Resource Locator).

As a result, it is advantageously possible according to the invention that different parts or views (or of states or operating states) of the application can be realized again in a simple and repeatable manner.

According to the invention, it is also preferably provided that after the start of the application in dependence of the last time you exit the application displayed directly the first or second possible view is shown.

The invention therefore also relates to a possibility complex

Store navigation within a mobile application to be able to restore it when restarting the application.

Web applications today are often based on a single hypertext markup language (HTML) page that interactively responds to user actions. It is known that one can basically realize the navigation within this single page on the location (address field) of the browser or the browser component. This works via a so-called anchor, which is added at the end by means of a "#" symbol, although to date there is no concept of storing the quite complex state of an application there.

The model proposed by the present invention is a

Interplay of navigation and interface logic: The so-called views or "views" (ie the individual areas of an application) each have a unique name. Each view can support a subview (for example, a tab system within the "page"), and each view can have a parameter, such as a user's unique ID, e-mail, etc. The reduction This information has made it possible to implement a uniform system that provides enough options for almost all current smartphone applications to represent the current state.

The following is an example of how these three information can be combined to form a unique identifier:

For example, the identifier looks like this: "viewld.subViewld: parameter". Both "subViewId" and "parameter" are optional. This identifier itself is then used as a segment within a structure. Within an application, for example, it would be conceivable that the user is currently viewing the third e-mail from his personal mailbox, in which case a complete navigation path might look like this: "inbox: private / mail: 3". The

Separation of the individual identifiers occurs via a slash. Here, the IDs of the views ("inbox" and "mail") are each used with parameters ("private" and "3").

This identification information for the exact designation of a selected view (and in particular the view that the application had before the digital terminal was turned off) is sent to the actual URL by means of a so-called anchor

(for example, by "#") added. So, for example as follows:

"Http: //www.webmail.eom/#inbox: private / mail: 3".

In the case of a normal browser, the user may e.g. Create a bookmark for the current position in the application or send a link, which shows exactly the right position at the receiver again. He also has the opportunity to modify the URL accordingly and thus to obtain a navigation in the application. The filing in the URL is preferable to other models, since only so reasonable with different browser tabs / windows can be handled. The user could thus use the application independently in two browser windows.

Even in the case of a web application that has no visible navigation bar for the user, you can still work with this method. Here it is particularly interesting to exactly restore the state of the application at the start. For this purpose, the path is stored within the application in the fixed memory of the application and read out again when the application is restarted.

According to another preferred embodiment of the present invention, it is provided that a proxy unit is used during the creation of the model code of the application which can be used for the majority of types of the digital terminal, the proxy unit providing access control information (HTTP ACCESS CONTROL header) into a message received from an external server.

As a result, it is advantageously possible, even for the situation of cross-domain restrictions, to create a possibility on a desktop system in order to test mobile applications directly in the browser (of the developer's desktop system).

In the development of web applications (for digital terminals such as smartphones) on the desktop can not normally be accessed on remote resources. Here, the so-called cross-domain policy, which are common for typical desktop development systems. This is mainly done to protect the classic browser from running third-party code. However, this useful feature may be in the way of the developer when interacting with a service that you trust. Within a native application, which is distributed eg on the basis of PhoneGap on smartphones, the typical browser limitations do not apply. The problem here is primarily during development. Because while the generated application has full access to the Internet, this is not true during development - as far as the browser of the desktop system is used for testing.

To provide the testing capability necessary to provide communication with external services without having to install additional software to be installed on the application developer's computer (as this would increase the initial effort again, for example, it would be possible to locally (on the development device) setting up an HTTP server and redirecting the application as well as the communication via this HTTP server), the method according to the present invention utilizes functionality in current browsers, in which a service provider uses its own specific HTTP headers Unlock services for cross-domain communication. Since these releases often (and in relevant servers) are not made (and are usually not manipulated in third-party services), according to the present invention, for example, a generic proxy (as a proxy unit) set up (and for example a plurality of development sites are hosted centrally). The generic proxy (or proxy unit) acts as an interface to communicate with a service. Communication is always routed automatically through the proxy (or proxy unit) as soon as it is determined that it is accessing another domain. In the created application is thus always communicated directly and no load on the proxy generated. The proxy (or proxy unit) redirects all requests as it is, but inserts the "HTTP access control" header in each response to signal the browser permission to process that response accordingly It is advantageously possible that this central proxy (or the proxy unit) is available to all application developers in parallel and only needs to be serviced once.Through anchoring within the framework code, the switch between proxy use and direct communication is completely transparent to the user Application developer who also does not need to set up and administer an HTTP server on his own development computer

Application based on web technologies can now be done directly in the desktop browser accessing the local file system. According to the invention, it is particularly preferably provided that during the creation of the usable for the plurality of types of the digital terminal

Model codes of the application synthetic operating events are generated, wherein such synthetic operating events correspond to a use of the touch-sensitive screen.

In general, digital devices have as smartphones

touch-sensitive screen, a so-called touch screen. By analogy with the use of so-called. Mouse events (or mouse events) for the programming of such Internet sites or applications, which are primarily intended for operation with equipped with a computer mouse devices are therefore in the range of

touch-sensitive screens so-called touch events used as operating events. However, classic desktop computers usually do not have one

Input option. A common approach is to edit both mouse events and touch events on the application side. The problem that exists here is that most touch devices also fire mouse events and conflicts can occur here, as both events may fire or affect the outcome of these possibly other events (keyword: preventDefault). According to the present invention, it is contemplated to use so-called synthetic events, that is, synthetic events. Synthetic events are fired in order to simulate such touch events on (development) devices without support for touch events via mouse events.

For example, the natively-available touch events touchstart, touchmove, and touchend are emulated with the mouse events mousedown, mousemove, and mouseup. In this example, the "mousemove" can only be ignored while the mouse button is pressed in. Implemented as part of a framework, this emulation is available to all technology-based applications that can continue to work normally with events You do not have to go through a special API, so the solution is transparent to the application developer: An application that is supposed to run on touch devices will only be able to test with touch events and can already test it on the desktop in a normal browser dramatically improves productivity by eliminating the need to test the application on the end device or simulator Testing in the desktop browser allows a save reload workflow and is therefore always more efficient than the step typically required for simulators / emulators Compilation and deployment.

The mobile web browser available touch events are quite limited. Depending on the digital device, only simple touch events (touchstart, touchmove, touchend) are supported or gestures (pinch / zoom) are supported (for example, on iPhone). All other touch events must be laboriously manually programmed in the application.

Through the use of synthetic events is a breakthrough in the

Application development succeeded. The new tap events, which include quick typing, touchhold, touch-release to control a lingering finger and swipe to detect swipe movements, give the application developer easy access to common finger actions to use the application logic.

These synthetic fired events are handled by the application developer as well as the native events and do not represent a difference in use. This makes the use particularly easy.

According to the invention, it is also preferred that the synthetic

Operating events are generated by means of a computer mouse and with a developing device, which has no touch-sensitive screen.

It is further particularly preferred if the synthetic operating events one or more of the following use of the touch-sensitive

Screen corresponding operating events correspond to:

- start of touch (touchstart),

- touch movement (touchmove),

- end of touch (touchend),

- approaching two fingers (pinch),

- spreading two fingers (zoom),

- fast tap,

- touchhold,

- end of the lingering touch (touchrelease),

- swipe.

Another object of the present invention relates to an apparatus for generating a running on a touch-sensitive screen digital terminal running application, wherein a code of the application is at least partially transferable from a server device to the digital terminal, wherein the transmission of the code the application is at least partially triggerable by user interaction, the device being configured such that:

a model code usable for a plurality of types of the digital terminal Application is buildable, and

- The code of the application based on the model code is generated.

Another object of the present invention relates to a code of an application, which according to a method of the invention or in a

inventive device is generated.

Embodiments of the invention are illustrated in the drawings and explained in more detail in the following description. The figures do not limit the general idea of the invention.

Short description of the drawing

FIG. 1 schematically shows a digital terminal which has a

touch-sensitive screen, wherein an application of a

Server device is transmitted to the digital terminal.

Figure 2 shows schematically the generation of a code or a plurality of different codes for different types of digital terminals, wherein the different codes are based on a model code or derived therefrom.

Embodiment (s) of the invention

In Figure 1, a digital terminal 15 is shown schematically, which has a touch-sensitive screen 15 ', wherein an application 20 is transmitted from a server device 10 to the digital terminal 15. After the transfer of the application 20, its functionality is available on or on the digital terminal 15. The transmission is preferably carried out by means of a radio interface, ie the digital terminal 15 has a radio interface and the server device 10 also has a radio interface or is (at least indirectly) connected to a radio interface, for example via a base station unit of a mobile network or via a wireless Network connection (WLAN connection). According to the invention, the server device 10 can either be a central server (for example a central server of a manufacturer of the digital terminal. This is made visible to a user, for example, by a representation representing the application (a so-called "icon") is displayed on the touch-sensitive screen 15 'or can be displayed.

FIG. 2 schematically shows the generation of a code 31 or a plurality of different codes 31, 32, 33 for different types of digital terminals 15, wherein the various codes 31, 32, 33 are based on a model code 30 or derived from this.

According to the present invention, the creation of applications (so-called "apps") of mobile digital terminals is greatly facilitated and simplified so that the provision of such applications can be made faster. This is inventively realized in that the model code 30 is preferably written in a language that can handle all types of such mobile digital terminals. Because of the different, sometimes very different operating systems, with which such digital terminals are operated (such

For example, Android, a mobile version of Windows, the operating system of the iPhone or the iPad, etc.) comes as a common language essentially Hypertext Markup Language (HTML) and / or JAVA Script in question.

Claims

claims

A method of generating a live application (20) on a digital terminal (15) having a touch sensitive screen, wherein a code (31) of the application (20) is at least partially transmitted from a server device (10) to the digital terminal (15) where the transmission of the code of the application is at least partially triggered by user interaction, characterized in that the method comprises the steps of:

- creating a model code (30) of the application (20) and usable for a plurality of types of the digital terminal (15) and

- generating the code (31) of the application (20) based on the model code (30).

2. The method according to claim 1, characterized in that the model code (30) for the plurality of types of the digital terminal (15) is platform independent.

3. The method according to claim 1 or 2, characterized in that the code (31) of the application (20) is a hypertext markup language (HTML) code.

4. The method according to any one of the preceding claims, characterized in that the creation of the model of the plurality of types of the digital terminal (15) usable model code (30) of the application (20) is a developing device is used which has no touch-sensitive screen.

5. The method according to any one of the preceding claims, characterized in that the application (20) has at least a first possible view and a second possible view, wherein the first and second view correspond to different view modes of the application, wherein the first possible view by means of a first uniform resource locator (URL) and the second possible view being referenced by a second Uniform Resource Locator (URL).

6. The method according to claim 5, characterized in that after the start of

Application (20) is shown depending on the last time you exit the application displayed directly the first or second possible view.

7. The method according to any one of the preceding claims, characterized in that during the creation of the for the plurality of types of the digital terminal (15) of the application (20) a proxy unit is used, the proxy unit incorporating access control information (HTTP ACCESS CONTROL header) into a message received from an external server.

8. Method according to one of the preceding claims, characterized in that during the preparation of the model code (30) of the application (20) which can be used for the plurality of types of the digital terminal (15), synthetic

Operating events are generated, wherein such synthetic operating events correspond to a use of the touch-sensitive screen.

9. The method according to claims, characterized in that the synthetic

A method according to claim 8 or 9, characterized in that the synthetic operating events correspond to one or more of the following operating events corresponding to use of the touch-sensitive screen:

- start of touch (touchstart),

- touch movement (touchmove),

- end of touch (touchend),

- approaching two fingers (pinch),

- spreading two fingers (zoom),

- fast tap,

- touchhold,

- end of the lingering touch (touchrelease),

- swipe.

11. Device (1) for generating a touch-sensitive one

Digital application terminal (15) executable application (20), wherein a code (31) of the application (20) at least partially from a server device (10) to the digital terminal (15) is transferable, wherein the transmission of the code of the application at least partially triggerable by user interaction, characterized in that the device is configured such that:

a model code (30) of the application (20) which can be used for a plurality of types of the digital terminal (15) can be produced, and

the code (31) of the application (20) can be generated based on the model code (30) is.

12. Code of an application (20), which is generated according to a method according to any one of claims 1 to 10 or in a device according to claim 11.