JP4614309B2 - Content editing method, program and system - Google Patents

Description

  The present invention relates to content editing technology, and more particularly to editing technology related to the processing order of multimedia content.

  In this specification, the grid refers to each one of a plurality of regions partitioned in a lattice pattern, but does not limit the shape of the region.

  In recent years, with the rapid development of computer systems, it has become possible for even individual users to handle various multimedia contents such as video, music, and characters in an integrated manner using a personal computer or the like. .

  For example, a plurality of slides can be edited by using Microsoft PowerPoint (hereinafter referred to as “PowerPoint”) which is a registered trademark of Microsoft Corporation. According to PowerPoint, it is possible to browse slides on which multimedia materials, tables, drawings, and the like can be pasted according to the order that each slide has. Follow the steps below to create a new work using PowerPoint. 1. Click [New] on the [File] menu, and click the [Standard] tab. 2. Double-click the New Presentation icon and select the layout for the first slide. 3. Enter a title and other information. 4). Click [New Slide] on the [Frequently Used Functions] toolbar, scroll to see another layout, and select the layout to use for the second slide. 5. Add this if you want to add your own content. Repeat steps 4 and 5. 6). When finished, click [Save] on the [File] menu. 7. Name the created presentation and click [Save]. On this occasion. PowerPoint generates as many slides as you need and pastes multimedia materials such as sound, images, text, and videos onto the slides.

  More specifically, when a sound material to be reproduced by mouse operation is pasted on the slide, the following procedure is performed. 1. In slide display mode, display the slide where you want to insert the sound. 2. On the [Insert] menu, point to [Video and Sound]. 3. To insert a sound from the clip gallery, click [Sound from Gallery] and double-click the sound clip to be inserted. When setting the sound to be played when the slide is switched, point to [Switch Screen] in the [Slide Show] menu, and specify the sound by operating the pull-down menu in the sound column of the displayed dialog.

  Next, when inserting a slide of an existing work into the work being created, point to [Slide from File] on the [Insert] menu, specify the original work in the displayed dialog, and list the slides. Display. Next, when the slide to be inserted is designated by double-clicking from the list display, the double-clicked slide can be inserted behind the current slide.

  To set the time interval for switching slides, point to [Screen Switch] from the [Slide Show] menu on the menu bar, and enter the time (in seconds) in the screen switching timing field of the displayed screen switching dialog box. . In PowerPoint, an object that reproduces sound or a hyperlink object can be pasted on a slide as an object that operates by a mouse operation. When an animation is set for a plurality of objects on the screen, the animation can be reproduced sequentially. The execution order can be changed in the displayed dialog by pointing to [Animation Settings] from the [Slide Show] menu on the menu bar.

  In PowerPoint, attributes such as the color, shape and font of the object pasted on the slide can be changed by operating the toolbar / menu bar on the editing screen. Also, by using the "Copy / Paste Format" function, you can acquire the color, shape, and font attributes of any object at once and set the acquired attributes to another object at once. Can do. To acquire attributes using the [Copy / Paste Format] function, select the object to be acquired and click the [Copy / Paste Format] button on the toolbar. Immediately after that, clicking on another object can apply the acquired attribute.

  When capturing an image from an image scanner or the like, point to the [Figure] menu from the [Insert] menu on the menu bar, and click [From Scanner]. At this time, an image for controlling the scanner set in the computer is displayed. The image can be captured by specifying the resolution and capture range with this image (see, for example, Non-Patent Document 1).

PowerPoint Online Manual, “Insert Sound”

As described above, since PowerPoint has a wide range of functions, it also supports temporary editing of multimedia content. PowerPoint requires computer-specific operations such as menu dialog operations, and the more functions that are provided, the more complicated the operations tend to become, which is as expected for users who are not familiar with computer operations. It was difficult to create a work.
In addition, within the range of functions provided by PowerPoint, it was possible to create works of a fixed format, but it was difficult to create works of free format.

  With PowerPoint, you can only create works that allow you to view slides of the same size at the same display position. For example, it is difficult to make a user-oriented expression by freely changing the display size and display position, such as making the screen size desired to be expressed for each slide.

  The functions that are lacking in PowerPoint will be described in more detail below. In PowerPoint, when adding a new slide, point to [New Slide] in the [Insert] menu of the menu bar. Each menu operation is also required when pasting sounds, images, or movies on a slide. These operations are basic operations for creating a work, but cannot be performed without knowing the meaning of terms displayed on the menu and the location of the menu. Furthermore, even when setting the sound, the setting method differs depending on whether the sound to be played by mouse operation on the slide is set or the sound to be played when the slide is switched. Since there are various setting methods depending on whether or not to play, the operation becomes complicated.

  In addition, PowerPoint works are the same for all pages of slide size and display position, and because the slide is composed of one screen, all pages are unified. Yes. You cannot change the display size or display position for each slide, or create a slide composed of multiple screens.

  In addition, in PowerPoint, when inserting a slide of an existing work into a work being created, a list of the insertion source slides is displayed in a dialog opened by a menu operation, and the user performs an operation of selecting a slide to be inserted. Here, since the selected slide is always inserted after the current slide, it is necessary to set the current before the insertion position every time the insertion operation is performed.

  In addition, when setting the time interval for switching slides in PowerPoint, enter the number of seconds in the dialog. If the number of seconds specified here is less than the playback time of the sound to be played when the slide is switched, the sound playback is interrupted when the slide is switched. In order to switch the slide after the sound reproduction ends, it is necessary to refer to the sound reproduction time and set the time as the slide switching time interval.

  In addition, when changing the background, character, or frame attributes of an object with a slide pasted in PowerPoint, it is possible to acquire and set one attribute or all attributes with a single operation. It was not possible to change a group of related attributes, such as font style, etc.

  The object of the present invention is to make multimedia editing easier and more attractive for many users by making the user interface easier to use and providing visual operability than existing applications. That is. For example, to provide multimedia creation / editing technology that enables even users who are not familiar with computer operations to create works as they wish without having to refer to manuals. With the goal.

  According to one aspect of the present invention, there is provided a content editing method in an application system capable of associating processing of parts by pasting another part on a screen with respect to a part, and performing processing related to content. A step of displaying a content processing start button component for starting on the screen, a step of displaying on the screen a mount component having a plurality of cells in which the order is defined for each cell, and a series of processing relating to the contents are in the order. The content editing method includes a step of pasting the content processing start button component to the grid so as to be executed along the line.

  When the above method is used, the order is defined for each of the plurality of cells on the mount component, and the content processing order can be specified by pasting the desired content processing start button component on the cell. The contents of processing and the order of processing can be set all at once, and the operation becomes simple.

  According to another aspect of the present invention, there is provided a content editing method in an application system capable of associating processing of parts by pasting another part on a screen with respect to a part, and processing related to content Displaying on the screen a content processing start button component for starting the screen, displaying a mount component having a plurality of cells on the screen, pasting the content processing start button component on the cell, Designating the processing order of the content processing start button parts pasted on the cells so that a series of processing related to the content is executed in a certain order.

  Using the above method, after selecting and pasting the content to be processed, the processing order of the content can be specified in an extended manner, so that the processing details and timing can be customized later There is.

  According to another aspect of the present invention, there is provided a content editing method in an application system capable of associating processes of parts with each other by pasting another part on a screen with respect to a part. A step of displaying a content processing start button component for starting processing related to the screen, and a mount component on which processing related to the content is executed by pasting the content processing start button component, the mount having calendar information There is provided a content editing method including: displaying a part on a screen; and pasting the content processing start button part on the mount part so as to associate the calendar information with the content processing start button part. The

  According to the above method, it is possible to associate the calendar information with the content execution process, and it is easy to sensuously create a work that is completed when the content is processed in order.

  The content editing technology according to the present invention makes multimedia editing easier and more attractive for many users by making the user interface easier to use and providing a visual operability than existing applications. It is to provide a means to make things better. For example, even a user who is not familiar with computer operations can intuitively create a desired work without referring to a manual or the like.

  In this specification, the controller is a window for starting various operations, and icons for displaying a function for generating a mount and a browser for handling various materials are displayed on the controller. ing. The material includes, for example, parts as well as photographs and sounds. A mount or capsule binder is a window that is the basis for creating a work. You can create a work by attaching multimedia content materials and parts to a window called a mount. The parts include a capsule button, a close button, a simultaneous button, and the like, and a window for taking out these various parts is a parts box. The button is an icon for performing some processing.

  Before describing the embodiments of the present invention, specific considerations made by the inventors will be described first. The inventor considered it convenient to change the display size and display position for each slide or to create a slide composed of a plurality of screens. Adding slides and adding sounds is even more convenient if you can unify the operations when adding material to your work. In addition, 1) simplify the operation of creating an existing work as one slide of the work being created, and 2) adjust the slide switching time interval according to the playback time of various multimedia materials included in the slide. 3) Button components pasted on slides are executed in order, 4) Individual attributes can be changed / acquired, and multiple attributes can be changed / acquired at once, It is convenient if it is possible to 5) organize information according to date and time information, 6) arbitrarily determine the resolution of an image when capturing image data or the like.

  The content editing technique according to the present invention has a feature that an event indicating which order or procedure is activated can be associated with a plurality of parts to be pasted on a mount part. Due to the order, continuity, and direction associated with the mount, each component that is affixed to the mount can have a story or a certain processing function.

  Next, the basic concept of the multimedia editing technique according to this embodiment will be described. Here, in the description of the previous application (Japanese Patent Laid-Open No. Hei 7-152546) regarding the configuration and basic operation of an object-oriented programming system using graphics, which is a precondition of the content editing technique according to the present embodiment. This will be explained based on. FIG. 53 is an overall configuration diagram showing an embodiment of an object-oriented programming system using graphics.

  This system can be broadly divided into a keyboard 5300 for inputting commands and characters, a mouse (pointing device) 5310 for performing operations on components displayed on the screen, and a central processing unit 5320 for executing various processes. The display 5330 displays various components on the screen, a memory 5340 that stores various processing programs, and a component object database 5350 that stores various components. Among these, the mouse 5310 includes a right button 5310a and a left button 5310b.

  The memory 5340 stores an operating system 5341 that controls operations of various components displayed on the screen of the display 5330, and a window system 5342 that displays various components as windows on the screen of the display 5330. . Note that these systems 5341 and 5342 use known techniques. Further, in the memory 5340, a component program group 5343 in which the behavior with respect to the external operation and the display form on the screen are defined in the form of “processing program” for each component, and the component management for managing the coupling between the components. A kernel program 5344 is stored.

  The part object database 5350 stores, for example, a bar meter 5351, a pie chart 5352, a band graph 5353, a STOP button 5354, a Japan map 5355, a calculator 5356, a button 5357, and the like. 54 (A) and 54 (B) are diagrams showing the basic structure of each component. For example, in the case of the bar meter 5351, FIG. 54A shows a display form on the display screen, and FIG. 54B shows the internal structure of the bar meter 5351. In FIG. 54, the bar meter 5351 is shown as an example, but the basic structure of the object-oriented component handled in this embodiment is all configured in the same manner as in FIG.

  As shown in FIG. 54 (B), each part handled in the present embodiment includes a control unit (controller: C) 5400 that defines a behavior with respect to an external operation, a holding area that holds a coupling relationship with others, and an on-screen And a display form definition section (view: V) 5410 having a definition area for defining the display form of each part and an internal mechanism definition section (model: M) that holds its name and current state in the form of “slot” 5420.

  FIG. 55 shows the configuration of each part (M, V, C) of the part. This will be described with reference to FIGS. Each unit includes a plurality of processes described in a program format as shown in the figure, and is stored in a part program group 5343. In FIG. 55, the control unit 5400 includes a process 5500a for a click (x, y) 5500 that is a pressing operation of the left button 5310b of the mouse 5310 and a pressing operation of the right button 5310a of the mouse 5310. A process 5505a for right_click (x, y) 5505 and a process 5510a for key_in (c) 5510 which is a key input operation by the keyboard 5300 are described.

