Electronic device and method for inserting data into execution screen of application, and recording medium

Abstract

Provided are an electronic device and a method for inserting data into an execution screen of an application. The method for inputting an image into an execution screen of an application by an electronic device includes the operations of: identifying a first image input method corresponding to at least one user input for inputting the image into the execution screen of the application; identifying whether the application supports the first image input method; identifying a second image input method supported by the application when the application does not support the first image input method; obtaining a code of a framework for inputting the image into the execution screen of the application by using the second image input method; and providing the obtained code of the framework to the application.

Description

Electronic device and method for inserting data into the execution screen of an application, and recording medium

[0001] The present disclosure relates to an electronic device and method for inserting data into an execution screen of an application, and to a recording medium.

[0002] As multimedia and network technologies advance, electronic devices are able to utilize a variety of data through various applications, and various input methods are provided to input data into applications.

[0003] However, the data input methods supported by each application were not identical, and when user input was received using a data input method not supported by the application, the application was unable to process the user input. Furthermore, it was difficult for electronic devices to modify the application's code to allow the application to process data input methods not supported by the application.

[0004] Accordingly, there is a need for a technology that enables data input operations to be performed through other data input methods supported by the application without modifying the application's code, even if user input is received through a data input method not supported by the application.

[0005] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

[0006] As a technical means for achieving the above-described technical problem, one embodiment of the present disclosure may provide a method for an electronic device to input an image into an execution screen of an application, including: receiving at least one user input for inputting an image into an execution screen of the application; identifying a first image input method corresponding to the at least one user input; identifying the image and an input location of the image on the execution screen based on the at least one user input; and identifying whether the application supports the first image input method; identifying a second image input method supported by the application when the application does not support the first image input method; generating code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location; and providing the generated code of the framework to the application.

[0007] In addition, one embodiment of the present disclosure may provide an electronic device for inputting an image into an execution screen of an application, including: a display; a memory for storing commands; and at least one processor operatively connected to the display and the memory and configured to execute the commands, wherein the at least one processor, by executing the commands, receives at least one user input for inputting an image into an execution screen of the application, identifies a first image input method corresponding to the at least one user input, identifies the image and an input location of the image on the execution screen based on the at least one user input, identifies whether the application supports the first image input method, and, when the application does not support the first image input method, identifies a second image input method supported by the application, and generates code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location, and provides the generated code of the framework to the application.

[0008] In addition, one embodiment of the present disclosure may provide a computer-readable recording medium having recorded thereon a program for executing a method for inputting an image into an execution screen of an application, the method including: receiving at least one user input for inputting an image into an execution screen of the application; identifying a first image input method corresponding to the at least one user input; identifying the image and an input location of the image on the execution screen based on the at least one user input; and identifying whether the application supports the first image input method; identifying a second image input method supported by the application when the application does not support the first image input method; generating code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location; and providing the generated code of the framework to the application.

[0009] In addition, one embodiment of the present disclosure may provide a method for an electronic device to input an image into an execution screen of an application, the method including: receiving at least one user input for inputting an image into an execution screen of an application; identifying a first image input method corresponding to the at least one user input; identifying whether the application supports the first image input method; identifying a second image input method supported by the application when the application does not support the first image input method; and inputting the image into the application through the second image input method using code of a framework for inputting the image into the execution screen of the application through the second image input method.

[0010] FIG. 1 is a diagram illustrating an overview of an electronic device inputting an image into an execution screen of an application according to one embodiment of the present disclosure.

[0011] FIG. 2 is a flowchart of a method for inputting an image into an execution screen of an application according to one embodiment of the present disclosure.

[0012] FIG. 3 is a flowchart of a method for inputting an image into an application based on a user input of an image input through a keyboard by an electronic device according to an embodiment of the present disclosure.

[0013] FIG. 4a is a drawing showing an example of an execution screen of an application according to one embodiment of the present disclosure.

[0014] FIG. 4b is a drawing showing an example of displaying an execution screen of an application and an execution screen of a keyboard application according to one embodiment of the present disclosure.

[0015] FIG. 4c is a diagram illustrating an example in which an image list is displayed within an execution screen of a keyboard application according to one embodiment of the present disclosure, and an image selected from the image list is displayed within an input field.

[0016] FIG. 4d is a drawing showing an example of an image input into an execution screen of an application according to one embodiment of the present disclosure.

[0017] FIG. 5 is a flowchart of a method for an electronic device to input an image into an application based on a user input of dragging and dropping an image according to one embodiment of the present disclosure.

[0018] FIG. 6 is a diagram illustrating an example of an image being input into an application when a user input of drag and drop is received according to one embodiment of the present disclosure.

[0019] FIG. 7 is a flowchart of a method for an electronic device to input an image into an application based on a user input for pasting an image according to one embodiment of the present disclosure.

[0020] FIG. 8 is a diagram illustrating an example of an image being input into an application when a user input for pasting an image is received according to one embodiment of the present disclosure.

[0021] FIG. 9 is a block diagram of an electronic device within a network environment according to various embodiments.

[0022] FIG. 10 is a diagram illustrating a software stack of an electronic device according to one embodiment of the present disclosure.

[0023] Below, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In addition, for the purpose of clearly explaining the present disclosure in the drawings, parts irrelevant to the description are omitted, and similar parts are designated with similar reference numerals throughout the specification.

[0024] The terms used in this disclosure are described as currently common terms, taking into account the functions mentioned herein. However, these terms may mean various other terms depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, etc. Therefore, the terms used in this disclosure should not be interpreted solely based on their names, but rather based on the meanings of the terms and the overall content of this disclosure.

[0025] Additionally, while terms such as first, second, etc. may be used to describe various components, the components should not be limited by these terms. These terms are used to distinguish one component from another.

[0026] Throughout the specification, when a part is said to be "connected" to another part, this includes not only the cases where the parts are "directly connected" but also the cases where the parts are "electrically connected" with other elements intervening. Furthermore, when a part is said to "include" a component, this does not exclude other components, but rather includes other components, unless otherwise stated.

[0027] The phrases “in one embodiment” and the like appearing in various places throughout this disclosure do not necessarily all refer to the same embodiment.

[0028] An embodiment of the present disclosure may be represented by functional block configurations and various processing steps. Some or all of these functional blocks may be implemented by various hardware and / or software configurations that perform specific functions. For example, the functional blocks of the present disclosure may be implemented by one or more microprocessors or by circuit configurations for a given function. Furthermore, for example, the functional blocks of the present disclosure may be implemented in various programming or scripting languages. The functional blocks may be implemented by algorithms that execute on one or more processors. Furthermore, the present disclosure may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical and physical configurations.

[0029] Additionally, the connecting lines or connecting members between components depicted in the drawings are merely exemplary representations of functional connections and / or physical or circuit connections. In an actual device, connections between components may be represented by various functional connections, physical connections, or circuit connections that may be replaced or added.

[0030] The present disclosure will be described in detail with reference to the attached drawings below.

[0031] FIG. 1 is a diagram illustrating an overview of an electronic device inputting an image into an execution screen of an application according to one embodiment of the present disclosure.

[0032] Referring to identification numbers 1 and 2 of FIG. 1, an electronic device (100) according to one embodiment may input an image into the execution screen of an application (e.g., application (946) of FIG. 9) when a user input for inputting an image is received and the application does not support an image input method corresponding to the user input, input the image into the execution screen of the application through another image input method.

[0033] For example, referring to identification number 1, the electronic device (100) may receive a user input for inputting an image into the execution screen of an application and determine whether the application supports a first image input method corresponding to the user input. In addition, for example, referring to identification number 2, if the application does not support the first image input method, the electronic device (100) may input an image into the execution screen of the application using a second image input method different from the first image input method. The electronic device (100) may obtain a code of a framework for inputting an image using the second image input method and provide the code to the application. For example, in a software stack such as FIG. 10, a code of a framework stage for the second image input method may be obtained and the obtained code may be provided to the application. The application may display an image on the execution screen of the application according to the second image input method based on the provided code. Additionally, for example, to convert an image input method (e.g., from a first image input method to a second image input method), the application can display an image in the second image input method on the application's execution screen by obtaining (e.g., editing, creating, adding) source code outside the framework in the software stack.

