Program, information processing device, and label data sharing system

Abstract

To provide a program, an information processing device, and a label data sharing system by which posting of label data is facilitated in a system for utilizing label data.SOLUTION: In a label data sharing system 100, a client application 13, which is a program, enables a CPU 121 of a terminal 12 to edit label data that can be printed by a label printer 11, and store or print the edited label data. When the CPU 121 performs at least one of storing and printing of the label data, the client application 13 causes the CPU to propose posting of the label data stored or printed. The client application 13 causes the CPU 121 to upload the to-be-posted label data to a server 22, thereby posting the label data to be registered on the server 22.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The technical field disclosed in this specification relates to a program, an information processing device, and a label data sharing system used in a system that utilizes label data. [Background technology]

[0002] Conventionally, a system for utilizing content data is known in which a server for storing content data is provided on the Internet, content data is posted from a user's device, i.e., uploaded to the server, and the content data is then downloaded to another user's device.

[0003] An example of a document disclosing the above-mentioned system is Patent Document 1. In the point management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and purchased by User B's PC and downloaded from the WWW server, points are added to User B, the purchaser, according to the purchase amount, and further points are added to User A, the contributor, according to the data size of the photo data when the photo data is uploaded or downloaded. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-99746 A Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, a system has been considered in which a user who creates label data used to print labels with a label printer can upload the label data to a server, and another user can download the label data from the server and use it. In such a system, it is desirable to have many users post label data. Patent Document 1 describes having users select photo data to post, but does not describe any measures to encourage users to post content such as photo data, so there is room for improvement. [Means for solving the problem]

[0006] A program made to solve the above-mentioned problems is a program executable by a computer of an information processing device, and is capable of causing the computer to execute an editing process to edit label data, the label data being data that can be printed by a label printer, and is capable of causing the computer to further execute a saving process to save the label data edited in the editing process, and a printing process to cause the label printer to print the label data edited in the editing process or the label data saved in the saving process, and is further capable of causing the computer to execute a suggestion process to suggest posting of the label data to be saved or printed, when at least one of saving of the label data by the saving process and printing based on the label data by the printing process has been performed, and is further capable of causing the computer to execute a posting process to post the label data, and in the posting process, the label data to be posted is uploaded to a server, and the uploaded label data is registered on the server.

[0007] According to the program disclosed in this specification, when label data is saved or printed, the information processing device suggests posting the label data that was to be saved or printed. When label data is saved or printed, there is a high possibility that editing of the label data has been completed. In response to saving or printing of label data, the information processing device suggests posting the label data that was the subject of processing, so that posting of the label data can be expected.

[0008] An information processing device in which the program is incorporated, a system including the information processing device, a control method for realizing the functions of the program, and a computer-readable storage medium storing the program are also novel and useful. Effect of the Invention

[0009] According to the technology disclosed in this specification, a technology is realized that promotes the posting of label data in a system that aims to utilize label data. [Brief description of the drawings]

[0010] [Figure 1] 1 is a schematic configuration diagram of a system according to an embodiment. [Diagram 2] FIG. 11 is a sequence diagram showing a procedure for suggesting posting of label data. [Diagram 3] FIG. 13 is an explanatory diagram showing an example of an editing screen. [Figure 4] 13 is a flowchart showing a procedure for automatic editing processing. [Diagram 5] FIG. 11 is an explanatory diagram showing an example of automatic editing of label data. [Figure 6] FIG. 11 is a sequence diagram showing a posting procedure. [Figure 7] FIG. 11 is an explanatory diagram showing an example of a posting screen. [Figure 8] FIG. 11 is a sequence diagram showing a download procedure. [Figure 9] FIG. 11 is a sequence diagram showing an instruction receiving procedure. [Figure 10] FIG. 11 is an explanatory diagram showing an example of a selection screen. [Figure 11] FIG. 11 is a sequence diagram showing a server editing procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, a detailed description will be given of an embodiment of a label data sharing system with reference to the accompanying drawings. This specification discloses a label data sharing system that connects a server and a plurality of information processing devices via a network to share label data used for printing labels with a label printer.

[0012] As shown in Fig. 1, a label data sharing system 100 (hereinafter referred to as "system 100") according to this embodiment is a system provided to a user by, for example, a vendor of a label printer 11. The system 100 includes a plurality of terminals 12 and a server 22, which are connected via an internet line 21. Each terminal 12 is connectable to at least one label printer 11. The internet line 21 is an example of a network.

[0013] The terminal 12 is a device having a communication function, a display function, and an operation receiving function. As shown in FIG. 1, the terminal 12 has a controller 120 including a CPU 121 and a memory 122. The terminal 12 is an example of an information processing device. The CPU 121 is an example of a computer. The terminal 12 also has a user interface (hereinafter, referred to as a "user IF") 123 and a communication interface (hereinafter, referred to as a "communication IF") 124, which are electrically connected to the controller 120. Note that the controller 120 in FIG. 1 is a general term for hardware and software used to control the terminal 12, and does not necessarily represent a single piece of hardware actually present in the terminal 12. The terminal 12 may be a mobile terminal such as a smartphone or a tablet computer, or may be a personal computer.

[0014] The user IF 123 includes hardware for displaying a screen for notifying the user of information and hardware for accepting operations by the user. The user IF 123 may be a combination of a display capable of displaying information and a mouse, keyboard, or the like having an operation acceptance function, or may be a touch panel having a display function and an operation acceptance function.

[0015] The communication IF 124 includes hardware for communicating with external devices such as the label printer 11 and the server 22. The communication standards of the communication IF 124 are Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The terminal 12 may be equipped with multiple communication IFs 124 compatible with multiple communication standards.