Further, various messages described in the display form definition unit 5410 and processing for the messages are as follows.
1. set (s, v) 5515: This is a message for setting the value “v” in the “slot” designated by “s”, and processing 5515a for this message.
2. gime (s) 5520: A message requesting the value of the “slot” designated by “s”, and processing 5520a for this message.
3.update 5525: A message notifying other parts that the state of the self part has changed, and processing 5525a for this message.
4. click_action 5530: A message when the own part is clicked, and processing 5530a for this message.
5. move_action 5535: This is a message when an operation of moving the own part is performed, and processing 5535a for this message.
6. move (x, y) 5540: A message requesting the operation of moving the own part, and processing 5540a for this message.
7. key_in_action (c) 5545: A message of key input operation from the keyboard 100, and processing 5545a for this message.
8. event (a, mx, my, e, args) 5550: A message notifying the occurrence of an event, and processing 5550a for this message.
9. eval (e, args) 5555: A message for requesting evaluation of the message, and processing 5555a for this message.
10. model_update 5560: A change notification message from the internal mechanism definition unit 5320, and processing 5560a for this message.
11. redraw 5565: A message for redisplaying the numerical value on the display screen, the height of the meter, etc., and processing 5565a for this message.

  In the internal mechanism definition unit 5420, a process 5570a for model_set (s, v) 5570, which is a message for setting the value of “slot” designated by “s”, and the value of “slot” designated by “s” A process 5575a for model_gime (s) 5575, which is a message requesting the above, is described.

  FIG. 56 is an explanatory diagram for explaining the flow of various messages. In FIG. 56, one component includes a control unit 5400, a display form definition unit 5410, and an internal mechanism definition unit 5420. The control unit 5400 sets the address V5402 of the display form definition unit 5410 corresponding to its own part. It has an address area 5401 to be held.

  The display form definition unit 5410 also has an address area 5411 that holds the address C5413 of the control unit 5400 and the address M5412 of the internal mechanism definition unit 5420 corresponding to the self part, and a parent-child table 5414 that holds a parent-child relationship with other parts. have. The parent-child table 5414 holds parts that are “parent” and “child” of the own part. For example, in the case of a bar meter in Sapporo, the parent part is the Japan map 5355, the address is “a”, and there are no child parts. Further, the display form definition unit 5410 has a slot connection table 5425 that holds connection relationship information with other components. The slot combination table 5425 performs “ON” and “OFF” of an area 5426 for storing the name of the own slot, an area 5427 for storing the name of the parent slot, and a set (s, v) 5515 which is a message from the child part. It consists of a set field 5428 and gime (s) 5520 “ON” and “OFF” gime field 5429 and update 5525 “ON” and “OFF” update messages 5430 which are messages sent to the child parts. Has been.

  The internal mechanism definition unit 5420 includes an address area 5421 that holds the address V5402 of the display form definition unit 5410 corresponding to the self part, a slot table 5422 configured with a slot name 5423 and a slot value 5424 of the self part.

  Hereinafter, the operation of one component having such a configuration will be described. In FIG. 56, when the user 5600 performs various operations 5610 such as a click performed on the display 5330, the operation 5610 is first detected by the window system 5342, and a message click (x, y) is displayed according to the operation content. 5500, right_click (x, y) 5505, and key_in (c) 5510 are generated. These messages are transmitted from the window system 5342 to the component management kernel program 5344.

  The component management kernel program 5344 sends messages (click (x, y) 5500, right_click (x, y) 5505, and key_in (c) 5510) corresponding to the transmitted various operations to the component control unit 5400. . Upon receiving these messages, the control unit 5400 sends messages such as click_action (x, y) 5530, move_action (x, y) 5535, and key_in_action (c) 5545 to the corresponding display form definition unit 5410 of its own part. Send. Upon receiving these messages, the display form definition unit 5410 sends messages such as model_set (s, v) 5570, model_gime (s) 5575, etc. to the corresponding internal mechanism definition unit 5420 of its own part.

  From the contents of these messages, the internal mechanism definition unit 5420 sends model_update 5560 to the display form definition unit 5410 as a corresponding process to notify the change in value.

  With the above processing, the association processing (paste processing) by superposition is performed. In addition, to summarize the prior art, with respect to the operation target thing of the prior art, a control unit that defines a behavior for an external operation, an internal mechanism definition unit that defines a process for the external operation, and holds the processing result, Defines the display form with graphics on the screen, obtains the processing result of the internal mechanism definition unit, transmits the processing result to other associated object-oriented parts, and displays it on the screen according to the definition of the display form A programming processing method of a programming system for constructing an application by combining the processing of a plurality of object-oriented parts constituted by a display form definition unit to be executed, wherein a) storing the object-oriented parts as one unit of graphic parts; b ) Object-oriented parts displayed graphically on the screen are superimposed on the screen. C) storing the correspondence relationship; d) detecting an external operation on any of the plurality of associated object-oriented components, and controlling the object-oriented component in the control unit. A step of transmitting an external operation; e) a step of combining the processing of a plurality of object-oriented parts having a correspondence relationship according to the correspondence relationship information stored in the correspondence relationship storing step; It can be understood as a programming processing method of an oriented programming system.

  With the above basic concept in mind, an embodiment for carrying out the present invention will be specifically described below with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of a multimedia content editing method according to an embodiment of the present invention, and is a diagram related to FIG. As shown in FIG. 1, the content editing system according to the present embodiment includes a central processing unit 101, a keyboard 102, a display device (display) 103, a mouse 104, and a hard disk (storage device) 105. Interfaces for various multimedia devices such as an image scanner 106, a digital camera 107, a video capture device 108, and a microphone 109 are provided so as to be compatible with multimedia. The central processing unit 101 performs multimedia editing processing. The keyboard device 102 is an interface for inputting characters. The display device 103 displays graphics, and the mouse 104 is a pointing device. The hard disk 105 stores programs for operating the central processing unit, materials such as images, video, and audio, and multimedia contents. The image scanner 106 digitizes characters and images and imports them into a personal computer PC or the like. The digital camera 107 captures images and photos. The video capture device 108 captures a video such as a moving image. The microphone 109 captures audio information.

  2 to 7 are diagrams showing examples of display screens when processing by the multimedia content editing technique according to the present embodiment is performed. In the present embodiment, drag and drop with a mouse is the basic operation. In FIG. 2 to FIG. 7, the drag and drop operation is indicated by an arrow. In this embodiment, a plurality of screens are displayed at the same time, but one time is called a slide. That is, the slide may be composed of one or more screens.

  The work by the content editing technique according to the present embodiment is based on a window called a mount or a capsule binder. Create a work by pasting multimedia content materials and parts into this window.

  The part has a button called a capsule button, and when a capsule button is clicked, another screen called a capsule screen opens. This capsule screen has the same function as the mount, and can be pasted with multimedia content materials and parts. The difference between the mount and the capsule screen is that the former is located in the lowest layer of the work and the latter is located in the second and higher layers. When creating a work based on a mount, a work having two or more layers can be created by pasting capsule buttons on the mount or capsule screen.

  As described above, the screen of the work located in the lowermost layer has a capsule binder in addition to the mount. The mount can attach multimedia content materials and parts at any position. On the other hand, the capsule binder is partitioned in a grid shape, and only one or more buttons can be pasted in the grid. The capsule binder has a function of sequentially executing the buttons on the grid based on the order defined in the grid. You can create a work that opens the capsule screens in sequence by attaching capsule buttons to each cell of the capsule binder. That is, when a slide opened from a certain square is regarded as one page, a work that displays a plurality of pages in order can be created.

  In this way, by changing the mount, capsule binder, and capsule button, the composition of the screen of the work can be freely changed.

  Next, more detailed processing will be described. With reference to FIG. 2, a method for pasting multimedia content materials and parts onto a mount / capsule screen will be described.

  A window denoted by reference numeral 201 is a controller. The controller 201 starts an operation for content editing processing according to the present embodiment. The controller 201 has a function for generating a mount, a function for displaying a browser for handling various materials, and the like. Is displayed.

  When these various icons are clicked, a photo browser screen 202 displaying a photo icon 202a displayed by a thumbnail of the photo, a sound browser screen 203 displaying a sound icon 203a, a parts box screen 204, a video browser screen 209, Each of, is displayed. The parts box screen 204 includes a capsule button 204a, text 204b, a closing button 204c, a homepage link button 204d, a simultaneous button 204e, and an arrow button 204f which is a connected part.

  When the scanner button 202b on the photo browser screen 202 is clicked, the image scanner screen 207 is displayed. For example, when the preview button 207a is clicked, an actual preview screen 207b is displayed. When the recording button 203b of the sound browser 203 is clicked, various settings relating to the sound can be made, and the sound recorder 205 is displayed to record the voice and capture the recorded sound, and playback, stop 205b, and recording 205a are possible.

  When the capsule button 204a of the parts box 204 is dragged and dropped to a predetermined position on the mount 206 and the sound button 203a is dragged and dropped at the same place, the sound button and the capsule button are overlapped. When the capsule screen 208 is displayed, a preview 207b of the image scanner screen 207 can be displayed by, for example, drag and drop, a text icon is displayed by the text button 204b of the parts box 204, and a close icon is displayed by the close button 204c. Can be made. When the sound button and the capsule button are overlapped, a sound is produced at the same time as the capsule screen 208 is displayed.

The procedure for producing a work composed of one mount and one capsule screen shown in FIG. 2 is as follows, for example.
(1) The mount icon 201a of the controller 201 is dragged and dropped onto the screen to display the mount 206.
(2) Drag and drop the photo icon 201b of the controller 201 to display the photo browser 202.
(3) From the photo browser 202, drag and drop the greengrocer's storefront photo onto the mount 206 and paste it.
(4) Drag and drop the component icon 201c of the controller 201 to open the component box 204.
(5) Drag and drop the capsule button 204a from the component box 204 onto the pear of the photo on the mount 206 and paste it.
(6) The capsule button pasted in (5) is opened, and the capsule screen 208 is displayed.
(7) Drag and drop the scanner icon 202b from the photo browser 202 to display the image scanner screen 207.
(8) The preview button 207a on the image scanner screen 207 is clicked to display a thumbnail 207b of the pear photo being set in the image scanner in the preview area.
(9) The range to be captured is determined by dragging the rectangle displayed on the thumbnail in the preview area of the image scanner screen 207 with the mouse.
(10) The rectangle specified in (9) is dragged and dropped onto the capsule screen 208, a pear photograph is taken from the image scanner, dragged and dropped onto the capsule screen 208, and pasted.
(11) Drag and drop the text component 204b from the component box 204 onto the capsule screen 208, and enter “pear close-up” therein.
(12) Drag and drop the text part 204b from the parts box 204 onto the mount 206 and paste it in the box.
(13) A button 204c to be closed from the component box 204 is dragged and dropped on the capsule screen 208 and pasted.
(14) Drag and drop the sound icon 201d of the controller 201 to display the sound browser 203.
(15) The sound button 203 is dragged and dropped from the sound browser 203 onto the capsule button pasted in (5) above to generate and paste a sound button.
(16) Drag and drop the icon 203b from the sound browser 203 to display the sound recorder 205.
(17) Click the recording button of the sound recorder 205 and input the voice “This orange is from Ehime” from the connected microphone.
(18) Click the stop button 205b of the sound recorder 205 to stop recording. In response to this, a sound button for reproducing the sound recorded in (17) is automatically generated on the sound recorder 205.
(19) Drag and drop the sound button generated in (18) onto the mandarin orange photo pasted in (3) and paste it.
(20) Drag and drop the homepage link button 204d from the parts box 204 onto the apple of the photo pasted in (3) and paste it.
(21) Specify the URL of the homepage where the state of the apple production is posted as the link destination in the homepage link button 204d pasted in (20).

  Through the above processing, a work in which one mount and one capsule screen are associated is completed. For example, when the button on the pear is clicked, a pear photo capsule screen 208 is opened with a voice explanation of the pear. When the close button on the opened pear screen is clicked, the capsule screen 208 can be closed. Clicking the button above the apple will launch a WWW browser and display the linked home page. When the button above the orange is clicked, the voice input in the process (17) is reproduced.

  In the process (8), it is possible to determine the size of an image to be captured and capture and to generate a photograph displaying the image at a time by a drag-and-drop operation. The size of the captured image can be set according to the size of the mount of the drop destination. You can also paste thumbnails directly into your work, so you don't need to save them to a file. Therefore, the editor can capture a photo without being aware of the size of the image or the saved file.

  Next, a method for specifying the execution order of buttons on the mount / capsule screen will be described with reference to FIGS. When the work shown in FIGS. 3 and 4 is activated in the automatic reproduction mode, a button pasted on the work is automatically executed.

  There are four methods (a) to (c) for defining the button execution order on the mount / capsule screen. (A) A method of individually specifying the extension. (A) A method of sorting in accordance with the label value included in the button. (C) A method in which the order is designated by arrow parts, etc. (d) A method in which the execution order of processing is given to each cell provided on the mount as an attribute, and the order is designated by pasting a button part on this. .

  Here, (a) is referred to as the forward mode, (b) is referred to as the label order mode, (c) is referred to as the specified order mode using the arrow parts, and (D) is referred to as the forward mode according to the grid. Any of the above modes can be specified for the mount / capsule screen.

FIG. 3 shows a work in which four capsule buttons are pasted on the mount 301.
In fact, it is a work that shows the fullness of the moon. Clicking on the capsule button (from 1 to 4) above the moon enlarges the capsule screen showing an example of how the moon looks. For example, when the four capsule buttons are desired to be executed in the order close to the sun, the order can be defined by the method (a). The operating procedure for defining is described below.

(1) Activate the forward mode given from the mount 301 in an extended manner. (2) Click the button that says “Day 1”. (3) Click on the button labeled “Day 3”. (4) Click the button labeled 7th day. (5) Click on the button labeled 14th day. This completes the process.
When the extended designation mode is activated in (1), the click operation becomes the order designation operation. In (2) to (5), click the buttons in the order you want to execute. A tag indicating the order by number is displayed on the button to which the order is assigned.
You can exit this mode by clicking other than the button. Buttons that are not assigned an order are sorted in the order from the top left of the screen and are arranged at the end of the order.

  The example shown in FIG. 3 is an example in the case where operations are executed in the order from the sun, but in addition to the method (a), the order can also be defined using the method (a) described below. .

  Four buttons display labels. In (A), the execution order of the buttons is the order sorted in the character code order using the character string of the label as a key. The contents of the label are “1st day”, “3rd day”, “7th day”, and “14th day”. When the labels of the four buttons are sorted, they are in the order of “1st day”, “3rd day”, “7th day”, “14th day”, and the buttons are executed in this order.

  FIG. 4 is a diagram illustrating an example of a work that defines an execution order between two buttons using an arrow part (a connected part). With reference to this work example, the execution method designation method and the execution time interval designation method of (c) will be described.

