METHOD, SYSTEM AND USER INTERFACE FOR CREATING AND DISPLAYING OF PRESENTATIONS
A method and system for creating at least one presentation, comprising: at least one computer; at least one application operable on the at least one computer, the at least one application configured for: receiving a plurality of assets; and allowing at least one user to define the at least one presentation over the time that the at least one presentation is to be displayed, using at least two assets to be simultaneously presented for at least one selected point in time.
This application claims the benefit of U.S. Provisional Application No. 61/354,984, filed Jun. 15, 2010, which is incorporated by reference in its entirety.
BRIEF DESCRIPTION OF THE FIGURESThe widgets can comprise at least one text chat widget, at least one audio/video chat widget, at least one asset browser widget, at least one discussion widget, at least one audio recording/playback widget. at least one video recording/playback widget, at least one stream recording/playback widget, at least one audio/video editing widget, at least one document viewing widget, at least one document editing widget, at least one linking widget, at least one activity widget, at least one slide show editing/viewing widget, at least one diagram editing/viewing widget, at least one drawing suite widget, at least one whiteboard widget, at least one polling widget, at least one survey widget, at least one assessment widget, at least one spreadsheet widget, at least one user list widget, at least one source code viewing and editing widget, at least one tracking widget, at least one, glossary widget, at least one screen sharing and/or screen recording widget, at least one wiki widget, at least one bookmark widget, at least one calculator widget, at least one presentation index widget, at least one layers widget, at least one integrations widget, or at least one third party platform interactive widget, or any combination thereof. It should be noted that any widget can be provided using third-party software. In addition, those of ordinary skill will see that any widget function(s) can be combined with any other widget function(s) to form other widgets.
Referring to
In one embodiment, the creation/playback application 120, can run on the server computer 110 (as shown in
At this point, it should be noted that state change/time definition data can describe and/or define a change to the state of the information presentation (including describing changes in state for the creation playback application itself and describing changes to other state change/time definition objects/data) for a given point in time. The state change/time definition data can specify a state change to be: immediately executed, executed at some point in the future, or executed at some point in the past: or any combination thereof. In this way, state change/time definition data can collectively and together define an information presentation and an information presentation over time, and together with the creation/playback application 120, flexibly accommodate a number of capabilities of the system 100.
In one example of capabilities, a collection of -state change/time definition data for various points in the past and future can represent an information presentation over time and can be received by the creation/playback application. As previously mentioned, state change/time definition objects, in addition to defining state changes to both the application and to other state change/time definition objects, can define state changes to the information presentation, and specifically, state changes as they pertain to the use or state of assets, wherein assets, as well as assets meta-data is also received/to be received by the state-time application. Using such information presentation data as described, the creation/playback application 120 can: render the information presentation over time, visually on a timeline area and/or playback the information presentation by executing the state change/time definition data at the appropriate times, thereby “playing back” the information presentation (e.g., by actuating, activating, and displaying the assets).
As previously detailed, state change/time definition data can be of an immediate run nature; i.e., defined to be executed immediately. In the previous example, one use of immediate run state change/time definition data could be for initializing the application and information presentation. The capability of implementing immediate run slate change/time definition data can support a number of other capabilities of the system. For example, immediate run state changes can be used to initialize the application and the information presentation into a known state, and can allow for a user, at any point in time, including at the application's initialization, to access the information presentation at any point of the information presentation's potential duration, as well as to sync the stale of the application that may be defined for that point in time. Another example using this capability could be where a second user can enter into the application and immediately be synced to the state of the application and information presentation of a first user, thereby immediately replicating exactly what the first user sees at that point in time.
The creation/playback application 120 can continually listen for, receive, process, store and execute all information presentation data, including immediate-run state change/time definition data. In this way, the state of the creation/playback application 120 and the information presentation (and all of both of their constituent parts) can be continually updated and modified in real-time. By providing for essentially any real time change and any real time update, any real-time capability can be achieved, including that of various real-time collaborative capabilities, including, but not limited to: real-time capabilities within widgets (for instance real-time updates to the text chat widget), real-time viewing of information presentations, real-time viewing of many user's devices' cursor pointers and locations, and collaborative editing of information presentations.
Additional details related to the state change/time definition data is further described below with respect to
Referring back to
It should be noted that the various components of
The application load manager module 205 can be an initialization module containing all the logic for instantiating and integrating all other modules within the creation/playback application 120. The application load manager module 205 eon also be responsible for helping to coordinate the creation/playback application's simultaneous capabilities using the various modes (e.g., editor mode, run-time mode, collaboration mode, etc.). In this way, the application load manager module 205 can execute multiple algorithms for such multi-mode capability when needed.
The editor mode module 210, run-time mode module 215, and collaboration mode module 220 can be three or more independent modules (herein referred to collectively as per-mode modules) that can enable the creation/playback application instances to encapsulate, expose and/or contain per-mode focused initialization algorithms and per-mode focused execution algorithms. Each per mode module can enable the creation/playback application 120 to be run in its respective mode. In some embodiments, a per-mode module can be run separately and independently of any dependency on other per-mode modules, while other modules (such as the application load manager module 205) can also use various combinations of the per mode modules to combine the per-mode capabilities together within the application and by users of the application.
The per-mode modules can receive the CARA 235 and the full creation/playback application context, and can populate and/or inject custom per-mode instructions/functionality and capability into any and all dependent module instances in the application. For example, custom handling capability and routines can be provided and/or injected into: the timeline area renderer module 286 to support timeline area rendering capability; or the user input analyzer and router module 240 to support per mode user input handling functionality; or any combination thereof.
The bus/network communications I/O manager 225 can be responsible for all communications between the creation/playback application 120 and; external support components; external data stores; other remote applications (e.g., other creation/playback applications instances in use by other users); any other network connected resource, or other remote systems; or any combination thereof. For example, some creation/playback application instances can be dependent on receiving live data from ether creation/playback application instances or from the system 100. In addition, the bus/network communications I/O manager 225 can be responsible for communications between the creation/playback application 120 and; external application support systems 203; external database(s) 201; or other remote systems 202; or any combination thereof. In some embodiments, the bus/network communications I/O manager 225 can communicate using numerous protocols (e.g., TCP/IP, IP protocols).
The data loader/initial application updater module 230 can be responsible tor receiving information presentation data from the bus/network communications I/O manager module 22$. The data loader/initial application updater module 230 can then add the received data or references to the data to various data store modules within the creation/playback application 120. The data loader/initial application updater module 230 can also identify any state change objects that need to be executed and pass the state change objects off for execution. The data loader/initial application updater module 230 can also; add assets and assets meta data to the local asset database 245; add non-immediate (future or past state change data) to the local state change and timing database 250; identify state change objects which should be immediately executed upon receipt and pass these state change objects to the state change proxy module 260 for immediate execution.
The CARA (Central Application Reference and API) 235 can provide and/or implement structured APIs and make the creation/playback application 120 addressable from any other module or component within the creation/playback application 120. In some embodiments, any module and any state change can be invoked through access via CARA 235. In some embodiments, CARA 235 can: provide access to all application state data; organize access to some or all other modules/data/objects/instructions within the creation/playback application 120; or expose/implement encapsulated state change routines; or any combination thereof.
The user input analyzer and router module 240 can handle user input for all of the user interface module's submodules. The user input analyzer and router module 240 can also, independently, or in conjunction with injected dependencies (see description of per-mode modules 210,215,220), analyze: the state of the information presentation and the information presentation stale or data for any given point in time, the state of the creation/playback application 120: or the source graphical user interface (GUI) of the input: or any combination thereof. In addition, the user input analyzer and router module 240 can respond or perform actions based on such analysis. The actions it can take can include: updating/adding/deleting state changes and/or state change/time definition data and/or state change/time definition objects; prompting for additional user input: identifying updated/added/deleted state changes and/or state change objects which necessitate notification of the update/add/change to other components of the creation/playback application 120; or notifying and providing dependent modules with changes to state changes and/or state change objects (note that dependent modules can include state change proxy module 260, local state change and timing database 250, multi data broadcaster module 265); or any combination thereof. The user input analyzer and router module 240 can be responsible for implementing the contextual and predictive user interface capabilities further described with respect to
The local asset database 245 can store assets and/or asset instances along with metadata. The local state change and timing database 250 can store local data for any state change objects.
The time controller and manager module 253 can be responsible for implementing/executing all time related aspects of the creation/playback application 120 within information presentations. A time controller (e.g., contained within the time controller and manager module 255) can be invoked on an as-needed basis by state change commands/objects through the state change proxy module 260, such as to initialize, start or stop the time controller and/or the playback of the information presentation. In addition, in some embodiments the user can start or stop or activate or inactivate the time controller, and/or the playback of the information presentation, or the time controller can be started automatically by the creation/playback application 120. The time controller can implement an internal clock management functionality based on the system 100's hardware or software clock capabilities and data received from subsequent state change invocations. For example, suppose an information presentation starts with a set of predefined state change/time changes, contained and included in the initialization payload processed after the application initializes. The predefined state change/time data can include immediate run state changes (e.g., intended to initialize the information presentation and/or initialize or configure the creation/playback application 120). These immediate run state changes can invoke the time controller with relevant data describing the structure of the information presentation, whereby the information presentation is a time oriented presentation by virtue of the data provided. Using this data, the time oriented information presentation can then be implemented and managed over time, wherein the time controller executes the relevant state changes described in the state change/time definition data and state change/time data objects by invoking a state change proxy module (and passing the state change/time data/objects) when the appropriate time in the duration of information presentation is reached. The time controller and manager module 255 can be started as a routine on CARA 235 and/or invoked through and immediate state change command/object, or started by the user or automatically by the creation/playback application as previously described.
The state change proxy module 260 can execute all state changes contained/described in the collection of l-n state change/time data/objects it is invoked with. Additionally, the state change proxy module 260 can interact/query on an as-needed basis with the dependent state change module 261. The state change proxy module 260 can also be used to implement the automatic/manual mode configurations of the system 100. For example, the stale change proxy module 260 can monitor values on CARA 235, and if it is determined that the user has entered manual mode, can prevent certain classes of state changes from being invoked/executed (e.g., layout change state changes).
The dependent state change module 261 can analyze a collection/list of state changes to be executed, and can augment the collection/list with additional implied or dependent, state change directives, if needed.
The multicast data broadcaster module 265 can be responsible for: generating messages and/or state change/time definition data/objects for all dependent creation/playback application instances and then passing messages/objects to the bus/network communications I/O manager module 225 to be sent outside the creation/playback application 120, for example, such as for sending real lime updates to other user's creation/playback application instances, either directly to such instances, or to instances external application support systems 203 for the recipient system to determine all dependent creation/playback application instances and send to all dependent instances; or any combination thereof.
The asset load manager 275 can be responsible for all asset loading needs in the creation/playback application 120. As such, the asset load manager can monitor or listen to the local state change and timing database 250 for updated/added/removed state change/time objects. Upon notification and receipt of the updated/added/removed object, the object can be analyzed for references to any dependent assets referenced by the state change object. In addition, the asset load manager 275 can provide for speed and efficiency within the system 100 and across any computer networks used, as the asset load manager 275 can contain logic to load assets or portions of assets for the information presentation as the assets are needed.
The user interface module 280 can comprise modules that enable an editor and/or a user to define and/or control a presentation by allowing the editor and/or user to enter commands or provide user input through a user interface, as well as to visually represent the state of the system and the information presentation. The user interface module 280 can accommodate multiple approaches for defining, playing back and interacting with an information presentation. The user interface module 280 can be comprised of a stage module 281, a timeline display area module 282, a GUI controls module 283, a layout manager module 284 and a timeline area renderer module 285.
The stage module 281 can be the graphical area in which all elements of the creation/playback application 120 and information presentation are visually displayed. The elements that can be visually displayed can include, but are not limited to, all graphical user interface controls for the creation/playback application 120 and all assets.
The timeline display area module 282 can be the graphical area in which all elements relating to the information presentation's and creation/playback application's state over time can be visually displayed, including a timeline(s) and tracks as described below. In addition, the timeline display area can visually display other elements of the creation/playback application 120 and information presentation.
The GUI controls module 283 can encapsulate and/or provide any and all necessary graphical user interface elements and components used anywhere in the user interface by other user interface modules. Part or the controls module 283 can be provided/fulfilled by the native support of the system 100 on which the creation/playback application 120 is running.
The layout manager module 284 can comprise many components/instruction sets for providing various layouts for the assets within the creation/playback application 121 or on the information presentation scream(s). The layout manager module 284 can provide flexible, input driven algorithms for laying out l-n assets in various positions. It can also encapsulate and provide for automatic or convenience layout capabilities with additional encapsulated algorithms with predefined default values or which can evaluate the context of the assets which it is laying out and automatically determine the best layout. With respect to evaluation or context and subsequent automatic layout, the layout manager module 284 can analyze various aspects of the system 100, including, but not limited to: number of assets to be laid out, type of assets, dimensions and/or aspect ratio of assets to be laid out (e.g., 8.5 inch by 11 inch document, 800 pixel by 600 pixel presentation document, 4:3 video document, 16:9 video document, etc), font size(s) of text within the assets, or available space on the user interface within creation/playback application 120 or information presentation on the particular device that is being used for display; or any combination thereof. For example, depending on the configuration of the application, the layout manager module 284 can determine that two assets are to be displayed (e.g., a 4:3 video, and an 800 by 600 presentation), and then determine that there is enough available space to layout the assets side by side on the screen. Likewise, the layout manager module 284 could determine that there is not enough space to optimally display both assets, and provide a side by side layout which only can show one asset at a time but can allow the user to “slide” back and forth between the two assets. In this scenario, it could also determine to show the two assets as one on top of the other.
The timeline area renderer module 286 can be responsible for rendering relevant state change and time definition data visually in the timeline area(s) and attaching GUI behavior/interaction handling code/instructions to the timeline area(s). The timeline area renderer module 286 can: contain core and generic subroutines used in various modes as well as routines intended for a per mode basis and/or be injected with additional per-mode subroutine codes in order to render the timeline area.
Various ModesIn one embodiment, the user can interact with the at least one timeline, the timeline being rendered visually by the user interface module(s), to define the information presentation, wherein the creation/playback application can create state change/time definition data fen the defined state changes that comprise the defined information presentation. An additional editor mode capability can include the ability for the creation/playback application 120 to enter a record mode. While the record mode is activated, a user can make state changes to an information presentation and assets in real-time and the creation/playback application 120 can monitor and record all input made by the user as it relates to state changes of the information presentation, assets, creation/playback application 120, etc. Some specific examples of recordable state changes include, but are not limited to: actuating, activating, moving, showing, hiding assets: taring the whiteboard widget; editing a document using the document editing widget; editing a spreadsheet using the spreadsheet editing widget; drawing using the drawing suite widget; motoring with a device's cursor pointer; or manipulating or interacting with any assets or widgets; or any combination thereof. After a record mode session is ended, the recorded state changes can be rendered in the timeline area. The user can repeatedly engage the record mode to either overwrite recorded state change/time definition data or to supplement it with additional recorded state change/time definition data. Recorded state change/time definition data can be immediately edited using the other editor mode capabilities, such as interacting with the timeline area. Additionally, the creation/playback application 120 can persist the information presentation data and it's constituent parts (i.e., to an external database 201, a remote system 202, an external application support system or sub system 203), and recall them again for editing as well as playback at any time. It should be noted that an editor user can include any person or computer capability that uses any device for defining the information. It should be noted that the record mode capability of the system is recording actual changes to the underlying data and state of the creation playback application and the information presentation such that that information presentation and full sequence of events may be “played back” at a later, rather than recording the screen or a video.
As indicated in
The collaboration mode capabilities, enabled in one embodiment of a collaboration mode module 220, can enable users to collaborate in real-time and non real-time in ways that may not be directly supported through any disclosed assets. For example, users of the system could use a collaboration mode capability whereby all users are able to view any other user's interactions or user invoked changes to the state of the information presentation, assets or application. Another example could be where each user can view the cursor indicator or mouse pointer or all other users viewing an information presentation collaboratively (hereinafter called a multi-cursor view). In this example, a multi-cursor view is not necessarily provided for by any other module, and thusly could be provided for by the collaboration mode module 220. When the multi-cursor view is activated the collaboration mode module 220 can send state change/time definition data through the multicast data broadcaster module 265 to notify the other users' applications to also activate this feature immediately. After all users' applications have the feature activated, each of the respective collaboration mode modules 220 can then be responsible for (e.g., while the feature is activated) engaging the multicast data broadcaster module 220 to send the coordinate details of the respective users' cursors as state change/time definition data.
Those of ordinary skill in the art will see that any of the capabilities/functions of any of the modes can be combined with the capabilities of other modes.
By manipulating the information presentation during playback, such as selecting/configuring/changing the layout or adding/removing assets from the screen, or inviting other users to collaborate, the creation/playback application 120 can change from playing the information presentation in its predefined format (automatic play mode) into manual play mode, wherein the creation/playback application 120 can no longer implement some or all of the predefined information presentation's state changes, such as the display/activation of assets and layout changes. The user/editor can immediately switch back to automatic mode with a single user gesture, such as clicking on a button. This capability is also detailed in
The user interface module 280, together with other modules, can accommodate multiple approaches for defining, playing back, visualizing and interacting with an information presentation. In one embodiment, one of the multiple approaches that can be implemented using the user interface module 280 can be the implementation by the creation/playback application 120 of a visual timeline with zero or more tracks within a timeline display area, wherein the visual timeline and tracks are a specific graphical user interface that can be used interactively by the user with the system to: a) define states of the information presentation, states of the assets, and states or the creation/playback application 120 and/or the changes of the state of the information presentation, the state of the assets, and the state of the creation/playback application over time: b) interact with the information presentation, the assets, and the creation/playback application's states and state changes over time; or c) generally interact with the information presentation, the assets, and the creation/playback application; or any combination thereof). The graphical user interface can also be used to visually represent for the user the information presentation, the assets and the creation playback application (e.g., changes of the state over time).
Tracks can flexibly accommodate the user in various capacities in visualizing, interacting with and configuring/defining an information presentation, its assets and the creation/playback application's state over time. The timeline area can have multiple tracks all certain tracks devoted to visualizing or configuring certain aspects of the state over time. For example, a multi-track embodiment in any mode may contain a track for each of the l-n assets to be displayed or activated/actuated and certain aspects of state related to that specific type of asset. Tracks of this nature can be referred to as asset tracks. In addition there can be tracks that can be specifically implemented for defining and controlling other aspects of the information presentation over time, such as the layout of the information presentation, the abilities or constraints of the user to modify the layout of the information presentation, the functional capabilities of the assets and the information presentation, or the logic and rules regarding if real-time interactive widgets should be displayed and provided; or any combination thereof. Tracks of this nature can be referred to as control tracks. Examples of control tracks include: asset layout control tracks purposed around controlling/defining the layout of the assets; application layout control tracks purposed around controlling/defining the layout of the creation/playback application; user constraint tracks purposed around defining certain actions that can or cannot be taken by the user; or any combination thereof. Additional detailed information with regards to tracks can be found in
The widgets can comprise at least one text chat widget, at least one audio/video chat widget at least one asset browser widget, least one discussion widget, at least one audio recording/playback widget, at least one video recording/playback widget, at least one stream playback widget, at least one audio/video editing widget, at least one document viewing widget, at least one document editing widget, at least one linking widget, at least one activity widget, at least one slide show editing/viewing widget, at least one diagram editing/viewing widget, at least one drawing suite widget, at least one whiteboard widget, at least one polling widget, at least one survey widget, at least one assessment widget, at least one spreadsheet widget, at least one user list widget, at least one source code viewing and editing widget, at least one tracking widget, at least one glossary widget, at least one screen sharing and/or screen recording widget, at least one wiki widget, at least one bookmark widget, at least one calculator widget, at least one presentation index widget, at least one layers widget, at least one integrations widget, or at least one third party platform interactive widget; or any combination thereof. It should be noted that any widget can be provided using third-party software. In addition, those of ordinary skill will see that any widget function(s) can be combined with any other widget function(s) to form other widgets.
The text chat widget can enable real-time text-based into discussion between multiple users of the system or the information presentation.
The audio/video chat widget can enable real-time audio and video chat between users of the system through their respective devices, whereby each user can simultaneously view real-time video and audio feeds/streams being broadcast from many users of the system. In some embodiments, it may use the stream playback widget. Various video camera and audio input sources can be supported through standard technologies and interfaces on various devices. Examples include web cam technology built into many notebook computers and video camera support built into mobile device. In addition, the audio/video chat widget can support a record mode and can used to record a uses audio and/or video input for use in a variety of ways in non real-time scenarios. For example, the audio and/or video recorded could be used as an asset within an information presentation or within any other widget, such as being used in an audio and/or video mode embodiment of the discussion widget.
The document editing widget can enable a user to create, edit, save and/or recall and view documents and/or can provide rich text editing similar to a document editor (e.g., Microsoft Word, etc.).
The slide show editing/viewing widget can enable a user to design, create, edit, save, recall or view (or any combination thereof) slide oriented documents (e.g., slide show presentations) and slide shows similar to other slide show presentation emit on tools (e.g., Microsoft PowerPoint, Apple Keynote, etc).
The linking widget can be used independently and standalone or in conjunction or as part of any other asset or widget. The linking widget allows any other assets or object within an asset or widget, or within rich text element (e.g., image, video, drawing/diagrams element such as a shape, highlight, bitmapped image, etc; discussions within the discussion widget) or any text within any asset to be linked to or contain links including, but not limited to: 1) one or more points in time in the information presentation; 2) other assets; 3) other states of other assets; 4) other layers in the layers widget; 5) other information presentations; or 6) any other URI or URL; or any combination thereof, any of which can be displayed within the linked from/original information presentation or outside of the information presentation.
The activity widget can be used in conjunction with other widgets in order to assemble or connect a sequence of other widgets or a sequence of layers or screens containing widgets together into a multistep interactive user activity, wherein such activity can be added to and become a part of an information presentation. Further, the activities can be timed or time limited and can be required or not required to be completed by the user.
The diagram editing/viewing widget can enable a user to design, create, edit, save and/or recall and view various types of diagram oriented documents similar to other diagram creation and viewing tools (e.g., Microsoft Visio, etc).
The drawing suite widget can enable a user to design, create, edit, save, recall, insert or view (or any combination thereof) various types of image files and assets of various types including raster/bitmap formats (e.g., GIF, PNG, JPEG) vector file formats (e.g., SVG, EPS, Adobe Illustrator), various image or vector objects or drawing shapes (i.e., circles, squares, highlights, text,). The drawing suite widget can support both vector drawing and image manipulation capabilities and raster/bitmap image manipulation and capabilities, and can combine capabilities of various other standard drawing and image manipulation tools (e.g., Adobe Illustrator, Adobe Photoshop, Adobe fireworks). As may be the case with any widget, the drawing widget may be placed/moved/positioned over top of any other asset or over all assets displayed within the creation/playback application. It is important to note that any widget can be placed on top of any other widget within the user interface and stage of the creation/playback application or within a layer (i.e., within the layer widget) or any combination thereof.
The asset browser widget can enable a user to browse, preview, view, or interact with (or any combination thereof) any asset that may or may not be related to a given in formation presentation. The asset browser widget may use other widgets if necessary in order to provide its capabilities related to browsing the assets. In addition, the asset browser widget can be one way in which a user may select and add assets to an information presentation or to the stage.
The discussion widget can provide various ways for a user to engage in discussions with other users of the system, according to several embodiments. The discussion widget can be used tor various functions for message oriented communication, such as posting, replying, viewing, or archiving messages (or any combination thereof). The discussion widget can be configured to support discussions in several ways, including: ongoing and/or thread oriented discussions similar in structure to other widely used online discussion/message boards (also known as forums); ongoing lists of comments similar in structure to other widely used comment systems; or in other ways (including question and answer, etc.). The discussions and posts/messages can be text or rich text based (i.e., text with various font sizes, colors, embedded drawings, embedded video and/or multimedia, embedded images, etc. examples of which could be Microsoft Word documents or HTML documents), as well as audio and/or video based. For example, discussions, messages, discussion posts and comments can be posted by users in an audio and/or video format, or audio and/or video in rich text format, wherein such audio and/or video may have been recorded using the audio/video chat widget's record mode capability Discussions and messages can be associated with a given point or several points in time within an it presentation, and as such, can be rendered visually on the timeline in various ways. The discussion widget can be configured to notify a number of devices when an interaction with the discussion widget has happened (e.g., notifications to mobile phones, SMS messages, email, notification popups in the creation playback application, when messages are posted or replied to). In addition, the discussion widget and its constituent posts/messages and the posts/messages content can provide for access (such as through links, etc.) directly into the information presentation, at the exact point in time for which the discussion or posts/messages can be associated or other points in time in the information presentation. In addition, the discussion widget and its constituent post/messages can both be linked as well as contain links in any way provided for by the linking widget, and both can also easily reference and be linked to other discussions and posts/messages.
The audio recording/playback widget can allow for recording of at least one audio document and/or the selection of at least one audio document, or controlling, viewing or hearing the playback of the audio document, or any combination thereof. The video recording/playback widget can allow for recording of at least one video document and/or enable a user to select at least one video document, or control, view or hear the playback of the video document, or any combination thereof.
The stream playback widget can allow a user to select and/or to connect to at least one real-time (e.g., live) audio, real-time video, or real-time data stream, or to view and/or hear the streams, or any combination thereof.
The audio/video editing widget can enable a user to flexibly edit audio or video documents and assets or any combination thereof in a non-linear fashion similar to other non-linear editing systems. Similar to other non-linear editing systems, a user can create, define and output/save video and audio files and/or assets that are composited or mixed from multiple video and audio files/assets in a non-destructive manner (e.g., without destructing, degrading or modifying the original video and audio assets). The user can use many standard user interface elements and approaches similar to the user interface of other non-linear video and editing systems, such as layers, visual in/out points, etc.
The document viewing widget can enable a user to load and view text based documents in various formats (e.g., Microsoft Office, PDF).
The whiteboard widget can enable a user to draw and diagram independently, above, and/or in conjunction with (e.g., on) any other asset, individually (e.g., visible to only one user) or collaboratively (e.g., with other users in real-time (e.g., live) and non real-time (e.g., non-live)). In addition to its own native drawing capabilities, the whiteboard widget can make use of other widgets, such as, but not limited to, the drawing widget and diagram editing and viewing widget.
The polling widget can enable a user to define and/or participate in question based polls, both in real-time and non-real time. The survey widget can enable a user to define and participate in surveys, both in real-time and non-real time.
The assessment widget can allow users to define or view/access/participate in assessments (such as quizzes and exams) using numerous question types (e.g., multiple choice, true/false, branching, matching, drag and drop, short answer, essay, etc.) and at least one question. The assessment widget can be configured to present to the user one or more questions or assessment activities at any paint during an information presentation. The assessment widget can be configured in various ways including presenting any or all questions/assessment activities modally (e.g., where the user must provide an answer or a correct answer before proceeding within the information presentation). The assessment widget can also allow determining, storing and/or displaying scores, both within an information presentation and across multiple information presentations. Assessments created/defined using the widget can be timed or time limited and individual questions in the assessment can be timed or time limited. The assessment widget can also be configured in various ways to ensure to ensure security of the assessment data, authenticity of the user and the integrity of the assessment. For example the assessment widget can secure a users device such that only the creation playback application (and no other applications or limited access to other applications) can be used during an assessment or track usage of any other applications on the device (e.g., both capabilities can be used to prevent cheating, etc.). Additionally, the assessment widget can use or be used in combination with various real-time assets and widgets to ensure integrity or the assessment and authenticity of the user and to prevent cheating. For example, the audio/video chat widget can be used to verify the authenticity of the user and to proctor and/or monitor users as they use the application and participate in an assessment.
The spreadsheet widget can create/define/edit and/or allow viewing of spreadsheets (e.g., Excel) and/or spreadsheet oriented activities similar to other spreadsheet applications (e.g., Microsoft Excel, etc.).
The user list widget can allow for users of the system or information presentation to see information about other users of the system or information presentation, and/or interact with other users or solicit interactions with other users of the system or of the information presentation. For example, a user could activate the user list widget and see a list of all users (e.g., editors, viewers, contributors) of an information presentation as well as additional information, such as their name, online status (or last time online), availability. A user could also interact with other users, such as “knocking” on their door or requesting various forms of collaboration, such as chat, collaboration mode, shared white board, etc.
The source code viewing and editing widget can enable a user with software development tool capabilities, ranging from enabling a user to formatted and color coded computer programming source code (e.g., source code formatting) to enabling a user to participate in a fully integrated development environment. In the integrated development environment embodiment, the source code viewing and editing widget can provide for capabilities such as, but not limited to: source formatting, code highlighting, editing of source code, code completion and hinting, step oriented debugging capabilities, linking to object code, or compiling and execution of code, or any combination thereof. In addition, the source code viewing and editing widget can be one way of implementing and providing for programming to CARA 235. This ability to program against and for CARA 235 could be used to define an information presentation and the state of the information presentation and assets over time programmatically. For example, a user could choose to write code for or “script” to define an information presentation and the state of an information presentation over time or a portion of an information presentation or any asset at any point m time in an information presentation, as an alternative to or in conjunction with using the applications various other capabilities (e.g., user interface) available for defining an information presentation.
The tracking widget can enable a user to track and/or view his progress within an information presentation and across information presentations. Further, it can track and log every single action or interaction a user takes and the time at which it happened, providing for an analysis and reporting data set. The glossary widget can enable a user to view and/or access a glossary for a specific information presentation, or across information presentations. The screen sharing and screen recording widget can enable a user to replicate and/or broadcast in real-time and/or record or playback (e.g., in real-time or non-real time) at least one portion of a user's device's screen, and/or to view another user's recording and/or broadcast on other user's screen. The screen sharing and screen recording widget also allows users of the system to take control of other user's systems (i.e., operating systems) such that a user or multiple users can control another user's computer. In addition, the recorded video of the screen capture can be used as an asset in an information presentation or within other assets.
The layers widget can provide a user and/or editor with the ability to create and edit multiple layers upon the stage within the creation/playback application. Each layer operates similarly to the stage and can be used to display one or more assets. From the user interface of the creation/playback application 120 users can choose to view the one or more layers containing the assets together or separately, depending on their capabilities, as allowed/disallowed by an editor. (Details regarding constraint controls discussed later in this disclosure).
The wiki widget can provide a user with wiki oriented collaborative knowledge building functions similar to other wikis using rich text, such as Wikipedia. The bookmark widget can enable a user to bookmark and/or recall any point in time in an information presentation or an asset at any point in time, and/or to share and or send these bookmarks with/to other users and other systems. The calculator widget can enable a user to display a graphical calculator (including various types of calculators, such as standard, accounting, scientific, binary, graphing, etc.) and or to define calculator-based exercises or activities to he used in an information presentation. Those of ordinary skill in the art will see that various calculators (e.g., scientific calculator, accounting calculator, etc.) can be used. The presentation index widget can enable a user to define and/or access an index of various points in time in art information presentation.
The third party platform widget can enable a user to integrate/use widgets built or compiled for/from a variety of platforms. The third party platform widget can include, but is not limited to, a widget built for the Adobe Flash platform ((SWF files etc). Microsoft SilverLight, or other technologies or web technologies (e.g., HTML, JavaScript, CSS, etc.), used separately or in combination.
Each state change/time definition object can generally contain a time value, which can be the time in milliseconds for the state change to be executed. The time can be either absolute time or time relative to another time or relative to the start time of the presentation. In addition, the state change/time definition object can comprise an indicator set to a value indicating a state change is to be executed immediately upon receipt. Furthermore, the state change/time definition object can comprise a relative-to indicator, which can indicate what the time value is relative to.
The state change data within each state change/time definition object can define an actual change in state to the information presentation, a change in state to the creation playback application 120, or a change in state to other state change/time definition objects. In one embodiment, each state change/time definition data can be: a discrete unit with a named reference or memory address based reference to a data values in memory within the application context and a new value to change to; a discrete unit with a named or memory address based reference to executable instructions along with input values for the executable instructions; or a discrete unit with executable instructions along with input values for the executable instructions; or any combination thereof.
Methods of Using the Creation/Playback ApplicationIn 3825, the creation/playback application 120 can open a network communication connection to the server computer 110 using a bus/network communications I/O manager 225. Remote server access can be connected via any IP/Socket Protocol. In 3830, the creation/playback application instance can notify the server computer 110 that the initialization is complete. In 3835, the creation/playback application instance can process incoming data related to the initially received information presentation data. This can be done by invoking the data loader/initial application updater module 230 with the initialization payload data, as set forth in 3850-3855.
In 3850, the information presentation data can be received. In 3851, the assets and assets metadata can be added/updated to the local assets database 245. In 3852, the real-time or other state change/time definition objects that require immediate processing and execution can be separated and identified. In 3853, these real-time or other state change/time definition objects that require immediate processing and execution can be handed to the state change proxy module 260 to be immediately executed. In 3855, the state change/time definition objects can be added and/or updated in the local state change and timing database 250 with other state-change/time definition objects which will potentially need to be executed later.
In 3840, the creation/playback application instance can begin the process of continually listening for incoming information presentation data, as set forth in 3842-3844. In 3842, the creation/playback application 120 listens for newly received data. In 3842, it is determined whether new data is received. If yes, new data is received, in 3843, the data is sent to be processed (as described and illustrated in 3835). If no, new data is not received, in 3844, the process returns to 3842, where the creation/playback application 120 continually listens for new incoming data.
In
In
In
In
The user can also select whatever layout the user prefers using a variety of means. By means of a user modifying the information presentation during playback, such as selecting/configuring/changing the layout or adding/removing assets from the screen, or inviting other users to collaborate in collaborate mode, the creation/playback application 120 can change from playing the information presentation in its predefined formal (e.g., automatic play mode) into manual play mode, wherein the creation/playback application in manual play mode can no longer implement some or all the predefined information presentation's state changes, such as the display/activation of assets and layout changes. The user can immediately switch back to automatic mode with a single user gesture, such as clicking on a button. In the example, after the user removes the calculator widget, the creation/playback application 120 is now in manual mode. As the system in run-time mode continues to play the information presentation, and the time and time line of the information presentation reaches the respective point in time, the state of the information presentation as per defined by the editor user during the use of the system in editor mode is such that the information presentation uses a three asset layout, displaying the video widget, the slide show editing/viewing widget with loaded slide presentation on slide number 9, and the calculator widget. However, some or all of these state changes, may not be executed, as a result of the various constraints that may have been implemented as part of the information presentation, and because the creation/playback application 120 is in manual mode. The state change where an audio asset is played is executed, while the video asset (which video has ended) remains on the screen in the layout defined by the user. In addition, the user can continue to modify the information presentation as described above. For example, an asset can be added by having the user click on an icon representing the asset browser, and then drag and drop different assets to a certain pan of the screen. Those of ordinary skill in the art will sec that other methods arc also possible for adding an asset.
In a manner similar to
In a manner similar to
For example, in Scenario 1, a user Hiroko can view Professor X's predefined information presentation of a slide show in 1. In 2, Hiroko can view Professor X's predefined information presentation of a slide show and video. In 3, although Professor X is not online, Hiroko can activate the chat widget and video-chat widget and collaborate and interact with other available friends and information presentation viewers in real-time. When Hiroko modifies/edits the run-time information presentation and adds the chat widget, the information presentation mode can change to manual mode.
In Scenario 2 of
In Scenario 3 of
Scenes 2 and 3 take place in London where it is 5:00 PM. Using the creation/playback application 120 in run-time mode, users arc able to witness and interact with the information presentation and with other available users, including the editor user, in real-time, using such capabilities as the chat widget, video chat, etc. In Scene 2, the user is viewing the information presentation in automatic mode. In Scene 2, the presenter has specified a 3 asset layout that includes a live video feed, a slide show presentation, and a calculator widget. In Scene 3, however, the user has opted to run the live information presentation in manual mode, configuring his workspace (as allowed by the editor user) to his liking. The user in Scene 3 has opted to listen to the audio stream of the live information presentation, while viewing the slides, and activating the chat widget to converse with other users.
Scenes 4 and 5 take place in Tokyo, Japan. Since it is 1:00 AM in Japan at the time of the live information presentation, users will opt not to not sec the information presentation until they wake up the next morning. In Scene 4, a user is viewing a published on-demand version of the information presentation at a later point in time (non-real time). The user can view it in automatic mode, seeing the information presentation exactly as the instructor intended/defined/recorded, or the user may (where permitted by the editor) modify the layout of the information presentation and view it in manual mode. In Scene 5, a user is viewing a non-real time version of the information presentation, but is chatting with the professor who delivered the presentation at a time in which both parties happen to be online.
In Scenario 2, the editor user loads, then uses the predefined information presentation within the creation/playback application 120 in editor mode, in front of a live audience setting during a presentation. In addition, he can have set the creation playback application 120 into record submode. In 1, Professor X interrupts his information presentation using the creation playback application 120 and the predefined information presentation to show the audience how to calculate something. In 2, Professor X activates the calculator widget and begins showing the audience how to calculate the answer to a problem. He asks the audience to try to calculate it themselves and discuss their results. In 3, once complete, Professor X decides to take questions from students and other users of the system 100 viewing the information presentation and activates the chat widget that is available and running in the background to be displayed for both live audience members and all other users of the system 100 viewing the information presentation.
In Scenario 3, a user accesses the system and the information presentation from a remote location, in real-time as it is being defined and delivered by the editor user. This user uses the system in automatic mode, such that the information presentation is played back exactly as it is being defined by the editor user. Thus, in 1, John is in London and watches Professor X's information presentation live in real time. He sees a video of Professor X on the right and the slides on the left. In 2, since John is viewing the information presentation in automatic mode, when Professor X activates the calculator widget, John's screen automatically reorients itself to display the calculator widget. In 3, once Professor X activates the chat widget, John's screen reorients itself to display the chat widget so that he can have discussions with users.
In Scenario 4, another user also accesses the system and the information presentation from a remote location, in real-time as if is being define and delivered by the editor user. However, this user opts to inactivate and hide some of the widgets that the presenter/editor user is displaying, thereby putting the application into manual mode. If a slate change was to be activated but cannot due to the inactivation of some of the widgets, the user is notified of the specific state change that was to be implemented, but was not implemented due to being in manual mode, through a notification indicator popping up on the screen. In this scenario, the editor user added a calculator widget to display within the information presentation, and the user was notified of this state change via a pop-up window. Thus, in 1, Julie, like John views the information presentation from a remote location in real time. She finds the video footage too distracting and so opts to only see the slides by closing the video widget. In 2, because Julie is not in manual mode, when Professor X adds a calculator to the screen, she only receives a popup notification indicating that a state change has occurred. If she desires, she can click on the pop-up to see the predefined stage as it appears in automatic mode. In 3, when Professor X activates the chat widget, Julie remembers a question. She clicks to activate the chat widget and joins the discussion Professor X has started.
In Scenario 5, the user watches the information presentation, initially in automatic mode, as it was recorded/defined by the editor user hours earlier. The user then changes and customizes the layout, thereby changing to manual mode, and then uses the real time interactive text chat widget. Thus, in 1, Hiroko is in Tokyo during the class, so she views the information presentation in non-real-time the next day. In 2, the screen can be configured to Hiroko's liking. For example, when Professor X activated the calculator widget. Hiroko can choose to close the video widget. In 3, because Professor X activated the chat widget and enabled it to run continuously, Hiroko can chat with other present viewers of the information presentation or other users of the system. Moreover, because Professor X decided to make himself “known” when he logs on. Hiroko can ask him questions in real-time.
Continuing on in
The discussion board widget depicted in
For example, referring to
In 7, the user interface presents Professor X with various options for adding the diagram to the stage and information presentation using a diagram viewing editing/widget, including automatic layout options where the application automatically detects the best layout option. The application can also automatically add the diagram asset or widget to the stage without prompting the user, Professor X. In 8, Professor X activates the drawing widget. In 9, using various keyboard shortcuts, and/or on screen prompts, etc., Professor X is able draw on/within and/or interact with both individual widgets or assets, as well as the stage as a whole. For example, Professor X makes some modifications to the diagram in real time, the state changes for which are being recorded. Likewise, Professor X can draw shapes overlaying and overlapping the various assets on the stage. It should be noted that 9 is only one example of the combining of widget capabilities together with other widgets, in this case the drawing suite widget being used and combined with the diagram viewing/editing widget, as well as the document editing widget. In addition, 9 is also one example of the ability to put assets on top of other assets, in this case, the drawing suite widget being used to draw over top of the entire stage within the creation/playback application 20.
Referring to
In 11A, after creating the new layer, Professor X adds a new slide show editing/viewing widget to the layer on the stage. Professor X edits the slide show, adding some text in bullet point form, then adds a calculator to the screen and performs an example calculation, all of which may still be recorded.
In 11B, Professor X then changes back to the first layer to continue with the main portion of the presentation.
Referring to
In 13, all of the changes of state of the information presentation that have been recorded are rendered and represented visually on the multi-track timeline. Professor X would now like to make some additions and changes to the information presentation. Specifically, Professor X would like to make some areas of the diagram he used into links to: 1) one or more points in time in the information presentation; 2) other assets/widgets; 3) other states of other assets/widgets; 4) other layers in the layers widget; 5) other information presentations; or 6) any other URI or URL; or any combination thereof. Any of these options can be displayed within the linked from/original information presentation or outside of the information presentation. Those of ordinary skill in the art will see that there are other link types that may be created and applied to objects in the system.
Referring back to 13 on
In 14, after locating the point in the it presentation where the diagram was added, Professor X now begins interacting with the diagram viewing/editing widget and the application in order to create the links he would like.
In 15, it is demonstrated how, in this embodiment, by selecting and right clicking on an object (e.g., shape, image, text, etc.), Professor X can access the linking widget. In this example, Professor X is making the large blue arrow in the diagram link to another point in the information presentation, such that when a user clicks the arrow, the playhead will jump to another point in time in the presentation and the presentation will play from that point in time. The user interface in this embodiment allows a user to enter a time in hours, minutes, and seconds format, or to use the timeline and playhead to select the point in time (i.e., by clicking and dragging the playhead to the desired location/time in the information presentation to link to).
Referring to
In 17, Professor X finishes creating the presentation and uses the save capability of the system 100 and creation/playback application to save the presentation.
In 2, Presenter X is preparing to give a live presentation to both a live and remote audience. He will also be recording the presentation for later editing or playback. Before or during the presentation. Presenter X can configure the application in many ways. Examples of such ways include, but are not limited to: what he will see while presenting, what his main control device will be, what other users will see, how other presenters may interact by default, what the constraints are on a user's ability to change the stage and activate other widgets and assets, and what other connected devices and systems to integrate with.
Referring to
In 4, Professor X next chooses to display one or more poll questions to the users and audience, using the polling widget. In this embodiment he is able to select a poll/survey question from a bank of existing questions or he can create a new question. Additionally, a depiction of what a user my see on their embodiment is included, wherein such user's embodiment is displaying a poll response window (part of the polling widget). As with all embodiments, users can be either in the live audience or the remote audience, and can be using a desktop PC, a mobile/smartphone, a tablet PC, a television, or any other computing or audiovisual device.
Referring to
In 6, Presenter X decides to do a hands-on demonstration for the users using the document camera. Presenter X uses the integrations widget to switch the video feed to the connected document camera. Presenter X clicks/selects the tools icon to access the integrations widget and is presented with a menu of relevant options based on the state of the information presentation and other context. Presenter X is able to select various routing options for this document camera video, including adding a new video to the stage is this scenario he chooses to route the document camera to the screen in place of the current video on the stage.
Referring to
In 8, after Presenter X completes the hands on demonstrations using the document camera, he decides he will do a demonstration using screen sharing, such that he may display his computer/tablet/device desktop and its running applications. Using his chosen device, Presenter X selects to activate the screen sharing widget, and opts to use full screen sharing over the whole stage, rather than replacing a particular widget that may be currently visible to the users on the stage of the creation/playback application 120.
In 9, an example is depicted of what users, as well as Presenter X, may see while Presenter X is using the screen sharing widget. Presenter X sees a full set of controls 7601 over his desktop (which he can also hide). Users will see limited set of controls based on constraints, and are able to see Presenter X's desktop.
It is important to note that the sequences of screenshots illustrated in this disclosure can represent: 1) an information presentation being delivered and controlled live and in real-time by an editor user and viewed live by one or more users; or 2) an information presentation which was predefined and is being played back by users at a later time; or 3) any combination thereof.
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope of the present invention. Thus, the present invention should not be limited by any of the above-described exemplary embodiments.
In addition, it should be understood that the figures described above, which highlight the functionality and advantages of the present invention, are presented for example purposes only. The architecture of the present invention is sufficiently flexible and configurable, such that it may he utilized in ways other than that shown in the figures.
In addition, it should be noted that the terms “a”, “an”, “the”, “said”, etc. in the specification, figures and claims signify “at least one”, “the at least one”, “said at least one”, etc.
Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope of the present invention in any way.
Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase “means for” or “step for” arc not to be interpreted less than 35 U.S.C. 112, paragraph 6.
Claims
1. A system for creating at least one presentation, comprising:
- at least one computer;
- at least one application operable on the at least one computer, the at least one application configured for:
- receiving a plurality of assets; and
- allowing at least one user to define the at least one presentation over the time that the at least one presentation is to be displayed, using at least two assets to be simultaneously presented for at least one selected point in time.
2. The system of claim 1, wherein the at least one application is further configured for:
- displaying the at least one presentation.
3. The system of claim 1, wherein the assets are interactive and/or non-interactive.
4. The system of claim 3, wherein the interactive assets comprise at least one widget.
5. The system of claim 3, wherein the non-interactive assets are real-time and/or non real-time.
6. The system of claim 4, wherein the at least one widget is configured for:
- gathering user input;
- providing dialogue with at least one user;
- providing interactivity between at least one user and the at least one presentation;
- providing interactivity between at least one user and at least one asset; or
- providing interactivity between multiple users; or any combination thereof.
7. The system of claim 4, wherein the at least one widget comprises: at least one text chat widget, at least one audio/video chat widget, at least one asset browser widget, at least one discussion widget, at least one audio recording/playback widget, at least one video recording/playback widget, at least one stream playback widget, at least one audio/video editing widget, at least one document viewing widget, at least one document editing widget, at least one linking widget, at least one activity widget, at least one slide show editing/viewing widget, at least one diagram editing/viewing widget, at least one drawing suite widget, at least one whiteboard widget, at least one polling widget, at least one survey widget, at least one assessment widget, at least one spreadsheet widget, at least one user list widget, at least one source code viewing and editing widget, at least one tracking widget, at least one glossary widget, at least one screen sharing and/or screen recording widget, at least one wiki widget, at least one bookmark widget, at least one calculator widget, at least one presentation index widget, at least one layers widget, at least one integrations widget, or at least one third party platform interactive widget, or any combination thereof.
8. The system of claim 2, wherein the at least one application is further configured for:
- displaying the assets in at least one layout configuration.
9. The system of claim 2, wherein the displaying can be done in automatic or manual mode.
10. The system of claim 9, wherein the at least one user can determine which mode to use.
11. The system of claim 1, wherein the at least one computer is:
- non-networked;
- in a television;
- connected with at least one intranet; connected with at least one Internet; or in at least one mobile device; or
- any combination thereof.
12. The system of claim 11, wherein the at least one mobile device comprises: at least one laptop; at least one phone; at least one personal assistant device; at least one tablet computer; or any combination thereof.
13. The system of claim 2, wherein at least one widget can be displayed on top of at least one other widget.
14. The system of claim 1, wherein the at least one application is further configured for allowing at least one user to define at least one proposed layout of the at least one presentation.
15. The system of claim 1, wherein the at least one application is further configured for:
- interacting directly and/or indirectly with at least one user; or
- interacting between at least one user and at least one other user; or
- any combination thereof.
16. The system of claim 1, wherein the at least one application is further configured for:
- allowing at least one editor to define the at least one presentation by utilizing at least one track for defining the state of the at least one presentation and/or at least one change of the at least one state of the at least one presentation.
17. The system of claim 16, wherein the at least one track comprises at least one asset track and/or at least one control track.
18. The system of claim 1, wherein the at least one application is further configured for predicting the at least one editor's intentions relating to defining the at least one presentation by determining where the at least one editor clicks on at least one screen.
19. The system of claim 18, wherein the at least one application is further configured for presenting the at least one editor with at least one option for defining the at least one presentation.
20. The system of claim 1, wherein the at least one application is further configured for defining constraints related to at least one user's ability to modify the at least one presentation.
Type: Application
Filed: Jun 1, 2020
Publication Date: Sep 17, 2020
Inventor: Robert Taylor (Atlanta, GA)
Application Number: 16/889,000