[0016] A client application program (hereinafter referred to as a "client application") 13 is installed in the memory 122 of each terminal 12. The client application 13 is an example of a program. Each terminal 12 is also capable of storing label data 14. The label data 14 is data that can be printed by the label printer 11, and is data that is created using the client application 13.

[0017] The client application 13 is an application program provided by the vendor of the label printer 11. The client application 13 has various functions, such as an editing function that causes the terminal 12 to create and edit label data 14 based on instructions from a user, a storage function that causes the created label data 14 to be stored in the memory 122 of the terminal 12, and a printing function that transmits the created label data 14 to the label printer 11 to print it.

[0018] The label printer 11 is, for example, a printing device that includes a thermal transfer print head and prints on a roll of label paper while unwinding it. For example, the label printer 11 prints images on the stored label paper and transports the label paper based on label data received from the terminal 12, and can cause the printed portion to protrude outside the machine. The label printer 11 can communicate with the terminal 12 via wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The label printer 11 may also be able to communicate with the terminal 12 via wired communication based on the USB standard.

[0019] The server 22 is a device having at least a storage function and a communication function. A server program 23 is built into the server 22. The server 22 can also access a user database (hereinafter referred to as "user DB") 24 and a label database (hereinafter referred to as "label DB") 25. The user DB 24 is a database that stores user information indicating users of the system 100. The label DB 25 is a database in which label data can be registered.

[0020] By using the system 100, a user of the terminal 12 can share the label data 14 created using the client application 13 with other users. The server program 23 can receive, via the client application 13, an instruction to upload the label data 14 created on the terminal 12 to the server 22, and an instruction to download label data registered in the label DB 25 to the terminal 12. Note that in this specification, uploading to the server 22 is sometimes referred to as "posting."

[0021] Next, a procedure for proposing posting of label data 14 on terminal 12 included in system 100 will be described with reference to the sequence diagram in Fig. 2. Note that the procedures and processing steps of each program described below basically indicate processing by CPU 121 of terminal 12 or the CPU of server 22 according to instructions written in each program. Processing by each CPU also includes hardware control using the API of the OS. In this specification, the operation of each program will be described without describing the OS.

[0022] In the system 100 of this embodiment, a user first starts the client application 13 on the terminal 12 (A01). After starting up, the client application 13 can display, for example, an editing screen for editing label data on the user IF 123 of the terminal 12 based on a user operation (A02). The user can edit the label data on the displayed editing screen (A03).

[0023] For example, as shown in Fig. 3(A), the editing screen 30 includes a label image display area 31 that displays an image of a label based on the label data being edited. The client application 13 can also accept editing operations for the label data displayed in the label image display area 31 of the editing screen 30. Editing operations include, for example, pasting an object, inserting data to be printed into an object, and changing the position and size of an object. The editing screen 30 includes a print button 32 that accepts a print instruction based on the displayed label data, and a save button 33 that accepts an instruction to save the displayed label data.

[0024] When editing of the label data is finished, the user operates, for example, the print button 32 or the save button 33 in Fig. 3(A) to instruct printing or saving of the completed label data (A05). The client application 13 performs processing for printing or saving based on the user's instruction (A06). For example, when the client application 13 receives a print instruction in A05, the client application 13 transmits the displayed label data to the label printer 11 as a print target in A06, and causes the label printer 11 to print based on the label data. The processing in A06 when a print instruction is received in A05 is an example of printing processing.

[0025] Furthermore, when a save instruction is accepted at A05, the client application 13 performs processing for saving the label data being displayed as the data to be saved. For example, as shown in Fig. 3(B), the client application 13 places the edit screen 30 in a state in which operations cannot be accepted and displays a save dialog 40 on the user IF 123. The save dialog 40 includes an input field 41 for accepting input of a file name to be saved, a save confirmation button 42 for accepting a save instruction, and a cancel button 43 for accepting cancellation of the save instruction. The client application 13 waits until either the save confirmation button 42 or the cancel button 43 is operated.

[0026] When the save confirmation button 42 is operated in the save dialog 40, the client application 13 saves the label data that was displayed on the edit screen 30 when the save instruction was accepted in the memory 122. The process of A06 in this case is an example of a save process. Note that when the cancel button 43 is operated, the client application 13 ends the display of the save dialog 40 and returns to the edit screen 30.

[0027] When the process of printing or saving the label data is completed, the client application 13 causes a posting suggestion dialog suggesting posting to be displayed on the user IF 123 of the terminal 12 (A08). A08 is an example of the suggestion process. The posting suggestion dialog displayed after saving the label data includes, for example, a message indicating that saving has been completed and a button for accepting a user selection, as shown in FIG. 3(C). The posting suggestion dialog displayed after accepting a print instruction may include, for example, a message indicating that print data has been sent to the label printer 11.

[0028] In A08, the client application 13 displays a posting suggestion dialog 50 for accepting a selection of whether or not to post on the user IF 123, as shown in Fig. 3(C), for example. The posting suggestion dialog 50 includes, as buttons for accepting a user's selection, for example, a "Post as is" button 51, an "Automatically edit and post" button 52, and a "Don't post" button 53. The client application 13 waits until any of the buttons 51, 52, and 53 is operated.