[0034] The electronic device (100) may be, but is not limited to, a smartphone, a tablet PC, a PC, a smart TV, a mobile phone, a PDA (personal digital assistant), a laptop, a media player, a microserver, a GPS (global positioning system) device, an e-book reader, a digital broadcasting terminal, a navigation device, a kiosk, an MP3 player, a digital camera, a home appliance, or any other mobile or non-mobile computing device. Furthermore, the electronic device (100) may be a wearable device, such as a watch or glasses, equipped with a display. However, the electronic device (100) is not limited thereto, and may include any type of device capable of displaying an application execution screen and receiving user input through a display.

[0035] In this document, images may be of various types, such as still images, moving images, GIF images, images with sound, emoticons, and emojis. Furthermore, one embodiment of the present disclosure may also be applied when inputting data files other than images.

[0036] FIG. 2 is a flowchart of a method for inputting an image into an execution screen of an application according to one embodiment of the present disclosure.

[0037] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.

[0038] According to one embodiment, operations 200 to 270 may be understood to be performed in a processor (e.g., processor (920) of FIG. 9) of an electronic device (e.g., electronic device (100) of FIG. 1 and / or electronic device (901) of FIG. 9).

[0039] Referring to FIG. 2, an electronic device may input an image within the execution screen of an application in response to a user input attempting to input an image using an image input method not supported by the application.

[0040] In operation 200, an electronic device (100) according to one embodiment may receive a user input for inputting an image into an execution screen of an application. The user input for inputting an image into the execution screen of the application may be a user input for inserting and displaying an image into the execution screen of the application. The electronic device (100) may receive one or more user inputs for inputting an image into the execution screen of the application.

[0041] For example, one or more user inputs for inputting an image into the execution screen may be user input via a first image input method. The first image input method may include, for example, at least one of a method for inputting an image selected from a list of images displayed via a keyboard, a method for inputting an image by drag and drop, or a method for inputting an image by copy and paste.

[0042] For example, a method of inputting an image selected from a list of images displayed via a keyboard may include an input method of displaying an image via a keyboard application and the user selecting the displayed image, and may include touch input by the user's finger or stylus pen.

[0043] However, the first image input method is not limited thereto, and may be various image input methods for inputting an image to the display. For example, the first image input method may be an input method according to a user input for an image displayed in various ways on the display of the electronic device (100), and may include, for example, a drag and drop for an image, a touch selection for an image, a copy and paste input for an image, etc. In addition, for example, the user input may be a selection input for an image displayed within the execution screen of the application as well as a keyboard application.

[0044] In operation 210, the electronic device (100) according to one embodiment may identify a first image input method corresponding to a user input. The first image input method corresponding to the user input may include, for example, at least one of a method of inputting an image selected from a list of images displayed via a keyboard, a method of inputting an image by drag and drop, or a method of inputting an image by copy and paste.

[0045] For example, if the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the user input may include user input for selecting an input field of the application, user input for calling up the image list in a keyboard application that is activated according to selection of the input field, and user input for selecting an image from the image list.

[0046] For example, if the first image input method is a method of inputting an image by drag and drop, the user input may include a user input of selecting an input field of the application, a user input of calling an image list from a keyboard application that is activated according to selection of the input field, and a user input of selecting an image from the image list and dragging and dropping the selected image onto the execution screen of the application. In addition, for example, if the first image input method is a method of inputting an image by drag and drop, the user input may include a user input of selecting an image from the execution screen of another application and dragging and dropping the selected image onto the execution screen of the application (e.g., an input field).

[0047] For example, if the first image input method is a method of inputting an image by copying and pasting, the user input may include at least one of a user input of selecting (e.g., long-pressing) a specific location on the application's execution screen (e.g., an input field on the application's execution screen), a user input of selecting a paste item from a menu displayed according to the selection of the specific location, a user input of selecting a clipboard item from a menu displayed according to the selection of the specific location, or a user input of selecting an image on the clipboard. In addition, for example, the image to be pasted may be an image copied in various situations. For example, the copied image may be an image stored in memory (the clipboard) through a user input of long-pressing an image on the execution screen of a specific application or other input, and an image displayed on the application and another application (e.g., an Internet browser) may be copied.

[0048] In operation 220, the electronic device (100) according to one embodiment can identify an image and / or an input location of an image. The electronic device (100) can identify an image selected by a user input and / or a portion of an area on the execution screen of an application on which the selected image is to be displayed.

[0049] For example, when the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the electronic device (100) can identify the image selected by the user input from the image list of the keyboard application as an image to be input by the application. For example, the electronic device (100) can identify the image selected by the user input in operation 200 as an image to be displayed within the execution screen of the application. In addition, the electronic device (100) can identify an input field of the application, or a part of the execution screen of the application where an input value through the input field is displayed (e.g., another area other than the input field on the execution screen of the application) as an input location of the image. For example, the input area of ​​the image may be one of the distinct areas within the GUI that constitutes the execution screen of the application. For example, the input area of ​​the image may include an input field area, a data display area, etc. within the GUI of the execution screen of the application.

[0050] For example, when the first image input method is a method of inputting an image by drag and drop, the electronic device (100) can identify the dragged and dropped image as an image to be input into the application. In addition, the electronic device (100) can identify a portion of the execution screen of the application including the location where the image is dropped as the input location of the image. For example, the electronic device (100) can identify a GUI area including the dropped location (e.g., an input field area of ​​the application, a data display area, etc.) as the input location of the image based on the coordinate values ​​of the location where the image is dropped.

[0051] For example, if the first image input method is a method of inputting an image by copying and pasting, the electronic device (100) can identify the copied image as an image to be input into the application. In addition, the electronic device (100) can identify the location where the image is to be pasted as the input location of the image.

[0052] In operation 230, the electronic device (100) according to one embodiment can determine whether the application supports the first image input method. The electronic device (100) can determine whether the application supports the first image input method by identifying at least one image input method supported by the application and determining whether the at least one identified image input method is the first image input method corresponding to the user input.

[0053] For example, an application may support only some of the following methods: inputting an image selected from a list of images displayed via a keyboard, inputting an image by drag and drop, and inputting an image by copy and paste. Accordingly, the first image input method corresponding to the user input may not be included in the input methods supported by the application. For example, the electronic device (100) may determine whether the application has a keyboard handler, a graphic handler for drag and drop, and / or a graphic handler for copy and paste, but is not limited thereto. The electronic device (100) may determine the image input method supported by the application through various methods other than the method of determining whether the application has a handler.

[0054] As a result of the determination in operation 230, if it is determined that the application does not support the first image input method, in operation 240, the electronic device (100) according to one embodiment can identify a second image input method supported by the application. According to one embodiment, the electronic device (100) can check whether there is a bypass path for the first image input method, and if there is a bypass path, select an input method of the bypass path (e.g., the second image input method). According to one embodiment, even before receiving a user input, the electronic device (100) can perform an operation of identifying an image input method supported by the application in advance when executing the application.

[0055] For example, if the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, and the application does not support the first image input method, the electronic device (100) can identify that the application supports a method of inputting an image by drag & drop, and / or a method of inputting an image by copy & paste.

[0056] For example, if the first image input method is a method of inputting an image by drag and drop and the application does not support the first image input method, the electronic device (100) can identify that the application supports a method of inputting an image selected from a list of images displayed through a keyboard and / or a method of inputting an image by copy and paste.

[0057] For example, if the first image input method is a copy & paste method and the application does not support the first image input method, the electronic device (100) can identify that the application supports a method of inputting an image selected from a list of images displayed via a keyboard and / or a method of inputting an image by drag & drop.

[0058] In operation 250, an electronic device (100) according to an embodiment may obtain a code of a framework for inputting an image using a second image input method. The electronic device (100) may obtain the code of the framework for inputting an image using the second image input method based on link information of an image to be input on an execution screen of an application and an input location within the execution screen of the application where the image is to be input. The link information of the image may include, for example, uniform resource identifier (URI) information of the image. The link information of the image may include, for example, a location of an image stored in an electronic device, a location of an image stored on a clipboard, a web address of the image, etc.