Two capsule buttons 401a and 401b and an arrow part 401c are pasted on the mount 401, and an arrow part 401c is pasted between the two capsule buttons 401a and 401b. The arrow component 401c can be generated from the component box 402 by drag and drop, like the capsule button.
An arrow component 401c on the mount 401 has a function of sequentially transmitting events to the two capsule buttons 401a and 401b arranged at both ends.

  The shape of the arrow itself represents the direction, and the button parts are processed in the order indicated by the direction. That is, the arrow component 401c has a start point and an end point, and is executed in the order of a button located near the start point and a button located near the end point. Therefore, the button to be executed first may be arranged near the start point of the arrow part 401c, and the button to be executed next may be arranged near the end point.

  In the case of the work shown in FIG. 4, the process is executed in the order of a button 401 a labeled “July 7” and a button 401 b labeled “July 14”. The arrow component 401c may include time information on the execution interval of the two buttons 401a and 401b, that is, time interval information from when the button near the start point is executed to when the button near the end point is executed. This time interval information can be designated by inputting a numerical value on the execution interval designation screen 403 opened from the arrow part 401c.

  FIG. 5 is a diagram illustrating how colors, fonts, and frame attributes are changed for objects on a work. As shown in FIG. 5, the attribute change setting screen 502 is a screen for changing the background color attribute, character attribute, and frame attribute of the object. A background color setting button 502a, a character attribute setting button 502b such as a character size, a font, a character style, and a character color; , Is displayed. These buttons display the current attribute value currently specified. The current attribute value can be changed by a menu dialog opened from an inverted triangle button located on the right side of each button. In addition, the buttons for setting these attributes are surrounded by lines in pairs for each of the background color attribute, the character attribute, and the frame attribute. It can be seen that the figures surrounded by the lines are surrounded by another line from the outside, and the display is classified hierarchically.

  In order to change a certain attribute, the object to be changed on the screen being edited is selected and the button of the target attribute in the attribute change setting screen 502 is clicked, or the attribute change setting screen 502 Drag and drop the button with the desired attribute to the object to be changed. It is also possible to collectively change a plurality of attribute groups or all attributes, each of which is a set of related attributes such as character size, font, character style, and character color. In that case, the figure surrounding the attribute button is dragged and dropped onto the object to be changed.

  For example, an operation method for collectively setting character attributes such as the character size, font, character style, and character color specified on the attribute change setting screen 502 to the text material object 503a at the lower end on the mount screen 503 is as follows. It is as follows.

(1) The “color / font / frame” icon 501a of the controller 501 is dragged and dropped to display the attribute change setting screen 502. (2) In the attribute change setting screen 502, character attributes such as the character size, font, character style, and character color to be changed are designated. (3) Drag and drop the figure surrounding the character attribute button on the attribute change setting screen 502 to the text material object 503 a at the bottom of the mount screen 503.

  By the same operation, all the attributes, that is, the background color, the character attribute, and the frame attribute can be set collectively. In this case, in the above procedure (3), the figure surrounding the background color 502a, the character attribute 502b, and the frame attribute 502c on the attribute change setting screen 502 may be dragged and dropped onto the target object. It has been described that the current attribute value on the attribute change setting screen 502 can be specified by a menu dialog. In addition to this operation, there is also a method of designating the current attribute value by a drag and drop operation to the object attribute change setting screen 502 on the screen being edited. In this case, in addition to an operation for designating one attribute, an operation for designating a plurality of attributes at a time is also possible. When one attribute is specified, an object on the work having the attribute value to be specified is dragged and dropped onto a target attribute button on the attribute change setting screen 502. On the other hand, when a plurality of attributes, for example, all character attributes are specified at once, an object on the work is dragged and dropped onto a figure surrounding the character attributes on the attribute change setting screen 502. When all the attributes, that is, the background color, the character attribute, and the frame attribute are specified at once, the graphic 502a, 502b, and 502c enclosing the background color, character attribute, and frame attribute on the attribute change setting screen 502 are displayed on the work. Drag and drop the object.

  Next, with reference to FIG. 6, a method for pasting buttons on the capsule binder and a method for specifying the execution interval of buttons on the capsule binder will be described. As described above, by using the capsule binder 602, it is possible to create works that display slides in order. The mechanism for displaying slides in order is as follows.

  The capsule binder 602 is partitioned into a grid, for example, a square lattice, and each grid is assigned a number, for example. By pasting button parts on the cells to which the numbers are assigned, the execution order of the parts is defined. Each cell of the capsule binder 602 has a slot for event transmission. Each cell is given an order as described above, and the order is defined by the position of the cell. When the automatic reproduction mode is activated, the capsule binder 602 sequentially transmits events to the cells according to the defined order. As a result, the event is transmitted to the button component pasted on the grid, and the button that receives the event executes the respective processes.

  If you paste a capsule button or a homepage link button that has a function to open another screen, it will be a work in which slides are displayed in order. In addition, one or more button parts can be pasted in the same cell, and when the capsule binder transmits an event to the cell, one or more button parts pasted in the same cell are attached. Convey events at the same time. Upon receiving this, the button parts in the same cell operate simultaneously. Therefore, a screen opened from one or more buttons pasted in the same cell can be a component of the same slide.

FIG. 6 shows a capsule binder work. The procedure for making this work is, for example, as follows.
(1) Drag and drop the capsule binder icon 601b of the controller 601 to generate a capsule binder 602. (2) Drag and drop the component icon 601c of the controller 601 to open the component box 606. (3) Drag and drop the capsule button 606a from the component box 606 onto the first grid of the capsule binder 602 and paste it. (4) The capsule button pasted in (3) is opened, and the capsule screen 603 is displayed. (5) Drag and drop the text component 606b from the component box 606 onto the capsule screen 603, and input “Investigated about fruit”. (6) Drag and drop the sound icon 601a of the controller 601 to display the sound browser 604. (7) A sound button is created and pasted by dragging and dropping a sound effect sound icon from the sound browser 604 onto the first cell of the capsule binder 602. (8) Drag and drop the homepage link button 606e from the parts box 606 onto the second grid of the capsule binder 602 and paste it. (9) Enter the URL of the homepage explaining “mandarin orange” as the link destination in the homepage link button 606e pasted in (8). (10) Drag and drop the capsule button from the component box 606 onto the second grid of the capsule binder 602 and paste it. (11) The capsule button pasted in (10) is opened, and the capsule screen 608 is displayed. (12) Drag and drop the text component 606b from the component box 606 onto the capsule screen 608, and input "Checked about oranges". (13) Drag and drop the work icon 607 a “Description of apple” in the drawer 607 onto the third grid of the capsule binder 602.

  A capsule button 606a and a sound button 601a are attached to the first cell of the capsule binder 602, a homepage link button 606e and a capsule button 606a are applied to the second cell, and a capsule button 606a is applied to the third cell. Yes. A slide consisting of one capsule screen from the first square, a slide consisting of a capsule screen and a WWW browser screen from the second square, and a slide consisting of one capsule screen from the third square, A work consisting of three slides is completed. The sound is played at the same time as the first slide opens.

  It is also possible to insert an existing work as a capsule screen that opens from another work by drag and drop operation. For example, in the above process (13), drag and drop the work “Apple's explanation” stored in the drawer onto the grid and include the work screen of “Apple's explanation” on the drop-down grid. Generate a capsule button. Clicking this capsule button will open the “Apple Description” screen.

The numerical value for each capsule binder is the event transmission interval from the current cell to the next cell when starting in auto play mode, that is, the time interval from displaying the current slide to displaying the next slide. Can be specified, but if there is a movie or sound in each slide, and the playback time is longer than the specified numerical time, the switching time is extended to that playback time .
The switching time can be the playback time of the sound or video contained in the capsule button affixed on the grid. As a result, it is possible to avoid the interruption of the reproduction of the sound or moving image due to the switching of the slide. In the work of FIG. 6, if the transmission interval of the event to the grid is 3 seconds and the playback time of the sound of the first grid is 10 seconds, the time to switch to the second slide is 10 seconds and it switches to the third slide. Time is 3 seconds.

As an operation for changing the display order of the slide, there are an operation for moving a slide component (such as a capsule button) to another cell, and an operation for moving the entire cell. The former is the same as on the mount, grabbing the component and dragging it, and dropping it on the destination grid. In the latter case, grab and drag the cell and drop it at the destination.
At this time, the capsule binder determines from the drag start position whether the operation is for the grid or for the button.

  Next, with reference to FIG. 7, a description will be given of an execution order of buttons and a method of specifying an execution target in a calendar capsule binder in which the capsule binder function is expanded.

  As shown in FIG. 7, the calendar capsule binder 701 is obtained by adding calendar information to the capsule binder. When year / month information is input in a dialog opened from the “year / month setting” button 701a of the calendar capsule binder 701, a date is associated with each cell, and the date is displayed on each cell. When the buttons on the grid are automatically executed by starting the automatic reproduction mode, the buttons to be executed can be narrowed down on the automatic execution target button setting screen 702. On the automatic execution target button setting screen 702, a specific day of the week is specified as a condition, and as a result, the buttons in the fourth column are targets for automatic execution. The execution order among the buttons in the fourth column is the date order. As shown in the figure, it is possible to easily display how the month is filled in each date in July 2002. When July 3 is clicked, the state 703 of the moon on July 3 is displayed with sound effects. Clicking on July 10 displays a month appearance 704 on July 10 and clicking on July 24 displays a moon appearance 705 on July 24 together with comments.

  FIG. 8 is a diagram showing communication channels between components called slots. In the present embodiment, the concept of slot is introduced as a mechanism for operating other button parts, a mount / capsule screen, and a capsule binder screen in response to a mouse event for clicking a button part. The slot is a communication channel between other parts such as a button part and a mount / capsule screen, a button part and a capsule binder, and a button part and a button part. There are multiple types of slots with different functions, each with a name.

  For example, when an open slot of a capsule button receives a click mouse event, it reports that the event was in its open slot. If the sound button is overlaid at this time, the play slot and the open slot of the sound button are combined, and the event transmitted to the capsule button is also transmitted to the play slot of the sound button and the specified sound is played. To do.

  FIG. 8 shows each part, the name of the slot attached to it, and the operation when an event occurs in that slot. A part that ends with a “button”, such as a XX button, is a part that receives a mouse click event and transmits the event to its own slot.

  FIG. 9 is a flowchart showing the flow of main processing of the present embodiment. When the process is started, a controller is first displayed in step 901. When an operation input is made in step 902, in step 903, it is determined on which window the operation was performed, and the process branches. In step 904, an operation on the controller is processed. If the result is an end operation, it is determined in step 905 whether the process is ended. If not completed, the process returns to step 902.

  If the determination result in step 903 is an operation in the drawer, go to step 906. If the operation is on the photo browser, go to step 907. If it is an operation on the video browser, go to step 909. If it is an operation above, go to Step 908. If it is an operation on the mount / capsule screen, go to Step 910. If it is an operation on the capsule binder, go to Step 911. If there is, the operation branches to step 912. If the operation is on the image scanner screen, the operation branches to step 913. If the operation is on the component box, the operation branches to step 915. After completion of each operation, the process returns to step 902 again.

  FIG. 10 is a flowchart showing the flow of the operation process 904 on the controller. In step 1001, the operation is determined. If the operation is an end operation, a value of “end” is returned. If the determination result in step 1001 is the generation of the mount, the process branches to step 1002 to generate the mount with the mouse release position as the upper left corner. If the capsule binder is generated, the process branches to step 1003 to generate the capsule binder with the mouse release position as the upper left corner.

  If it is a drawer display, the process branches to step 1004 to display the drawer with the mouse release position as the upper left corner. If it is the display of the photo browser, the process branches to step 1005, and the photo browser is displayed with the mouse release position as the upper left corner. If the display is a sound browser, the process branches to step 1006 to display the sound browser with the mouse release position as the upper left corner. If the display is a video browser, the process branches to step 1007, and the video browser is displayed with the mouse release position as the upper left corner. If it is the display of the parts box, the process branches to step 1008 to display the parts box with the mouse release position as the upper left corner.

  If the attribute setting tool screen is displayed, the process branches to step 1009 to display the attribute setting tool screen with the mouse release position as the upper left corner. If it is switching to the trial mode, the process branches to step 1010, and the mode is switched to the test mode. If the mode is switched to the creation mode, the process branches to step 1011 to switch to the mode creation mode. Return is made after the end of each operation (return to step 902 in FIG. 9).

  Next, operations on the component box will be described with reference to FIG. Reference is also made to FIGS. 1 and 2 as appropriate. FIG. 11 is a flowchart showing an operation flow (915) in the component box. As shown in FIG. 11, first, in step 1101, the press position of the mouse 104 is determined. If it is on the capsule part, in step 1102, the capsule part is set to the variable “part” by drag and drop operation. (Substitute the value of the variable). If the mouse press position is on the close button 204c, the close button is set in the variable “component” in step 1103. If the press position of the mouse 104 is on the simultaneous button 204e, the simultaneous button 204e is set in the variable “component” in step 1104. If the press position of the mouse 104 is on the homepage link button 204d, the homepage link button 204d is set in the variable “component” in step 1105. If the press position of the mouse 104 is on the arrow 204f, an arrow part is set in the variable “part” in step 1106. If the press position of the mouse 104 is on the text part 204b, the text part is set in the variable “part” in step 1107. If the press position of the mouse 104 is other than that, the process returns.

  If a value is set in the “component” variable, it is determined in step 1108 whether or not the mouse event is a drag-and-drop. If the mouse event is a drag-and-drop, the process returns to step 1109. If not, the process returns. To do. In step 1109, it is determined whether the drop position is on the mount / capsule screen or on the capsule binder. If the drop position is on the mount / capsule screen, the process proceeds to step 1110, where the drop position is on the capsule binder. If not, return to Step 1111, otherwise return.

  In step 1111, it is determined whether the variable “part” is a capsule button or a homepage link button on the capsule binder. If so, the process returns to step 1112. In step 1110, after calling the component generation procedure in the mount / capsule screen with the variable “component” as an argument, the process returns.

  In step 1112, after calling the component generation procedure in the capsule binder with the variable “component” as an argument, the process returns.

  Next, component generation processing on the mount / capsule screen will be described with reference to FIG. Reference is also made to FIGS. 1 and 2 as appropriate. As shown in FIG. 12, it is a flowchart showing the flow of the component generation process (910) on the mount / capsule screen. As shown in FIG. 12, in step 1201, an argument component is generated with the mouse release position as the upper left corner. In step 1202, it is determined whether the argument component is the text 204b or the arrow 204f, or whether the paste destination is the text or the photograph or the arrow. Will return.

  In step 1203, the process branches depending on the argument component. If the part is the close button 204c, the process proceeds to step 1204. If the paste destination is either a capsule button, a close button, a simultaneous button, a homepage link button, a sound button, a mount / capsule screen, the close button in step 1205 Call the slot combination procedure with a component as an argument.

  If the part is the capsule button 204a, if the paste destination is a capsule button, a close button, a simultaneous button, a homepage link button or a sound button in step 1206, the capsule button slot combining procedure is used in step 1207 with the part as an argument. Call. If the part is the simultaneous button 204e, in step 1208, if the paste destination is a capsule button, a close button, a simultaneous button, a homepage link button, or a sound button, in step 1209 the slot combination procedure for the simultaneous button is performed. Is called as an argument.

  If the part is the sound button 201d, in step 1210, if the paste destination is a capsule button, a close button, a simultaneous button, a homepage link button, or a sound button, the sound button slot combining procedure is performed in step 1211. Is called as an argument. If the part is the homepage link button 204d, if the pasting destination is a capsule button, a close button, a simultaneous button, a homepage link button or a sound button in step 1212, in step 1213, a slot link procedure for the homepage link button 204d. Is called with the part as an argument. Return after the above processing is completed.

  Next, component generation processing will be described with reference to the drawings. FIG. 13 is a flowchart showing the flow of the part generation processing 911 on the capsule binder. This will be described with reference to FIGS. As shown in FIG. 13, in step 1301, it is determined whether or not the mouse release position is above the grid. Will return. In step 1302, it is determined whether the argument component is the capsule button 204a, the homepage link button 204d, or the sound button 201d. If it is any of these, the process proceeds to step 1303.

  In step 1303, an argument part is generated on the cell at the mouse release position. In step 1304, the process branches depending on the argument component. If the part is the capsule button 204a, in step 1305, the slot combination procedure of the capsule button 204a is called with the part as an argument. If the part is the homepage link button 204d, in step 1306, the slot combination procedure of the homepage link button 204d is called with the part as an argument. If the part is the sound button 201d, in step 1307, the slot combination procedure of the sound button 201d is called with the part as an argument. Return after the above processing.