[0029] The user selects whether or not to post by operating one of the buttons 51, 52, or 53 included in the posting suggestion dialog 50 (A09). The "Post as is" button 51 is a button that accepts an instruction to post the label data that was to be printed or saved as is, without making any changes. The "Auto-edit and post" button 52 is a button that accepts an instruction to automatically change the contents of the label data that was to be printed or saved to specified contents, and post the changed label data. The "Do not post" button 53 is a button that accepts an instruction not to post the label data.

[0030] First, automatic editing will be described. When an instruction to automatically edit and post, that is, an operation on the button 52 is received (alt: [Edit and post]), the client application 13 executes automatic editing processing (A11). The operation on the button 52 is an example of an instruction to change the content of a specific object included in the proposed label data to predetermined content and post it. Note that the proposed label data is the label data that was the target of printing or saving in A06.

[0031] The automatic editing process is a process of extracting text objects and image objects contained in the proposed label data and changing the contents of the extracted objects to dummy characters and images. The procedure of the automatic editing process will be described with reference to the flowchart in Fig. 4. The automatic editing process is executed by the CPU 121 of the terminal 12 based on the description of the client application 13.

[0032] First, the CPU 121 determines whether the proposed label data includes a text object (B01). A text object is an example of a specific object to be changed. A text object is an object whose contents can be edited by receiving a user's operation on an editing screen for editing label data such as that shown in FIG. 3(A). In other words, the text indicated by the text object is text entered or edited by the user, and may include personal information of the user, such as the user's name and contact information.

[0033] When it is determined that the label data includes a text object (B01: YES), the CPU 121 acquires information about the text shown in the text object, such as the font type, character size, and number of characters (B02). Information about the font type, character size, and number of characters is included in the text object as supplementary information.

[0034] Furthermore, the CPU 121 acquires the language type of the text shown in the text object (B03). The CPU 121 can acquire the language type being used, for example, by inquiring of the OS of the terminal 12. Furthermore, if the client application 13 is capable of accepting the setting of the language to be used, the CPU 121 acquires the language type set in the client application 13. The CPU 121 may acquire the language type based on the font type acquired in B02.

[0035] Based on the information acquired in B02 and B03, the CPU 121 creates dummy text (B04) and changes the text object of the label data to a text object including the dummy text (B05). B05 is an example of a change process. The dummy text is an example of predetermined text. Specifically, the CPU 121 changes the text shown in the text object of the label data to dummy text with predetermined content. By changing the text shown in the text object to text with the predetermined content, label data for posting that does not include personal information is created.

[0036] The client application 13 may have in advance, for example, one or more sample character strings as character strings of predetermined contents for dummy text to be used in each language. The CPU 121 creates, as dummy text, a character string of the number of characters acquired in B02, using characters of the language type acquired in B03, the font type acquired in B02, and the character size. By arranging the same number of characters of the same font type and size as the text included in the text object, the change in the impression of the label before and after the change can be reduced.

[0037] For example, if the number of characters in a text object is greater than the number of characters in a prepared sample string, CPU 121 may repeat the sample string until the number of characters in the text object is reached. Also, for example, if the number of characters in a text object is less than the number of characters in a sample string, CPU 121 may treat a portion of the sample string up to the same number of characters as the number of characters in the text object as dummy text.

[0038] The sample character string used for the dummy text may be any character string that does not include personal information of the user, and may be, for example, a character string that indicates that it is a dummy, such as "sample" or "test," or it may be a repetition of the same characters, or it may be a character string that is widely used in that language for checking printing, etc. The sample character string may be a character string made up of characters randomly selected by the CPU 121, or it may be a character string that is not dependent on the user, such as the name of the vendor of the label printer 11.

[0039] When the label data includes multiple text objects, the CPU 121 executes B02 to B05 for all the text objects. For example, text 71 in italic Roman characters in the label data 70 shown in Fig. 5(A) is changed to dummy text 81 in italic Roman characters of the same font type as shown in Fig. 5(B). Also, for example, text 72 in bold Japanese characters in the label data 70 shown in Fig. 5(A) is changed to dummy text 82 in bold Japanese characters of the same font type as shown in Fig. 5(B). The client application 13 may have, for example, "sample" for Japanese characters and "sample" for Roman characters as sample character strings when the language is Japanese.

[0040] Furthermore, the client application 13 may determine whether the text included in the text object is a common noun. If it is determined that the text is a common noun, the client application 13 may not change the text to dummy text. If the text includes a symbol, the CPU 121 may not change the symbol. The client application 13 may prepare, for example, a plurality of sample character strings each associated with a category, and create dummy text using a character string in the same category as the category of the text shown in the text object.

[0041] After B05, or when it is determined that the proposed label data does not include a text object (B01: NO), the CPU 121 determines whether the label data includes an image object (B11). An image object is an example of a specific object to be changed. An image object is an object whose contents can be edited by receiving a user's operation on an editing screen for editing label data such as that shown in FIG. 3(A). In other words, an image included in an image object is an image selected by a user, and may include personal information of the user, such as a face photo of the user or a family member.

[0042] If it is determined that the label data includes an image object (B11: YES), the CPU 121 acquires the vertical and horizontal sizes of the image object (B12). Furthermore, the CPU 121 creates a dummy image showing a predetermined content according to the size acquired in B12 (B13), and changes the image object to the dummy image (B14). B14 is an example of a change process. The dummy image is an example of a predetermined image.

[0043] The client application 13 may have, for example, a sample image showing predetermined content for creating a dummy image. The predetermined content shown by the sample image may be any content that does not include personal information of the user, and may be, for example, a plain, single color, may include a meaningless pattern, or may include an image that is not of the user, such as the logo of the vendor of the label printer 11. The CPU 121 creates a dummy image, for example, by adjusting a sample image prepared in advance to the size of an image object of the label data.