[0059] For example, the framework can identify whether the application does not support an image handler according to a specified input method at the framework level, and code for connecting the specified input method to another input method may already be generated at the framework level. Accordingly, the electronic device (100) can select the code of the framework that has already been generated, and acquire the code of the framework for inputting an image using the second image input method so that the image (e.g., link information of the image) input using the first image input method is included in the selected code and transmitted.

[0060] For example, if the second image input method supported by the application and different from the first image input method is a method of inputting an image by drag and drop, the electronic device (100) can obtain the code of a framework for dragging and dropping an image. For example, the electronic device (100) can obtain the code for registering a DragListener for a portion of an area where an image is to be input within the execution screen of the application.

[0061] For example, the code for a framework for dragging and dropping images can be obtained by editing at least part of the code in Table 1 below.

[0062]

[0063] Additionally, the code below (e.g. pseudo code) can be used to obtain the code of the framework for dragging and dropping images, for example.

[0064]

[0065] For example, if a second image input method supported by an application and different from the first image input method is a method of inputting an image by drag and drop, the electronic device (100) can convert the user's input into a user input of the second image input method, that is, the drag and drop method. For example, if a user input occurs to select an image from a list of images displayed through a keyboard, that is, the first image input method, the image can be input using the drag and drop method supported by the application.

[0066] For example, if the second image input method supported by the application and different from the first image input method is a method of inputting an image by copying and pasting, the electronic device (100) can obtain the code of the framework for copying and pasting an image. For example, the electronic device (100) can obtain the code of the framework for overriding the image pasting operation for some area where an image is to be input within the execution screen of the application.

[0067] For example, the code for a framework for copying and pasting images can be obtained by editing at least part of the code in Table 2 below.

[0068]

[0069] Additionally, the code below (e.g. pseudo code) can be used to obtain the code of the framework for copying and pasting images, for example.

[0070]

[0071] For example, if a second image input method supported by an application and different from the first image input method is a method of inputting an image by copy and paste, the electronic device (100) can convert the user's input into a user input by the copy and paste method, which is the second image input method. For example, if a user input occurs to select an image from a list of images displayed through a keyboard, which is the first image input method, the image can be input by the copy and paste method supported by the application.

[0072] For example, if a second image input method supported by an application and different from the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the electronic device (100) can obtain a code of a framework for inputting an image selected from a list of images displayed via the keyboard. For example, the electronic device (100) can obtain a code of a framework for overriding InputConnection to input an image into a portion of an area where an image is to be input within an execution screen of the application.

[0073] For example, by editing at least part of the code in Table 3 below, the code for a framework for inputting an image via a keyboard can be obtained.

[0074]

[0075] Additionally, the code below (e.g. pseudo code) can be used to obtain the code of the framework for inputting an image via the keyboard, for example.

[0076]

[0077] For example, if a second image input method supported by an application and different from the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the electronic device (100) can convert a user input into a user input by the input method by selecting an image from a list of images displayed via the keyboard, which is the second image input method. For example, if a user input of inputting an image occurs via drag and drop, which is the first image input method, the image can be input by inputting an image selected from a list of images displayed via the keyboard, which is supported by the application.

[0078] In operation 260, the electronic device (100) according to one embodiment can display an image on the execution screen of the application through the second image input method. The electronic device (100) can display the image at a specific location on the execution screen of the application through the second image input method using the code of the framework obtained in operation 250. For example, the code of the framework obtained in operation 250 can be transmitted to the application, and the application can display the image on the execution screen of the application through the second image input method based on the transmitted code of the framework. Accordingly, the electronic device (100) can check whether there is a bypass route of the first image input method, and if there is a bypass route, select an input method of the bypass route (e.g., the second image input method), and display the image through the selected second image input method. Although operations 230, 240, 250, and 260 are described above as separate operations, they are not limited thereto. At least two or more of the operations 230, 240, 250 and 260 may be performed as one operation by the electronic device (100).

[0079] If it is determined in operation 230 that the application supports the first image input method, in operation 270, the electronic device (100) can input an image into the execution screen of the application according to the first image input method.

[0080] Meanwhile, while the above description describes inputting an image into the application's execution screen based on user input, this is not limited thereto. For example, the electronic device (100) may input data files other than images into the application's execution screen. In this case, the image input method may be a data input method, and the code of the framework for inputting the data may be obtained.

[0081] In one embodiment, even if user input for inserting data into an application is not supported by the application, data entry operations based on user input can be performed without modifying the application's code by modifying or selecting the framework's code for another data input method, thereby improving the user experience.

[0082] FIG. 3 is a flowchart of a method for inputting an image into an application based on a user input of an image input through a keyboard by an electronic device according to an embodiment of the present disclosure.

[0083] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.

[0084] According to one embodiment, operations 300 to 370 may be understood to be performed in a processor (e.g., processor (920) of FIG. 9) of an electronic device (e.g., electronic device (100) of FIG. 1 and / or electronic device (901) of FIG. 9).

[0085] In Fig. 3, the first image input method may be a method of inputting an image selected from a list of images displayed via a keyboard.

[0086] In operation 300, an electronic device (100) according to one embodiment may receive a user input selecting an input field of an application. The input field of the application may be at least a portion of a graphical user interface (GUI) for receiving user input for the application. The input field may be, for example, a field for receiving a user's keyboard input in conjunction with a keyboard application.

[0087] For example, a method of inputting an image selected from a list of images displayed via a keyboard may include an input method of displaying an image via a keyboard application and the user selecting the displayed image, and may include touch input by the user's finger or stylus pen.

[0088] However, the first image input method is not limited thereto, and may be various image input methods for inputting an image to the display. For example, the first image input method may be an input method according to a user input for an image displayed in various ways on the display of the electronic device (100). For example, the user input may be a selection input for an image displayed within the execution screen of the application as well as a keyboard application.

[0089] According to one embodiment, when a user input for selecting an input field is received, the electronic device (100) can identify whether some areas, starting from some areas close to the input field of the application, support the method of inputting an image by drag and drop. For example, the electronic device (100) can search for some areas, starting from some areas close to the input field of the application, that support the DragListener operation. In addition, the electronic device (100) can, for example, store the Listener of the searched areas for the system for the image input operation according to the drag and drop input method. When the user selects the input field, the electronic device (9100) can improve the response speed of the electronic device (100) to the user's image input by identifying and storing the Listener of the draggable View in advance.

[0090] In operation 310, the electronic device (100) according to one embodiment may display an execution screen of a keyboard application. As an input field of the application is selected, the electronic device (100) may display the execution screen of the keyboard application on the screen of the electronic device (100).

[0091] In operation 320, the electronic device (100) according to one embodiment may identify an image to be input and an input location of the image based on a user input to the keyboard application. The electronic device (100) may identify an image to be input and an input location of the image within the execution screen of the application based on the user input to the keyboard application. For example, the electronic device (100) may receive a user input for selecting an object for displaying a list of images within the execution screen of the keyboard application, and may receive a user input for selecting an image to be input into the application from the displayed image list. In this case, for example, the electronic device (100) may identify an image selected from the image list as an image to be input into the application. In addition, since the keyboard application is activated based on a user input for selecting an input field of the application, for example, the electronic device (100) may identify a portion of the execution screen of the application, into which the input field and / or a value entered into the input field is to be input, as an input location of the image. For example, the input area of ​​the image may be one of distinct areas within a GUI constituting the execution screen of the application. For example, the input area of ​​an image may include an input field area, a data display area, etc. within the GUI of the application's execution screen.

[0092] In operation 330, the electronic device (100) according to one embodiment can determine whether the application supports an image input method via a keyboard. For example, the electronic device (100) can determine whether the application includes a keyboard handler. However, the present invention is not limited thereto, and the electronic device (100) can determine whether the application supports an image input method through various methods other than the method of determining whether the application includes a handler.

[0093] If it is determined in operation 330 that the application does not support an image input method via a keyboard, in operation 340, the electronic device (100) may identify some areas within the application's execution screen that support the second image input method. For example, the electronic device (100) may identify some areas within the application's execution screen that support an image input method via drag and drop. According to one embodiment, even before receiving a user input, the electronic device (100) may perform an operation of identifying an image input method supported by the application in advance when executing the application.