Next, the capsule button slot combining process will be described with reference to the drawings.
FIG. 14 is a flowchart showing the flow of the capsule button slot combination processing 1305. Reference is made to FIGS. As shown in FIG. 14, the paste destination is determined in step 1401, and if the paste destination is the homepage link button 204d, the open slot of the argument capsule button 204a is pasted in step 1402 to the homepage link button of the paste destination. Combine with 204d browser open slot. If the paste destination is the close button 204c, in step 1403, the open slot of the argument capsule button 204a is combined with the event transmission slot of the close button of the paste destination. If the pasting destination is the capsule button 204a, the open slot of the capsule button 204a as an argument is combined with the open slot of the pasting capsule button in step 1404. If the pasting destination is the simultaneous button 204e, in step 1405, the open slot of the argument capsule button is combined with the event transmission slot of the pasting destination simultaneous button. If the pasting destination is the sound button 201d, the open slot of the argument capsule button 204a is combined with the play slot of the pasting sound button 201d in step 1406. If the paste destination is the cell of the capsule binder 602 (FIG. 6), the open slot of the capsule button of the argument is combined with the event transmission slot of the cell of the capsule binder 602 of the paste destination in step 1407. Return after the above processing.

  Next, the close button slot combination processing 1205 will be described with reference to the drawings. This will be described with reference to FIGS. FIG. 15 is a flowchart showing the flow of the slot combining process for the close button. As shown in FIG. 15, the paste destination is determined in step 1501, and if the paste destination is the capsule button 204a, the event transmission slot of the close button of the argument is set in step 1502 to the capsule button 204a of the paste destination. Combine with an open slot. If the paste destination is the close button 204c, in step 1503, the event transmission slot of the close button of the argument is combined with the event transmission slot of the close button of the paste destination. If the pasting destination is the homepage link button 204d, in step 1504 the event transmission slot of the close argument button is combined with the browser open slot of the pasting homepage link button. If the pasting destination is the simultaneous button 204e, the event transmission slot of the button for closing the argument is combined with the event transmission slot of the pasting destination simultaneous button in step 1505. If the pasting destination is the sound button 201d, in step 1506, the event transmission slot of the button for closing the argument is combined with the play slot of the pasting sound button. If the pasting destination is the mount 206 / capsule screen 208, the event transmission slot of the close argument button 204c is combined with the closed slot of the pasting mount / capsule screen in step 1507. Return after the above processing.

  Next, the slot link process of the home page link button will be described with reference to the drawings. Reference is made to FIGS. FIG. 16 is a flowchart showing the flow of the slot link process for the homepage link button. As shown in FIG. 16, the paste destination is determined in step 1601, and if the paste destination is the capsule button 204a, the browser open slot of the homepage link button 204d of the argument is pasted in the capsule button 204d in step 1602 Combine with open slots. If the paste destination is the close button 204c, the browser open slot of the homepage link button 204d of the argument is combined with the event transmission slot of the close button 204c of the paste destination in step 1603. If the pasting destination is the homepage link button 204d, in step 1604, the browser open slot of the homepage link button 204d of the argument is combined with the browser open slot of the homepage button of the pasting destination. If the paste destination is the simultaneous button 204e, in step 1605, the browser open slot of the homepage link button of the argument is combined with the event transmission slot of the paste destination simultaneous button 204e. If the paste destination is the sound button 201d, the browser open slot of the argument home page link button 204d is combined with the play slot of the paste destination sound button in step 1606. If the paste destination is the cell of the capsule binder 602 (FIG. 6), the browser open slot of the homepage link button 204d of the argument is combined with the event transmission slot of the cell of the capsule binder 602 as the paste destination in step 1607. Return after the above processing.

Next, sound button slot combination processing will be described with reference to the drawings.
FIG. 17 is a flowchart showing the flow of sound button slot combination processing. This will be described with reference to FIGS. As shown in FIG. 17, the paste destination is determined in step 1701, and if the paste destination is a capsule button, the play slot of the argument sound button 201d is changed to the open slot of the capsule button of the paste destination in step 1702. Combine with. If the paste destination is the close button 204c, in step 1703 the argument sound button 201d play slot is combined with the paste destination close button 204c event transmission slot. If the pasting destination is the home page link button 204d, the play slot of the argument sound button 201d is combined with the browser open slot of the pasting home page button 204d in step 1704. If the paste destination is a simultaneous button, in step 1705, the play slot of the argument sound button is combined with the event transmission slot of the paste destination simultaneous button. If the paste destination is the sound button 201d, in step 1706, the play slot of the argument sound button 201d is combined with the play slot of the paste sound button 201d. If the paste destination is the cell of the capsule binder 602 (FIG. 6), the play slot of the argument sound button is combined with the event transmission slot of the cell of the capsule binder 602 of the paste destination in step 1707. Return after the above processing.

  Next, the simultaneous button slot combination processing will be described with reference to the drawings. FIG. 18 is a flowchart showing the flow of the simultaneous button slot combination processing. This will be described with reference to FIGS. In step 1801, the paste destination is determined. If the paste destination is a capsule button, in step 1802, the event transmission slot of the argument simultaneous button 204e is combined with the open slot of the paste-up capsule button. If the paste destination is the close button 204c, the event transmission slot of the simultaneous argument button 204e of the argument is combined with the event transmission slot of the close button 204c of the paste destination in step 1803. If the pasting destination is the homepage link button 204d, the event transmission slot of the argument simultaneous button 204e is combined with the browser open slot of the pasting homepage link button in step 1804. If the pasting destination is the sound button 201d, in step 1805, the event transmission slot of the argument simultaneous button 204e is combined with the play slot of the pasting sound button 201d. If the paste destination is the simultaneous button 204e, in step 1806, the event transmission slot of the argument simultaneous button 204e is combined with the event transmission slot of the paste destination simultaneous button 204e. Return after the above processing.

  Next, an operation process 910 on the mount / capsule screen will be described. FIG. 19 is a flowchart showing the flow of operation processing on the mount / capsule screen. This will be described with reference to FIGS. As shown in FIG. 19, the operation on the mount / capsule screen varies greatly depending on whether the mode is an “automatic reproduction mode”, a “creation mode”, or a “trial mode”. The “automatic playback mode” is a mode for viewing a work. When this mode is activated, the buttons on the mount / capsule screen are automatically executed. “Making mode” is a mode for editing a work. In this mode, the capsule button, sound button, close button, simultaneous button, and homepage link do not work as buttons. That is, the part is only selected without executing the predetermined function shown in FIG. 8 by the left click event of the mouse. The “trial mode” is a content execution mode. In this mode, the parts of the buttons perform the function as the original buttons.

  As shown in FIG. 19, the operation is determined in step 1901. If the operation is an automatic reproduction start operation, the process branches to step 1905. If the operation is an automatic reproduction end operation, the process branches to step 1914. If yes, the process branches to step 1902. In step 1905, it is determined whether or not the mode is the automatic reproduction mode. If the mode is not the automatic reproduction mode, the mode is switched to the automatic reproduction mode in step 1906. In step 1907, the mount / capsule screen currently being operated is used as an argument. Call the automatic playback procedure on the mount / capsule screen and return.

If it is determined in step 1905 that the automatic reproduction mode is selected, the process returns without doing anything. In step 1914, it is determined whether the mode is the automatic playback mode. If the mode is the automatic playback mode, the process proceeds to step 1915. If the mode is not the automatic playback mode, the process returns. In step 1915, the automatic reproduction is terminated.
In step 1916, the automatic regeneration mode is canceled, the mode set by the controller is switched, and the process returns.

In step 1902, the mode is determined. If it is a trial mode, the process proceeds to step 1903. If it is the creation mode, the process proceeds to step 1913.
If it is in auto play mode, it returns. In step 1903, the type of operation is determined. If it is a mouse click operation, the process branches to step 1904. If it is not a mouse click operation, it returns. In step 1904, the mouse click position is determined. If the click is on the capsule button 204a, the event procedure from the capsule button 204a to the bottom is called with the capsule button 204a clicked in step 1908 as an argument. If it is a click on the close button 204c, the event procedure from the top to the bottom of the close button 204c is called with the close button 204c that was clicked in step 1911 as an argument. If it is a click operation on the simultaneous button 204e, the event procedure from the top to the bottom of the simultaneous button 204e is called with the simultaneous button 204e clicked in step 1909 as an argument. If the click operation is performed on the homepage link button 204d, the event procedure from the top to the bottom of the homepage link button is called with the homepage link button 204d clicked in step 1912 as an argument. If the click operation is on the sound button 201b, the event procedure from the top to the bottom of the sound button is called with the sound button 201d clicked in step 1910 as an argument. Otherwise, return. Return after the above processing.

  Next, the editing operation processing 913 on the mount / capsule screen will be described with reference to the drawings. FIG. 20 is a flowchart showing the flow of the editing operation on the mount / capsule screen. As shown in FIG. 20, in step 2001, a determination is made regarding the content of the operation. If the operation is an operation that gives the execution order of the buttons in an extended manner, in step 2002, the argument is attached to the mount / capsule currently being operated. The execution order of buttons is extended as a screen, and the grant procedure is called to return. If the operation is an operation for switching to the forward mode given in an extended manner, in step 2003, the button execution order mode is switched to the forward mode given in an extended manner, and then the process returns. If the operation is a switching operation to the label order mode, in step 2004, the button execution order mode is switched to the label order mode and then the process returns. If the operation is a switching operation to the designated order mode using the arrow component, in step 2005, the button execution order mode is switched to the designated order using the arrow component, and the process returns. If the operation is to change the screen size by drag-and-drop, the screen size is changed in step 2006 and then the process returns. If the operation is a change of the display position of the screen by drag and drop, the process returns after changing the display position of the screen in step 2007. If the operation is an operation for closing the screen, the screen display position and the screen size are recorded in step 2008, and the screen is closed in step 2009. The “extending order mode”, “label order mode”, and “designated order mode using arrow parts” will be described later.

