Program, information processing device, and label data sharing system

Abstract

The purpose of the present invention is to provide technology by which posting of label data is promoted in a system that facilitates use of label data.　A client application 13 enables the CPU 121 of a terminal 12 to edit label data that can be printed by a label printer 11, the client application 13 being capable of storing or printing the edited label data. When at least one of the storage and the printing of the label data is performed by the CPU 121, the client application 13 furthermore proposes posting of the label data to be stored or printed. The client application 13 can furthermore post the label data by causing the CPU 121 to upload the label data to be posted to a server 22, the uploaded label data being registered in the server 22.

Description

Program, information processing device, and label data sharing system

[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.

[0002] A conventional system for utilizing content data is known in which a server that stores 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 points management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and then 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.

[0004] Japanese Patent Application Laid-Open No. 2002-99746

[0005] In recent years, systems have been considered that allow users who create label data to upload the label data used to print labels with a label printer to a server, where other users can download and use the label data from the server. In such systems, it is desirable to have many users post label data. While Patent Document 1 describes allowing users to select photo data to post, it does not describe any measures to encourage users to post content such as photo data, leaving room for improvement.

[0006] A program made to solve the above-described 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 further capable of causing the computer to 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 the label data to be saved or printed when at least one of saving the label data in the saving process and printing based on the label data in 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 saved or printed. When label data is saved or printed, there is a high possibility that editing of the label data has been completed. Since the suggestion to post the label data that was the subject of processing is made in response to saving or printing of label data, 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.

[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.

[0010] FIG. 1 is a schematic configuration diagram of a system according to an embodiment; FIG. 2 is a sequence diagram showing a procedure for suggesting posting of label data; FIG. 3 is an explanatory diagram showing an example of an editing screen; FIG. 4 is a flowchart showing the procedure of automatic editing processing; FIG. 5 is an explanatory diagram showing an example of automatic editing of label data; FIG. 6 is a sequence diagram showing a posting procedure; FIG. 7 is an explanatory diagram showing an example of a posting screen; FIG. 8 is a sequence diagram showing a download procedure; FIG. 9 is a sequence diagram showing an instruction acceptance procedure; FIG. 10 is an explanatory diagram showing an example of a selection screen; and FIG. 11 is a sequence diagram showing a server editing procedure.

[0011] Hereinafter, a label data sharing system according to an embodiment will be described in detail with reference to the accompanying drawings. This specification discloses a label data sharing system that connects a server and multiple information processing devices via a network to share label data used for printing labels with a label printer.

[0012] As shown in Figure 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 comprises a plurality of terminals 12 and a server 22, which are connected via an internet line 21. Each terminal 12 can be connected to at least one label printer 11. The internet line 21 is an example of a network.

[0013] The terminal 12 is a device equipped with a communication function, a display function, and an operation reception function. As shown in FIG. 1 , the terminal 12 includes 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 includes 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 collective 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 user operations. 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 include Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The terminal 12 may be equipped with multiple communication IFs 124 that support multiple communication standards.

[0016] A client application program (hereinafter referred to as "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 can also store label data 14. The label data 14 is data that can be printed by the label printer 11 and is data 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 user instructions, a saving function that causes the created label data 14 to be saved in the memory 122 of the terminal 12, and a printing function that sends the created label data 14 to the label printer 11 and prints it.

[0018] The label printer 11 is a printing device that includes, for example, 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, allowing 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 installed in 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 label data 14 created using the client application 13 with other users. The server program 23 can receive, via the client application 13, instructions to upload the label data 14 created on the terminal 12 to the server 22 and instructions to download label data registered in the label DB 25 to the terminal 12. In this specification, uploading to the server 22 is sometimes referred to as "posting."

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

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

[0023] 3A, 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 on the editing screen 30. Editing operations include, for example, pasting an object, inserting data to be printed into an object, and changing the position or size of an object. The editing screen 30 also includes a print button 32 that accepts a print command based on the displayed label data, and a save button 33 that accepts a save command for 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. 3A 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, if the client application 13 receives a print instruction in A05, it sends the displayed label data to the label printer 11 as the 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 received in A05, the client application 13 performs processing to save the label data being displayed. For example, as shown in FIG. 3B , the client application 13 disables operation on the editing screen 30 and displays a save dialog box 40 on the user IF 123. The save dialog box 40 includes an input field 41 for receiving input of a file name to be saved, a save confirmation button 42 for receiving a save instruction, and a cancel button 43 for canceling 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 received 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 closes 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 complete, the client application 13 displays a posting suggestion dialog box, which suggests posting, on the user IF 123 of the terminal 12 (A08). A08 is an example of the suggestion process. The posting suggestion dialog box displayed after saving the label data includes, for example, a message indicating that saving has been completed and a button for accepting the user's selection, as shown in FIG. 3(C). The posting suggestion dialog box displayed after accepting a print instruction may include, for example, a message indicating that the print data has been sent to the label printer 11.

[0028] In A08, the client application 13 displays, on the user IF 123, a posting suggestion dialog 50 that accepts a selection of whether or not to post, as shown in FIG. 3C , 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 "Do not 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 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 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, we will explain automatic editing. When an instruction to automatically edit and post, that is, an operation on button 52 (alt: [Edit and post]), is received, the client application 13 executes the automatic editing process (A11). The operation on 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 selected for printing or saving in A06.

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

[0032] The CPU 121 first 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 content can be edited by accepting user operations on an editing screen for editing label data, such as that shown in FIG. 3A. In other words, the text represented by a text object is text entered or edited by the user, and may include the user's personal information, such as the user's name and contact information.

[0033] If 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 additional 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 containing 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 one or more sample character strings as character strings of predetermined content 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 and characters of the font type and size acquired in B02. By arranging the same number of characters of the same font type and size as the text included in the text object, it is possible to minimize the change in the impression of the label before and after the change.

[0037] For example, if the number of characters in a text object is greater than the number of characters in a prepared sample string, the 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, the CPU 121 may use 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 dummy text may be any character string that does not include personal information of the user, such as "sample" or "test," which indicates that the text is dummy, or may be a repetition of the same characters, or may be a character string that is widely used in that language for checking printing, etc. The sample character string may also be a character string made up of characters randomly selected by the CPU 121, or may be a character string that is not specific to the user, such as the name of the vendor of the label printer 11.

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

[0040] The client application 13 may also 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 symbols, the CPU 121 may not change the symbols. The client application 13 may also prepare, for example, multiple types 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 if it is determined that the proposed label data does not contain a text object (B01: NO), the CPU 121 determines whether the label data contains 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 accepting user operations on an editing screen for editing label data, such as that shown in FIG. 3A. In other words, the image included in the image object is an image selected by the user and may contain personal information about the user, such as a photo of the user or their family members.

[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 the user's personal information, and may be, for example, a solid 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 by, for example, adjusting a sample image prepared in advance to the size of the image object in the label data.

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

[0045] For example, image object 77 containing a photographic image in label data 70 shown in FIG. 5A is changed to image object 87, which is a dummy image, as shown in FIG. 5B. By changing the image of the image object to a dummy image, it is possible to create label data for posting that does not contain personal information. Furthermore, by changing to a dummy image that matches the size of the original image object, it is possible to minimize the change in the impression of the label before and after the change. Note that if label data contains multiple image objects, the CPU 121 executes B12 to B14 for all image objects.

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

[0047] The CPU 121 may also change objects other than text objects and image objects. For example, if 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 leave objects other than text objects and image objects unchanged. For example, the CPU 121 may leave the clip art 73, date / time object 74, frame object 75, and graphic object 76 of the label data 70 shown in Fig. 5(A) unchanged. In this case, as shown in Fig. 5(B), the label data 80 edited by the automatic editing process includes the same objects as before editing: clip art 83, date / time object 84, frame object 85, and graphic object 86.

[0049] After B14, or when it is determined that the proposed label data 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 explanation of the posting suggestion procedure in Fig. 2, after the automatic editing process in A11, the client application 13 starts the posting procedure for posting without requiring any operation by the user to start posting (A12). The posting procedure will be explained 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 on the user IF 123 for accepting input of login information including a user ID, 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 a posting start instruction 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 in A12 of Fig. 2, the label data to be posted is label data that has been edited in the automatic editing process (e.g., label data 80 in Fig. 5(B)). That is, in C11, the client application 13 automatically selects the label data that has been edited in 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 in A05 of Fig. 2. Because it has been edited in the automatic editing process, there is little chance that personal information will be included in the uploaded label data, preventing information leaks.

[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 posting instructions (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, i.e., 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. 7A, a preview of the label data to be posted is displayed as a label image 61 on the posting screen 60. The posting screen 60 displayed after the automatic editing process (FIG. 4) is performed displays an image of the label data after the automatic editing process. C15 in this case is an example of a preview process. The client application 13 may itself have a browser function, or may launch a browser to display the screen.

[0056] Furthermore, the server program 23 accepts input of various information on the posting screen 60. The user enters 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 scrolling 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 label data on the posting screen 60.

[0057] The server program 23 displays the content 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, as shown in FIG. 7B , for example. The posting instruction button 62 is a button that accepts the selection to post. Note that the posting instruction button 62 may be a button that becomes active after the required information has been input.

[0058] The posting screen 60 also accepts the user's selection as to whether or not to post. The user can check the automatically edited label data that will actually be posted by looking at the label image 61 included in the posting screen 60, thereby avoiding posting unintended content. If the user wishes to cancel the post 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 post.

[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 label data in the label DB 25 and are an example of a posting process.

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

[0061] Even if 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, after the client application 13 transmits 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. For example, 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 whose text or image object content has been changed by the automatic editing process is label data that has been changed for posting, not label data that the poster uses. For example, if the changed label data is saved by overwriting the original label data, editing work may be required to restore it to its original state. The client application 13 does not save the changed label data, which avoids inconvenience to the poster.

[0063] Returning to the explanation of the posting suggestion procedure in Fig. 2 , after the posting procedure ( Fig. 6 ) executed in A12, the client application 13 terminates the connection with the server 22 and causes the user IF 123 to display a home screen of the client application 13 (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 selection of a function to be executed by the client application 13. The client application 13 may also display an editing screen.

[0064] The client application 13 may remain connected to the server 22 even after the posting procedure is completed. The server 22 may then display the top screen of the server program 23 on the terminal 12. The server program 23 receives label data from the terminal 12 and registers 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 terminal 12 starts executing the client application 13, connects to the server 22, receives an instruction to use the server program 23, and completes the connection with the server 22. When the server program 23 receives the connection instruction from the client application 13, it transmits screen data showing, for example, a top screen to the terminal 12. The user can transmit an instruction to start the download procedure to the server 22 via, for example, the top screen of the server program 23 displayed on the terminal 12. Note that the download procedure can also be executed immediately after the above-described posting procedure is executed.

[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 accepts 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 the user to 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 includes, for example, images of multiple downloadable label data items and accepts user selections. 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 sends 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 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 sends 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 and use the label data stored in the memory 122 using the client application 13. In other words, the system 100 allows label data to be shared among multiple terminals 12. For example, if the label data selected for download is automatically edited on the posting terminal and then posted after modification, the contents of the text objects and image objects will have been changed to dummy data. Therefore, it is unlikely that the personal information of the posting user will be included. Furthermore, the downloading user can easily use the downloaded label data by editing the dummy data to make it more suitable for them.

[0071] Returning to the explanation of the posting suggestion procedure in Fig. 2 , when an operation on 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 in A21 is the same as the posting procedure in A12 shown in Fig. 6 . The operation on 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 predetermined content.

[0072] In the posting procedure A21, the client application 13 sends the label data to be printed or saved (e.g., label data 70 in FIG. 5A ) 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 contains personal information such as a store name, a user who wants to share the label data as is with other users can automatically transition to the posting screen by simply operating button 51, providing a high degree of freedom in posting. After the posting procedure 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 editing screen, or may maintain a connection with 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 the label data. When an operation on the button is accepted, the client application 13 may remember that the label data to be posted is being 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 label 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. Accepting editing of the suggested label data in response to an instruction not to post makes it easier for the user to post label data.

[0076] The client application 13 can accept various instructions other than instructions to edit label data. For example, the client application 13 accepts user operations on the home screen displayed on the user IF 123 of the terminal 12 at A13 or A22 in Fig. 2. The procedure when various instructions input by user operations 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 to post label data (alt: [Post instruction]), the client application 13 displays a selection screen on the user IF 123 (E11) that accepts the selection of label data to be posted. For example, as shown in Fig. 10, the selection screen 90 includes a post button 91 and images 92, 93, and 94 of each label data item stored in the memory 122, and accepts 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 then operates the post button 91 to instruct posting (E13). This executes the posting procedure ( FIG. 6 ) described above (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 when the posting suggestion dialog 50 is made 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 select label data, making it easier for the user to post label data.

[0080] The client application 13 may also be able to accept designation of dummy data that can be used in the automatic editing process. That is, the client application 13 may use the sample character string or sample image accepted as dummy data to create dummy text in B04 or a dummy image in B13 of the 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 storage processing. If dummy data is stored in the memory 122, the client application 13 reads the dummy data and creates dummy text and dummy images in B04 and B13 of the automatic editing processing (FIG. 4). Note that the client application 13 may be able to accept registration of dummy data for each object type or each label data category. Alternatively, only one of E21 and E22 may be performed.

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

[0083] Although the procedure for the client application 13 to execute 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 for suggesting posting shown in Fig. 2 differs from the procedure for suggesting posting shown in Fig. 2 in that the procedure is executed when an operation on the "Automatically edit and post" button 52 is accepted in the displayed posting suggestion dialog 50 (A08, Fig. 3(C)). The other procedures are the same as those of 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 sequence diagram of Fig. 11, the steps up to displaying the posting screen are different 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 a description thereof will be omitted.

[0085] In this case, the client application 13 does not execute the automatic editing process, but sends a posting start instruction to the server 22, regarding the label data that was selected for printing or saving on the editing screen 30 ( FIG. 3A ) 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 posting start instruction sent in C11 (F01). Note that the client application 13 may send the change command together with the posting start instruction of 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 for 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] The server program 23 then generates screen data for the posting screen, including an image of the changed label data (C12), and sends it to the terminal 12. In this way, the label data to be posted will have the contents of the text objects and image objects automatically changed to dummy contents. The user can also check the changed label data to be posted on the posting screen displayed on the terminal 12.

[0088] The server program 23 may also be able to accept 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 accepting an instruction for automatic editing. When the server program 23 accepts a user operation on the button for accepting an instruction for automatic editing on the posting screen, the server program 23 executes automatic editing processing 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 performs the automatic editing process, the client application 13 does not need to have an automatic editing function, which allows for a smaller size of the client application 13. On the other hand, if the client application 13 performs 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 by accepting the registration of dummy data, etc. 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 a print or save instruction 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 that has been edited. 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 this embodiment is merely an example and does not limit the present invention in any way. Therefore, the present invention can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the printing method of the label printer 11 is not limited to thermal transfer, but may be inkjet, electrophotographic, or thermal. Furthermore, the print 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 the figures 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. Furthermore, the automatic editing process may not be necessary. For example, the posting suggestion dialog 50 may be a display that only accepts the selection of whether or not to post. Furthermore, the client application 13 may display an image of the label data to be posted on the terminal 12 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 label data 14 stored in memory 122. When a print instruction for label data 14 stored in 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 may not be possible 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 those of the original label data when creating dummy text in the automatic editing process, but it may match only one, two, or none of these. The client application 13 may, for example, make a change by placing an image object of a dummy image within the range of a text object in the original label data. However, if dummy text that is 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] In addition, in the embodiment, when the client application 13 receives a selection not to post by the user operating button 53 in the posting suggestion dialog 50 (Figure 3 (C)), the client application 13 returns to the editing screen 30 (A31), but it may also return to the home screen.

[0097] Furthermore, 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] The client application 13 may also associate label data with information indicating whether it has already been posted and store it in the memory 122. For example, when the client application 13 receives a print instruction for label data associated with information indicating that it has already been posted, the client application 13 may not suggest posting the label data. When suggesting posting of label data, the client application 13 may store information indicating that it has already been proposed or information indicating the number of times it has been proposed in association with the label data, and may not suggest posting label data that has been proposed a predetermined number of times or more.

[0099] Furthermore, in any flowchart disclosed in the embodiments, the execution order of multiple processes in any multiple steps can be changed or they can be executed in parallel as long as no contradiction occurs in the processing content.

[0100] The processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as an ASIC, or a combination thereof. The processes disclosed in the embodiments may be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method.

[0101] 11 Label printer 12 Terminal 121 CPU 21 Internet line 22 Server 100 System

Claims

1. A program executable by a computer of an information processing device, the program being configured to cause the computer to execute an editing process to edit label data, the label data being data that can be printed by a label printer, the program being further configured to cause the computer to execute a saving process to save the label data edited by the editing process, and a printing process to cause the label printer to print the label data edited by the editing process or the label data saved by the saving process, the program being further configured to cause the computer to execute a suggestion process to suggest posting the label data to be saved or printed, when at least one of saving the label data by the saving process and printing based on the label data by the printing process has been performed, and the program being further configured to cause the computer to execute a posting process to post the label data, the posting process uploading the label data to be posted to a server, and the uploaded label data being registered on the server.

2. A program as recited in claim 1, wherein the suggestion process suggests posting of the label data selected for saving or printing, and further accepts a selection of whether or not to post the suggested label data, and causes the computer to execute the posting process of posting the suggested label data when the selection of posting is accepted in the suggestion process.

3. A program as recited in claim 2, the program being configured to cause the computer to: display a selection screen which allows the user to select label data to be posted; and, after the label data to be posted is selected on the selection screen, to execute the posting process to post the selected label data; and, when a selection to post is accepted in the suggestion process, to cause the computer to execute the posting process to post the suggested label data without displaying the selection screen.

4. A program as recited in claim 1, configured to cause the computer to execute a modification process for modifying the content of a specific object included in the label data to be posted to a predetermined specified content, the specific object being 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 being registered in the server.

5. A program as recited in claim 4, configured to: in said modification process, extract the specific object included in the label data to be posted, and change the content of the extracted specific object to the specified content; and in said posting process, when said modification process is executed, upload to said server the label data in which the content of the specific object has been changed to the specified content by said modification process.

6. A program as recited in claim 5, capable of causing the computer to execute a storage process that receives dummy data indicating the specified content to be changed by the change process and stores the received dummy data, wherein the change process extracts the specific object included in the label data to be posted, and changes the content of the extracted specific object to the dummy data stored in the storage process.

7. A program as recited in claim 4, wherein the modification process transmits a modification command to the server in association with the label data to be posted, and the server, upon receiving the modification command, modifies the content of the specific object included in the uploaded label data to be posted to the specified content.

8. A program as recited in claim 4, wherein the suggestion process proposes posting of the label data to be saved or printed, and further accepts a selection of whether, for the proposed label data, to change the content of the specific object included in the proposed label data to the specified content and post it, to post it without changing it to the specified content, or not post it at all, and when the suggestion process selects to change to the specified content and post it, the computer is caused to execute the change process and the post process to post the proposed label data, and the label data with the content of the specific object changed by the change process is registered on the server, and when the suggestion process selects to post it without changing it to the specified content, the computer is caused to execute the post process to post the proposed label data without executing the change process, and the label data with the content of the specific object unchanged is registered on the server.

9. The program according to claim 8, further comprising: a program configured to cause the computer to execute the editing process for accepting editing of the proposed label data when a selection is made not to post in the proposal process.

10. A program as claimed in claim 4, wherein 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 specified text showing the specified content.

11. A program as claimed in claim 10, configured to: change the text displayed in said text object by said change process so that the number of characters after the change is adjusted to the number of characters before the change.

12. The program according to claim 10, configured to: change the text displayed in the text object by said change process to match a character size after the change to a character size before the change.

13. A program as claimed in claim 10, configured to: match the type of font after the change to the type of font before the change when the change is made to the text shown in the text object by the change process.

14. The program according to claim 10, wherein the change process changes the text displayed in the text object to a language type that matches the language type before the change.

15. A program as described in claim 4, wherein 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 specified image indicating the specified content.

16. A program as claimed in claim 15, configured so that, when the image set in the image object is changed by the change process, the specified image is adjusted to have the same size as the image before the change, and the adjusted specified image is set as the image of the image object after the change.

17. A program as recited in claim 4, further comprising: causing the computer to execute a preview process for previewing the label data modified by the modification process after the modification process is executed and before the modified label data is registered on the server; the preview display allows the user to choose whether or not to post the label data; and if the choice to post is accepted, the label data in which the content of the specific object has been modified by the modification process is registered on the server.

18. A program as claimed in claim 4, configured to cause the computer to not store the label data changed in the change process in the information processing device even if the label data changed in the change process is registered in the server.

19. An information processing device configured as follows: capable of executing an editing process to edit label data, the label data being data that can be printed by a label printer; the information processing device further capable of executing a saving process to save the label data edited by the editing process, and a printing process to cause the label printer to print the label data edited by the editing process or the label data saved by the saving process; the information processing device further executes a suggestion process to suggest posting the label data to be saved or printed, when at least one of saving the label data by the saving process and printing based on the label data by the printing process has been performed; the information processing device further executes a posting process to post the label data, the posting process uploading the label data to be posted to a server, and the uploaded label data being registered on the server.

20. A label data sharing system comprising a first information processing device, a second information processing device, and a server, wherein the first information processing device and the second information processing device are connectable to the server via a network, wherein the first information processing device is capable of editing label data, the label data being data that can be printed by a label printer, the first information processing device further has a save function for saving the edited label data, and a print function for causing the label printer to print the edited label data or the saved label data, the first information processing device further suggests posting of the label data to be saved or printed, when at least one of saving the label data and printing based on the label data has been performed, the first information processing device is further capable of uploading the label data to the server, and the server is capable of registering the uploaded label data, the second information processing device is capable of selecting one of the label data registered in the server, and the second information processing device is further configured to download the selected label data from the server when a download instruction for the selected label data is received.

Images