[0094] According to one embodiment, the electronic device (100) can identify whether some areas, starting from a certain area close to an input field of an application, support a method of inputting an image by drag and drop. For example, in operation 340, the electronic device (100) can search in advance for some areas, starting from a certain area close to an input field of an application, that support a DragListener operation. In addition, the electronic device (100) can, for example, store a Listener of the searched areas in advance for the system for an image input operation according to the drag and drop input method. Accordingly, the electronic device (100) can more quickly identify some areas that support a method of inputting an image by drag and drop, and can improve the response speed of the electronic device (100) to a user's image input.

[0095] In operation 350, the electronic device (100) according to one embodiment may obtain the code of the framework for inputting an image using the second image input method. For example, the framework may identify whether an image handler for a specified input method is not supported for each application at the framework level, and code for connecting the specified input method to another input method may already be generated at the framework level. Accordingly, the electronic device (100) may select the code of the already generated framework, and may obtain the code of the framework for inputting an image using the second image input method so that the image input using the first image input method is contained in the selected code and transmitted. The electronic device (100) may obtain the code of the framework level for the second image input method, for example, in a software stack such as that shown in FIG. 10, and provide the obtained code to the application. The framework may provide functions and architectures necessary for the operation of the application. For example, the View System (11) within the framework (10) of the software stack of FIG. 10 may provide multiple views to the application. Multiple views can be UI components, such as icons, text, images, etc. For example, the View System (11) can provide functions for changing the image input method. For example, the View / TextView of the View System (11) can provide a method for changing the image input event of the corresponding view to an input event of a different image input method.

[0096] For example, when the second image input method is a method of inputting an image by drag and drop, the electronic device (100) can obtain a code of a framework for dragging and dropping an image. For example, the electronic device (100) can obtain a code for a graphic handler of drag and drop. For example, the electronic device (100) can obtain a code for registering a DragListener for a portion of an area where an image is to be input within the execution screen of the application. Accordingly, an image and an input location of the image identified from a user input entered by a keyboard input method can be used as the source data and destination of the DragListener, and the application can input an image into the execution screen of the application by dragging and dropping by performing a drop action (ACTION_DROP) based on the source data and destination values ​​of the DragListener. In this case, for example, the performance of at least one action among other types of actions (e.g., ACTION_DRAG_STARTED, ACTION_DRAG_ENTERED, ACTION_DRAG_EXITED, ACTION_DRAG_ENDED) can be omitted.

[0097] For example, if the second image input method is a method of inputting an image by copy and paste, the electronic device (100) can obtain a code of a framework for copying and pasting an image. For example, the electronic device (100) can obtain a code for a graphic handler for copy and paste. For example, the electronic device (100) can obtain a code of a framework for overriding an image pasting operation for a certain area where an image is to be input within an execution screen of an application.

[0098] Additionally, for example, to convert an image input method (e.g., from a first image input method to a second image input method), the application may be enabled to display images in the second image input method on the application's execution screen by obtaining (e.g., editing, creating, adding) source code from an area outside the framework in the software stack.

[0099] In operation 360, an electronic device (100) according to one embodiment may provide a framework code to an application. Based on the provided framework code, the application may display an image at a specific location within the application's execution screen through a second image input method.

[0100] Meanwhile, if it is determined in operation 330 that the application supports an image input method via a keyboard, the electronic device (100) can input an image into the execution screen of the application in operation 370.

[0101] Meanwhile, while the above description describes inputting an image into the application's execution screen based on user input, this is not limited thereto. For example, the electronic device (100) may input data files other than images into the application's execution screen. In this case, the image input method may be a data input method, and framework code for inputting the data may be generated.

[0102] In one embodiment, even if the application does not support user input for entering data selected from a list of images displayed via a keyboard, the data entry operation based on the user input can be performed without modifying the application's code by modifying or selecting the code of the framework for another data input method, thereby improving the user experience.

[0103] FIG. 4a is a drawing showing an example of an execution screen of an application according to one embodiment of the present disclosure.

[0104] Referring to FIG. 4A, the execution screen of the application may include an input field (40), and the electronic device (100) may receive a user input for selecting the input field (40). For example, the application may be a messenger application, and the electronic device (100) may receive a user input for selecting an input field (40) for entering text into the messenger application. However, the present invention is not limited thereto, and the application may be various applications that allow image input via a keyboard, as well as a messenger application. For example, the application may be, but is not limited to, a mail application, a word processing application, a note application, a game application, a chat application, etc. (Additional examples, etc.)

[0105] FIG. 4b is a drawing showing an example of displaying an execution screen of an application and an execution screen of a keyboard application according to one embodiment of the present disclosure.

[0106] Referring to FIG. 4B, when an input field (40) is selected by a user, the electronic device (100) can display an execution screen (41) of a keyboard application on the screen of the electronic device (100). For example, the keyboard application may be a keyboard application pre-installed on the terminal, such as Google Keyboard, Samsung Keyboard, etc., or a keyboard application downloaded and installed through an application store. According to one embodiment, the execution screen (41) of the keyboard application may include an object (42) for inputting an image through the keyboard application. In addition, the electronic device (100) can receive a user input for selecting an object (42) on the execution screen (41) of the keyboard application.

[0107] FIG. 4c is a diagram illustrating an example in which an image list is displayed within an execution screen of a keyboard application according to one embodiment of the present disclosure, and an image selected from the image list is displayed within an input field.

[0108] Referring to the identification number 7 of FIG. 4C, when the input field (40) is selected in FIG. 4A, the electronic device (100) can identify that the image input method via the keyboard is not supported by the application. The identifying operation can be performed when the input field is selected, and can be performed, for example, when receiving a user input for selecting an object (42) within the execution screen (41) of the keyboard application of FIG. 4B, or when receiving a user input for selecting an image (45). When identifying that the image input method via the keyboard is not supported by the application, the electronic device (100) can search for some area (44) within the execution screen of the application that supports the drag-and-drop input method.

[0109] Additionally, as an object (42) is selected in FIG. 4b, an image list (43) may be displayed within the execution screen of the keyboard application. The electronic device (100) may receive a user input for selecting an image (45) from among the images within the image list (43). For example, the image may include various types of images, such as still images, moving images, GIF images, images with sound, emoticons, and emojis.

[0110] If the image input method via the keyboard is not supported by the application, the images in the image list (43) cannot be displayed. For example, if the image input method via the keyboard is not supported by the application, the images in the image list (43) are not displayed, and the area where the images are to be displayed may be displayed with, for example, a hatching or gray color. However, according to one embodiment of the present disclosure, even if the application does not support the image input method via the keyboard, the images can be input by bypassing them through another input method supported by the application, and thus, as in FIG. 4c, the images in the image list (43) can be displayed as if the application supports the image input method via the keyboard.

[0111] Referring to the identification number 8 of FIG. 4C, when the image (45) is selected in the identification number 7 of FIG. 4C, the image (45) can be input and displayed within the input field (49). The electronic device (100) can obtain link information of the image (45) and identify the location on the screen of the input field (49) that supports drag-and-drop. Based on the link information of the image (45) and the location on the screen of the input field (49), the electronic device (100) can obtain the code of the framework for image input of drag-and-drop. In addition, the electronic device (100) can provide the obtained code to the application, and the application can cause the image (45) to be displayed within the input field (49) based on the received code.

[0112] According to one embodiment, the image (45) displayed within the input field (49) may be displayed in a smaller size than the image (45) displayed within the image list (43).

[0113] FIG. 4d is a drawing showing an example of an image input into an execution screen of an application according to one embodiment of the present disclosure.

[0114] As the image (45) is selected in FIG. 4c, the electronic device (100) can obtain link information of the image (45) and identify the location on the screen of a portion (44) that supports drag-and-drop. Referring to FIG. 4d, the electronic device (100) can obtain a code of a framework for image input of drag-and-drop based on the link information of the image (45) and the location on the screen of the portion (44). In addition, the electronic device (100) can provide the generated code to an application, and the application can cause the image (45) to be displayed in the portion (44) based on the received code.

[0115] For example, when an image (45) is selected from the image list (43) at identification number 7 in FIG. 4c, the image (45) may be displayed in an input field (49) as in identification number 8 in FIG. 4c and ultimately input into the application through additional user input (e.g., user input selecting a transmit button), or the image may be directly input into a certain area (44) as in FIG. 4d.

[0116] FIG. 5 is a flowchart of a method for an electronic device to input an image into an application based on a user input of dragging and dropping an image according to one embodiment of the present disclosure.