Other operations are omitted in this specification for the following two reasons.
(1) Button combination editing is the same as the algorithm used when generating a component. (2) Specifying the link destination of the homepage link button, editing the label of the button, changing the attributes of the material and parts, such as setting the video playback mode, and editing the material and parts are performed using general multimedia editing software (so-called It is the same as that called drawing software).

  Next, a process for extending the execution order of the buttons in an extended manner will be described with reference to the drawings. FIG. 21 is a flowchart showing the flow of processing for assigning the execution order of buttons in an extended manner. This will be described with reference to FIGS. As shown in FIG. 21, in step 2101, a list of buttons pasted on the argument mount / capsule screen is acquired and stored in the variable child button list. In step 2102, the child button list acquired in step 2101 is sorted in order from the upper left origin using the upper left coordinates of the button as a key, and stored in the variable coordinate order button list. In step 2112, the ordered list is initialized. In step 2103, 1 is substituted into the variable current number for initialization. In step 2104, the event is monitored and the event is waited for. If an event has occurred, the process proceeds to step 2105. The contents of the event that occurred in step 2105 are determined. If it is a button click event, the process branches to step 2114. If it is a click event other than a button, the process branches to step 2113. Monitor events.

  In step 2113, the first button in the coordinate order button list is added to the already-assigned button list in order, and the process returns. It is determined whether the button clicked in step 2114 has been registered in the order-assigned button list. If it has been registered, the process returns to step 2104 to monitor the event. If not registered, the process proceeds to step 2106. A current number is assigned to the button clicked in step 2106, and a tag displaying the number is displayed on the upper right of the button, and the process proceeds to step 2107. In step 2107, the current number is incremented. In step 2108, the clicked button is registered in the order-assigned button list. The button clicked in step 2109 is deleted from the coordinate order button list. In step 2111, it is determined whether the coordinate order button list is empty, and if it is empty, the process returns. If the coordinate order button list is not empty, the process returns to step 2104 to monitor the event. In step 2113, the first button in the coordinate order button list is added to the already-assigned button list in order, and the process returns.

  Next, automatic reproduction processing on the mount / capsule screen will be described with reference to the drawings. FIG. 22 is a flowchart showing the flow of automatic reproduction processing on the mount / capsule screen. As shown in FIG. 22, when automatic reproduction is started, the buttons pasted on the mount / capsule screen are automatically executed. The execution order can be specified from any one of the following three modes, ie, “extended order mode”, “label order mode”, and “designated order mode using arrow parts”.

  In the “externally assigned order mode”, processing is executed in the order in which buttons are clicked and extended externally. In the “label order mode”, the processing is executed in the order of the button labels. In the “designation order mode using arrow parts”, the buttons connected by the arrow parts are processed in the order indicated by the arrow parts.

  In step 2201, the execution order mode is determined. If it is in the label order mode, the process proceeds to step 2203. If it is in the designation order mode using the arrow parts, the process proceeds to step 2204. In step 2204, the automatic reproduction procedure in the designation order using the arrow parts is called with the mount / capsule screen as an argument.

  In step 2202, a list of buttons pasted on the argument mount / capsule screen is acquired, substituted in the variable child button list, and the process proceeds to step 2205. In step 2205, the child button list acquired in step 2202 is sorted in the order of extension, and the process proceeds to step 2207. In step 2203, a list of buttons pasted on the mount / capsule screen of the argument is acquired, substituted in the variable child button list, and the process proceeds to step 2206. In step 2206, the child button list acquired in step 2203 is sorted in the order of labels set in the buttons, and the process proceeds to step 2207. In step 2207, the time interval set on the mount / capsule screen is acquired and substituted into the variable T. This time interval is an interval from the current button to the next button. In step 2208, the button registered at the beginning of the sorted child button list is acquired and substituted into the variable execution button.

  In step 2209, the type of the execution button is determined. If it is a capsule button, the process proceeds to step 2211. If it is a homepage link button, the process proceeds to step 2212. If it is a sound button, the process proceeds to step 2213. If yes, the process branches to step 2214. If it is any other button, the process proceeds to step 2217. A “simultaneous button” exists as a button to be executed, but the description thereof is omitted. If it is any other button, the process branches to step 2217. In step 2211, an event procedure from the bottom to the top of the capsule button is called with the execution button as an argument, and the process proceeds to step 2215. In step 2215, the automatic reproduction procedure on the mount / capsule screen is called recursively as the capsule screen opened from the execute button with the argument. In step 2212, the event procedure from the bottom to the top of the homepage link button is called with the execution button as an argument.

  In step 2213, the event procedure from the bottom to the top of the sound button is called with the execution button as an argument. In step 2214, the event procedure from the bottom to the top of the link button that closes the execution button as an argument is called. In step 2216, a “time waiting timer” is started. In step 2217, it is determined whether or not the execution button is the last in the sorted child button list, and if it is the last, the process returns. If it is not the last, in step 2210, the next registered button in the sorted child button list is substituted into the execution button, and the process returns to step 2209.

  Next, automatic reproduction processing in the specified order using arrow parts will be described with reference to the drawings. FIG. 23 is a flowchart showing the flow of automatic reproduction processing in the specified order using arrow parts. Reference is made to FIGS. As shown in FIG. 23, in step 2301, the time interval set in the argument mount / capsule screen is acquired and substituted into the time interval of the variable mount / capsule screen. In step 2302, the arrow parts present on the argument mount / capsule screen are stored in the unexecuted arrow parts list. In step 2303, the unexecuted arrow parts list is sorted in order from the top left of the screen. In step 2304, the buttons present on the argument mount / capsule screen are stored in the unexecuted button list. In step 2305, the acquisition of a list of parts connected by arrow parts is called with the first argument as an unexecuted arrow list and the second argument as an unexecuted button list, and the returned value is stored in the connected parts list. . In step 2306, it is determined whether the connected parts list is empty. If it is empty, the process returns. If it is not empty, go to Step 2307. In step 2307, the part registered at the beginning of the linked parts list is substituted into the variable part. In step 2308, the time interval of the variable arrow is initialized to 0 hours. In step 2309, the type of the part is determined. If the part is a capsule button, the process branches to step 2310. If the part is a homepage link button, the process branches to step 2311. If the part is a sound button, The process branches to step 2312. If the part is a close button, the process branches to step 2316. If the part is an arrow part, the process branches to step 2314. If the part is another part, the process proceeds to step 2319. A “simultaneous button” exists as a button to be executed, but a description thereof is omitted. In step 2310, an event from the bottom to the top of the capsule button is called with the component as an argument. In step 2315, automatic playback in the order specified by the arrow part is called with the capsule screen opened from the part as an argument. In step 2311, an event from the bottom of the homepage link button to the top is called with the component as an argument. In step 2312, an event from the bottom to the top of the sound button is called with the component as an argument. In step 2316, an event from the bottom to the top of the button that closes the argument as a part is called. In step 2314, the time interval set for the arrow component is substituted into the time interval of the variable arrow. In step 2319, it is determined whether or not the part is at the end of the linked parts list. If it is not the last time, the timer is started for the time set at the time interval of the variable arrow in step 2318 to enter a waiting state.

  In step 2317, the part registered next to the linked parts list is substituted into the variable part, and the process returns to step 2308. In step 2320, the parts in the linked parts list are deleted from the unexecuted arrow list and the unexecuted button list. In step 2321, it is determined whether the unexecuted arrow parts list is empty, and if it is empty, the process returns. If it is not empty, go to Step 2322. In step 2321, it is determined whether the unexecuted button list is empty. If it is empty, the process returns. If it is not empty, the timer is started for the time set for the time interval of the variable mount / capsule screen, and the process returns to the waiting state.

  Next, acquisition of a list of parts connected by arrow parts will be described with reference to the drawings. FIG. 24 is a flowchart showing the flow of processing for acquiring a list of parts connected by arrow parts. Please refer to FIGS. As shown in FIG. 24, in step 2401, a variable connected component list is initialized. In step 2402, the unexecuted arrow list of the first argument is copied and substituted into the variable arrow list. In step 2403, the unexecuted button list of the second argument is copied and substituted into the variable button list.

  In step 2404, the arrow part registered at the beginning of the arrow list is assigned to the variable selection arrow. In the step 2405, a button on the extension line in the direction opposite to the arrow of the selection arrow is searched from the button list among the buttons overlapping with the circle area whose radius is “selection arrow length / 2” and whose center is the selection arrow start point. If it is found, it is stored in the variable selection button. In step 2406, it is determined whether or not a button is found by the search in step 2405. If a button is found, the process branches to step 2407, and if it is not found, the process branches to step 2409. In step 2407, a selection button is registered at the end of the connected component list. In step 2408, the selection button is deleted from the button list. In step 2409, the selection arrow is registered at the end of the connected component list. In step 2410, the selection arrow is deleted from the arrow list. In step 2411, a button on the extension line in the direction of the arrow of the selection arrow is searched from the button list among the buttons overlapping with the circle area whose radius is “selection arrow length / 2” and whose center is the end of the selection arrow. If found, substitute it into the selection button. In step 2412, it is determined whether or not the button has been found in the search processing in step 2411. If it is found, the process branches to step 2413. If not found, the connected parts list is returned. In step 2413, the selection button is registered at the end of the connected component list. In step 2414, the selection button is deleted from the button list. In step 1415, the arrow part overlaps with a circle area whose radius is “selection arrow length / 2” and whose center is the center of the selection button, and the selection button exists on the extension line in the direction opposite to the arrow of the arrow part. Of the arrow parts that satisfy the condition, the arrow part closest to the selection button is searched, and if found, it is substituted into the variable selection arrow. In step 2416, it is determined whether or not an arrow part has been found by the search in step 2415. If an arrow part has been found, the process returns to step 2405. If not found, the connected parts list is returned.

  Next, the flow of the editing operation on the capsule binder will be described. FIG. 25 is a flowchart showing the processing of the editing operation on the capsule binder. Refer to FIG. 6 as appropriate.

  The operation on the capsule binder 602 differs depending on whether the button on the cell or the cell is operated. If you drag and drop a button on the grid, it will be an editing operation for pasting the buttons. When the cell is dragged and dropped, the editing operation of the cell configuration is performed, such as changing the order of the cells or duplicating / deleting the cells.

  As shown in FIG. 25, the content of the operation is determined in step 2501. If the operation is a drag and drop operation of a capsule button or sound button 601a or homepage link button 606e on the grid, the process branches to step 2502. If the operation is a drag-and-drop operation of a square, the process branches to step 2503. The button dragged and dropped in step 2502 is assigned to the variable button. In step 2504, the mouse release position is determined. If the mouse release position is on the trash can icon on the controller, the process branches to step 2505. If the mouse release position is on the grid of the capsule binder, the process branches to step 2506. After discarding the button in step 2505, the process returns.

If there is a slot connection relationship with the button paste destination in step 2506, it is canceled, and in step 2507, the button is moved to the mouse release position, and the flow advances to step 2508. In step 2508, the type of button is determined. If the button is a capsule button, the process branches to step 2509. If the button is the homepage link button 606e, the process branches to step 2510.
If the button is a sound button, the process branches to step 2511. In step 2509, the capsule button slot combination procedure is called with the button as an argument, and the process returns.

  In step 2510, the homepage link button slot combination procedure is called with the button as an argument, and the process returns. In step 2511, the sound button slot combination procedure is called with the button as an argument, and the process returns. In step 2503, the mouse release position is determined. If the mouse release position is on the trash can icon on the controller, the process branches to step 2513. If the mouse release position is on the grid of the capsule binder 602, the process branches to step 2514. In step 2513, the cell deletion procedure is called and the process returns. In step 2514, the move / copy procedure for the cell is called and the process returns.

Next, the processing of the cell move / copy operation will be described with reference to the drawings. Reference is made to FIG. 6 as appropriate. FIG. 26 is a flowchart showing the flow of the cell move / copy operation. As shown in FIG. 26, in step 2601 the cell number being dragged is acquired and substituted into the variable drag cell number. In step 2602, the drop destination number is acquired and substituted into the variable drop number. In step 2603, the drop destination number is substituted into the variable insertion destination number. In step 2604, the largest number among the cell numbers to which the buttons are attached is acquired and substituted for the final variable number. In step 2605, it is determined whether or not the drop position is included in the right half of the cell. If included, the insertion destination number is incremented in step 2606. If not included, the process proceeds to step 2607. In step 2607, it is determined whether the shortcut key [CTRL] is pressed. If the shortcut key [CTRL] is pressed, it is determined that the copy operation is for the cell, and the process proceeds to Step 2608. If it has not been pressed, it is determined that the operation is to move the cell, and the process proceeds to step 2614. In step 2614, the insertion number is assigned to variable I, and in step 2615, the drag number is assigned to variable J. Thereafter, a process of moving the cell of the drag number to the cell of the insertion destination number is performed. In step 2616, I and J are compared, and if I and J are equal, the process returns. If J is greater than I, go to step 2617. If J is smaller than I, go to step 2618. In step 2617, the J-th cell is evacuated to WORK. In step 2619, I and J are compared. If J is smaller than I, the process proceeds to step 2625. If J is larger than I, the J-1st cell is shifted to Jth in step 2621, J is decremented in step 2622, and the process returns to step 2619. In step 2618, the J-th cell is evacuated to WORK. In step 2620, I and J are compared. If J is larger than I, the process proceeds to step 2625. If J is smaller than I, the J + 1st cell is shifted to Jth in step 2623, J is incremented in step 2624, and the process returns to step 2620. In step 2608, the insertion destination number is assigned to I. In step 2609, I is compared with the insertion destination number +1. If I is smaller, in step 2610 the I-th cell is shifted to the I + 1-th cell, and in step 2611 I is incremented. If I is larger, go to Step 2612. In step 2612, the cell of the drag number is copied. At this time, copy the button attached to the grid. In step 2613, the eyelid copied in step 2612 is stored in the insertion destination eye number.