[0044] For example, the client application 13 may have sample images of multiple sizes and select the sample image with the closest size as the dummy image. Also, when the sample image is larger than the image of the image object of the label data, the client application 13 may trim the sample image to create the dummy image. Also, the client application 13 may enlarge or reduce the sample image to create a dummy image of the same size as the image object of the label data.

[0045] For example, an image object 77 including a photo image in label data 70 shown in FIG. 5(A) is changed to an image object 87 that is a dummy image, as shown in FIG. 5(B). By changing the image of the image object to a dummy image, it is possible to create label data for posting that does not include personal information. In addition, by changing to a dummy image that matches the size of the original image object, it is possible to reduce the change in the impression of the label before and after the change. Note that if the label data includes multiple image objects, the CPU 121 executes B12 to B14 for all image objects.

[0046] The client application 13 may also prepare a plurality of sample images, each associated with a category, and create a dummy image by selecting a sample image in the same category as the category of the image of the label data. The client application 13 may also prepare color and monochrome sample images, and create a dummy image by using a sample image selected to match the color of the image of the label data. The client application 13 may also create a dummy image by filling the image of the image object with one or more colors included in the image object of the label data. The client application 13 may also create a dummy image by performing a blurring process on the image of the image object.

[0047] The CPU 121 may also change objects other than text objects and image objects. For example, when the proposed label data includes paid content, the CPU 121 may replace the content with free content.

[0048] On the other hand, the CPU 121 may not change objects other than text objects and image objects. For example, the CPU 121 may not change the clip art 73, the date / time object 74, the frame object 75, and the graphic object 76 in the label data 70 shown in Fig. 5(A). In this case, as shown in Fig. 5(B), the label data 80 after editing by the automatic editing process includes the same objects as before editing, such as the clip art 83, the date / time object 84, the frame object 85, and the graphic object 86.

[0049] After B14, or when it is determined that the label data of the proposal target does not include an image object (B11: NO), the CPU 121 ends the automatic editing process, and returns to the posting suggestion procedure of FIG.

[0050] Returning to the description of the posting suggestion procedure in Fig. 2. After the automatic editing process in A11, the client application 13 starts a posting procedure for posting continuously (A12) without requiring an operation by the user to start posting. The posting procedure will be described with reference to the sequence diagram in Fig. 6.

[0051] In the posting procedure, the client application 13 accepts a user's login (C01). The client application 13 displays a login screen for accepting input of login information including a user ID on the user IF 123, and accepts the user's input. The client application 13 then transmits the accepted login information to the server program 23 and requests login authentication (C02). The server program 23 performs login authentication based on the user information stored in the user DB 24. Note that if the user has already logged in before this posting procedure, the client application 13 skips steps C01 and C02.

[0052] If the login is successful, the client application 13 adds label data to be posted and transmits an instruction to start posting to the server 22 (C11). That is, in C11, the client application 13 uploads the label data to be posted to the server 22. C11 is an example of a posting process.

[0053] In the posting procedure executed at A12 in FIG. 2, the label data to be posted is label data that has been edited by the automatic editing process (for example, label data 80 in FIG. 5(B)). That is, at C11, the client application 13 automatically selects the label data that has been edited by the automatic editing process and uploads it to the server 22. In this case, the label data to be posted is likely to be different from the label data that was printed or saved at A05 in FIG. 2. Because it has been edited by the automatic editing process, there is a low possibility that personal information will be included in the label data to be uploaded, thereby preventing information leakage.

[0054] When the server program 23 of the server 22 receives an instruction to start posting from the client application 13, it generates screen data for a posting screen that is a screen for accepting the posting instruction (C12) and transmits the generated screen data to the client application 13 (C13). The screen data generated in C12 includes an image or thumbnail image of the label data to be posted, that is, an image based on the label data transmitted from the client application 13 in C11.

[0055] The client application 13 displays a posting screen on the user IF 123 based on the screen data transmitted from the server 22 (C15). For example, as shown in FIG. 7(A), a preview of an image of the label data to be posted is displayed as a label image 61 on the posting screen 60. An image of the label data after the automatic editing process (FIG. 4) is displayed on the posting screen 60 after the automatic editing process is executed. C15 in this case is an example of a preview process. The client application 13 may itself have a browser function, or may start a browser to display the screen.

[0056] Furthermore, the server program 23 accepts input of various information on the posting screen 60. The user inputs necessary information into input fields on the posting screen 60, such as title, description, and category (C21). On the posting screen 60, various input fields are displayed as shown in FIG. 7(B) by accepting a scroll operation by the user. When the client application 13 accepts an operation on the posting screen 60, it transmits information indicating the accepted operation to the server 22 (C22). Note that the server program 23 does not accept input to the label image 61 on the posting screen 60. In other words, the user cannot edit the label data on the posting screen 60.

[0057] The server program 23 displays the contents on the posting screen 60 based on the input information transmitted from the client application 13. The posting screen 60 includes a posting instruction button 62, for example, as shown in Fig. 7(B). The posting instruction button 62 is a button that accepts the selection of posting. Note that the posting instruction button 62 may be a button that becomes active after the input of necessary items is accepted.

[0058] The posting screen 60 is also a screen that accepts the user's selection as to whether or not to post. The user can check the automatically edited label data to be actually posted by the label image 61 included in the posting screen 60, and therefore can avoid posting unintentionally. If the user wishes to cancel the posting after checking the label image 61, the user closes the posting screen 60 without operating the posting instruction button 62. Alternatively, the posting screen 60 may include a button that accepts the selection to cancel the posting.