[0117] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.

[0118] According to one embodiment, operations 500 to 570 may be understood to be performed in a processor (e.g., processor (920) of FIG. 9) of an electronic device (e.g., electronic device (100) of FIG. 1 and / or electronic device (901) of FIG. 9).

[0119] In Fig. 5, the first image input method may be a method of inputting an image according to a user input of dragging and dropping an image.

[0120] In operation 500, an electronic device (100) according to an embodiment can display an execution screen of a first application and an execution screen of a second application together. The electronic device (100) can display an image within the execution screen of the second application, and the electronic device (100) can display the execution screen of the first application and the execution screen of the second application together on the screen of the electronic device (100) so that an image within the execution screen of the second application can be dragged and dropped onto the execution screen of the first application.

[0121] In operation 510, an electronic device (100) according to one embodiment may receive a user input for dragging and dropping an image within an execution screen of a second application onto an execution screen of a first application. The electronic device (100) may receive a user input for selecting an image within the execution screen of the second application, dragging the selected image onto the execution screen of the first application, and dropping the dragged image onto the execution screen of the first application.

[0122] In operation 520, the electronic device (100) according to one embodiment can identify an image to be input into the execution screen of the first application and an input location of the user input based on a drag-and-drop user input. For example, the electronic device (100) can identify an image that is the target of the drag-and-drop user input. For example, the electronic device (100) can identify an input location where the image is to be input within the execution screen of the first application based on a location where the dragged image is dropped. In this case, the input location where the image is to be input may be a portion of the execution screen of the first application.

[0123] In operation 530, the electronic device (100) according to one embodiment may determine whether the first application supports an image input method through a drag-and-drop user input. For example, the electronic device (100) may determine whether the first application has a graphic handler for drag-and-drop.

[0124] If it is determined in operation 530 that the first application does not support an image input method through a drag-and-drop user input, in operation 540, the electronic device (100) can identify some area within the execution screen of the first application that supports the second image input method.

[0125] In operation 550, an electronic device (100) according to one embodiment may obtain code of a framework for inputting an image using a second image input method.

[0126] For example, the framework can identify whether the application does not support an image handler according to a specified input method at the framework level, and code for connecting the specified input method to another input method may already be generated at the framework level. Accordingly, the electronic device (100) can select the code of the framework that has already been generated, and obtain the code of the framework for inputting an image using the second image input method so that the image input using the first image input method is contained in the selected code and transmitted.

[0127] For example, if the second image input method is a method of inputting an image by copy and paste, the electronic device (100) can obtain a code of a framework for copying and pasting an image. For example, the electronic device (100) can obtain a code for a graphic handler for copy and paste. For example, the electronic device (100) can obtain a code of a framework for overriding an image pasting operation for a portion of an image to be input within the execution screen of the first application.

[0128] For example, if the second image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the electronic device (100) may generate a code of a framework for inputting an image selected from a list of images displayed via the keyboard. For example, the electronic device (100) may generate a code for a keyboard handler for image input via the keyboard. For example, the electronic device (100) may generate a code of a framework for overriding InputConnection for inputting an image into a portion of an area where an image is to be input within the execution screen of the first application.

[0129] In operation 560, an electronic device (100) according to one embodiment may provide a code of a framework to a first application. Based on the code of the provided framework, the first application may display an image at a specific location within the execution screen of the first application through a second image input method.

[0130] Meanwhile, if it is determined in operation 530 that the first application supports an image input method through drag-and-drop user input, the electronic device (100) can input an image into the execution screen of the first application in operation 570.

[0131] Meanwhile, while the above description describes inputting an image into the application's execution screen based on user input, this is not limited thereto. For example, the electronic device (100) may input data files other than images into the application's execution screen. In this case, the image input method may be a data input method, and framework code for inputting the data may be generated.

[0132] In one embodiment, even if the application does not support user input for entering data by drag and drop, the data entry operation based on user input can be performed without modifying the application's code by modifying or generating the code of the framework for another data entry method, thereby improving the user experience.

[0133] FIG. 6 is a diagram illustrating an example of an image being input into an application when a user input of drag and drop is received according to one embodiment of the present disclosure.

[0134] Referring to identification number 3 of FIG. 6, an execution screen (60) of a first application and an execution screen (62) of a second application may be displayed on the screen of an electronic device (100). For example, the first application may be an application for sending messages, and the second application may be an application for Internet browsing.

[0135] The electronic device (100) can display the execution screen (60) of the first application and the execution screen (62) of the second application together through a multi-window.

[0136] The electronic device (100) can receive a user input for dragging and dropping an image (63) within the execution screen (62) of the second application to an input field (61) within the execution screen (60) of the first application. According to one embodiment, the electronic device (100) can identify in advance whether it supports the image input method of dragging and dropping before receiving the user input for dragging and dropping, but is not limited thereto.

[0137] Referring to the identification number 4 of FIG. 6, the electronic device (100) can obtain link information of the image (63) as the image (63) is dropped into the input field (61) within the execution screen (60) of the first application, and can identify the location on the screen of the input field (61) as a portion of the execution screen (60) of the first application that supports an image input method via a keyboard. The electronic device (100) can generate a code of a framework for image input using the image input method via a keyboard based on the link information of the image (63) and the input field (61). In addition, the electronic device (100) can provide the generated code to the first application, and the first application can cause the image (63) to be displayed within the input field (61) based on the received code. In this way, the present disclosure can improve the user experience by enabling image pasting by changing the intermediate operation of the framework without modifying the code of the application.

[0138] According to one embodiment, the image (63) displayed within the input field (61) may be displayed in a smaller size than the image (63) displayed within the execution screen (62) of the second application.

[0139] FIG. 7 is a flowchart of a method for an electronic device to input an image into an application based on a user input for pasting an image according to one embodiment of the present disclosure.

[0140] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.

[0141] According to one embodiment, operations 700 to 760 may be understood to be performed in a processor (e.g., processor (920) of FIG. 9) of an electronic device (e.g., electronic device (100) of FIG. 1 and / or electronic device (901) of FIG. 9).

[0142] In Fig. 7, the first image input method may be a method of inputting an image according to a user input of pasting an image.

[0143] In operation 700, the electronic device (100) according to one embodiment may receive a user input for pasting an image on an execution screen of an application. For example, when a user input for selecting a location to input an image (e.g., long touch, right click) within the execution screen of the application is received, the electronic device (100) may display a menu including an object for pasting. For example, even if the application does not support a function for pasting an image, it may support a function for pasting text, and in this case, based on a user input (e.g., long touch, right click) on the execution screen of the application, the electronic device (100) may display a menu including an object for pasting. In addition, the electronic device (100) may receive, for example, a user input for selecting an object for pasting, and display a list of images stored in the clipboard. In addition, the electronic device (100) may receive a user input for selecting an image from the clipboard. For example, the images stored in the clipboard may be images stored in the clipboard by at least one other application based on user input to at least one other application.

[0144] In operation 710, the electronic device (100) according to one embodiment can identify an image to be input and an input location based on a user input. The electronic device (100) can identify an image selected from a list of images stored in the clipboard. In addition, the input location of the image can be identified based on a user input selecting a location where the image is to be input within the execution screen of the application (e.g., long touch, right click).

[0145] In operation 720, the electronic device (100) according to one embodiment may determine whether the application supports an image input method via pasting of an image. For example, the electronic device (100) may determine whether the application including the image input location has a graphic handler for pasting.

[0146] If it is determined in operation 720 that the application does not support an image input method through pasting of an image, in operation 730, the electronic device (100) can identify some area within the execution screen of the application that supports the second image input method.

[0147] In operation 740, an electronic device (100) according to one embodiment may generate code for a framework for inputting an image using a second image input method.

[0148] For example, if the second image input method is a method of inputting an image by drag and drop, the electronic device (100) can generate code for a framework for dragging and dropping an image. For example, the electronic device (100) can generate code for a graphic handler for drag and drop. For example, the electronic device (100) can generate code for registering a DragListener for a certain area where an image is to be input within the execution screen of the application.