Next, processing of the cell deletion operation will be described with reference to the drawings. FIG. 27 is a flowchart showing the flow of processing for the cell deletion operation. Reference is also made to FIG. 6 as appropriate.
As shown in FIG. 27, in step 2701, the cell number being dragged with the mouse is acquired and substituted into the variable drag cell number. In step 2702, the largest number among the cell numbers to which the buttons are attached is acquired and substituted for the final variable number. In step 2703, the cell of the drag cell number is deleted, and at the same time, the button attached to the cell is deleted. In step 2704, the variable I is initialized by substituting the drag number. In step 2705, I is compared with the final number. If I is smaller than the final number, in step 2706, the I + 1st cell is shifted to the Ith cell. If I is greater than the final number, return.

  Next, processing for obtaining the final number of the mesh will be described with reference to the drawings. FIG. 28 is a flowchart showing the flow of processing for obtaining the final number of the cells. The description will be given with reference to FIG. 6 as appropriate. As shown in FIG. 28, this process is a process of acquiring the largest number among the cell numbers to which the buttons are attached and returning the value. First, in step 2801, initialization is performed by substituting 0 for I representing the current cell number. In step 2802, the total number of cells is substituted into the variable MAX. In step 2803, initialization is performed by assigning 0 to the final variable number to which the return value is assigned. In step 2804, I and MAX are compared, and if I is larger than MAX, the final number is returned. If I is less than or equal to MAX, the process proceeds to step 2805. In step 2805, I is incremented. In step 2806, it is determined whether a button is pasted on the I-th cell. If a button is pasted on the I-th cell, I is substituted for the final number (step 2807), and the process jumps to step 2804. If no button is pasted on the I th cell, the process jumps to step 2804.

  Next, operations on the capsule binder will be described with reference to the drawings. FIG. 29 is a flowchart showing a flow of operations on the capsule binder. Reference is also made to FIG. As shown in FIG. 29, the capsule binder also has three modes of “automatic reproduction mode”, “creation mode”, and “trial mode”, similar to the mount / capsule screen. The “automatic playback mode” is a mode for viewing a work. When this mode is activated, the buttons on the capsule binder 602 are automatically executed for each cell. “Making mode” is a mode for editing a work, and the order of the cells can be changed or deleted, and the editing operation for pasting the buttons on the cells can be performed. In this mode, the capsule button, sound button, close button, simultaneous button, and home page link do not act as buttons. That is, the part is only selected without executing the predetermined function shown in FIG. 8 by the mouse click event. This operation is an operation for editing the combination of buttons. On the other hand, the “trial mode” is a content execution mode. In this mode, the function as the original button can be executed by the buttons.

  As shown in FIG. 29, the type of operation is determined in step 2901, and if it is an automatic playback start operation, it is determined in step 2913 whether or not the mode is the automatic playback mode. If so, the mode is switched to the automatic reproduction mode in step 2903, the automatic reproduction procedure on the capsule binder in step 2904 is called, and the process returns. If it is determined in step 2913 that the mode is the automatic reproduction mode, the process returns. If it is an automatic reproduction end operation, it is determined in step 2914 whether or not the mode is the automatic reproduction mode. If it is the automatic reproduction mode, the automatic reproduction is terminated in step 2905, the automatic reproduction mode is canceled in step 2907, the mode is switched to the mode set by the controller, and the process returns.

  If it is determined in step 2914 that the mode is not the automatic reproduction mode, the process returns. If it is not an automatic reproduction start operation or an automatic reproduction end operation, the process branches to step 2902. In step 2902, the mode is determined. If the mode is a trial mode, the process branches to step 2908. If it is the creation mode, the process branches to step 2906. If it is in auto play mode, it returns. The operation in step 2908 is determined, and if it is a mouse click operation, the process branches to step 2909. If it is not a mouse click operation, it returns.

  In step 2909, the mouse click position is determined. If the click is on the capsule button, the event procedure from the capsule button to the bottom is called with the capsule button clicked in step 2910 as an argument. If the click is on the close button, the event procedure from the top to the bottom of the close button is called with the close button clicked in step 2911 as an argument. If the click is on the sound button, the event procedure from the top to the bottom of the sound button is called with the sound button clicked in step 2911 as an argument. If the click is on the homepage link button, the event procedure from the top to the bottom of the homepage link button is called with the homepage link button clicked in step 2912 as an argument. Otherwise, return. Return after the above processing.

Next, the automatic reproduction operation process on the capsule binder will be described with reference to the drawings. FIG. 30 is a flowchart showing the flow of the automatic reproduction operation on the capsule binder. This will be described with reference to FIG. The automatic regeneration processing of the capsule binder 602 is a mechanism in which events are transmitted to the cells of the capsule binder 602 in the order of the cells. One or more buttons can be attached to one cell of the capsule binder 602, and they are connected to an event transmission slot existing in the cell to which these buttons are attached. Here, a list of buttons pasted in the same cell is acquired, and a process of simultaneously transmitting events to those buttons is performed. First, the capsule binder automatic regeneration process is a mechanism in which events are transmitted in the order of cells to each cell of the capsule binder. One or more buttons can be attached to one cell of the capsule binder, and these are connected to the event transmission slot existing in the cell.
Here, a list of buttons pasted in the same cell is obtained, and an event is simultaneously transmitted to these buttons.

  In step 3001, the largest number among the cell numbers to which the buttons are attached is acquired and substituted for the final variable number. In the subsequent steps, event transmission is performed sequentially only for the cell with the button among the cells from the first cell to the final cell. In step 3002, the event transmission time interval from the current cell set in the capsule binder to the next cell is acquired and substituted into the variable T. Normally, this time interval is used, but if the playback of a sound or video started from a certain cell exceeds the time interval, the process proceeds to the next cell after the reproduction ends. In step 3003, initialization is performed by substituting I for 1 as the current cell number used in the next loop. In step 3004, it is determined whether I is smaller than the final number +1, and if smaller, branch to step 3005. If not, return. In step 3005, a list of buttons directly attached to the I-th cell is obtained and substituted into the variable button list. In step 3005, the number of elements in the button list is referred to. If this list is not empty, the process branches to step 3007. If this list is empty, the process jumps to step 3019. In step 3007, the current time is acquired and substituted for the variable button execution start time. In step 3008, the top element of the button list is acquired and assigned to the variable button. In step 3009, the type of button is determined. If the button is a capsule button, in step 3011 an event procedure from the bottom to the top of the capsule button is called using the argument as a button, and the process proceeds to step 3014. If the button is a homepage link button, the event procedure from the bottom to the top of the homepage link button is called using the argument as a button in step 3012, and the process proceeds to step 3014. If the button is a sound button, an event procedure from the bottom to the top of the sound button is called using the argument as a button in step 3013, and the process proceeds to step 3014. In step 3014, it is determined whether or not the button is the last in the button list. If it is the last, the process proceeds to step 3016. If it is not the last, the button registered next to the button list is acquired in step 3010, substituted for the button, and the process returns to step 3009 again. In step 3016, the elapsed time from the variable button execution start time to the current time (that is, the execution time of the I-th cell) is calculated and substituted for the variable elapsed time. In step 3017, it is determined whether or not the variable elapsed time exceeds the variable T. If not, the T-elapsed time waiting timer is started in step 3018. If exceeded, the process proceeds to step 3019. In step 3019, a (T-elapsed time) waiting timer is started. In step 3019, I is incremented. In step 3020, a procedure for closing the screen associated with the button is called with the button list as an argument.

  In the flowchart of FIG. 30, automatic execution processing is sequentially performed for all cells. However, when the capsule binder to be automatically reproduced has a calendar attribute (when it is a calendar capsule binder), for example, a specific cell is targeted. Automatic execution processing is performed sequentially for the specified row or column cell.

Next, event processing from the top to the bottom of the capsule button will be described with reference to the drawings. FIG. 31 is a flowchart showing a flow of event processing from the top to the bottom of the capsule button. When an event is transmitted to a button by a click operation or the like, the button that receives the event performs processing of the function of the button and then transmits the event to the button to which the button is pasted. The button that received it transmits an event to the button to which the button is pasted. This process is repeated until there are no pasted buttons. In this way, events are transmitted in the order of pasting from the buttons pasted in front. FIG. 31 shows this event transmission process. As shown in FIG. 31, in step 3101, the behavior procedure after receiving the capsule button event is called with the capsule button of the argument as an argument. In step 3102, the paste destination of the capsule button of the argument is determined. If it is on the capsule button, the event procedure from the capsule button to the bottom is called recursively with the paste destination of the capsule button of the argument as the argument in step 3103. To return. If the determination destination in step 3102 is on the close button, the event procedure from the top to the bottom button is called with the argument capsule button paste destination as an argument in step 3104, and the process returns. If the paste destination of the determination in step 3102 is on the simultaneous button, in step 3105, the event procedure from the top to the bottom of the simultaneous button is called with the argument capsule button paste destination and the call type as an argument, and the process returns. . The call type of the simultaneous button event will be described later. If the paste destination of the determination in step 3102 is on the homepage link button, in step 3106, the event procedure from the top of the homepage link button to the bottom is called with the paste destination of the argument capsule button as an argument, and the process returns. If the determination destination in step 3102 is on the sound button, in step 3107, the event procedure from the top to the bottom of the sound button is called with the argument capsule button paste destination as an argument, and the process returns.
If the paste destination of the determination in step 3102 is other than anything, the process returns without doing anything.