[0059] When the user operates the posting instruction button 62 (C23), the client application 13 transmits information indicating that the posting instruction button 62 has been operated to the server 22 (C24). When the server program 23 receives the information indicating that the posting instruction button 62 has been operated, it registers the label data being displayed on the posting screen 60 in the label DB 25 (C25). C24 and C25 are processes for registering the label data in the label DB 25, and are an example of a posting process.

[0060] The server program 23 stores the label ID for identifying the label data, the user ID indicating the poster, and various input information input on the posting screen 60 in association with the label data in the label DB 25. The user ID indicating the poster is, for example, the user ID of the user who inputs the login information in C01. The server program 23 may notify the client application 13 of the completion of registration.

[0061] Even if the label data is registered in the label DB 25 based on a user operation, the label data changed by the automatic editing process is not saved in the memory 122 of the terminal 12. For example, the client application 13 may delete the changed label data from the memory 122 of the terminal 12 after transmitting an instruction to start posting in C11 to the server 22. The client application 13 may delete the changed label data from the memory 122 of the terminal 12 after the posting instruction button 62 is operated in C23, or after the posting screen 60 is closed without the posting instruction button 62 being operated.

[0062] Label data in which the contents of a text object or an image object have been changed by the automatic editing process is label data changed for posting, and is not label data used by the poster. For example, if the changed label data is saved by overwriting the original label data, editing work may be required to restore the original label data. Since the client application 13 does not save the changed label data, the inconvenience to the poster can be avoided.

[0063] Returning to the explanation of the posting suggestion procedure in Fig. 2. After the posting procedure (Fig. 6) executed at A12, the client application 13 terminates the connection with the server 22 and displays the home screen of the client application 13 on the user IF 123 (A13). The home screen is, for example, a screen that is displayed when the client application 13 is started up, and is a screen that accepts the selection of a function to be executed by the client application 13. The client application 13 may display an editing screen.

[0064] The client application 13 may maintain a connection to the server 22 even after the posting procedure is completed. The server 22 may then display a top screen of the server program 23 on the terminal 12. The server program 23 can receive label data from the terminal 12 and register it in the label DB 25, and can also transmit the label data registered in the label DB 25 to the terminal 12.

[0065] Next, a download procedure, which is a procedure for transmitting label data registered in the label DB 25 to the terminal 12, will be described with reference to the sequence diagram of FIG. 8. This procedure can be executed, for example, after the execution of the client application 13 is started on the terminal 12, an instruction to connect to the server 22 and use the server program 23 is received, and the connection with the server 22 is completed. When the server program 23 receives a connection instruction from the client application 13, it transmits screen data showing a top screen, for example, to the terminal 12. The user can transmit an instruction to start the download procedure to the server 22 via the top screen of the server program 23 displayed on the terminal 12. It should be noted that the download procedure can also be executed consecutively after the execution of the above-mentioned posting procedure.

[0066] When the server program 23 receives a download start instruction from a user (D01), it transmits screen data of a label selection screen that receives the selection of label data to be downloaded to the terminal 12 (D02). If the user has not yet logged in, the server 22 may request that the user log in.

[0067] The client application 13 displays a label selection screen on the user IF 123 based on the screen data sent from the server 22 (D03). The label selection screen is a screen that includes, for example, images of multiple downloadable label data and accepts user selection. When the client application 13 accepts a user operation on the displayed label selection screen (D11), it sends information about the accepted operation to the server program 23 (D12).

[0068] On the label selection screen, for example, label data registered in the label DB 25 by the above-mentioned posting procedure (FIG. 6) is displayed in a selectable manner. The terminal 12 that transmits the label data to the server 22 by the posting procedure (FIG. 6) is an example of a first information processing device. On the other hand, the terminal 12 that selects and downloads the label data registered in the label DB 25 is an example of a second information processing device.

[0069] The user selects the label data to be downloaded and inputs a download instruction (D15). The download instruction is an instruction to download the selected label data to the terminal 12. The server program 23 reads the label data selected by the user's operation from the label DB 25 (D16) and transmits the read label data to the terminal 12 (D17). The client application 13 saves the label data received from the server 22 in the memory 122 (D18).

[0070] As a result, the user who issued the download instruction can read out the label data stored in the memory 122 using the client application 13 and use it. In other words, the system 100 allows label data to be shared among multiple terminals 12. For example, if the label data selected to be downloaded is automatically edited on the posting terminal and the modified and posted label data, the contents of the text objects and image objects are changed to dummy data. Therefore, it is unlikely that the personal information of the posting user is included. Furthermore, the user who downloaded the label data can easily use the downloaded label data by editing the dummy data to make it more suitable for himself or herself.

[0071] Returning to the explanation of the posting suggestion procedure in Fig. 2, when an operation on the button 51 is received in the posting suggestion dialog 50 shown in Fig. 3(C) (alt: [Post as is]), the client application 13 executes the posting procedure (A21) without performing automatic editing processing. The posting procedure of A21 is the same as the posting procedure of A12 shown in Fig. 6. The operation on the button 51 is an example of an instruction to post the content of a specific object included in the proposed label data without changing it to a specified content.

[0072] In the posting procedure of A21, the client application 13 transmits the label data to be printed or saved (for example, the label data 70 in FIG. 5(A)) to the server program 23. In this case, the label data to be posted is the original label data that has not been automatically edited. For example, even if the label data includes personal information such as a store name, a user who wants to share the data with other users as is can automatically move to the posting screen by simply operating the button 51, so that the degree of freedom in posting is high. After the posting procedure of A21, the client application 13 displays, for example, the same home screen as when the application was started (A22). The client application 13 may display an edit screen, or may maintain a connection to the server 22 and display the top screen of the server program 23.