[0149] For example, if the second image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the electronic device (100) may generate a code of a framework for inputting an image selected from a list of images displayed via the keyboard. For example, the electronic device (100) may generate a code for a keyboard handler for image input via the keyboard. For example, the electronic device (100) may generate a code of a framework for overriding InputConnection for inputting an image into a portion of an area where an image is to be input within an execution screen of an application.

[0150] In operation 750, an electronic device (100) according to one embodiment may provide a framework code to an application. Based on the provided framework code, the application may display an image at a specific location within the application's execution screen through a second image input method.

[0151] Meanwhile, if it is determined in operation 720 that the application supports an image input method through pasting of an image, the electronic device (100) can input the image into the execution screen of the application in operation 760.

[0152] Meanwhile, while the above description describes inputting an image into the application's execution screen based on user input, this is not limited thereto. For example, the electronic device (100) may input data files other than images into the application's execution screen. In this case, the image input method may be a data input method, and framework code for inputting the data may be generated.

[0153] In one embodiment, even if the application does not support user input for entering data via copy and paste, the data entry operation based on the user input can be performed without modifying the application's code by modifying or generating the framework's code for another data entry method, thereby improving the user experience.

[0154] FIG. 8 is a diagram illustrating an example of an image being input into an application when a user input for pasting an image is received according to one embodiment of the present disclosure.

[0155] Referring to identification number 5 of FIG. 8, a list of images (80) stored in a clipboard may be displayed on the execution screen of the application, and the electronic device (100) may receive a user input for selecting an image (82) in the image list (80). The images in the list of images (80) stored in the clipboard may be images copied in advance by the user.

[0156] Referring to the identification number 6 of FIG. 8, an electronic device (100) according to one embodiment may obtain link information of an image (82) when an image (82) is selected in an image list (80) and identify a location where the image (82) is to be input on an execution screen of an application. Based on the link information of the image (82) and the location where the image (82) is to be input, the electronic device (100) may generate a code of a framework for image input by drag and drop. In addition, the electronic device (100) may provide the generated code to the application, and the application may cause the image (82) to be displayed on the execution screen of the application based on the received code.

[0157] Meanwhile, while the above description describes inputting an image into the application's execution screen based on user input, this is not limited thereto. For example, the electronic device (100) may input data files other than images into the application's execution screen. In this case, the image input method may be a data input method, and framework code for inputting the data may be generated.

[0158] According to one embodiment of the present disclosure, a method for an electronic device to input an image into an execution screen of an application may include: receiving at least one user input for inputting an image into the execution screen of the application (e.g., operation 200); identifying a first image input method corresponding to the at least one user input (e.g., operation 210); identifying the image and an input location of the image on the execution screen based on the at least one user input (e.g., operation 220); identifying whether the application supports the first image input method (e.g., operation 230); identifying a second image input method supported by the application when the application does not support the first image input method (e.g., operation 240); generating code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location (e.g., operation 250); and providing the generated code of the framework to the application (e.g., operation 260).

[0159] Additionally, according to one embodiment, as the generated code of the framework is provided to the application, the image can be input into the execution screen of the application by using the generated code of the framework by the application.

[0160] Additionally, according to one embodiment, the operation of identifying the second image input method supported by the application may identify whether a portion of the execution screen corresponding to the input location supports the second image input method.

[0161] Additionally, according to one embodiment, the two image input methods may be selected from among a plurality of image input methods supported by the application.

[0162] Additionally, according to one embodiment, when the first image input method is a method of inputting an image selected from a list of images displayed through a keyboard running for the application, the at least one user input may include a user input for selecting an input field of the application.

[0163] Additionally, according to one embodiment, in response to receiving user input selecting the input field, the application may identify whether it supports the first image input method.

[0164] In addition, according to one embodiment, the second image input method includes a method of inputting an image by drag and drop, and the operation of identifying the second image input method supported by the application can identify whether a portion of the execution screen corresponding to the input location supports a function of recognizing drag and drop.

[0165] Additionally, according to one embodiment, the second image input method supported by the application can be identified by identifying whether the function of recognizing the drag and drop is supported for a plurality of partial areas within the execution screen.

[0166] Additionally, according to one embodiment, the second image input method may include a method of inputting an image by copy and paste.

[0167] Additionally, according to one embodiment, the first image input method may include at least one of a method of inputting an image selected from a list of images displayed through a keyboard running on the application, a method of inputting an image by drag and drop, or a method of inputting an image by copy and paste.

[0168] In addition, according to one embodiment, the second image input method may be an input method different from the first image input method among a method of inputting an image selected from a list of images displayed through a keyboard running for the application, a method of inputting an image by drag & drop, or a method of inputting an image by copy & paste.

[0169] FIG. 9 is a block diagram of an electronic device (901) within a network environment (900) according to various embodiments. Referring to FIG. 9, in the network environment (900), the electronic device (901) may communicate with the electronic device (902) via a first network (998) (e.g., a short-range wireless communication network), or may communicate with the electronic device (904) or a server (908) via a second network (999) (e.g., a long-range wireless communication network). In one embodiment, the electronic device (901) may communicate with the electronic device (904) via the server (908). According to one embodiment, the electronic device (901) may include a processor (920), a memory (930), an input module (950), an audio output module (955), a display module (960), an audio module (970), a sensor module (976), an interface (977), a connection terminal (978), a haptic module (979), a camera module (980), a power management module (988), a battery (989), a communication module (990), a subscriber identification module (996), or an antenna module (997). In some embodiments, the electronic device (901) may omit at least one of these components (e.g., the connection terminal (978)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (976), the camera module (980), or the antenna module (997)) may be integrated into one component (e.g., the display module (960)).

[0170] The processor (920) may, for example, execute software (e.g., a program (940)) to control at least one other component (e.g., a hardware or software component) of the electronic device (901) connected to the processor (920) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (920) may store commands or data received from other components (e.g., a sensor module (976) or a communication module (990)) in a volatile memory (932), process the commands or data stored in the volatile memory (932), and store result data in a non-volatile memory (934). According to one embodiment, the processor (920) may include a main processor (921) (e.g., a central processing unit or an application processor) or an auxiliary processor (923) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (921). For example, when the electronic device (901) includes the main processor (921) and the auxiliary processor (923), the auxiliary processor (923) may be configured to use less power than the main processor (921) or to be specialized for a given function. The auxiliary processor (923) may be implemented separately from the main processor (921) or as a part thereof.

[0171] The auxiliary processor (923) may control at least a portion of functions or states associated with at least one component (e.g., a display module (960), a sensor module (976), or a communication module (990)) of the electronic device (901), for example, on behalf of the main processor (921) while the main processor (921) is in an inactive (e.g., sleep) state, or together with the main processor (921) while the main processor (921) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (923) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (980) or a communication module (990)). In one embodiment, the auxiliary processor (923) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (901) itself where the artificial intelligence is performed, or can be performed through a separate server (e.g., server (908)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0172] The memory (930) can store various data used by at least one component (e.g., the processor (920) or the sensor module (976)) of the electronic device (901). The data can include, for example, software (e.g., the program (940)) and input data or output data for commands related thereto. The memory (930) can include a volatile memory (932) or a non-volatile memory (934).

[0173] The program (940) may be stored as software in the memory (930) and may include, for example, an operating system (942), middleware (944), or an application (946).

[0174] The input module (950) can receive commands or data to be used in a component of the electronic device (901) (e.g., a processor (920)) from an external source (e.g., a user) of the electronic device (901). The input module (950) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0175] The audio output module (955) can output audio signals to the outside of the electronic device (901). The audio output module (955) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0176] The display module (960) can visually provide information to an external party (e.g., a user) of the electronic device (901). The display module (960) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. In one embodiment, the display module (960) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0177] The audio module (970) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (970) can acquire sound through the input module (950), output sound through the sound output module (955), or an external electronic device (e.g., electronic device (902)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (901).

[0178] The sensor module (976) can detect the operating status (e.g., power or temperature) of the electronic device (901) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (976) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0179] The interface (977) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (901) with an external electronic device (e.g., the electronic device (902)). In one embodiment, the interface (977) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0180] The connection terminal (978) may include a connector through which the electronic device (901) may be physically connected to an external electronic device (e.g., the electronic device (902)). In one embodiment, the connection terminal (978) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0181] The haptic module (979) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. According to one embodiment, the haptic module (979) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0182] The camera module (980) can capture still images and videos. According to one embodiment, the camera module (980) may include one or more lenses, image sensors, image signal processors, or flashes.

