Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: The embodiments set forth techniques for managing storage space in user devices. A storage space manager can be configured to receive a request to increase an available amount of storage space within the user device, identify applications where at least a portion of the application's associated data can be deleted to increase the available storage space, determining particular applications whose identified associated data should be deleted, and causing the associated data to be deleted. According to some embodiments, applications managed by the storage space manager are not adapted to manage storage space themselves. Instead, these applications can be registered to the storage space manager and can be grouped into subsets that share sections of storage space within the user device. Moreover, the storage space manager can be a subsystem storage space manager that interfaces with a higher-level system storage manager that orchestrates storage space management within the user device.

Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: The embodiments set forth techniques for managing storage space in user devices. A storage space manager can be configured to receive a request to increase an available amount of storage space within the user device, identify applications where at least a portion of the application's associated data can be deleted to increase the available storage space, determining particular applications whose identified associated data should be deleted, and causing the associated data to be deleted. According to some embodiments, applications managed by the storage space manager are not adapted to manage storage space themselves. Instead, these applications can be registered to the storage space manager and can be grouped into subsets that share sections of storage space within the user device. Moreover, the storage space manager can be a subsystem storage space manager that interfaces with a higher-level system storage manager that orchestrates storage space management within the user device.

Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: A computer-implemented method for building a software application is disclosed. The method includes: generating a plurality of application resources; creating a plurality of tags; applying one of the tags on each of the plurality of application resources; grouping the application resources by their tags to form at least two asset packs, each identifiable by at least one tag shared by all application resources in the asset pack; and creating an asset pack manifest comprising a location of each of the asset packs and an order in which the asset packs are to be downloaded.

Abstract: Methods and systems are disclosed that allow automated testing of an application program that is configured to receive a touch input. A testing mechanism can be configured to identify the touch input that is designed to produce a specified result. The testing mechanism can generate one or more signals simulating the touch input. The testing mechanism can then check the state of the user interface of the application program being tested and determine whether the actual result conforms to the specified result.

Abstract: Disclosed is a system, method, and program for generating user interface output on an output device attached to a remote computer. The remote computer communicates over a network to at least one server. The remote computer and server may comprise any computing device known in the art or any appliance or device including an embedded computing device. An object is transmitted to the remote computer including user interface components and data. The remote computer generates user interface output from the user interface components and data in the object. The computer further transmits to the remote computer standard application program interfaces (API) that are a member of a set of standard APIs in a first format. The remote computer converts the standard APIs in the first format to user interface APIs in a second format to manipulate the object and generate further user interface output from the components and data in the object.

Abstract: Disclosed is a system, method, and program for translating source code statements to executable code. A source code statement including an application program interface (API) that is a member of a set of standard APIs calling an object in a first format is processed. A mapping is used to determine at least one user interface API corresponding to the determined standard API. The user interface API provides an implementation of the standard APIs in a user interface program. A mapping is determined of the called object to a corresponding object in a second format utilized by the user interface program is accessed. The source code statement comprising the standard API calling the object in the first format is converted to the determined user interface API calling the corresponding object in the second format. The user interface program is capable of executing the user interface API calling the corresponding object.

Abstract: Disclosed is a system, method, and program for generating a user interface for an application program. A determination is made of application program interfaces (APIs) in an application program that are members of a set of standard API interfaces. The application program further includes code in a computer language to perform application program operations. A determination is made from a mapping of at least one user interface API corresponding to the determined standard API interface. The user interface APIs are capable of controlling a user interface program to perform user interface operations. The standard APIs in the application program are converted to user interface APIs to generate the user interface for the application program. The code in the computer language is converted to executable code to perform the application program operations.

Abstract: Disclosed is a system, method, and program for providing a plurality of translator programs for translating source code in a cross-platform computer language, such as Java, to program statements capable of executing on multiple operating system platforms. The translator programs determine whether a source code statement in an application program comprises an application program interface (API) that is a member of a set of standard API interfaces, such as the API interfaces specified in the W3C DOM specification. The translator programs determine from a mapping at least one native operating system API interface corresponding to the determined standard API interface. Native operating system API interfaces provide an implementation of the standard API interfaces. The translator programs further convert the source code statement comprising the standard API interface to the determined native operating system API interface.

Abstract: Described is a method, system, and program for generating an application graphical user interface (GUI) window used by an executing application program. The application program uses an operating system handle addressing the application GUI window to generate content into the application GUI window. A frame element, including GUI components of the application GUI window is added to a user interface object including GUI components used by a user interface program. Application program interfaces (APIs), generated by the application program, are executed to call the handle to generate content into the application GUI window. Standard APIs that are members of a set of standard API interfaces are received to manipulate the GUI components in the frame element to modify a display of the application GUI window. The standard APIs are converted to user interface APIs.

Abstract: Provided is a method, system, program, and data structures for installing components in a computer runtime environment. A kit file is retrieved including information on program components to load into memory. The retrieved kit file information is used to retrieve the program components for the kit file. The retrieved program components for the kit file are loaded into the runtime environment. A determination is made as to whether there are dependency kit files associated with the retrieved kit file. Program components for each determined dependency kit file are maintained in the runtime environment, wherein classes and interfaces are resolved using the program components loaded into the runtime environment.

Abstract: Disclosed is a system, method, and program for implementing components of a user interface as an object. A user interface is implemented in a first user interface program object including elements compatible with a first user interface program. A standard application program interface (API) calling a first standard object to create a second standard object as an element of the first standard object is received. The standard API is a member of a set of standard APIs, such as the W3C APIs. A second user interface program API is generated to create a second user interface program object corresponding to the second standard object. The second user interface program object is embedded as an element in the first user interface program object.