[0073] 3C, when an operation on the button 53 is received (alt: [Don't post]), the client application 13 does not perform the posting procedure and closes the posting suggestion dialog 50. As a result, the editing screen 30 is displayed again on the user IF 123 (A31).

[0074] The posting suggestion dialog 50 may further include a button for accepting an instruction to manually edit and post. When an operation on the button is accepted, the client application 13 may store that the posting target is to be edited and display an editing screen. By accepting manual editing of the suggested label data, the user can, for example, rewrite only the parts of the text object included in the label data that the user does not want to make public and input an instruction to post the data.

[0075] When an instruction to manually edit and post is received, and an instruction to complete editing is received, the client application 13 may automatically execute the posting procedure with the edited label data as the posting target. Also, the button 53 for accepting an instruction not to post may be a button for accepting an instruction to manually edit and post. By accepting editing of the suggested label data by an instruction not to post, it becomes easier for the user to post the label data.

[0076] The client application 13 can accept various instructions other than the instruction to edit the label data. For example, the client application 13 accepts a user operation on a home screen displayed on the user IF 123 of the terminal 12 at A13 or A22 in Fig. 2. The procedure when various instruction inputs by the user operation are accepted will be described with reference to the sequence diagram in Fig. 9.

[0077] The client application 13 displays a home screen (E01) and accepts a user instruction (E02). If the accepted instruction is an instruction to post label data (alt:[post instruction]), the client application 13 displays, on the user IF 123, a selection screen for accepting selection of label data to be posted (E11). For example, as shown in Fig. 10, a selection screen 90 includes a post button 91 and images 92, 93, and 94 of each label data stored in the memory 122, and is a screen for accepting user operations.

[0078] The user selects the label data to be posted by operating one of images 92, 93, or 94 on the displayed selection screen 90 (E12), and instructs posting by operating the post button 91 (E13). This causes the posting procedure described above (FIG. 6) to be executed (E14), and the label data selected by the user is uploaded to the server 22.

[0079] In this case, the user must determine the label data to be posted by operating the selection screen 90. On the other hand, as described above, if the selection of posting is accepted at the time of suggestion by the posting suggestion dialog 50 and the posting procedure is executed, the label data to be posted is determined to be the label data for which an instruction to print or save has been accepted on the editing screen. Since the label data to be posted has been determined, the client application 13 starts executing the posting procedure without displaying the selection screen 90. This eliminates the user's need to take the trouble of selecting label data, making it easy for the user to post the label data.

[0080] Furthermore, the client application 13 may be able to accept designation of dummy data that can be used in the automatic editing process. That is, the client application 13 may be able to use the sample character string or sample image accepted as dummy data to create dummy text in B04 or a dummy image in B13 in the above-mentioned automatic editing process (FIG. 4). If the user's instruction accepted on the home screen displayed in E01 is an instruction to specify dummy data (alt:[dummy specification instruction]), the client application 13 accepts the designation of dummy data.

[0081] Specifically, the client application 13 accepts input of a sample character string (E21) and specification of a sample image (E22), and stores the accepted data as dummy data in the memory 122 (E23). E23 is an example of a storage process. If the dummy data is stored in the memory 122, the client application 13 reads out the dummy data and creates dummy text and a dummy image in B04 or B13 of the automatic editing process (FIG. 4). The client application 13 may be able to accept registration of dummy data for each type of object or each category of label data. Also, only one of E21 and E22 may be performed.

[0082] When dummy data is stored in the memory 122, the client application 13 uses the dummy data in the automatic editing process, so that the contents of the text object and the image object are automatically changed to the dummy data specified by the user. For example, if a promotional logo is registered as a sample image, the user's face photo is automatically changed to the logo, so that label data with promotional information added and personal information removed can be easily posted.

[0083] Although the procedure in which the client application 13 executes the automatic editing process has been described above, the server program 23 of the server 22 may execute the automatic editing process instead of the client application 13. In this case, the procedure when the operation on the "Automatically edit and post" button 52 is accepted in the displayed posting suggestion dialog 50 (A08, FIG. 3(C)) is different from the posting suggestion procedure shown in FIG. 2. The other procedures are the same as the posting suggestion procedure shown in FIG. 2.

[0084] When the server program 23 executes the automatic editing process, upon receiving an operation on the button 52 (alt: [edit and post]), the client application 13 first connects to the server 22, as shown in the sequence diagram of Fig. 11. Note that in the procedure of the sequence diagram of Fig. 11, the procedure up to displaying the posting screen differs from the posting procedure of Fig. 6. The same steps as the posting procedure of Fig. 6 are denoted by the same reference numerals and will not be described.

[0085] In this case, the client application 13 does not execute the automatic editing process, but sends an instruction to start posting to the server 22, regarding the label data that was targeted for printing or saving on the editing screen 30 (FIG. 3(A)) as the label data to be posted (C11). Then, the client application 13 sends a change command, which is information indicating that automatic editing has been instructed, to the server 22 in association with the instruction to start posting sent in C11 (F01). Note that the client application 13 may send the change command together with the instruction to start posting in C11.

[0086] When the server program 23 receives a change command associated with an instruction to start posting, it executes the automatic editing process shown in Fig. 4 on the label data associated with the change command (F02). That is, the server program 23 changes the contents of the text objects and image objects included in the received label data to dummy contents created using sample character strings and sample images.

[0087] Then, the server program 23 generates screen data for the posting screen including an image of the changed label data (C12) and transmits it to the terminal 12. In this manner, the label data in which the contents of the text objects and image objects have been automatically changed to dummy contents becomes the subject of posting. In addition, the user can check the changed label data to be posted on the posting screen displayed on the terminal 12.

[0088] Furthermore, the server program 23 may be capable of receiving an instruction for automatic editing after displaying the posting screen on the terminal 12. In this case, the server program 23 may, for example, cause the terminal 12 to display a posting screen including an image of the label data before the change received at C11 and a button for receiving an instruction for automatic editing. When a user's operation on the button for receiving an instruction for automatic editing is received on the posting screen, the server program 23 executes an automatic editing process and causes the terminal 12 to display a posting screen including an image of the label data after the change. In this case, the instruction for automatic editing is an example of a change command.

[0089] If the server 22 executes the automatic editing process, the client application 13 does not need to have an automatic editing function, and the size of the client application 13 can be reduced. On the other hand, if the client application 13 executes the automatic editing process, the load on the server 22 is reduced. Furthermore, if the client application 13 executes the process, individual editing is also possible, such as by accepting the registration of dummy data. In either case, the user does not need to edit the label data, and there is a high possibility that label data that does not contain personal information will be registered.

[0090] As described above in detail, when the client application 13 of this embodiment receives an instruction to print or save on the editing screen 30, it displays the posting suggestion dialog 50 that suggests posting the target label data. The label data that is the target of printing or saving is likely to be label data for which editing has been completed. Since the client application 13 suggests posting the target label data in response to saving or printing the label data, it is expected that the label data will be posted.

[0091] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the present invention can be improved and modified in various ways without departing from the scope of the present invention. For example, the printing method of the label printer 11 is not limited to the thermal transfer method, but may be, for example, an inkjet method, an electrophotographic method, or a thermal method. Furthermore, the printing medium is not limited to label paper, but may be, for example, plain roll paper, fanfold paper, or cut paper.

[0092] Furthermore, the display screens shown in each figure are merely examples, and the wording in the figures, the arrangement of each piece of information, the shape of buttons, and the like are not limited to the examples shown in the figures. Furthermore, automatic editing processing may not be required. The posting suggestion dialog 50 may be, for example, a display that only accepts the selection of whether or not to post. Furthermore, the client application 13 may cause the terminal 12 to display an image of the label data to be posted before sending an instruction to start posting to the server 22.

[0093] Furthermore, in the embodiment, an example has been shown in which a print instruction or a save instruction is accepted for label data edited on the editing screen 30 (FIG. 3), but the client application 13 can also accept an instruction to print the label data 14 stored in the memory 122. When a print instruction for the label data 14 stored in the memory 122 is accepted, the client application 13 may also display the posting suggestion dialog 50 to suggest posting.

[0094] In the embodiment, the client application 13 changes text objects and image objects in the automatic editing process, but it may change only one of them, or may change other objects as well. For example, the client application 13 may be able to accept the setting of the type of object to be changed when registering dummy data. On the other hand, it is not necessary to register dummy data.

[0095] In the embodiment, the client application 13 matches all of the font type, character size, number of characters, and language type to the original label data when creating dummy text in the automatic editing process, but it may match only one or two of these, or none at all. The client application 13 may, for example, make a change to place an image object of a dummy image within the range of a text object of the original label data. However, if dummy text close to the text object of the original label data is generated and modified, it is easier to maintain the impression of the label data to be posted.

[0096] Also, in the embodiment, when the client application 13 receives a selection not to post by the user operating the button 53 in the posting suggestion dialog 50 (FIG. 3(C)), the client application 13 returns to the editing screen 30 (A31), but the client application 13 may also return to the home screen.

[0097] Also, although the client application 13 does not save the edited label data in the memory 122 in the automatic editing process, it may be possible to accept a save instruction.

[0098] Furthermore, the client application 13 may store the label data in the memory 122 in association with information indicating whether the label data has already been posted. For example, when the client application 13 receives a print instruction for label data associated with information indicating that the label data has already been posted, the client application 13 may not suggest posting the label data. Furthermore, when proposing posting of label data, the client application 13 may store information indicating that the label data has already been proposed or information indicating the number of times the label data has been proposed in association with the label data, and may not suggest posting of label data that has been proposed a predetermined number of times or more.

[0099] In addition, in any of the flowcharts disclosed in the embodiments, the order of execution of multiple processes in any of the steps can be arbitrarily changed or the processes can be executed in parallel as long as no contradiction occurs in the process content.

[0100] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as ASIC, or a combination of these. The processes disclosed in the embodiments may be realized in various forms, such as a recording medium having a program for executing the processes recorded thereon, or a method. [Explanation of symbols]

[0101] 11. Label Printer 12 Terminal 121 CPU 21 Internet connection 22 Server 100 Systems

Claims

1. A program executable by a computer of an information processing device, The computer includes: The apparatus is capable of executing an editing process for editing label data, the label data being data that can be printed by a label printer, The computer further comprises: a storage process for storing the label data edited in the editing process; a printing process for causing the label printer to print the label data edited in the editing process or the label data stored in the storage process; It is possible to execute The computer further comprises: executing a suggestion process for suggesting the submission of the label data to be saved or printed when at least one of the label data is saved by the save process and the label data is printed by the print process; The computer further comprises: A posting process for posting the label data can be executed, and in the posting process, the label data to be posted is uploaded to a server, and the uploaded label data is registered in the server. A program that is configured to:

2. The program according to claim 1, In the proposal process, Proposing the submission of the label data to be saved or printed, and accepting a selection of whether or not to submit the proposed label data; The computer includes: executing the posting process to post the label data to be proposed when a selection to post is accepted in the suggestion process; A program that is configured to:

3. The program according to claim 2, The computer includes: It is possible to display a selection screen that allows the user to select label data to be posted, and after the label data to be posted is selected on the selection screen, it is possible to execute the posting process for posting the selected label data, The computer further comprises: when a selection to post is accepted in the suggestion process, executing the posting process to post the proposed label data without displaying the selection screen; A program that is configured to:

4. The program according to claim 1, The computer includes: A modification process can be executed to modify the content of a specific object included in the label data to be posted to a predetermined content, the specific object is an object whose content can be edited by the editing process, and the label data in which the content of the specific object has been modified by the modification process is registered on the server. A program that is configured to:

5. The program according to claim 4, In the change process, extracting the specific object included in the label data of the posting target, and changing the content of the extracted specific object to the predetermined content; In the posting process, when the change process is executed, the label data in which the content of the specific object has been changed to the predetermined content by the change process is uploaded to the server; A program that is configured to:

6. The program according to claim 5, The computer includes: a storage process is executed to receive dummy data indicating the predetermined content to be changed by the change process and to store the received dummy data; In the change process, extracting the specific object included in the label data of the posting target, and changing the content of the extracted specific object to the dummy data stored in the storage process; A program that is configured to:

7. The program according to claim 4, In the change process, a change command is transmitted to the server in association with the label data to be posted, and the server receiving the change command changes the content of the specific object included in the uploaded label data to be posted to the predetermined content; A program that is configured to:

8. The program according to claim 4, In the proposal process, propose posting the label data to be saved or printed, and further accept a selection as to whether to post the proposed label data after changing the content of the specific object included in the proposed label data to the specified content, to post the proposed label data without changing the content to the specified content, or not to post the proposed label data; The computer includes: When the user selects to change the content to the specified content and post the label data in the suggestion process, the change process and the posting process for posting the label data to be proposed are executed, and the label data in which the content of the specific object has been changed by the change process is registered in the server, When the user selects to post the label data without making any changes to the specified content in the suggestion process, the user is not prompted to perform the change process, and the posting process is executed to post the label data to be proposed, and the label data with the content of the specific object unchanged is registered in the server. A program that is configured to:

9. The program according to claim 8, The computer includes: executing the editing process for accepting editing of the proposed label data when the user selects not to post the proposed label data in the suggestion process; A program that is configured to:

10. The program according to claim 4, the specific object to be changed by the change process is a text object, and text shown in the text object is changed to a predetermined text showing the predetermined content; A program that is configured to:

11. The program according to claim 10, In the change of the text shown in the text object by the change process, the number of characters after the change is adjusted to the number of characters before the change. A program that is configured to:

12. The program according to claim 10, In the change of the text shown in the text object by the change process, a character size after the change is adjusted to a character size before the change. A program that is configured to:

13. The program according to claim 10, In the change of the text shown in the text object by the change process, the type of font after the change is matched to the type of font before the change. A program that is configured to:

14. The program according to claim 10, In the change of the text shown in the text object by the change process, the language type after the change is matched to the language type before the change. A program that is configured to:

15. The program according to claim 4, the specific object to be changed by the change process is an image object, and an image set in the image object is changed to a predetermined image indicating the predetermined content; A program that is configured to:

16. The program according to claim 15, In the change of the image to be set in the image object by the change process, the predetermined image is adjusted to have a size equal to the size of the image before the change, and the adjusted predetermined image is set as the image after the change of the image object. A program that is configured to:

17. The program according to claim 4, The computer includes: After the change process is executed and before the changed label data is registered in the server, a preview process is executed to display a preview of the label data changed by the change process, and the user can select whether or not to post the label data in the preview display. When the user selects to post the label data, the label data in which the content of the specific object has been changed by the change process is registered in the server. A program that is configured to:

18. The program according to claim 4, The computer includes: Even if the label data changed in the change process is registered in the server, the label data changed in the change process is not stored in the information processing device. A program that is configured to:

19. The information processing device includes: An editing process for editing label data can be executed, the label data being data that can be printed by a label printer, The information processing device further comprises: a storage process for storing the label data edited in the editing process; a printing process for causing the label printer to print the label data edited in the editing process or the label data stored in the storage process; It is possible to carry out The information processing device further comprises: executing a suggestion process for suggesting the submission of the label data to be saved or printed when at least one of the label data is saved by the save process and the label data is printed by the print process; The information processing device further comprises: A posting process for posting the label data can be executed, and in the posting process, the label data to be posted is uploaded to a server, and the uploaded label data is registered in the server. The information processing device is configured as follows.

20. A label data sharing system comprising a first information processing device, a second information processing device, and a server, the first information processing device and the second information processing device being connectable to the server via a network, The first information processing device, The label data can be edited, and the label data is data that can be printed by a label printer; The first information processing device further comprises: A storage function for storing the edited label data; a printing function for causing the label printer to print the edited label data or the stored label data; having The first information processing device further comprises: When at least one of the label data is saved and the label data is printed, a proposal is made to post the label data to be saved or printed; The first information processing device further comprises: The label data can be uploaded to a server; The server, The uploaded label data can be registered, The second information processing device is It is possible to select one of the label data registered in the server, The second information processing device further comprises: downloading the selected label data from the server when a download instruction for the selected label data is received; A label data sharing system configured to:

Images