[0183] The power management module (988) can manage the power supplied to the electronic device (901). According to one embodiment, the power management module (988) can be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0184] A battery (989) may power at least one component of the electronic device (901). In one embodiment, the battery (989) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0185] The communication module (990) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (901) and an external electronic device (e.g., electronic device (902), electronic device (904), or server (908)), and the performance of communication through the established communication channel. The communication module (990) may operate independently from the processor (920) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (990) may include a wireless communication module (992) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (994) (e.g., a local area network (LAN) communication module, or a power line communication module). Any of these communication modules may communicate with an external electronic device (904) via a first network (998) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (999) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (992) may use subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (996) to verify or authenticate the electronic device (901) within a communication network such as the first network (998) or the second network (999).

[0186] The wireless communication module (992) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency communications (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (992) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (992) may support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (992) may support various requirements specified in the electronic device (901), an external electronic device (e.g., the electronic device (904)), or a network system (e.g., the second network (999)). According to one embodiment, the wireless communication module (992) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for URLLC realization.

[0187] The antenna module (997) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (997) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (997) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (998) or the second network (999), may be selected from the plurality of antennas, for example, by the communication module (990). A signal or power may be transmitted or received between the communication module (990) and the external electronic device via the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (997).

[0188] According to various embodiments, the antenna module (997) may form a mmWave antenna module. In one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band.

[0189] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0190] According to one embodiment, commands or data may be transmitted or received between the electronic device (901) and an external electronic device (904) via a server (908) connected to a second network (999). Each of the external electronic devices (902 or 904) may be the same or a different type of device as the electronic device (901). According to one embodiment, all or part of the operations executed in the electronic device (901) may be executed in one or more of the external electronic devices (902, 904, or 908). For example, when the electronic device (901) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (901) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (901). The electronic device (901) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (901) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (904) may include an Internet of Things (IoT) device. The server (908) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (904) or the server (908) may be included in the second network (999).The electronic device (901) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0191] According to one embodiment, the electronic device (901) of FIG. 9 may be the electronic device (100) of FIGS. 1 to 8, and the processor (920) of FIG. 9 may perform the operations of the electronic device (100) described in FIGS. 1 to 8.

[0192] According to one embodiment, the processor (920) may receive a user input for entering an image into the execution screen of the application. The user input for entering an image into the execution screen of the application may be a user input for inserting and displaying an image into the execution screen of the application. The processor (920) may receive one or more user inputs for entering an image into the execution screen of the application.

[0193] According to one embodiment, the processor (920) can identify a first image input method corresponding to the user input. The first image input method corresponding to the user input may include, for example, at least one of a method of inputting an image selected from a list of images displayed via a keyboard, a method of inputting an image by drag and drop, or a method of inputting an image by copy and paste.

[0194] For example, if the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the user input may include user input for selecting an input field of the application, user input for calling up the image list in a keyboard application that is activated according to selection of the input field, and user input for selecting an image from the image list.

[0195] For example, if the first image input method is a method of inputting an image by drag and drop, the user input may include a user input of selecting an image and dragging and dropping the selected image onto the application's execution screen.

[0196] For example, if the first image input method is a method of inputting an image by copying and pasting, the user input may include at least one of a user input of selecting a specific location on the application's execution screen (e.g., long touch), a user input of selecting a paste item from a menu displayed according to the selection of the specific location, a user input of selecting a clipboard item from a menu displayed according to the selection of the specific location, or a user input of selecting an image in the clipboard.

[0197] In one embodiment, the processor (920) can identify an image and an input location of the image. The processor (920) can identify an image selected by a user input and a portion of an area on the execution screen of an application where the selected image is to be displayed.

[0198] For example, if the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the processor (920) can identify the image selected from the image list of the keyboard application as an image to be input into the application. In addition, the processor (920) can identify an input field of the application, or a portion of the execution screen of the application where an input value via the input field is displayed, as an input location for the image.

[0199] For example, if the first image input method is a method of inputting an image by drag and drop, the processor (920) can identify the dragged and dropped image as an image to be input into the application. In addition, the processor (920) can identify a portion of the application's execution screen including the location where the image is dropped as the input location of the image.

[0200] For example, if the first image input method is a method of inputting an image by copying and pasting, the processor (920) can identify the copied image as an image to be input into the application. In addition, the processor (920) can identify the location where the image is to be pasted as the input location of the image.

[0201] In one embodiment, the processor (920) may determine whether the application supports the first image input method. For example, the application may support only some of the following methods: inputting an image selected from a list of images displayed via a keyboard, inputting an image by drag and drop, and inputting an image by copy and paste. Accordingly, the first image input method corresponding to the user input may not be included in the input methods supported by the application. For example, the processor (920) may determine whether the application has a keyboard handler, a graphical handler for drag and drop, and / or a graphical handler for copy and paste.

[0202] In one embodiment, if it is determined that the application does not support the first image input method, the processor (920) may identify a second image input method supported by the application.

[0203] For example, if the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, and the application does not support the first image input method, the processor (920) can identify that the application supports a method of inputting an image by drag & drop, and / or a method of inputting an image by copy & paste.

[0204] For example, if the first image input method is a method of inputting an image by drag and drop and the application does not support the first image input method, the processor (920) can identify that the application supports a method of inputting an image selected from a list of images displayed via a keyboard and / or a method of inputting an image by copy and paste.

[0205] For example, if the first image input method is a method of inputting an image by copy & paste and the application does not support the first image input method, the processor (920) can identify that the application supports a method of inputting an image selected from a list of images displayed via a keyboard and / or a method of inputting an image by drag & drop.

[0206] According to one embodiment, the processor (920) may obtain the code of a framework for inputting an image using the second image input method. The processor (920) may obtain the code of the framework for inputting an image using the second image input method based on link information of an image to be input on an execution screen of an application and an input location within the execution screen of the application where the image is to be input. The link information of the image may include, for example, uniform resource identifier (URI) information of the image.

[0207] For example, if the second image input method supported by the application and different from the first image input method is a method of inputting an image by drag and drop, the processor (920) can obtain the code of a framework for dragging and dropping an image. For example, the processor (920) can obtain the code for registering a DragListner for a certain area where an image is to be input within the execution screen of the application.

[0208] For example, the processor (920) can obtain code for a framework for dragging and dropping an image by editing at least a portion of the code of Table 1.

[0209] For example, if the second image input method supported by the application and different from the first image input method is a method of inputting an image by copying and pasting, the processor (920) may obtain the code of a framework for copying and pasting an image. For example, the processor (920) may obtain the code of a framework for overriding the image pasting operation for a certain area where an image is to be input within the execution screen of the application.

[0210] For example, the processor (920) can obtain code of a framework for copying and pasting an image by editing at least a portion of the code of Table 2.

[0211] For example, if a second image input method supported by an application and different from the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard, the processor (920) may obtain a code of a framework for inputting an image selected from a list of images displayed via the keyboard. For example, the processor (920) may obtain a code of a framework for overriding InputConnection to input an image into a portion of an area where an image is to be input within the execution screen of the application.

[0212] For example, the processor (920) can obtain code of a framework for inputting an image via a keyboard by editing at least a portion of the code of Table 3.

[0213] According to one embodiment, the processor (920) may provide the framework's code to the application. Based on the provided framework's code, the application may display an image at a specific location within the application's execution screen through the second image input method.

[0214] According to one embodiment, if it is determined that the application supports the first image input method, the processor (920) can input an image into the execution screen of the application according to the first image input method.

[0215] Meanwhile, while the above description describes inputting an image into the application's execution screen based on user input, this is not limited thereto. For example, the electronic device (100) may input data files other than images into the application's execution screen. In this case, the image input method may be a data input method, and the code of the framework for inputting the data may be obtained.

[0216] According to one embodiment of the present disclosure, an electronic device (e.g., 100) for inputting an image into an execution screen of an application includes a display (e.g., 960); a memory (e.g., 930) for storing commands; and at least one processor (e.g., 920) operatively connected to the display and the memory and configured to execute the commands, wherein the at least one processor, by executing the commands, receives at least one user input for inputting an image into the execution screen of the application, identifies a first image input method corresponding to the at least one user input, identifies the image and an input location of the image on the execution screen based on the at least one user input, identifies whether the application supports the first image input method, and, when the application does not support the first image input method, identifies a second image input method supported by the application, obtains code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location, and provides the obtained code of the framework to the application.