Next, processing of an event from the top to the bottom of the close button will be described with reference to the drawings. FIG. 32 is a flowchart showing a flow of processing of an event from the top to the bottom of the close button.
Similar to the processing flow shown in FIG. 31, the processing shown in FIG. 32 is performed sequentially from the button to the button that is the paste destination, from the button to the button that is the paste destination. The process of transmitting an event to the pasting button is shown. As shown in FIG. 32, the paste destination of the argument close button is determined in step 3201, and if it is on the capsule button, the event from the capsule button above to below is taken in step 3202 using the paste destination of the argument close button as an argument. Call the procedure and return. If the paste destination of the determination in step 3201 is on the close button, in step 3203, the event procedure from the top to the bottom of the close button is called with the paste destination of the close button of the argument as an argument, and the process returns. If the determination destination in step 3201 is on the simultaneous button, in step 3204 an event from the top to the bottom of the simultaneous button is called with the argument close button paste destination and call type as an argument, and the process returns. The call type of the simultaneous button event will be described later. If the paste destination of the determination in step 3201 is on the homepage link button, the event procedure from the top of the homepage link button to the bottom is called in step 3205 with the paste destination of the close argument button as an argument, and the process returns. If the determination destination in step 3201 is on the sound button, in step 3206, the event procedure from the top to the bottom of the sound button is called with the argument paste destination as the argument, and the process returns. If the paste destination of the determination in step 3201 is on the mount / capsule screen, the behavior procedure after receiving the event of the close button is called using the close button of the argument as an argument. If the pasting destination is anything else, it returns without doing anything.

  Next, event processing from the top to the bottom of the simultaneous button will be described with reference to the drawings. When the simultaneous button receives an event such as a click operation, the event is transmitted to the pasted slot, and then the event is propagated to all the simultaneous buttons created by duplicating yourself (referred to here as linked buttons). To do. FIG. 33 is a flowchart showing a flow of processing of an event from the top to the bottom of the simultaneous button. As shown in FIG. 33, the behavior after receiving the simultaneous button event is called in Step 3301, and the process proceeds to Step 3302. In step 3302, the paste destination of the simultaneous argument button is determined. If it is on the capsule button, the event procedure from the top to the bottom of the capsule button is called in step 3303 using the paste destination of the simultaneous argument button as an argument. Proceed to If the paste destination is on the close button, an event procedure from the top to the bottom button is called in step 3304 with the paste destination of the argument simultaneous paste as an argument, and the process proceeds to step 3308. If the paste destination is on the simultaneous button, in step 3305, call the event procedure from the top to the bottom of the simultaneous button with the first argument as the paste destination of the argument and the second argument as the call type. The process proceeds to step 3308. The call type mode will be described later. If the pasting destination is on the homepage link button, the event procedure from the top to the bottom of the homepage link button is called at step 3306 with the pasting destination of the argument simultaneous button as an argument, and the process proceeds to step 3308. If the paste destination is on the sound button, an event procedure from the top to the bottom of the sound button is called with the paste destination of the simultaneous argument button as an argument in step 3307, and the process proceeds to step 3308. If the pasting destination is other than that, the process proceeds to Step 3308. In step 3308, the call type of the argument is determined. If the call type is linked, the process returns. If the call type is not linked (not linked), the process proceeds to step 3308.

  The processing after step 3308 represents the processing in which the event is propagated to all the slots of the simultaneous buttons (buttons that are linked) created by duplicating the self receiving the event. The processing when an event is transmitted to buttons associated with the simultaneous button is a recursive call, and the call type is used as the second argument in order not to repeat the call between the buttons associated with the simultaneous button. Depending on the call type, it is discriminated whether it is an event from a partner or an event from a linked button. Buttons that are linked to the simultaneous buttons are managed in the simultaneous operation list. In step 3308, it is determined whether or not the call type of the argument is linked. If it is linked, the process returns as it is. If the call is not linked, the process proceeds to step 3309. In step 3309, the simultaneous operation list of the simultaneous button of the argument is substituted into the simultaneous operation list. In step 3310, the simultaneous button registered at the beginning of the simultaneous operation list is set in the variable button.

  Here, since the processing of the event for the argument simultaneous button has already been completed, it is determined in step 3311 whether or not the button is the simultaneous button for the argument in order to cancel the processing. In 3312, an event from the top to the bottom of the simultaneous button is recursively called with the first argument as a button and the call type of the second argument as an interlock. If the button is a simultaneous button with an argument, do not recursively call it. In step 3313, it is determined whether or not the button is at the end of the simultaneous operation list. If it is not the last in step 3314, the next simultaneous button is set in the button variable, and the process returns to step 3311 again.

  Next, event processing from the top to the bottom of the homepage link button will be described with reference to the drawings. FIG. 34 is a flowchart showing the flow of event processing from the top to the bottom of the homepage link button. Similar to the process shown in FIG. 31, the process shown in FIG. 34 is also pasted one after another, such as from the button to the button that is the paste destination, and from the button to the button that is the paste destination. It represents a process in which an event is transmitted to the previous button.

  As shown in FIG. 34, in step 3401, the homepage link button of the argument is used as an argument to call the behavior procedure after receiving the event of the homepage link button. In step 3402, the paste destination of the homepage link button of the argument is determined. If it is on the capsule button, the event procedure from the top to the bottom of the capsule button is called using the pastepoint of the homepage link button of the argument as the argument in step 3403. To return. If the pasting destination determined in step 3402 is on the close button, in step 3404 the event procedure from the top to the bottom button is called with the pasting destination of the argument home page link button as an argument, and the process returns. If the pasting destination determined in step 3402 is on the simultaneous button, in step 3405, the event procedure from the top to the bottom of the simultaneous button is called with the argument of the link destination of the homepage link button of the argument and the call type as an argument, and the return To do. The call type of the simultaneous button event will be described later. If the pasting destination determined in step 3402 is on the homepage link button, the event procedure from the top to the bottom of the homepage link button is called in step 3406 with the pasting destination of the homepage link button as an argument, and the process returns. If the paste destination determined in step 3402 is on the sound button, in step 3407, the event procedure from the top to the bottom of the sound button is called with the paste destination of the homepage link button of the argument as an argument, and the process returns. If the pasting destination determined in step 3402 is other than that, nothing is done and the process returns.

  Next, event processing from the top to the bottom of the sound button will be described with reference to the drawings. FIG. 35 is a flowchart showing the flow of event processing from the top to the bottom of the sound button. As in FIG. 31, processing for transmitting events to the pasting button one after another, such as from the button to the pasting button and from the button to the pasting button. Represents.

  As shown in FIG. 35, the behavior procedure after receiving the sound button event is called in step 3501 using the sound button as an argument as an argument. In step 3502, the paste destination of the argument sound button is determined, and if it is on the capsule button, the event procedure from the capsule button to the bottom is called in step 3503 with the paste destination of the argument sound button as an argument, and the return. To do. If the paste destination determined in step 3502 is on the close button, an event procedure from the top to the bottom button is called with the paste destination of the argument sound button as an argument in step 3504, and the process returns. If the pasting destination determined in step 3502 is on the simultaneous button, in step 3505, the event procedure from the top to the bottom of the simultaneous button is called with the argument sound button pasting destination and the call type not linked, and the process returns. . The call type of the simultaneous button event will be described later. If the pasting destination determined in step 3502 is on the homepage link button, the event procedure from the top to the bottom of the homepage link button is called with the pasting destination of the sound button of the argument as an argument in step 3506, and the process returns. If the paste destination determined in step 3502 is on the sound button, in step 3507, the event procedure from the top to the bottom of the sound button is called with the paste destination of the argument sound button as an argument, and the process returns. If the pasting destination determined in step 3502 is other than anything, the process returns without doing anything.

  Next, event processing from the bottom to the top of the capsule button will be described with reference to the drawings. Reference is also made to FIG. 6 as appropriate. FIG. 36 is a flowchart showing the flow of processing of events from the bottom to the top of the capsule button. As shown in FIG. 36, when an event is transmitted from the event transmission slot of the capsule binder 602 to the button pasted on the grid, the button paste destination to the button When an event is transmitted, the button that receives the event performs processing related to the function of the button, and then transmits the event to the button attached to the button. Further, the button that has received it transmits an event to the button attached to the button. This process is repeated until there are no pasted buttons. In this way, the events are transmitted in the order of pasting to the buttons pasted in front. FIG. 36 shows the flow of this event transmission process. In step 3601, the behavior procedure after receiving the capsule button event is called using the capsule button as an argument. In step 3602, a list of buttons pasted on the capsule button of the argument is acquired and substituted into the variable child button list. In step 3603, the button registered at the beginning of the child button list is substituted for the variable button. In step 3604, the type of the button is determined. If the button is a capsule button, an event procedure from the bottom to the top of the capsule button is called using the button as an argument in step 3606.

  If the button is a homepage link button, the event procedure from the bottom to the top of the homepage link button is called in step 3607 with the button as an argument. If the button is a sound button, an event procedure from the bottom to the top of the sound link button is called in step 3608 with the button as an argument. If the button is a close button, the event procedure from the bottom to the top of the close button is called in step 3609 with the button as an argument. If the button is other, the process jumps to step 3610. In step 3610, it is determined whether or not the button is the last in the child button list. If it is the last, the process returns. If it is not the last, the button registered next to the child button list in step 3605 is acquired and assigned to the button, and then the process returns to step 3604.

  Next, event processing from the bottom to the top of the homepage link button will be described with reference to the drawings. FIG. 37 is a flowchart showing a flow of event processing from the bottom to the top of the homepage link button. As in the process of FIG. 36, when an event is transmitted to the button from the button paste destination, the button that has received the event represents the process of transmitting the event to the button pasted on the button. Yes.

  As shown in FIG. 37, in step 3701, the homepage link button of the argument is used as an argument, and the behavior procedure after receiving the event of the homepage link button is called. In step 3702, a list of buttons pasted on the homepage link button of the argument is acquired and substituted into a variable child button list. In step 3703, the button registered at the beginning of the child button list is substituted into the variable button. In step 3704, the type of the button is determined. If the button is a capsule button, an event procedure from the bottom to the top of the capsule button is called with the button as an argument in step 3706. If the button is a homepage link button, the event procedure from the bottom to the top of the homepage link button is called in step 3707 with the button as an argument. If the button is a sound button, in step 3708, the event procedure from the bottom to the top of the sound link button is called with the button as an argument. If the button is a close button, an event procedure from bottom to top of the close button is called in step 3709 with the button as an argument. If the button is other, the process jumps to step 3710. In step 3710, it is determined whether or not the button is the last in the child button list, and if it is the last, the process returns. If it is not the last, in step 3705, the next registered button in the child button list is acquired and assigned to the button, and the process returns to step 3704.

  Next, processing of events from the bottom to the top of the sound button will be described. FIG. 38 is a flowchart showing a flow of event processing from the bottom to the top of the sound button. Similarly to the processing of FIG. 36, when an event is transmitted to the button from the button paste destination, the button that has received the event transmits the event to the button attached to the button. As shown in FIG. 38, in step 3801, the behavior procedure after receiving the sound button event is called with the sound button as an argument as an argument. In step 3802, a list of buttons pasted on the argument sound button is acquired and substituted into a variable child button list. In step 3803, the button registered at the beginning of the child button list is substituted for the variable button. In step 3804, the type of the button is determined. If the button is a capsule button, an event procedure from the bottom to the top of the capsule button is called using the button as an argument in step 3806.

  If the button is a homepage link button, the event procedure from the bottom to the top of the homepage link button is called in step 3807 with the button as an argument. If the button is a sound button, an event procedure from the bottom to the top of the sound link button is called in step 3808 with the button as an argument. If the button is a close button, the event procedure from the bottom to the top of the close button is called in step 3809 with the button as an argument. If the button is others, the process jumps to step 3810. In step 3810, it is determined whether or not the button is the last in the child button list, and if it is the last, the process returns. If it is not the last, in step 3805, the button registered next to the child button list is acquired and substituted for the button, and then the process returns to step 3804.

  Next, event processing from the bottom to the top of the close button will be described with reference to the drawings. FIG. 39 is a flowchart showing a flow of event processing from the bottom to the top of the close button. Similarly to FIG. 36, in FIG. 39, when an event is transmitted to the button from the button paste destination, the button that receives the event transmits the event to the button pasted on the button. Represents.

  As shown in FIG. 39, in step 3901, the behavior procedure after receiving the event of the close button is called using the close button of the argument as an argument. In step 3902, a list of buttons pasted on the close button of the argument is acquired and substituted into the variable child button list. In step 3903, the button registered at the beginning of the child button list is substituted for the variable button. In step 3904, the type of the button is determined. If the button is a capsule button, an event procedure from the bottom to the top of the capsule button is called using the button as an argument in step 3906.

  If the button is a homepage link button, the event procedure from the bottom to the top of the homepage link button is called in step 3907 with the button as an argument. If the button is a sound button, an event procedure from the bottom to the top of the sound link button is called in step 3908 with the button as an argument. If the button is a close button, an event procedure from bottom to top of the close button is called in step 3909 with the button as an argument. If the button is other, jump to step 3910. In step 3910, it is determined whether or not the button is the last in the child button list. If it is the last, the process returns. If it is not the last, in step 3905, the button registered next to the child button list is acquired and assigned to the button, and then the process returns to step 3904.

  Next, processing after capsule button event reception will be described with reference to the drawings. FIG. 40 is a flowchart showing the flow of processing after receiving a capsule button event. The capsule button opens the capsule screen when an event is received. FIG. 40 shows the flow of this processing. First, in order to obtain the opening position of the capsule screen, the difference between the capsule and the opening position of the capsule screen, that is, the offset, is stored in the capsule. In step 4001, the variable “position” stores the sum of the offset for opening the capsule screen and the position of the capsule button of the argument. In step 4002, the capsule screen associated with the capsule button of the argument is opened at that position, and the process returns.

Next, processing after receiving the close button event will be described with reference to the drawings.
FIG. 41 is a flowchart showing the flow of processing after receiving the close button event. The close button closes the pasteboard mount / capsule screen when an event is received. FIG. 41 shows this processing. As shown in FIG. 41, the paste destination of the close argument button is determined in step 4101. If the paste destination is a mount / capsule screen, the mount / capsule screen to which the close argument button is pasted in step 4102 Call the procedure to close the mount / capsule screen with the argument. If the pasting destination is other than that, return without doing anything.

