Patent Application
20100223554
1. Technical Field
The present invention relates generally to transitioning between sequential screens.
2. Description of the Related Art
This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present invention, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present invention. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
One use which has been found for computers has been to facilitate the communication of information to an audience. For example, it is not uncommon for various types of public speaking, (such as lectures, seminars, classroom discussions, keynote addresses, and so forth), to be accompanied by computer generated presentations that emphasize or illustrate points being made by the speaker. For example, such presentations may include music, sound effects, images, videos, text passages, numeric examples or spreadsheets, or audiovisual content that emphasizes points being made by the speaker.
Typically, these presentations are composed of “slides” that are sequentially presented in a specified order. Typically, to transition between slides, a first slide would be replaced by a second slide on the screen. In some circumstances, some form of animation might be performed on the slides as they move on and off. However, the slides themselves are generally static images. Due to the prevalence of such computer-generated and facilitated presentations, one challenge is to maintain the interest level generated by such presentations, i.e., to keep the audience interested in the material being presented on the screen.
Certain aspects of embodiments disclosed herein by way of example are summarized below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of certain forms an invention disclosed and/or claimed herein might take and that these aspects are not intended to limit the scope of any invention disclosed and/or claimed herein. Indeed, any invention disclosed and/or claimed herein may encompass a variety of aspects that may not be set forth below.
The present disclosure generally relates to techniques for providing object-aware transitions between slides of a presentation. Such object-aware transitions may include identifying each object on the slides being transitioned in and out. The objects or object-types may then be individually manipulated as part of the transition, such as by application of various effects, That is, the transition process may account for and independently animate or otherwise transition each of the objects or object-types composing the different slides.
In some instances, such object awareness can be leveraged as part of the transition. For example, in one embodiment, the same object, such as a graphic, word, number, or characters in a word or number, may be present in the outgoing and incoming slides. In one such example, the transition may take advantage of the presence of the common objects in the outgoing and incoming slides to provide an effect or animations specifically for those objects present in both slides. In this way, the presence of the object in both slides may be used to tailor the slide transition.
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description of certain exemplary embodiments is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
One or more specific embodiments of the present invention will be described below. These described embodiments are only exemplary of the present invention. Additionally, in an effort to provide a concise description of these exemplary embodiments, all features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
The disclosure is generally directed to providing object-aware transitions between slides of a presentation. In particular, in accordance with the present disclosure, different objects within each slide are identified and can be separately and independently handled during slide transitions. In certain embodiments, this involves identifying objects present in both an outgoing and incoming slide and providing specific animation or handling for those objects. With this in mind, an example of a suitable device for use in accordance with the present disclosure is as follows.
An exemplary electronic device 100 is illustrated in
In the presently illustrated embodiment, the exemplary electronic device 100 includes an enclosure or housing 102, a display 104, input structures 106, and input/output connectors 108. The enclosure 102 may be formed from plastic, metal, composite materials, or other suitable materials, or any combination thereof. The enclosure 102 may protect the interior components of the electronic device 100 from physical damage, and may also shield the interior components from electromagnetic interference (EMI).
The display 104 may be a liquid crystal display (LCD), cathode ray tube (CRT) or other suitable display type. For example, in one embodiment, a suitable LCD display may be based on light emitting diodes (LED) or organic light emitting diodes (OLED). In one embodiment, one or more of the input structures 106 are configured to control the device 100 or applications running on the device 100. Embodiments of the portable electronic device 100 may include any number of input structures 106, including buttons, switches, a mouse, a control or touch pad, a keyboard, or any other suitable input structures. The input structures 106 may operate to control functions of the electronic device 100 and/or any interfaces or devices connected to or used by the electronic device 100. For example, the input structures 106 may allow a user to navigate a displayed user interface or application interface.
The exemplary device 100 may also include various input and output ports 108 to allow connection of additional devices. For example, the device 100 may include any number of input and/or output ports 108, such as headphone and headset jacks, video ports, universal serial bus (USB) ports, IEEE-1394 ports, Ethernet and modem ports, and AC and/or DC power connectors. Further, the electronic device 100 may use the input and output ports 108 to connect to and send or receive data with any other device, such as a modem, external display, projector, networked computers, printers, or the like. For example, in one embodiment, the electronic device 100 may connect to a scanner, digital camera or other device capable of generating digital images (such as an iPhone or other camera-equipped cellular telephone) via a USB connection to send and receive data files, such as image files.
The electronic device 100 includes various internal components which contribute to the function of the device 100.
In the presently illustrated embodiment, the components may include the display 104 and the I/O ports 108 discussed above. In addition, as discussed in greater detail below, the components may include input circuitry 150, one or more processors 152, a memory device 154, a non-volatile storage 156, expansion card(s) 158, a networking device 160, and a power source 162.
The input circuitry 150 may include circuitry and/or electrical pathways by which user interactions with one or more input structures 106 are conveyed to the processor(s) 152. For example, user interaction with the input structures 106, such as to interact with a user or application interface displayed on the display 104, may generate electrical signals indicative of the user input. These input signals may be routed via the input circuitry 150, such as an input hub or bus, to the processor(s) 152 for further processing.
The processor(s) 152 may provide the processing capability to execute the operating system, programs, user and application interfaces, and any other functions of the electronic device 100. The processor(s) 152 may include one or more microprocessors, such as one or more “general-purpose” microprocessors, one or more special-purpose microprocessors and/or ASICS, or some combination thereof. For example, the processor 152 may include one or more instruction processors, as well as graphics processors, video processors, and/or related chip sets.
As noted above, the components may also include a memory 154. The memory 154 may include a volatile memory, such as random access memory (RAM), and/or a non-volatile memory, such as read-only memory (ROM). The memory 154 may store a variety of information and may be used for various purposes. For example, the memory 154 may store firmware for the electronic device 100 (such as a basic input/output instruction or operating system instructions), other programs that enable various functions of the electronic device 100, user interface functions, processor functions, and may be used for buffering or caching during operation of the electronic device 100.
The components may further include the non-volatile storage 156. The non-volatile storage 156 may include flash memory, a hard drive, or any other suitable optical, magnetic, or solid-state storage medium, or a combination thereof. The non-volatile storage 156 may be used to store data files such as media content (e.g., music, image, video, and/or presentation files), software (e.g., a presentation application for implementing the presently disclosed techniques on electronic device 100), wireless connection information (e.g., information that may enable the electronic device 100 to establish a wireless connection, such as a telephone or wireless network connection), and any other suitable data.
The embodiment illustrated in
The components depicted in
Further, the components may also include a power source 162. In one embodiment, the power source 162 may be one or more batteries, such as a lithium-ion polymer battery. The battery may be user-removable or may be secured within the housing 102, and may be rechargeable. Additionally, the power source 162 may include AC power, such as provided by an electrical outlet, and the electronic device 100 may be connected to the power source 162 via a power adapter. This power adapter may also be used to recharge one or more batteries if present.
With the foregoing discussion in mind, various techniques and algorithms for implementing aspects of the present disclosure on such devices 100 and accompanying hardware and memory devices are discussed below. Turning to
The presentation application may provide multiple modes of operation, such as an edit mode and a presentation mode. In such an embodiment, when in the edit mode, the presentation application may provide a convenient and user-friendly interface for a user to add, edit, remove, or otherwise modify the slides of a slide show, such as by adding text, numeric, graphic, or video objects to a slide. To display a created slide or a sequence of slides in a format suitable for audience viewing, a presentation mode of the presentation application may be employed. In some embodiments, the presentation application may provide a full-screen presentation of the slides in the presentation mode, including any animations, transitions, or other properties defined for each object within the slides.
As used herein, a “slide” should be understood to refer to such a discrete unit of an ordered or sequential presentation. Such a slide, therefore, may be understood to function as a container for a set of objects (as discussed below) that together convey information about a concept. For example, a slide may contain or include different types of multimedia objects (e.g., text, numbers, images, videos, charts, graphs, and/or audio, and so forth) that explain or describe a concept to which the slide is directed and which may be handled or manipulated as a unit due to their being associated with or contained on the slide unit. Further, because a slide may contain multiple objects, a slide may have an associated z-ordering of those objects as they are displayed on the slide. That is, to the extent that objects on the slide may overlap or interact with one another, they may be ordered or layered with respect to a viewer such that some objects are on top of or beneath other objects as they appear on the slide. In this way, a slide may not only have a width and length associated with it, but also a depth.
The order or sequence of the slides in a presentation or slideshow is typically relevant in that the information on the slides (which may include both alphanumeric (text and numbers) and graphical components) is meant to be presented in order or sequence and may build upon itself, such that the information on later slides is understandable in the context of information provided on preceding slides. That is, there is a narrative or explanatory flow associated with the ordering or sequence of the slides. As a result, if presented out of order, the information on the slides may be unintelligible or may otherwise fail to properly convey the information contained in the presentation. This should be understood to be in contrast to more simplistic or earlier usages of the term “slide” and “slideshow” where what was typically shown was not a series of multimedia slides containing sequentially ordered content, but projected photos or images which could typically be displayed in any order without loss of information or content.
As used herein, the term “object” refers to any individually editable component on a slide of a presentation. That is, something that can be added to a slide and/or be altered or edited on the slide, such as to change its location, orientation, or size or to change its content, may be described as an object. For example, a graphic, such as an image, photo, line drawing, clip-art, chart, table, which may be provided on a slide, may constitute an object. Likewise, a character or string of characters may constitute an object. Likewise, an embedded video clip may also constitute an object that is a component of a slide. Therefore, in certain embodiments, characters and/or character strings (alphabetic, numeric, and/or symbolic), image files (.jpg, .bmp, .gif, .tif, .png, .cgm, .svg, .pdf, .wmf, and so forth), video files (.avi, .mov, .mp4, .mpg, .qt, .rm, .swf, .wmv, and so forth) and other multimedia files or other files in general may constitute “objects” as used herein. In certain graphics processing contexts, the term “object” may be used interchangeably with terms such as “bitmap” or texture”.
In one embodiment, the objects provided on the slides of a presentation are identified, automatically or by a user, allowing each object to be independently manipulated, such an animated, when transitioning between slides. That is, for a slide being transitioned out, each object may be separately handled, so that different objects or types of objects may undergo a different effect as part of the transition. For example, turning to
By identifying each object on a slide, effects for transitioning an object on or off the screen may be specified (automatically or by a user) for each object or each type of object (such as graphics files, text boxes, videos, etc.) independently of one another. The effect used in transitioning an object may depend on some characteristic of the object, such as a file type, location on the slide, color, shape, size, and so forth. For example, how close an object is to an edge may be a factor in determining whether the object will be animated on to or off of a slide and, if such an animation is selected, which edge the animation will occur relative to, how fast the animation will occur, and so forth. While the transition effects for different objects or object types may be handled automatically in one embodiment (such as based upon the factors described above), in other embodiments, a user may specify what effects are associated with the transition of an object on or off the screen. For example, a user may use a presentation application interface screen to specify properties of one or more objects on a slide, including transition effects for moving the object on or off the screen.
Such object or content, aware transitions differ from traditional approaches to transition between slides in which each slide is represented by a static image (and, therefore, treated as a single unit) and transitions would generally be an animation between the static images. However, individual objects on the slides were not individually manipulated, such as animated, during transitions. Thus, object-aware transitions, in the present context, are transitions that have access to the different individual objects of which the slides or slides are composed, and where each object can be animated or otherwise manipulated independent of the others.
In terms of the various effects that each object can be subjected to in such object-aware transitions, virtually any animation and/or manipulation that can be performed on the respective type of object may be suitable. By way of example, turning now to
In practice, the identification of the graphic and character objects in the slide may be accomplished automatically, such as by an algorithm of a presentation application that identifies such objects by file type extensions or other indicators, or by user designation that the slide component is an object for purposes of object-aware transitions. Once the objects are identified and a transition effect, such as “rotate and slide”, is selected for the slide by the user, the manner in which the selected effect is applied to each object in the slide may be determined automatically. For example, it may be automatically determined that all objects will rotate and slide off of the slide from the vertical center of the slide, and the animation of each object may be determined accordingly. Alternatively, in other embodiments, the user may be able to specify particular effects or animations for each object of the slide, or to specify the manner in which an effect is accomplished, such as with or without vertical centering for an individual object.
In another example, turning now to
In yet another example, a sequence of screenshots depicting another animated slide transition is depicted in
In a further example, a sequence of screenshots depicting another animated slide transition is depicted in
In another example, a sequence of screenshots depicting another animated slide transition is depicted in
The preceding examples are illustrative of the manner in which individual objects on a slide may be differentially or independently manipulated, e.g., animated, without regard to other objects in a slide. The preceding examples, however, are not exhaustive, and it is to be understood that any animation or manipulation suitable for an object identified in a slide may be applied to that object without regard to the other objects in the slide or the objects in the previous or next slides in certain object-aware transition embodiments.
Further, as previously noted, the identification and assignment of animations may be largely automatic in some embodiments. For example, a user may design two or more sequential slides, such as by placing the desired objects on each slide in the desired locations. The user may then simply select a type of transition, such as the above-described isometric transition, for transitioning between two or more of the slides. In an automated implementation, the presentation application may, knowing only the selected transition and the type and location of the objects on the slides, assign suitable animation direction, speeds, effects, translucencies, and other animation effects to each object being transitioned in and out.
The preceding discussion describes implementations in which the transitions between slides do not take into account what the objects are that are in the slides or whether the same object is present in both the outgoing and incoming slide. However, in certain embodiments, the object-aware transition may take such object persistence into account. For example, in certain implementations where the same object, be it a text, numeric, graphic, and/or video object, is present in consecutive slides, an animation or manipulation may be applied to the object while maintaining the object on the screen. Thus, in one implementation, an object may be present in consecutive slides (though it may be in different locations, orientations, or at a different scale in the two slides) and an animation may be applied to the object such that the object appears to move, turn, resize, and so forth to reach the appropriate size, location, and/or orientation in the second slide after the transition.
As in the previously described embodiments, the identification of the object may be performed automatically or based on user inputs. In addition, the determination that the object is present in consecutive slides, though perhaps with different size or location properties, may be performed automatically. For example, the object may be a .jpg or a .gif image which is referenced by a common file name or location (such as an image gallery or library) when placed on the first and second slides or may be a text or numeric object that contains the same characters. Thus, an automated routine may determine that the same image file or character string (word, phrase, sentence, paragraph, and so forth) is present in both slides, even if it is at different locations in the slides or at different sizes. The presentation application may then also evaluate different attributes of the common object, such as size, position, color, rotation, font, and so forth, to determine if any of these attributes that differ between slides would preclude animation from one to the other. If however, the differences are susceptible to a transitional animation, the presentation application may automatically determine an animation for the transition between slides such that the common object appears to be moved, scaled, rotated, and so forth into the proper location for the incoming slide. Thus, in this embodiment, the user may do no more than design two sequential slides with one or more objects in common and the presentation application will identify the common objects on the sequential slides and provide appropriate animated transitions for the common objects when going from the first slide to the second.
By way of example and turning now to
In this example, a first slide 212 and a second slide 214 are provided to a routine capable of identifying (block 216) objects that can be animated and of acquiring information (e.g., metadata) associated with each identified object. For example, the identification process may be based on file name extensions, presence of text or characters, and so forth. In some embodiments, identified objects may also be generally characterized or classified based on the identifying feature (such as an image, shape, table, chart, movie, character string, etc.) to facilitate subsequent processing. In addition, as noted above, information or metadata for each identified object may also be determined. Such information or metadata may include, but is not limited to: a filename, a path describing a custom shape (such as a square, circle, star, and so forth), text attributes (such as automatic capitalization style, font metric information, or the character string itself), shadows and/or reflections applied to the object, masks or alpha masks applied to the object, rotation and/or scaling applied to the object, and so forth.
The objects and associated metadata 218, 220 identified for the respective first and second slides 212, 214 may be used to match and order (block 222) the objects such that objects present in both the first slide 212 and the second slide 214 are identified. For example, the objects identified in the first slide 212 and the second slide 214 may be compared in a pairwise process such that each object is matched with a corresponding object in the other slide or is determined to be present in only the first slide or the second slide (i.e., is unmatched). Based on the matching process, a correspondence table 224 may be generated specifying which objects in the first slide 212 correspond to which objects in the second slide 214.
In certain embodiments, different degrees of matching may be accommodated in the correspondence table 224. For example, an object may be determined to be present in both the first slide 212 and the second slide 214 in an identical form or with only changes in location, rotation, scale, and/or opacity. Such a match may be considered a “hard” or “solid” match in view of the certainty that the object is the same, i.e., is matched, or in view of the relative ease by which the object can be transformed from its form in the first slide 212 to its form in the second slide 214. Further, some metadata may indicate a clear identity match, such as where two image filenames are the same or where two text strings are identical and have the same style and metric information.
In other instances, a match may be construed to be a “soft” match where there is less certainty as to the match and/or where the transformation of the object between the first slide 212 and the second slide 214 is not simply a matter of moving, scaling, rotating or adjusting the opacity of the object. For example, an object in the first slide 212 and an object in the second slide 214 may have generally the same shape but may have different shadow styles, reflection styles, and/or fill styles. Such objects may be deemed to be a soft match in that they may represent the same object in the first and second slides 212, 214 but with some difference or differences that are not resolvable simply by moving, scaling, rotating, and/or changing the opacity of the object.
In addition to establishing the correspondence between objects in the first and second slides 212, 214, the matching and ordering step (block 222) may also establish an ordering 226 of the identified objects in the Z-dimension of the slides, i.e., in the depth dimension with respect to the slides. For example, different effect layers which can be viewed as overlying or underlying a slide may be viewed as being different layers in the Z-dimension. Such a synthesized Z-ordering 226 may be generated using the relative Z-positions of each object on the first slide 212 and/or second slide 214 such that the synthesized Z-ordering 226 provides a transitional or bridge Z-ordering between the two slides that may be used in a transition animation of the matched objects.
Turning now to
However, if the high level screen (block 244) determines that objects on both the first and second slide 212, 214 may potentially be matches 246 due to the objects being the same type, the objects in question may be characterized as possible matches 246. The possible matches 246 may be subjected to additional analysis to determine if object matches are present in both outgoing and incoming slides. For example, in the depicted embodiment, the possible matches 246 may be subjected (block 250) to denial testing to determine whether objects found in the first and second slide 212, 214 are different from one another.
In one embodiment, such denial testing may be implemented in a pairwise manner, i.e., each object 218 of a given type on the first slide 212 may be compared in a pairwise manner with each object 220 of the same type on the second slide 214. For example, each image object on the first slide 212 may be compared with each image object on the second slide 214 to check for differences between each pair of image objects. Examples of differences which may be checked for include, but are not limited to, differences in the aspect ratios of the objects, different masks associated with the objects, different or dissimilar filenames, and so forth. If an object is determined to be different from every object of the same type in the other slide, the object may be characterized as an unmatched object 248. If an object cannot be unequivocally characterized as different from every object of the same type on the other slide, the object maybe characterized as a possible match 246.
In some embodiments, such as the depicted embodiment, the denial tests (block 250) may merely throw a match in doubt, without ruling a match out. For example, an object on the first slide and an object on the second slide may have different shadow styles, reflection styles, fill styles, and so forth, but may be otherwise similar. Such possible matches may be characterized as “soft” matches 252 in that the objects clearly have some degree of dissimilarity, but not sufficient dissimilarity to state with certainty that the objects are not identical except for some visual distinction, such as shadow, reflection, fill, border thickness, and so forth.
The possible matches 246 and possible soft matches 252 may be further subjected to a confirmation test (block 254) to determine whether objects found in the first and second slide 212, 214 are identical to one another. For example, a confirmation test may verify that text strings found in the first slide 212 and the second slide 214 are identical to one another and/or may verify that the font metric and style information are the same. Likewise, in confirmation testing image objects or movie objects, the confirmation test may confirm that the objects being compared share the same source file (such as by comparing file name and file location). Shape objects may be confirmation tested to confirm that the shape objects have the same border path, and so forth. Group objects may be confirmation tested to confirm that they share the same sub-objects and aspect ratio, and so forth. Failure of a confirmation test may result in an object being classified as an unmatched object 248. A successful confirmation of two objects in different slides may result in those objects being deemed matches 258. In some embodiments, a confirmation test may also deem two objects as a soft match where unequivocal confirmation is not available.
In one embodiment, when an object in the first slide 212 and an object in the second slide 214 successfully pass both denial tests and confirmation tests, the pair of objects may be marked as a set or match 258 and both objects will be removed from further pairwise comparisons. Likewise, if a pair of objects is judged a soft match in either or both of the denial or confirmation test, the pair of objects may be marked as a possible soft match 252. In some embodiments, such soft matched objects may be removed from further comparison while in other embodiments soft matched objects may be subjected to further pairwise comparisons to determine if a full or hard match can be confirmed.
Based on whether an object in the first slide 212 or second slide 214 is classified as being a match with an object in the other slide or as being unmatched with an object in the other slide, a correspondence table 224 may be generated (block 262). Such a correspondence table 224 may, in one embodiment, list each object in the two slides along with an indication of whether or not a match was identified and, if a match was identified, what object in the other slide constitutes the match. Alternatively, the correspondence table may only list the matched objects, with objects not listed on the table being understood to have no match. In embodiments in which soft matches are identified, the correspondence table 224 may contain an additional field or descriptor to indicate that the match is soft, i.e., not exact or identical. Further, in some embodiments, a numeric or quantitative measure of the certainty of the match may be provided in lieu of, or in addition to, a qualitative (i.e., “hard” or “soft”) assessment.
In the depicted example the correspondence table 224, along with the orders 264, 266 of objects in the first and second slides, may be used to generate (block 270) a synthesized Z-order 226 of the objects in the two slides 212, 214. In one example, to establish the synthesized Z-order 226 of the identified objects, the Z-order 264 of the objects identified on the first slide (e.g., the outgoing slide) may be used to initially populate the synthesized Z-order 226. For each unmatched object on the outgoing slide (e.g., first slide 212) a determination may be made of which matched object occurs next in the outgoing slide's Z-order 264 and the respective unmatched object is inserted immediately before that matched object in the synthesized Z-order list 226. The incoming slide (e.g., second slide 214) may be handled similarly, but in reverse order, to maintain the correct relative Z-orders. Once completed, the synthesized Z-order 226 may provide a composite listing of the objects on both the outgoing and incoming slides (i.e., first slide 212 and second slide 214) with the appropriate “depth” or layer for each object on the slides for use in an animated transition between the slides.
The correspondence table 224 and the synthesized Z-order may be used to generate a series of animation frames for transitioning from the first slide 212 to the second slide 214, as depicted by the flowchart 300 of
In the depicted example, each object on the first slide 212 and the second slide 214 may be iteratively processed (block 308) based on the order specified in the synthesized Z-order 226. As part of the iterative processing, each object may be checked against the correspondence table 224 to determine if it is only on the outgoing slide (e.g., first slide 212), only on the incoming slide (e.g., second slide 214), or on both the outgoing and incoming slides.
If an object is determined (block 312) to be present on only the outgoing slide or is determined (block 316) to be present on only the incoming slide, a specified outgoing animation 318 or incoming animation 320 may be performed on the object. For example, if an object is determined to be only on the outgoing slide, the object may undergo a dissolve animation or an animation moving the object off the screen that occurs over all or part of a specified transition interval. For instance, in one embodiment an object present only on the outgoing slide may have its opacity increased from 0% to 100% over the entire transition interval. Conversely, an object present only in the incoming slide may undergo a materialize animation or an animation moving the object onto the screen over all or part of the specified transition interval. For example, an object present only on the incoming slide may have its opacity decreased from 100% to 0% over the entire transition interval.
In the depicted embodiment, if an object is determined (block 324) to be present in both the outgoing and incoming slides, an animation path 330 is generated (block 328) to transition the object from an initial position on the outgoing slide and a final position on the incoming slide. Information (e.g., metadata) about the object on each slide may be used in generating the animation path 330 to determine if the object has different scaling, rotation, and/or opacity on the two slides. If such differences are determined to exist for the object on the two slides, the animation path 330 may include scaling, rotating, and/or changing the opacity of the object from how it appears on the first slide 212 to how it appears on the second slide 214 such that a smooth transition of the object is perceived.
To animate the transition of the object between the first and second slides 212, 214 the object may be iteratively drawn (block 334), i.e., animated, at appropriate positions along the animation path based on the elapsed time of the transition interval. For example, if the specified transition interval is 1 second and the animation is to occur at 60 frames per second, the object will be drawn 60 times during the 1 second transition, with each drawing of the object corresponding to a respective position on the animation path 330. That is, in this example, the first drawing of the object along the animation path 330 will occur at t1= 1/60th of a second into the transition and will correspond to the object as it appears at a point or step 1/60 of the way along the animation path 330. Likewise, halfway through the transition animation, the object will be drawn at t30=½ of a second into the transition and will correspond to the object as it appears at the halfway point of the animation path 330.
In certain embodiments, the designation of an object match as being a soft match may affect the transition animation. For example, an object present in both the first slide 212 and the second slide 214 may be characterized as a soft match due to having certain dissimilarities in the respective slides that are not sufficient to characterize the objects as unmatched (such as borders of different thickness on two otherwise identical shapes or different filler, shadow, or reflection effects applied to otherwise identical shapes). In one such embodiment, the animation path 330 may include a fade out of the object as it appears on the first slide and a fade in of the object as it appears on the second slide to smoothly fade in the dissimilar features. In such embodiments, shaders or shader functionality provided by a graphics processor or chipset may be used to generate weighted or intermediate images on the animation path 330 that correspond to transitional images of the object as it appears in the first and second slide 212, 214. In this manner, the dissimilarities between the object on the first and second slides 212, 214 may be smoothly faded out or in over the course of the transition animation.
In certain embodiments, the animation of unmatched objects may be handled differently if matched objects are present than when no matched objects are present. For example, in one embodiment, if no matched objects are present on the first slide 212 and the second slide 214, the respective objects may be faded out and faded in over the full transition interval. That is, in such an embodiment, the objects on the outgoing slide may be faded out (i.e., opacity increasing from 0% to 100%) over the full length of the transition interval, such as 2 seconds, while the incoming objects may be materialized (i.e., opacity decreasing from 100% to 0%) over same interval. However, in the presence of one or more matched objects on the first and second slides 212, 214, the animation of the unmatched objects may be altered, such as accelerated. For example, in the presence of one or more matched objects being animated along an animation path 330 during a slide transition, the unmatched objects may be undergo an accelerated, i.e., shorter, fade in or fade out animation. For instance, in such an example an unmatched object being faded out in the presence of matched objects may be faded out by the halfway point of the transition or less, such as by the time 25%, 30%, or 33% of the transition interval has elapsed. Similarly, an unmatched object being faded in in the presence of matched objects may not begin fading in until the halfway point of the transition interval has been reached or later, such as by the time 66%, 70%, or 75% of the transition interval has elapsed.
With the foregoing discussion in mind, certain examples of such object-aware transitions are provided where one or more objects are present in both the outgoing and the incoming slide. For example, turning now to
In another embodiment of an object-aware transition that takes into account the persistence of objects between slides, a character-based example is provided. In this example, the actual characters, be they letters, numbers, punctuation, etc., on a slide may be evaluated separately for persistence between slides. That is, the characters within a text and/or numeric string may be considered to be the objects in the present context. In an automated implementation, when evaluating the character objects to determine if the character object is present in consecutive slides, the presentation application may evaluate different attributes of the character, such as the letter or number itself, the font, the font size, the color, the presence of certain emphasis (highlight, underlining, italics, bold, strikethrough, and so forth) and other attributes that may affect the similarity of the perceived character in consecutive slides. In certain embodiments, the character might be identical across the evaluated attributes to be retained or animated between slides. In other embodiments, certain attributes, such as color changes, emphases, and so forth, may still allow animation and retention of the character between slides.
In this example, while the characters may be present in consecutive slides, they need no be used in the same words or numbers, and therefore need not remain in the same order. Turning to
In the depicted example, the non-persistent characters are slid away and faded from view as part of the transition while the persistent character objects 350 remain in view and are slid into their new positions consistent with the word displayed on the second slide. As in previous embodiments, the character objects 350 may be animated or manipulated independently of one another. As will be appreciated, the present example depicts letters, however the characters may also be numbers, symbols, punctuation and so forth. In addition, though the present example described sliding and fading (or retaining) of the characters, in other embodiments other types of character animation may be employed. For example, instead of sliding on the screen, the transition animation may instead rotate or flip the word about a vertical or horizontal axis, with the changes to the word being accomplished during the rotation or flip of the word. Indeed, any suitable form of character animation may be employed in manipulating characters in such an embodiment. Further to the extent that a character or character string may be present multiple times on either or both of the outgoing and incoming slide, in certain embodiments matching processes, such as those described with respect to
As will be appreciated, the present techniques allow for identification of objects on slides of a presentation and the independent manipulation, such as animation, of the objects during slide transitions. As described herein, in some embodiments, no weight is given as to whether the same object or objects are present in consecutive slides. However, in other embodiments, the presence of an object or objects in consecutive slides may be noted and manipulation of the objects during slide transition may take advantage of the persistence of the objects. In certain embodiments, as described herein, the identification of objects and/or the transitional manipulation of the identified objects may be automatically derived, such as by a presentation application executing on a processor-based system.
While the invention may be susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and have been described in detail herein. However, it should be understood that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the following appended claims.
This application is a continuation of U.S. patent application Ser. No. 12/422,808 entitled “Object-Aware Transitions”, filed Apr. 13, 2009, which is a continuation-in-part of U.S. patent application Ser. No. 12,206,217, entitled “Object-Aware Transitions”, filed Sep. 9, 2008, both of which are herein incorporated by reference in their entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12422808 | Apr 2009 | US |
| Child | 12776531 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12206217 | Sep 2008 | US |
| Child | 12422808 | US |
