APPLICATION BUILDING SYSTEM, METHOD AND COMPUTER-READABLE MEDIUM

• US 20110167405A1
• Filed: 01/04/2011
• Published: 07/07/2011
• Est. Priority Date: 01/06/2010
• Status: Abandoned Application

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: MIN, Seung Ki
• Application Number:
  US12/984,135
• Publication Number:
  US 20110167405A1
• Time in Patent Office: Days
• US Class Current: 717/107
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An application building system includes a computer having a component container to download components from a server and to store the components, and the computer having a client to download the components from the component container, to load the downloaded components into a program, and to build the program.

The components having various functions may be reused when building an application and are prepared in advance and stored in the server. Program development capability of the application may be maximized by dynamically using the component container, and development time may be shortened.

Claims

1. An application building system, comprising:

a computer having a component container to download components from a server and to store the components; and

the computer having at least one client to download the components from the component container, to load the downloaded components into a program, and to build the program.

2. The application building system according to claim 1, wherein the client downloads the components from the component container and loads the components to the program, when the program is executed.

3. The application building system according to claim 1, further comprising a component ID list unit having an ID list of components to be loaded into the client.

4. The application building system according to claim 3, wherein the component container checks the component ID list stored in the component ID list unit and unloads unused components.

5. The application building system according to claim 1, wherein each of the components includes at least one module and the module has a function.

6. The application building system according to claim 1, further comprising a storage unit to store a plurality of components.

7. The application building system according to claim 6, wherein the component container downloads the components from the storage unit corresponding to a request of the client.

8. The application building system according to claim 1, wherein each of the components is a binary executable file.

9. The application building system according to claim 1, wherein the at least one client is a plurality of clients and the plurality of clients share the components of the component container.

10. The application building system according to claim 9, further comprising a plurality of component ID list units to respectively store ID lists of the components to be loaded to the plurality of clients,

wherein the component container unloads unused components based on the component IDs stored in the plurality of component ID list units.

15. The application building system according to claim 1, wherein the component container checks unused components and unloads the unused components.

11. An application building system, comprising:

a server to store a plurality of components; and

a terminal including a component container to store components transmitted from the server, and a client to make a request for at least one component from the server, to download the at least one component from the component container and to load the downloaded at least one components into a program.

12. The application building system according to claim 11, further comprising a storage unit to store the components transmitted from the server.

13. The application building system according to claim 11, wherein the terminal and the server communicate.

14. The application building system according to claim 11, wherein the client includes an interface to communicate with the server.

16. An application building method, comprising:

transmitting, by a processor, a request for components to a server;

downloading, by the processor, the components from the server and storing the components in a component container; and

downloading, by the processor, the components from the component container and loading the components into a program of a client.

17. The application building method according to claim 16, wherein the transmitting of the request for the components to the server includes:

communicating with the server through an interface included in the client.

18. The application building method according to claim 16, wherein the downloading of the components from the component container is performed based on a component downloading command loaded into the program of the client in advance.

19. The application building method according to claim 16, wherein the loading of the components into the program of the client includes sharing the components stored in the component container between a plurality of clients.

20. The application building method according to claim 19, further comprising:

checking ID lists of components to be loaded to the plurality of clients; and

deleting unused components from the components stored in the component container.

21. The application building method according to claim 16, wherein each of the components is a binary executable file.

22. The application building method according to claim 16, wherein the downloading of the components from the component container includes:

storing the components transmitted from the server in a storage unit; and

downloading the components from the storage unit and storing the components in the component container.

23. At least one non-transitory computer readable medium comprising computer readable instructions that control at least one processor to implement the method of claim 16.