FIG. 42 is a flowchart showing the behavior processing after the simultaneous button event is received.
The simultaneous button indicates that no operation other than the event transmission processing shown in FIG. 33 is performed after the event is received.

  Next, processing after receiving a sound button event will be described with reference to the drawings. FIG. 43 is a flowchart showing the flow of processing after receiving a sound button event. When a sound button receives an event, the sound contained in the sound button is played. FIG. 43 shows the flow of this processing. As shown in FIG. 43, in step 4301, the sound contained in the sound button of the argument is reproduced.

  Next, processing after receiving the homepage link button event will be described with reference to the drawings. FIG. 44 is a flowchart showing the flow of behavior processing after receiving a homepage link button event. When receiving the event, the homepage link button starts a WWW browser, and displays the homepage of the link destination included in the homepage link button. FIG. 44 shows the flow of this processing. As shown in FIG. 44, first, in order to obtain the opening position of the WWW browser screen, the difference between the opening positions of the homepage link button and the WWW browser screen, that is, the offset is stored in the homepage link button. In step 4401, the variable “position” stores the sum of the offset for opening the WWW browser screen and the position of the argument homepage link button. Next, in step 4402, the WWW browser screen displaying the link destination homepage associated with the argument homepage link button is opened at that position.

  Next, an operation process on the image scanner screen will be described as an example of handling digitized data / information. FIG. 45 is a flowchart showing the flow of operation processing on the image scanner screen. As shown in FIG. 45, the content of the operation is determined in step 4501, and if it is a preview display operation, the process branches to step 4502. If the operation is a drag and drop operation to the mount / capsule screen in the preview field, the process branches to step 4503. In step 4502, the connected image scanner is accessed, and a reduced image of the image being set in the image scanner is captured and displayed in the preview area. In step 4503, it is determined whether or not a reduced image is being displayed in the preview field. If it is being displayed, the process branches to step 4504. Returns if not displayed. In step 4504, the size of the paste-on mount / capsule screen at the drop destination is referred to, and the resolution for capturing from the scanner is determined based on the size. The resolution is the maximum rectangular size that retains the aspect ratio of the image size to be captured and that is inscribed in the rectangle of the pasteboard / capsule screen. In step 4505, the connected image scanner is accessed, and an image is captured at the resolution calculated in step 4504. In step 4506, the image in step 4505 is pasted as a photographic material at the drop position. In addition to image scanners, digital information in digital cameras and digital video cameras can be handled in the same way.

  Next, processing for closing the mount / capsule screen will be described with reference to the drawings. FIG. 46 is a flowchart showing the flow of processing for closing the mount / capsule screen. As shown in FIG. 46, in step 4601 the argument mount / capsule screen is closed, and the flow advances to step 4602. In step 4602, the button pasted on the mount / capsule screen of the argument is acquired, stored in the variable child button list, and the flow advances to step 4603. In step 4603, a button registered at the beginning of the child button list is acquired and substituted into a variable button. Thereafter, the process proceeds to step 4604. In step 4604, the type of button is determined. If it is a capsule button, the process branches to step 4605. If it is a homepage link button, the process branches to step 4608. If it is any other button, the process branches to step 4606.

  In step 4605, a procedure for closing the mount / capsule screen with the mount / capsule screen associated with the button as an argument is recursively called, and the flow advances to step 4606. In step 4608, the WWW browser screen associated with the button is closed, and the flow advances to step 4606. In step 4606, it is determined whether or not the button is the last button registered in the child button list, and if it is the last, the process returns. Otherwise, go to step 4607. In step 4607, the button registered next to the child button list is acquired, substituted into the button, and the process returns to step 4604.

  Next, processing for closing a screen associated with a button will be described with reference to the drawings.

  FIG. 47 is a flowchart showing a flow of processing for closing a screen associated with a button. As shown in FIG. 47, in step 4701, a button registered at the beginning of the argument button list is acquired and substituted into a variable button. Thereafter, the process proceeds to step 4702. In step 4702, the type of the button is determined. If it is a homepage link button, the process branches to step 4703, and if it is a capsule button, the process branches to step 4704. Otherwise, the process branches to step 4707. In step 4703, the WWW browser screen associated with the button is closed, and the process proceeds to step 4705. In step 4704, a procedure for closing the mount / capsule screen with the mount / capsule screen associated with the button as an argument is recursively called, and the flow advances to step 4705. In step 4705, the button pasted on the button is acquired, stored in the variable child button list, and the process proceeds to step 4706. In step 4706, a procedure for closing the screen associated with the button is called using the child button list as an argument, and the process proceeds to step 4707. In step 4707, it is determined whether or not the button is a button registered at the end of the child button list. Otherwise, go to step 4708. In step 4708, the button registered next to the child button list is acquired and substituted for the button, and the flow returns to step 4702.

  Next, processing of operations in the drawer will be described with reference to the drawings. FIG. 48 is a flowchart showing the processing flow of the operation in the drawer. As shown in FIG. 48, the content of the operation is determined in step 4801. If the operation is a double click on the work icon, the double clicked work is loaded in step 4802, and after returning to the editing state, the process returns. If the operation is a double-click on the box icon, in step 4803, the drawer that displays the documents stored in the double-clicked box is opened and then the process returns.

  If the operation is a drag-and-drop operation of the work icon on the mount / capsule screen or capsule binder, a capsule button is generated with the mouse release position at the upper left corner in step 4806, and the capsule that opens when the capsule button is clicked in step 4807 After assigning the work selected from the drawer as the screen, return.

  Next, operation processing on the photo browser will be described with reference to the drawings. FIG. 49 is a flowchart showing the flow of the operation on the photo browser. As shown in FIG. 49, the operation is determined in step 4901. If the operation is a folder designation, in step 4902 a thumbnail of the image file in the designated folder is created and displayed, and then the process returns. If the operation is a drag-and-drop operation on the thumbnail mount / capsule screen, in step 4903, the designated image material is pasted at the drop position, and the process returns.

  Next, processing of operations on the sound browser will be described with reference to the drawings. FIG. 50 is a flowchart showing the flow of operation processing on the sound browser. In step 5001, the operation is determined. If the operation is a folder designation, the file name and icon of the sound file in the folder designated in step 5002 are displayed as a set, and the process returns. If the operation is a drag and drop operation on a thumbnail mount / capsule screen or a cell on the capsule binder, the process advances to step 5003. In step 5003, the drop position is determined. If it is on the mount / capsule screen, the process branches to step 5004. If it is on the capsule binder, the process branches to step 5005. Otherwise, the process returns. In step 5004, the part generation on the mount / capsule screen is called with the sound button for reproducing the sound file associated with the icon dropped in step 5004 as an argument, and then the process returns. In step 5005, the part generation on the capsule binder is called with the sound button for reproducing the sound file associated with the icon dropped in step 5005 as an argument, and then the process returns.

  Next, processing of operations on the video browser will be described with reference to the drawings. FIG. 51 is a flowchart showing the flow of operation processing on the video browser. As shown in FIG. 51, when the operation is determined in step 5101 and the operation is a folder designation, a thumbnail of the first frame of the video file in the folder designated in step 5102 is created and displayed. Return. If the operation is a drag-and-drop operation on the thumbnail mount / capsule screen, the player of the specified video material is pasted at the drop position in step 5103. At that time, the display is in a stationary state at the first frame. Then return.

  Next, operations on the attribute change tool screen will be described with reference to the drawings. FIG. 52 is a flowchart showing the flow of operation processing on the attribute change tool screen. As shown in FIG. 52, the operation is determined in step 5201. If the operation is an operation of dragging and dropping an object on the work screen to the attribute change tool screen, the process branches to step 5202. If the operation determined in step 5201 is an operation of dragging and dropping a button or rectangle on the attribute change tool screen onto an object on the work screen, the process branches to step 5209. If it is a button click operation on the attribute change tool screen, the process branches to step 5216. In step 5202, the drop position is determined. If it is on the attribute setting button on the attribute change tool screen, the process branches to step 5203. If the drop position is on a rectangle that encloses the attribute setting buttons in an associated group, the process branches to step 5205. If the drop position is on the rectangle surrounding all the attribute setting buttons, the process branches to step 5207. The attribute assigned to the button dropped in step 5203 is acquired from the dropped object, set as the current attribute value on the attribute change tool screen, and the process advances to step 5204. In step 5204, the attribute acquired in step 5203 is reflected on the display of the attribute change tool screen as the current attribute, and the process returns. The attribute assigned to each button in the rectangle dropped in step 5205 is acquired from the dropped object, set as the current attribute value on the attribute change tool screen, and the flow advances to step 5206. In step 5206, the attribute acquired in step 5205 is reflected on the display of the attribute change tool screen as the current attribute, and the process returns. In step 5207, all attributes (background, font, frame) are acquired from the object, set as current attribute values on the attribute change tool screen, and the flow advances to step 5208. In step 5208, the attribute acquired in step 5207 is reflected on the display of the attribute change tool screen as the current attribute, and the process returns. In step 5209, the drag start position is determined. If it is the attribute setting button on the attribute change tool screen, the flow branches to step 5210. If the drag start position is a rectangle that encloses the attribute setting buttons in a related group, the process branches to step 5212. If the drag start position is a rectangle surrounding all the attribute setting buttons, the process branches to step 5214. The current attribute value of the attribute assigned to the button dragged in step 5210 is acquired from the change tool screen, and the process advances to step 5211. In step 5211, the attribute acquired in step 5210 is set in the drop target object to be changed, and the process returns.

  In step 5212, the current attribute value of the attribute assigned to each button in the dragged rectangle is acquired from the attribute change tool screen, and the flow advances to step 5213. In step 5213, the attribute acquired in step 5212 is set in the drop target object to be changed, and the process returns. In step 5214, all current attribute values are acquired from the attribute change tool screen, and the flow advances to step 5215. In step 5215, the attribute acquired in step 5214 is set in the drop target object to be changed, and the process returns. The current attribute value of the attribute assigned to the button clicked in step 5216 is acquired, and the process proceeds to step 5217. In step 5217, the attribute acquired in step 5216 is set to the object selected as the attribute change target on the work, and the process returns.

  As described above, according to the content editing technique according to the present embodiment, operations for adding material to a work, such as adding a slide and adding a sound, are unified with a drag-and-drop operation. Easy to operate. In addition, since the operation target is a visualized part, the operation is easy even if the user is not familiar with the terminology specific to the system. Also, operations such as changing the opening position and size of the slide screen can be performed by the same drag-and-drop operation as that for the object. Therefore, an intuitive editing operation can be performed without relying on the system manual.

  In addition, since the execution order of the button parts can be specified, multimedia contents can be automatically played back. As a method for specifying the execution order, there can be variations such as a method for setting the order individually, a method for setting the order according to the value of the button, and a method for setting with a part having an arrow shape.

  Furthermore, since the drop operation of the drag and drop operation corresponds to an operation for designating the insertion position, an operation such as setting the insertion position in advance before the insertion is not required. It is also possible to insert an existing work into another work in the same way as pasting multimedia material on a slide.

  In addition, by associating the slide switching time with the content playback time, for example, when the time specified as the slide switching time is less than the playback time of the sound that is played back when the slide is switched, It is possible to prevent the sound reproduction from being interrupted at the time of switching.

  Further, when changing the attributes of an object, all the attributes can be set for each classification associated with the attribute of the object or all at once. Furthermore, various information can be easily organized in association with calendar information, and the information can be referred to in an order defined by the calendar. It is also possible to automatically adjust the data size of the content in accordance with the data size of the import destination work.

  For example, when a plurality of grids are formed in a matrix, the order of the grids provided on the mount component is first defined in the column direction with respect to one row, and the column direction with respect to one row. When the ordering is completed, the same ordering may be performed for the next row. Conversely, when the ordering is defined in the row direction for one column and the ordering in the row direction for one column is finished, The directionality may be changed so that the same ordering is performed for the next column. However, regarding ordering, it is preferable that a certain regularity (continuity) is maintained.

It is a block diagram which shows the structural example of the content editing system by one embodiment of this invention. It is a figure which shows an example of editing operation by the content editing system by one embodiment of this invention, and is a figure which shows operation which edits a work by sticking various content on a mount, starting from a controller. It is a figure which shows an example of the work produced by editing operation by the content editing system by one embodiment of this invention, and is a figure which shows the outline | summary of the work produced by sticking a capsule button on a mount. It is a figure which shows an example of the work produced by editing operation by the content editing system by one embodiment of this invention, and designates the execution order of the button components affixed on the mount by affixing an arrow part. It is a figure which shows the mode of operation. It is an attribute regarding the work produced by the editing operation by the content editing system by one embodiment of this invention, Comprising: It is a figure which shows the mode of operation which changes a plurality of related attributes or all the attributes collectively. It is a figure which shows the edit process of the work produced by the edit operation by the content edit system by one embodiment of this invention, and the state of operation which pastes various button components on the capsule binder by which the area | region was demarcated like a grid FIG. It is a figure which shows the edit process of the work produced by edit operation by the content edit system by one embodiment of this invention, and is operation of sticking various button components on the calendar capsule binder by which the area | region was demarcated like a grid It is a figure which shows a mode. It is a figure which shows the content of the operation | movement when an event comes to the name of each component, its associated slot, and a slot. It is a flowchart figure which shows the main flow of editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on a controller among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of operation on a parts box among edit operation by the multimedia content edit system by one embodiment of this invention. It is a flowchart figure which shows the flow of a part production | generation process on a mount and a capsule screen among editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the process of the components production | generation on a capsule binder among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the slot coupling | bonding process of a capsule button among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a slot joint process of the close button among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the slot coupling | bonding process of a homepage link button among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the slot combination process of a sound button among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the slot joint process of a simultaneous button among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the process of operation on a mount and a capsule screen among edit operation by the multimedia content edit system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the edit operation on a mount and a capsule screen among edit operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation which gives the execution order of a button extendedly among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the automatic reproduction | regeneration on a mount and a capsule screen among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the automatic reproduction | regeneration processing based on the designation | designated order by an arrow component among the editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of acquisition of the list | wrist of the components connected with the arrow components among the edit operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the edit operation on a capsule binder among the edit operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the movement / copy operation of a cell among edit operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the deletion operation of a cell among the editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of acquisition of the last number of a cell among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on a capsule binder among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the automatic reproduction operation on a capsule binder among the editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the event from a capsule button to the bottom among editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the event from a close button top down among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the process of the event from simultaneous button top to bottom among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a processing of the event from the top of a homepage link button among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of the process of the event from the sound button top to the bottom among the edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the event from a capsule button below from the edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the event from the bottom of a homepage link button among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the event from the bottom of a sound button among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of processing of the event from the bottom of a close button among edit operations by the multimedia content editing system by one embodiment of this invention from the bottom. It is a flowchart figure which shows the flow of a process of the behavior after capsule button event reception among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the behavior after a close button event is received among the edit operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the behavior after simultaneous button event reception among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the behavior after reception of a sound button event among editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of the behavior after a homepage link button event reception among editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on an image scanner screen among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process which closes a mount and a capsule screen among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process which closes the screen linked | related with a button among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation in drawer among edit operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on a photograph browser among editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on a sound browser among editing operations by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on a video browser among editing operation by the multimedia content editing system by one embodiment of this invention. It is a flowchart figure which shows the flow of a process of operation on an attribute change tool screen among edit operation by the multimedia content editing system by one embodiment of this invention. 1 is a detailed system configuration diagram of a multimedia content editing system according to an embodiment of the present invention. FIGS. 54A and 54B are views showing the display form and internal structure of parts on the screen in the multimedia content editing system according to the embodiment of the present invention. It is a figure which shows the example of a program system of the multimedia content editing system by one embodiment of this invention. It is a figure which shows the transfer system of the message in the multimedia content editing system by one embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 ... Central processing unit, 102 ... Keyboard device, 103 ... Display device, 104 ... Mouse, 105 ... Hard disk, 106 ... Image scanner, 107 ... Digital camera, 108 ... Video capture device, 109 ... Microphone, 201 ... Controller, 202 ... Photo browser, 203 ... Sound browser, 204 ... Parts box, 205 ... Sound recorder, 206 ... Mount, 207 ... Image scanner screen, 208 ... Capsule screen, 209 ... Video browser, 602 ... Capsule binder.

Claims (8)

An object-oriented component that has a central processing unit, a storage device that stores a program for causing the central processing unit to perform content editing processing and content, and an interface unit with a display device and an input unit, and is visualized In a content editing method using an application system that can associate processing between parts by pasting another part on the screen (hereinafter referred to as “part”),
Displaying a content processing start button component for starting processing related to content on the screen of the display device;
Displaying a mount having a plurality of cells, the order of which is defined for each cell, on the screen of the display device;
Using the input unit, processing of the pasted content processing button is executed in the order according to the operation of pasting the content processing start button component on the screen on the display device. And storing in the storage device in which cell the content processing start button component is pasted and the order of each cell.
Two or more content processing start button components pasted to the same cell are combined in a communication channel between other components, and all of the execution start events received by a certain content processing start button component are combined in the communication channel. By being transmitted to the content processing start button component, the functions of all the content processing start button components are grouped and executed simultaneously ,
A step of displaying on the screen of the display device an attribute value button component group for changing or obtaining a plurality of attribute values related to the display of the component;
In accordance with the selection of a plurality of attribute values in the attribute value button component group and the operation of pasting the attribute value button component using the input unit on the component pasted on the screen, A step of batch-converting attributes related to the display of parts into selected attributes;
Including
The batch conversion step includes:
A content editing method, which is executed by a step of selecting a figure surrounding an attribute value button component of a background color, a character attribute, and a frame attribute, and dragging and dropping it on the target component . Furthermore, using the input unit, a step of pasting a mount part that does not have a grid on the screen of the display device to the grid;
Using the input unit, pasting a plurality of the content processing start button parts on the screen part of the display device to the mount part that does not have the cell;
Designating the processing order of the plurality of content processing start button parts pasted on the mount part having no grid by means of directional parts, so that a series of processes related to the content is executed in a certain order; The content editing method according to claim 1, including: The step of designating the processing order of the content processing start button component is as follows:
The content editing method according to claim 2 , further comprising a step of pasting a connection component that indicates a content processing order between the content processing start button components pasted on the grid. A step of displaying on the screen of the display device an attribute value button component group associated with a plurality of grouped attribute values;
A step of collectively converting items related to the grouped attribute by operating the attribute value button component group or executing a process related to the attribute of the grouped component collectively. The content editing method according to claim 2 . The step of designating the processing order of the content processing start button component is as follows:
The content editing method according to claim 2 , further comprising a step of designating an execution order as an attribute value of the content processing start button. The step of designating the processing order of the content processing start button component is as follows:
The content editing method according to claim 2 , further comprising a step of connecting the plurality of content processing start button parts by a connecting part having information related to a process execution order. The content editing method according to claim 6 , wherein the connection component includes time interval information between contents started by the content processing start button component connected by the connection component. Program for executing the method according to the computer in any one of claims 1 to 7.

Images