[0217] Additionally, according to one embodiment, as the acquired code of the framework is provided to the application, the image can be input into the execution screen of the application by using the acquired code of the framework by the application.

[0218] Additionally, according to one embodiment, the at least one processor can identify whether a portion of the execution screen corresponding to the input location supports the second image input method by executing the commands.

[0219] Additionally, according to one embodiment, the two image input methods may be selected from among a plurality of image input methods supported by the application.

[0220] Additionally, according to one embodiment, when the first image input method is a method of inputting an image selected from a list of images displayed through a keyboard running for the application, the at least one user input may include a user input for selecting an input field of the application.

[0221] Additionally, according to one embodiment, the at least one processor can, by executing the instructions, identify whether the application supports the first image input method in response to receiving a user input selecting the input field.

[0222] In addition, according to one embodiment, the second image input method includes a method of inputting an image by drag and drop, and the at least one processor can identify whether a portion of the execution screen corresponding to the input location supports a function of recognizing drag and drop by executing the commands.

[0223] Additionally, according to one embodiment, the second image input method supported by the application can be identified by identifying whether the function of recognizing the drag and drop is supported for a plurality of partial areas within the execution screen.

[0224] Additionally, according to one embodiment, the second image input method may include a method of inputting an image by copy and paste.

[0225] According to one embodiment of the present disclosure, a computer-readable recording medium having recorded thereon a program for executing a method for inputting an image into an execution screen of an application, the method comprising: receiving at least one user input for inputting an image into an execution screen of an application; identifying a first image input method corresponding to the at least one user input; identifying the image and an input location of the image on the execution screen based on the at least one user input; identifying whether the application supports the first image input method; identifying a second image input method supported by the application when the application does not support the first image input method; obtaining code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location; and providing the obtained code of the framework to the application.

[0226] Electronic devices according to the various embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments of this document are not limited to the aforementioned devices.

[0227] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order). When a component (e.g., a first) is referred to as "coupled" or "connected" to another component (e.g., a second) with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., by wire), wirelessly, or through a third component. The term "module" as used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integral component or a smallest unit or part of a component that performs one or more functions.For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0228] Various embodiments of the present document may be implemented as software (e.g., a program (940)) including one or more instructions stored in a storage medium (e.g., an internal memory (936) or an external memory (938)) readable by a machine (e.g., an electronic device (901)). For example, a processor (e.g., a processor (920)) of the machine (e.g., an electronic device (901)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0229] According to one embodiment, the method according to various embodiments disclosed in this document may be provided as a computer program product. The computer program product may be traded between sellers and buyers as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or may be provided through an application store (e.g., Play Store). TM) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server. According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separately arranged in other components. According to various embodiments, one or more components or operations of the above-described components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component of the plurality of components before the integration. According to various embodiments, the operations performed by a module, program or other component may be performed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be performed in a different order, omitted, or one or more other operations may be added.

Claims

1. A method for an electronic device to input an image into an application's execution screen, An operation (200) of receiving at least one user input for entering an image into the execution screen of the above application; An operation (210) of identifying a first image input method corresponding to at least one user input; An operation (220) for identifying the image and the input location of the image on the execution screen based on at least one user input; An operation (230) for identifying whether the above application supports the first image input method; An operation (240) of identifying a second image input method supported by the application, as the application does not support the first image input method; An operation (250) of obtaining a code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location; and An operation (260) of displaying the image on the execution screen of the application through the second image input method; A method comprising:

2. In paragraph 1, A method wherein the image is input into the execution screen of the application by using the acquired code of the framework as the acquired code of the framework is provided to the application.

3. In either of paragraphs 1 and 2, The action of identifying the second image input method supported by the above application is: A method for identifying whether a portion of the execution screen corresponding to the input location supports the second image input method.

4. In any one of paragraphs 1 to 3, A method wherein the above two image input methods are selected from among a plurality of image input methods supported by the application.

5. In any one of paragraphs 1 to 4, A method, wherein, when the first image input method is a method of inputting an image selected from a list of images displayed via a keyboard running for the application, the at least one user input includes a user input for selecting an input field of the application.

6. In paragraph 5, The operation of identifying whether the first image input method is supported is as follows: A method wherein, in response to receiving user input selecting said input field, the application identifies whether the application supports said first image input method.

7. In paragraph 6, The above second image input method includes a method of inputting an image by drag and drop, A method for identifying a second image input method supported by the application, wherein the operation comprises identifying whether a portion of the execution screen corresponding to the input location supports a function for recognizing drag and drop.

8. In paragraph 7, A method wherein the second image input method supported by the application is identified by identifying whether a function for recognizing the drag and drop is supported for a plurality of partial areas within the execution screen.

9. In paragraph 6, A method, wherein the second image input method includes a method of inputting an image by copy and paste.

10. In any one of paragraphs 1 to 9, The first image input method includes at least one of a method of inputting an image selected from a list of images displayed through a keyboard running on the application, a method of inputting an image by drag & drop, or a method of inputting an image by copy & paste. A method according to claim 1, wherein the second image input method is a different input method from the first image input method among a method of inputting an image selected from a list of images displayed through a keyboard running on the application, a method of inputting an image by drag & drop, or a method of inputting an image by copy & paste.

11. In an electronic device that inputs an image into the execution screen of an application, Display (960); Memory (930) for storing commands; and At least one processor (920) operatively connected to the display and the memory and executing the instructions; Including, The above at least one processor (920) executes the above instructions, Receiving at least one user input for entering an image into the execution screen of the above application, Identifying a first image input method corresponding to at least one of the user inputs, Identifying the image and the input location on the execution screen of the image based on at least one user input; Identify whether the above application supports the first image input method, Since the above application does not support the above first image input method, identify the second image input method supported by the above application, Based on the image and the input location, obtain a code of a framework for inputting the image into the execution screen of the application using the second image input method, An electronic device providing the obtained code of the above framework to the above application.

12. In paragraph 11, An electronic device, wherein the image is input into the execution screen of the application by using the acquired code of the framework as the acquired code of the framework is provided to the application.

13. In any one of paragraphs 11 and 12, The above at least one processor (920) executes the above instructions, An electronic device that identifies whether a portion of the execution screen corresponding to the input location supports the second image input method.

14. In any one of paragraphs 11 to 13, The above first image input method includes at least one of a method of inputting an image selected from a list of images displayed through a keyboard running in the application, a method of inputting an image by drag and drop, or a method of inputting an image by copy and paste. The second image input method is selected from among a plurality of image input methods supported by the application, An electronic device, wherein the second image input method is a different input method from the first image input method, and includes any one of a method of inputting an image selected from a list of images displayed through a keyboard running in the application, a method of inputting an image by drag and drop, or a method of inputting an image by copy and paste.

15. In any one of paragraphs 11 to 14, An electronic device, wherein, when the first image input method is a method of inputting an image selected from the image list displayed through the keyboard running for the application, the at least one user input includes a user input for selecting an input field of the application.

16. In paragraph 15, The above at least one processor (920) executes the above instructions, An electronic device, wherein in response to receiving user input selecting said input field, the application identifies whether the application supports said first image input method.

17. In any one of paragraphs 11 to 14, The above second image input method includes a method of inputting an image by drag and drop, An electronic device wherein the second image input method supported by the application is identified by identifying whether a plurality of partial areas within the execution screen support the function of recognizing the drag and drop.

18. An action for receiving at least one user input for entering an image into the execution screen of the application; An action for identifying a first image input method corresponding to at least one user input; An operation of identifying the image and the input location on the execution screen of the image based on at least one user input; An action to identify whether the above application supports the first image input method; An operation of identifying a second image input method supported by the application, as the application does not support the first image input method; An operation of obtaining a code of a framework for inputting the image into the execution screen of the application using the second image input method based on the image and the input location; and An action of providing the obtained code of the above framework to the above application; A computer-readable recording medium having recorded thereon a program for executing a method of inputting an image into an execution screen of an application, including:

Images