TWI567570B - Techniques for generating custom objects representing content files - Google Patents

Description

Technique for generating custom objects representing content files [related application]

The present application is a part of the continuation application of the prior U.S. Patent Application, filed on December 23, 2010, entitled "Techniques For Electronic Aggregation Of Information", as claimed in Title 35, US Code, Section 120. U.S. Patent Application Serial No. 12/ 073, 311, filed on March 28, 2011, which is hereby incorporated by reference in its entirety, the entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire The entire disclosure of the subject matter of the U.S. Patent Application is hereby incorporated by reference.

The present invention relates to techniques for producing custom objects that represent content archives.

A montage can contain aggregates of individual elements to form a single composite element. For example, a montage may comprise a composite image or video sequence consisting of a number of separate images containing a fast sequence of different images. Electronic montage systems have been designed to create digital montages using digital content, such as composite web pages containing web pages of different compositions that are served by different web applications. Sometimes, the component pages are organized according to a central theme, such as a web page related to a given search term used by the search engine, or a web that is consistently accessed by the user and stored in the history of the browser. page. Usually, due to the space limitations of the composite web page, the component web page is represented by the lower fidelity of the actual web page. Therefore, the user can select a component web page to retrieve a higher fidelity version of the selected web page for a more in-depth view.

However, as the amount of digital information increases, it becomes more and more difficult to build digital montages in a way that provides meaningful information to users. More specifically, it has become increasingly difficult to represent content from multiple content sources in digital montages in a manner that allows users to make informed judgments about whether or not to be interested in a particular content source. In view of these and other considerations, improvements in the present invention are needed.

The present invention is provided to introduce a selection of concepts further described in the following embodiments in a simplified form. The present invention is not intended to identify key features or essential features of the claimed subject matter, and is not intended to assist in determining the scope of the claimed subject matter.

Various embodiments are generally directed to electronic montage systems. Some embodiments are particularly directed to electronic montage systems configured to generate digital montages from heterogeneous data sources. The electronic montage system allows the user to generate a customized digital montage with a customized representation of the data source, allowing other users to quickly identify and select the source of interest for more detailed viewing. The electronic montage system can publish customized digital montages to other users via a release model, a communication model, or a combination of a release model and a messaging model.

In one embodiment, for example, a device can include logic devices configured to execute a montage application. A logic device can include, for example, a processing system having a processor and memory. The montage application can include a production component operative to provide a presentation surface having a plurality of presentation tiles, receiving control indicators to associate the content archive with the presentation display, and a content archive based content archive type A display block object for generating a content file and storing the rendered surface and the displayed square object as a montage.

The montage application may further include a production component that operates to produce a display block object for the digital montage. The production component can receive the control indicator to associate the content file with the presentation display block of the digital montage presentation surface, identify the content file type of the content file, and generate the display block object with the information from the content file based on the content file type. The production component can produce a display tile object as a display tile object surface having selected information from a content archive contained within one or more display tile object containers.

The montage application can still further include a rendering component operative to generate a first user interface view to render each display tile object of each associated presentation display block on the rendering surface, receive a control indicator to select the display block The object and the second user interface view are generated to present a content file corresponding to the displayed square object.

These and other features and advantages will be apparent from reading the following detailed description and the appended drawings. The above general description and the following detailed description are to be considered as illustrative only and not limiting kind.

Various embodiments are generally directed to an electronic montage system configured to generate digital montage from a heterogeneous data source. For example, an electronic montage system may allow a user to generate highly customized digital montages using content files generated by different software programs, such as applications.

The digital montage can include one or more display tile objects that contain a customized representation for the underlying content archive. The display block object may include a representation of the content file, an agent, or a "teaser". The display block object is a set of concise information from the associated content file that allows the content consumer to quickly and easily determine whether to be interested in the associated content file and enjoy a more detailed examination of the associated content file. The way it appears. The display block object can be constructed using information selectively extracted from the content file and can be formatted according to the type definition specifically created for the content file. Type definitions include detailed information about the content file (such as file extensions, data structure descriptions, formatting controls, embedded objects, embedded code, features, scripts) and other file-specific information. The type definition also includes a group rule relating to the type of information to be extracted from the content file, the format of the extracted information, the number of display object versions to be built, and the like. In this way, a wider range of content files can be used to create digital montages that provide meaningful information to the viewer when constructing highly representative display blocks. This method allows viewer capacity Easily read the display block objects in the montage, identify the content files of interest in many display block objects, and select the display block objects to quickly retrieve the content files for a more detailed view. Thus, embodiments can improve the affordability, scalability, modularity, extensibility, or interoperability of an operator, device, or network.

FIG. 1 illustrates a block diagram of a montage system 100 having a montage application 140. In one embodiment, for example, the montage system 100 and the montage application 140 may include various components such as, for example, components 110, 130. As used herein, the terms "system" and "application" and "component" are intended to refer to a computer-related entity, including a combination of hardware, hardware, and software, software, or software in execution. For example, a component can be implemented as a processor running on a processor, a processor, a hard disk drive, a plurality of storage drives (of optical and/or magnetic storage media), an object, an executable, an execution line sequence, a program And / or computer. By way of illustration, both an application running on a server and a server can be a component. One or more components can be located in a process and/or execution sequence, and the components can be located in a single computer and/or distributed between two or more computers, as desired for a given implementation. The embodiment is not limited to this case.

In the illustrated embodiment shown in FIG. 1, the montage system 100 and the montage application 140 can be implemented by electronics. Examples of electronic devices may include, but are not limited to, mobile devices, personal digital assistants, mobile computing devices, smart phones, cellular phones, cell phones, one-way pagers, two-way pagers, messaging devices, computers, personal computers (PCs). ), desktop computer, laptop computer, notebook computer, handheld computer, flat Board, server, server array or server group, web server, web server, internet server, workstation, mini computer, host computer, super computer, network appliance, website appliance, distributed computing Systems, multiprocessor systems, processor-based systems, gaming devices, consumer electronics, programmable consumer electronics, televisions, digital TVs, set-top boxes, wireless access points, base stations, subscriber stations, mobile User center, radio network controller, router, hub, gateway, bridge, switch, machine, or a combination of the above. Although the montage application 140 as shown in FIG. 1 has a limited number of components in a certain topology, it will be appreciated that the montage application 140 can include more or less elements in alternate topologies as desired for a given implementation.

The components 110, 130 can be communicatively coupled via various types of communication media. The components 110, 130 can coordinate operations between each other. Coordination can involve one-way exchange or two-way exchange of information. For example, components 110, 130 can communicate information via signals communicated by a communication medium. Information can be implemented as signals that are distributed to various signal lines. In these assignments, each message is a signal. However, other embodiments may alternatively use a material message. These data messages can be sent via various connections. Exemplary connections include a parallel interface, a serial interface, and a bus interface.

In the illustrated embodiment shown in FIG. 1, the montage system can include one or more content files 104- c and a montage application 140. Content files 104- c may contain digital content generated by software programs, such as applications, web applications, web services, and the like. The montage application 140 can generate the montage 120 using one or more selected content archives 104- c . In one embodiment, one or more content files 104- c can be manually selected by a user. In one embodiment, one or more content files 104- c may be automatically selected by the software program, such as by using search results associated with a given search term used by the search engine, or content that is consistently accessed by the user. File 104- c is stored in the browser history.

The montage application 140 can include the authoring component 110 and the rendering component 130, as well as other components. The fabrication component 110 can be used by a user to make or create a montage 120. Users who make or create montages 120 are sometimes referred to herein as "content producers." The presentation component 130 can be used by a user to view or navigate the montage 120. Users viewing or viewing Montage 120 may sometimes be referred to herein as "content consumers." The montage application 140 further includes other components as described in more detail with reference to Figures 2-11.

The authoring component 110 can generally manage the production operations for the montage application 140, including creating a user interface view and tools to allow the content producer to create, build, or otherwise make the montage 120. The montage 120 can include a single complex or aggregate of digital information elements from the selected content archive 104- c to form a single composite digital information element. The montage 120 can include, for example, a composite file having different component digital information elements generated by a heterogeneous application, such as an application application file. Sometimes, component digital information elements are organized according to a central theme, such as digital information elements about business projects, personal holidays, or holidays. Typically, the component digital information element is represented by the lower fidelity of the actual content file 104- c due to the spatial limitations of the composite file. Thus, the content consumer can select a component digital information element to retrieve a higher fidelity version of the associated content file 104- c for a more in-depth view.

In one embodiment, for example, fabrication component 110 can be configured to provide presentation surface 122 for montage 120. The presentation surface 122 can have a plurality of presentation display blocks 124- a defined or disposed on the presentation surface 122 in a certain topology. The authoring component 110 can receive the control indicator 102- b to associate certain content profiles 104- c with certain presentation display blocks 124- a . Authoring component 110 can generate a content file 126- e 104- c shows a block of file types and various content object type definitions and content files based on the associated 104- c. The authoring component 110 can store the presentation surface 122 and the display tile object 126- e as part of the montage 120, which can then be published or distributed to various content consumers.

It is worth noting that " a " and " b " and " c " and similar names are intended to mean any positive integer variable when used herein. Thus, for example, if a setpoint a = 5 is implemented, then a set of full presentation display blocks 124- a can include presentation display blocks 124-1, 124-2, 124-3, 124-4, and 125-5. The embodiment is not limited to this case.

The authoring component 110 can begin the authoring operation to create the montage 120 by providing a rendering surface 122 having a plurality of rendered display blocks 124- a . The presentation surface 122 can include any two-dimensional (2D) or three-dimensional (3D) topological space of any defined size with a coordinated system and boundaries. Examples of presentation surface 122 may include files for a word processing program, a slide for rendering a program, a worksheet for a spreadsheet program, a note for a note program, and a personal information management program. (PIM) contact cards and other spaces normally used by applications.

Presentation display block 124- a may include a defined area of presentation surface 122 that is designated for presenting a set of discrete information, such as display tile object 126- e . The defined area can be of any size, dimension or shape as desired for a given implementation. A given presentation surface 122 can have any number of presentation display blocks 124- a , and each presentation display block 124- a can have a set of definitions (eg, size, shape, dimension, geometry) to ensure that all rendered display blocks 124- a is suitable for presenting a given size of surface 122. The definition of the presentation display block 124- a may be based on the presentation surface 122, the content archive 104- c set, the association between the content archive 104- c and the presentation display block 124- a , and the display tile object associated with the content archive 104- c. 126- e , display characteristics, device characteristics, user preferences, and other factors change dynamically. The embodiment is not limited to this case.

In one embodiment, the content producer can customize the presentation surface 122 and present the display blocks 124- a . The user interface for the montage application 140 can provide various controls specifically defined to modify the presentation surface 122 and the set of presentation display blocks 124- a on the presentation surface 122. Examples of such controls may include, but are not limited to, schema controls, dimension controls, size controls, width controls, height controls, pixel controls, renewed controls, and the like. Alternatively, the content producer can select from any number of montage templates to provide different rendering surfaces and render display blocks 124- a .

The authoring component 110 can receive the control indicator 102- b to associate certain content profiles 104- c with certain presentation display blocks 124- a . The authoring component 110 can generate a user interface view and tools to allow the user to select the content archive 104- a , and the authoring component 110 can associate the content archive 104-a with the presentation display block 124- a . For example, a user may use an input device, such as an indicator device, to select a content file 104-1 and drag the content file 104-1 on the presentation display block 124-1. The user selection may generate a control indicator 102- b as a message or signal indicating selection of the authoring component 110. Alternatively, control indicator 120- b may be programmatically generated in accordance with a content selection algorithm. For example, content selection algorithm can have a defined set of rules to generate free search engine of search results is automatically selected content file 104- c, or by analyzing user browsing patterns to select content file 104- c. The embodiment is not limited to this case.

The content file 104- c can contain any digital information element or digital content generated by the software program, such as an application, a web application, a web service, a client application, a server application, a system program, and the like. Different software programs can produce different types of digital content. Thus, digital content generated by different software programs can contain heterogeneous digital content. Examples of content files 104- c may include, but are not limited to, application files, such as word processing files, spreadsheet files, presentation files, personal information management program (PIM) files, database files, publisher files, schemas Files, memo files, message files, project files, and more. Other examples of content files 104- c may include multimedia files such as audio files, video files, video files, audio/video (AV) files, animation files, game files, tag files, web files, social networking services (SNS) Files and so on. It will be appreciated that such files are only a few examples of content files 104- c , and embodiments are not limited to such examples.

In one embodiment, the content archives 104- c may include content files for a productivity suite of cross-correlation client applications, server applications, and web services designed for a particular operating system, the productivity suite such as for MICROSOFT WINDOWS, manufactured by Microsoft Corporation (Redmond, Washington) ^® is the MICROSOFT ^® OFFICE productivity suite. Examples of client applications may include, but are not limited to, MICROSOFT WORD, MICROSOFT EXCEL ^® , MICROSOFT POWERPOINT ^® , MICROSOFT OUTLOOK ^® , MICROSOFT ACCESS ^® , MICROSOFT INFOPATH ^® , MICROSOFT ONENOTE ^® , MICROSOFT PROJECT, MICROSOFT PUBLISHER, MICROSOFT SHAREPOINT ^® WORKSPACE , MICROSOFT VISIO ^® , MICROSOFT OFFICE INTERCONNECT, MICROSOFT OFFICE PICTURE MANAGER, MICROSOFT SHAREPOINT DESIGNER and MICROSOFT LYNC. Examples of server applications may include (but are not limited to) MICROSOFT SHAREPOINT Server, MICROSOFT LYNC server, MICROSOFT OFFICE FORMS Server, MICROSOFT OFFICE GROOVE ^® Server, MICROSOFT OFFICE PROJECT Server, MICROSOFT OFFICE PROJECT server and port FOLIO MICROSOFT OFFICE PERFORMANCEPOINT ^® server. Examples of web services may include, but are not limited to, MICROSOFT WINDOWS LIVE ^® , MICROSOFT OFFICE WEB APPLICATIONS, MICROSOFT OFFICE LIVE, MICROSOFT LIVE MEETING, MICROSOFT OFFICE PRODUCT WEB SITE, MICROSOFT UPDATE SERVER, and MICROSOFT OFFICE 365. Embodiments are not limited to these examples.

In one embodiment, the content archives 104- c may include content archives that are individually created by the same content producer of the montage application 140 to create the montage 120. For example, assume that the content producer is a project management program for a commercial project, and during the commercial project process, the content producer has created various application files associated with the business project, such as a word processing file, a spreadsheet file, and a presentation file. The content producer can use the authoring component 110 of the montage application 140 to create an execution report having a display tile object 126- e for each file that is individually created by the content producer.

Assembly 110 may be made based on the content file 104- c of various types of content files is generated for the selected content file 104- c shows a block object 126- e. Once the content file 104- c has been associated with the presentation display block 124- a , the authoring component 110 can generate the display tile object 126- e for the selected content archive 104- c . In one embodiment, a single content archive 104- c can be associated with a single presentation display block 124- a , thereby forming a one-to-one correspondence. In one embodiment, a plurality of content archives 104- c can be associated with a single presentation display block 124- a , thereby forming a one-to-many correspondence.

Display block object 126- e may include a representation, proxy, or "pre-announcement" for content file 104- c . Display block object 126- e is a set of concise information from an associated content file 104- c that allows the content consumer to quickly and easily determine whether or not to be interested in the associated content file 104- c , and Enjoy a more detailed examination of the associated content file 104- c .

Display block object 126- e can be generated using content portion 106- d retrieved from content file 104- c . The content portion 106- d can include a free content archive 104- c that stores a subset of the information that a set of complete information is exported or extracted. One advantage of the Montage 120 is that information from different content archives 104- c can be presented on a single presentation surface 122. However, each content archive 104- c can contain an amount of information that is greater than the amount of information that can be presented within a defined area of the single presentation display block 124- a . For example, if the content file 104-1 contains a block processing file, the authoring component 110 may not be able to adapt all of the information (eg, text, graphics, images, graphics, embedded objects) contained within the block processing file to The available area or space of display block 124-1 is presented, even when miniaturized into thumbnails. Thus, production component 110 can retrieve a subset of information from a set of information contained within content source 104-1, format the subset of information to fit a set of boundaries of display block 124-1, and will be formatted The subset of information is stored as a display block object 126-1. For example, display block object 126-1 can comprise a combination of the following: a title for a block processing file, a content producer (eg, an author) of the block processing file, and an image from the block processing file.

Display block object 126- e may also include or be associated with a reference (eg, address, metric, or link) to corresponding content file 104- c . When the user selects to display the tile object 126- e for a more detailed examination, the reference content file 104- c is retrieved from the reference to present the full fidelity presentation of the content file 104- c . In one embodiment, the reference may be for a content file 104- c stored in the local data storage area. In this case, point-to-point techniques can be used to retrieve the content file 104- c using the reference. In one embodiment, the reference may be for a content file 104- c stored in a remote data storage area. In this case, the network capture and access technology can be used to retrieve the content file 104-c using the reference.

In one embodiment, a single content archive 104- c can be associated with a single presentation display block 124- a . In this case, a single display block object 126- e is presented in each of the presentation display blocks 124- a . In one embodiment, a plurality of content archives 104- c can be associated with a single presentation display block 124- a . In this case, a plurality of display tile objects 126- e may be presented in a single presentation display block 124- a . Upon presentation, the content consumer can use the selector tool provided by the rendering component 130 to navigate between the plurality of display tile objects 126- e presented in the different presentation display blocks 124- a , and also present in A single presentation displays a navigation between the plurality of display block objects 126- e in the block 124- a such that the content consumer can select the display tile object 126- e of interest. For example, assume that the content producer associates images from respective content archives 104-1 through 104-100 with presentation display blocks 124-1. A thumbnail of the 100 images can be generated to display the tile objects 126-1 through 126-100 and is sized to fit a given dimension of the display block 124-1. A selector tool can be used to navigate between display tile objects 126-1 through 126-100 to select and magnify a given image.

Once the user has completed the authoring operation to associate the different content files 104- c with the different presentation display blocks 124- a of the presentation surface 122, the authoring component 110 can store the presentation surface 122 and the display tile objects 126- e as montages 120 section.

Presentation component 130 can generally manage rendering operations for montage application 140, including rendering user interface views and tools to present montage 120 on an electronic display of an electronic device. In one embodiment, for example, the presentation component 130 can generate a first user interface view to present each of the display tile objects 126- e within each associated presentation display block 124- a on the presentation surface 122 of the montage 120. . The presentation component 130 can receive the control indicator 132- f to select the display tile object 126- e and generate a second user interface view to present the content archive 104- c corresponding to the selected display tile object 126- e .

2 illustrates a more detailed block diagram of the authoring component 110 of the montage application 140. Some part of the production assembly 110 may be defined by the content type based on the type of the file 104- c from the content file 104- c ingestion of wisdom to generate 126- e for the associated content file 104- c of a block object . For example, part of the content files may include text from 104- c, the metadata for the content file 104- c, from the content file 104- c of the article or some of the Combinations of the above.

In one embodiment, the content files 104- c may be stored in the local data storage area 210 implemented within the same electronic device that implements the montage application 140. For example, the computing device can implement the montage application 140 using the content files 104-1, 104-2 stored on the mass storage device of the computing device. In one embodiment, the content archives 104- c may be stored in a remote data storage area 212 implemented by an electronic device different from the electronic device implementing the montage application 140. For example, the computing device can implement the montage application 140 using the content archive 104-3 stored on the mass storage device of the server device.

In the illustrated embodiment shown in FIG. 2, fabrication component 110 can include or implement multiple types of modules 202- g . Each type of module 202- g may correspond to a content file type of a respective content file 104- c . Examples of content file types for content files 104- c may include, but are not limited to, application file types, such as word processing file type, spreadsheet file type, presentation file type, PIM file type, database file type, Publisher file type, schema file type, note file type, message file type, and so on. Other examples of content files 104- c may include multimedia file types such as audio file type, video file type, video file type, AV file type, movie file type, game file type, tag file type, web page type, and the like. It can be appreciated that these types are only a few examples of content file types, and embodiments are not limited to such examples.

The type module 202- g can retrieve information from the content archive 104- c based on the type definition 204- h for the content archive type, and generate the display tile object 126- e based on the retrieved information and type definition 204- h . The type definition 204- h may include a set of definitions, rules, characteristics, methods, events, coordinates, or instructions to extract the selected portion from the content archive 104- c , and the type definition 204- h may format the extracted portion for rendering Displayed within the defined area of block 124- a . By implementing a particular type definition 204- h for a particular content archive 104- c , the authoring component 110 can generate a high degree of customization that is specifically designed for a particular situation (eg, business, personal) and a group of associated content consumers. Display the block object 126- e . The type definition 204- h may be a preset type definition provided by the montage application 140 or a user-defined type definition established using the montage application 140.

As an example, assume that content archive 104-1 is a block processing file 104-1, type module 202-1 is used for the word processing file type, and type definition 204-1 is a group definition for the word processing file type. . The type definition 204-1 may include various types of information used to establish the display of the tile object 126-1. For example, type definition 204-1 may include supported file formats associated with different versions of the word processing application, such as extensible markup language formats (eg, .docx, .docm, .dotx, .dotm), Carry format (for example, .doc, .dot) and open file format (for example, .odt). The type definition 204-1 may include a secure authentication (eg, a password, a credential, a shared key, or a private key) to access the encrypted file. Type definition 204-1 may include tools to access embedded or loaded code to obtain files (eg, macros, extensions). The type definition 204-1 may include supported fields in the file (eg, the Ask field, the Author field, the Database field, the Fillin field, the Includepicture field, the Includetext field, the Mailmerge field). The type definition 204-1 may include rules for handling links to files (eg, linked objects, master files, template references, linked cascading style worksheet references). The type definition 204-1 may include rules for disposing of a data set (eg, mail merge material). The type definition 204-1 may include rules for handling object linking and embedding (OLE) objects. Other information of type definition 204-1 is possible, and embodiments are not limited to this case.

Additionally, the type definition 204-1 may contain a set of rules regarding the type of information retrieved from the content archive 104-1. For example, the type definition 204-1 can include information for three categories, including the content and attribute categories (eg, paragraphs or attributes) of the content archive 104-1, and the content object category of the content archive 104-1, and associated rules. (eg, images, embedded objects) and content page categories within content file 104-1 or some combination of the above. It can be appreciated that any number of categories or categories can be defined for a given content file type.

In one embodiment, examples of content and feature categories can be illustrated in Table 1 below:

In one embodiment, an example of a content item category can be illustrated in Table 2 below:

In one embodiment, an example of a content page category can be illustrated in Table 3 below:

The authoring component 110 can use the type module 202-1 and the associated type definition 204-1 to retrieve the content portion 106-1 from the content archive 104-1 from the local data storage area 210. The type module 202-1 can then organize and format the content portion 106-1 to produce a display tile object 126-1. For example, the rules for type definition 204-1 may state that any text retrieved from the file (such as the first N paragraphs) will retain the formatting style specified within the file. Another rule may be that the content characteristics of the actual text in the file are not formatted into the Normal style defined in the file. Yet another rule may be that if all of the text of the content portion 106-1 may not be suitable for presenting the dimensions of the display block 124-1, the ellipsis "..." will be appended to the end of the text. These rules are only some illustrative rules, and other rules are possible. The embodiment is not limited to this case.

In some cases, the type definition 204-1 may define a set of rules to create a display tile object 126-1 from a combination of content and feature categories, content object categories, and content page categories, sometimes informally referred to as a "mashup." This provides a highly customized display tile object 126-1 that is constructed to represent the content of the content archive 104-1.

In one embodiment, examples of different combinations of classes can be illustrated in Table 4 below:

The type definition 204-1 may also provide rules that limit the display of the tile object 126-1 to a single category or type within the category. For example, the rule-definable type module 202-1 uses only textual content from the content archive 104-1, or only content objects in the form of images of the content archive 104-1.

The type definition 204-1 may further identify the device to generate the display tile object 126-1 for the content archive 104-1. For example, the rule definable type module 202-1 interacts with the server device to generate and retrieve the display tile object 126-1.

The type definition 204-1 may still further provide rules to generate a list of multiple versions of the display tile object 126-1 for presentation to the user for final selection. For example, the rules may produce P versions of the display block object 126-1, where P represents any positive integer (eg, P = 10). A list of multiple versions of the display block object 126-1 can be generated according to the examples given in Table 5 below:

The type module 202- g can use the information other than the information provided by the type definition 204- h to generate the display block object 126- e . For example, the type module 202- g can receive as input an information about the presentation display block 124- a selected for the content archive 104- a . The type module 202- g can receive information such as position, size, shape, dimensions, geometry, boundaries, proximity presentation display blocks 124- a , adjacent presentation display blocks 124- a, and the like. For example, if the type module 202-1 is using the type definition 204-1 to construct the display block object 126-1, the display block object 126-1 is too large for presenting the current dimension of the display block 124-1, then the type module 202 -1 may use information about adjacent or adjacent presentation display blocks 124-2, 124-3 to determine whether the current dimension of presentation display block 124-1 may be increased to accommodate larger display tile object 126-1, and may be correspondingly reduced The small presentation shows the current dimensions of blocks 124-2, 124-3. The authoring component 110 can implement various fitting algorithms to accommodate such situations.

FIG. 3A illustrates an embodiment of a user interface view 300 generated by fabrication component 110. The user interface view 300 can include a presentation surface 122 having a number of presentation display blocks 124- a that are empty before any display tile objects 126- e are created for the content archive 104- c . The user interface view 300 can also include various graphical user interface (GUI) tools 302- s for receiving control indicators 102- b from the author, such as copy command 302-1, cut command 302-2, and patch command 302- 3. In addition to the one shown in FIG. 3A, other GUI tools 302- s can be used, such as move commands, patch special commands, and the like.

The user interface view 300 can further include an archive navigation tool 304. The file navigation tool 304 can include a file management program application for a given OS designed to navigate a file system having stored data files. For example, the file navigation tool 304 can be used to navigate and present various content files 104- c from the local data storage area 210 or the remote data storage area 212. Examples of file navigation tool 304 may include MICROSOFT WINDOWS EXPLORER designed for the MICROSOFT WINDOWS operating system. Other file navigation tools are also available.

For example, during a production operation, the authoring component 110 can receive the control indicator 102- b to cause the content file 104-1 to be displayed with a display block from an input device, such as the indicator device 308 or the gesture 310 on the touchscreen display. 124-1 is associated. For example, the content producer can create the montage 120 by navigating and presenting the content archive 104 stored by one or both of the data storage areas 210, 212 using the archive navigation tool 304. The content producer can use various input devices, such as the indicator device 308 or the gesture 310 on the touch screen display, to select the content file 104- c for presenting the display block 124- a . As shown, the indicator device 308 can be used to select the content archive 104-1 and move the content archive 104-1 on the presentation display block 124-1 using drag and drop techniques. Alternatively, GUI input tool 302 can be used to perform similar operations.

FIG. 3B illustrates an embodiment of a user interface view 320 generated by the authoring component 110. The user interface view 320 can include a presentation surface 122 having a presentation display block 124-1 that is populated after the display tile object 126-1 for the content archive 104-1 is created. Once the content producer selects the content archive 104-1 and associates the content archive 104-1 with the presentation display block 124-1, the authoring component 110 can identify the content archive type of the content archive 104-1. In this example, authoring component 110 identifies the content file type of content archive 104-1 as an application file type, and more specifically, the word processing file. The authoring component 110 can utilize a type module 202-1 and a type definition 204-1 that are specifically designed to generate a display block object from a word processing file. The type module 202-1 can retrieve the appropriate content portion 106-1 from the content archive 104-1 using the type definition 204-1, wherein the content portion 106-1 includes the following information: content and feature categories, content object categories, content page categories. Or a combination of categories. The type module 202-1 can generate the display tile object 126-1 using the content portion 106-1 and present the display tile object 126-1 within the boundaries of the presentation display block 124-1.

FIG. 3C illustrates an embodiment of a user interface view 340 generated by the authoring component 110. The user interface view 340 illustrates the construction of the display tile object 126- e that has associated the given content archive 104- c with the corresponding presentation display block 124- a .

As previously described, there are situations where it is desirable to have some meaningful representation of the content archive 104- c , such as a MICROSOFT OFFICE file, website, map, feed, item, web blog (blog), and the like. The display tile object 126- e provides a customized representation for the content file 104- c that indicates that the user is prompted or the user to read or view the content from the content file 104- c . To be effective, show a box over the object 126- e wherein, a block object 126- e of a content file 104- c trailer or preview should be readable and attractive. Additionally, the display block object 126- e should be automatically generated without any forced user input or interaction. However, in some cases, a user interface control (eg, GUI input tool 302) may be presented to seek user input as appropriate.

To begin the display block creation operation, the authoring component 110 can receive the control indicator 102- b to associate the content archive 104- c with the presentation display block 124- a of the presentation surface 122 of the digital montage 120. Authoring component 110 can identify the contents of the file type file 104- c, and authoring component 110 can generate a display object block 126- e with content from the content files based on the content file 104- c type.

In various embodiments, the fabrication component 110 can automatically generate a display tile object 126- e having a display tile object surface 346 having or contained in one or more display tile object containers 342- u The selection information from the content file 104- c is taken . In one embodiment, for example, the selected information may include content from content archives 104- c or content portions retrieved from content archives 104- c , such as content portion 106-1 for content archives 104-1.

Similar to the presentation display block 124- a of the presentation surface 122, the display tile object container 342- u can include a display tile object surface 346 that is designed to present a set of discrete information, such as a content portion or a content portion clip 344- v . Define the area. The defined area can be of any size, dimension or shape as desired for a given implementation. A given display tile object surface 346 can have any number of display tile object containers 342- u , and each display tile object container 342- u can have a set of definitions (eg, size, shape, dimension, geometry) to ensure all The display tile object container 342- u is adapted to display a given size of the tile object surface 346. The definition of the display tile object container 342- u can be dynamically changed based on the following factors: other display tile object container 342- u , display tile object surface 346, content portion or content portion clip 344- v and display tile object container 342- u The association between, the one or more presentation display blocks 124- a , the presentation surface 122, a set of content archives 104- c , the association between the content archives 104- c and the presentation display blocks 124- a , and the content archives 104- c associated display block object 126- e , display characteristics, device characteristics, user preferences, and other factors. The embodiment is not limited to this case.

In one embodiment, the content producer can customize the display tile object surface 346 and the display tile object container 342- u . The user interface of the montage application 140 can provide various controls (e.g., GUI input tool 302) that are specifically defined to modify a display block object surface 346 and display a block object surface 346 on a set of display block object containers. The characteristics of 342- u . Examples of such controls may include, but are not limited to, schema controls, dimension controls, size controls, width controls, height controls, pixel controls, renewed controls, and the like. Alternatively, the content producer can select from any number of display block templates that provide different display block object surfaces and display tile object containers 342- u .

In one embodiment, for example, the authoring component 110 can select information from the content archives 104- c that are adapted to individually display the tile object container 342- u . Production component 110 can select such information based, for example, on the content file type of content archive 104- c . As described in detail with respect to FIG. 2, the authoring component 110 includes a plurality of type modules 202- g corresponding to each content file type, wherein each type module 202- g is configured to be defined based on the type of the type module 202- g 204- h retrieves a set of information from the content file 104- c in a specific manner. The authoring component 110 can identify the content file type of the content file 104- c , the usage type module 202-g, and the associated type definition 204-h from the content file 104- c to select information and generate the display block object 126 with the selected information. e .

In one embodiment, the authoring component 110 can execute a fitting algorithm designed to adapt the information from the content archive 104- c to one or more display tile object containers 342- u according to the container for the corresponding display tile object A set of container definitions of 342- u and the fitting algorithm form a filled container 348- w . In one embodiment, the container definition may include portions of the type definition 204- h of the type module 202- g . Additionally or alternatively, the container definition may contain information other than the information provided by the type definition 204- h . For example, the type module 202- g can receive as input the information about the display tile object container 342- u selected for the presentation display block 124- a of the content archive 104- c . The type module 202- g can receive information such as position, size, shape, dimensions, geometry, boundaries, adjacent display tile object containers 342- u , adjacent display tile object containers 342- u, and the like. For example, if the type module 202-1 is using the type definition 204-1 to construct the display block object 126-1 (the display block object 126-1 is for presenting the current dimension of the display block object container 342-1 of the display block 124-1) If it is too large, the type module 202-1 can use information about the adjacent or adjacent display block object containers 342-2, 342-3 to determine whether the current dimension of the display tile object container 342-1 can be increased to accommodate the content portion. A larger amount of information for 106-1, and the current dimensions of the displayed tile object containers 342-2, 342-3 can be correspondingly reduced. Fabrication component 110 can implement various fitting algorithms to accommodate these conditions.

There may be the following situations: a need to allow user-specific content files can be used to automatically generate 104- c, one set of block template selection display for a given object is a block of a block template 126- e. For example, if the user does not like any display block template or automatically generated display block object 126- e , the user can use a set of user interface controls to edit the display block template or the specific display block object 126- e , The customization is selected to display the contents of the block object 126- e . Examples of user interface controls may include, for example, GUI input tool 302.

As described with reference to FIG. 3B, once the content producer selects the content archive 104-1 and associates the content archive 104-1 with the presentation display block 124-1, the authoring component 110 can begin to display the creation and construction of the tile object 126-1. Or generated to represent the content contained in the content file 104-1.

For example, the authoring component 104-1 can identify the content file type of the content archive 104-1. In this example, authoring component 110 identifies the content file type of content archive 104-1 as an application file type, and more specifically, the word processing file. The authoring component 110 can utilize a type module 202-1 and a type definition 204-1 that are specifically designed to generate a display block object from a word processing file. The type module 202-1 can use the type definition 204-1 to retrieve the appropriate content portion 106-1 and/or the content portion clip 344- v from the content archive 104-1, wherein the content portion 106-1 includes the following information: Feature category, content object category, content page category, or category combination. The type module 202-1 can use the content portion 106-1 and/or the content portion clip 344- v to generate one or more filled containers 348- w for displaying the tile object 126-1. The type module 202-1 can then present the filled container 348- w within the boundaries of the display tile object 126-1.

Referring again to FIG. 3C, user interface view 340 illustrates the situation in which content archive 104-1 has been associated with presentation display block 124-1 as described with reference to FIGS. 3A, 3B. More specifically, the user interface view 340 illustrates the construction of the display tile object 126-1 after the given content archive 104-1 has been associated with the corresponding presentation display block 124-1. As shown in FIG. 3C, the user interface view 340 illustrates the display block object 126-1 having the filled container 348-1, and the filled container 348-1 is included during the display of the display block object 126-1 of the content file 104-1. The content portion from the content portion 106-1 of the content archive 104-1 is clipped 344-1. For example, the authoring component 110 can extract one or more content portion clips 344- v from the content portion 106-1 of the content archive 104-1. The type definition 204-1 may contain a set of rules regarding the type of information retrieved from the content archive 104-1. For example, the type definition 204-1 may include information of three categories including associated content and feature categories (eg, paragraphs or attributes) from the content archive 104-1, content objects of the content archive 104-1. Category (eg, image, embedded object) and content page category within content file 104-1 or some combination of the above categories. The authoring component 110 can use the rules provided by the type definition 204-1 to retrieve the selected content portion clip 344- v from the content portion 106-1 of the content archive 104-1. The user interface view 340 illustrates the situation where the content portion clip 344-1 is retrieved from the content portion 106-1 and the content portion clip 344-1 is placed within the corresponding display tile object container 342-1 to form a filled container 348- 1. The authoring component 110 can continue to retrieve the selected content portion clip 344- v from the content portion 106-1 in accordance with the rules provided by the type definition 204-1 to create additional filled containers 348-2 through 348- w until the tile object 126 is displayed. -1 is completely filled.

4 illustrates an example of a fabrication component 110 that produces display tile object 126-1. As shown, the content file 104-1 can include various types of content and feature category information, including a title 402, a first paragraph 404, a second paragraph 406, and various meta-data 408. The content file 104-1 may further include various types of content item category information, including an image 410, a bar chart 412, and an equation 414. The type definition 204-1 may include five rules, including: a first rule, using a specific display block template labeled "display block template 1"; a second rule, capturing a title 402; a third rule, from the metadata 408撷Taking the author; the fourth rule, taking the first N paragraphs 404, 406 (eg, N=2); and the fifth rule, drawing the first graphic, in which case the first graphic is a bar chart 412. The type module 201-1 can use the type definition 204-1 to retrieve the content portion 106-1 from the content archive 104-1 according to rules 1-5 of the type definition 204-1, and generate a display tile object 126-1, the display The tile object 126-1 is presented as a user interface view having specific information of the content portion 106-1 formatted according to "display block template 1".

FIG. 5 illustrates an embodiment of a messaging system 500 suitable for publishing or distributing montages 120 generated by the montage application 140. The content producer can use the montage application 140 to generate the montage 120 using various user interface views provided by the user interface component 538. The user interface component 538 can include a user interface component for the montage application 140 or a user interface component for executing the operating system of the montage application 140 (eg, MICROSOFT WINDOWS). Once the montage 120 has been generated, the content producer can distribute the montage 120 to various content consumers using a publishing model, a messaging model, or a combination of a publishing model and a messaging model.

In one embodiment, the montage application 140 can publish the montage and associated content archives 104- c from the local data store 210 to the remote data store 212 using the publish component 532. For example, the remote data store 212 can be implemented as part of a network storage server 550 that can be accessed by a network service, such as a social networking service (SNS). Content consumers can access web services to view web service versions.

In one embodiment, the montage application 140 can use the body message component 534 to send the montage 120 and associated content files 104- c as messages 516 and message attachments via a messaging infrastructure, such as message server 540. Content consumers can access and view the message version. Alternatively, the montage application 140 can use an external (non- ontology ) messaging application 542- k .

In one embodiment, the montage application 140 can receive the montage 120 and associated content archives 104 by publishing the montage 120 and associated content archives 104- c to a combination of the web service usage publishing model and the messaging model. c connected to the network 518- n version and sending the message having link 516 518- n. The content consumer can access the message 516, select the link 518- n, and view the network version of the Montage 120. In addition, the content consumer can select the display block object 126- e of the montage 120 to view the network version of the content file 104- c associated with the selected display tile object 126- e .

The montage application 140 can use the security component 536 to manage content consumers' permissions and access to the montage 120 and associated content files 104- c . Security component 536 can manage accounts, authentication information, authorization information, security information (eg, encryption/decryption algorithms, security keys, credentials, etc.), licensing levels, and the like. In one embodiment, the security component 536 can receive a control indication from the input device, representing a command from the content producer to authorize the network storage server 550 accessible by the network service to retrieve the content file 104- c from the local data. The storage area 210 is communicated to the remote data storage area 212.

In the illustrated embodiment shown in FIG. 5, messaging system 500 can include a plurality of computing devices 510- j , message server 540, and network storage server 550 all communicating via network 530. Computing device 510- j can each implement a montage application 140 and/or one or more messaging applications 542- k . Although the messaging system 500 as shown in FIG. 5 has a limited number of components in a particular topology, it will be appreciated that the messaging system 500 can include more or less elements in alternate topologies as desired for a given implementation.

Network 530 can include a communication architecture designed to convey information between various devices of messaging system 500. Network 530 can implement any well-known communication technology, such as a technology suitable for use with a packet switched network (eg, a shared network (such as the Internet), a private network (such as an intranet). Etc.), a circuit-switched network (for example, a public switched telephone network) or a combination of a packet switched network and a circuit-switched network (with appropriate gateways and decoders).

The message server 540 can include or use one or more server computing devices and/or server programs that operate to perform various methods in accordance with the described embodiments. For example, when installed and/or deployed, the server program can support one or more server roles of the server computing device to provide certain services and features. The exemplary message server 540 can include, for example, separate and enterprise server computers that operate a server OS (such as MICROSOFT OS, UNIX ^® OS, LINUX ^® OS, or other suitable server OS). Exemplary server programs may include, for example, communication server programs, such as the MICROSOFT OFFICE communication server (OCS), for managing incoming and outgoing messages; and communication server programs, such as the MICROSOFT switching server, for Providing unified messaging (UM) for email, voicemail, VoIP, instant messaging (IM), group IM, enhanced presence and audio-video conferencing; and/or other types according to the described embodiments Program, application or service.

The network storage server 550 can also include or use one or more server computing devices and/or server programs that operate in accordance with the described embodiments. Various methods. For example, when installed and/or deployed, the server program can support one or more server roles of the server computing device to provide certain services and features. The exemplary network storage server 550 can include, for example, a stand-alone and enterprise-class server computer that operates a server OS such as MICROSOFT OS, UNIX OS, LINUX OS, or other suitable server-based OS. An exemplary server program may include, for example, a network storage server program (such as MICROSOFT LIVE) that provides access to files and files (including multimedia or media files such as images, photos, photo albums, video, video albums, etc.). Road storage. Exemplary server The program may further include, for example, a web application (such as a social networking application), a search application, a file management program, a web blog (blog), a word processing program, a spreadsheet program, and a database program. , a graphics program, a file sharing program, a messaging application, a web service, a web application, a web server, and/or other types of programs, applications, or services in accordance with the described embodiments.

Computing devices 510- j can each include a processor 502 and a memory 504 communicatively coupled to processor 502. The processor 502 and the memory 504 can each be communicatively coupled to the communication interface 509. An illustrative architecture and examples of computing device 510- j can be described with reference to FIG.

Communication interface 509 may comprise or implement various communication technologies allow computing devices to communicate with each other via a network 510- j 530 and other devices communicate with system 500. Communications. For example, the various devices of the messaging system 500 can each include a communication interface 509 that implements various types of standard communication components designed to cooperate with the network 530, such as one or more communication interfaces, network interfaces, networks. Road interface cards (NICs), radios, wireless transmitters/receivers (transceivers), wired and/or wireless communication media, physical connectors, and the like. By way of example and not limitation, communication media includes wired communication media and wireless communication media. Examples of wired communication media may include wires, cables, metal leads, printed circuit boards (PCBs), backplanes, switch fabrics, semiconductor materials, twisted pairs, coaxial cables, fiber optics, propagated signals, and the like. Examples of wireless communication media may include acoustics, radio frequency (RF) spectrum, infrared, and other wireless media.

In various embodiments, communication interface 509 can include a plurality of different types of transports 512- m . Each of the transfer tools 512- m can implement or utilize the same or different sets of communication parameters to convey information between the various devices of the messaging system 500. In one embodiment, for example, each of the transfer tools 512- m can implement or utilize a different set of communication parameters to convey information between the computing device 510- j and the message server 540. Some examples of communication parameters may include, but are not limited to, communication protocols, communication standards, radio frequency (RF) bands, radios, transmitters/receivers (transceivers), radio processors, baseband processors, network scanning thresholds Value parameters, RF channel parameters, access point parameters, rate selection parameters, frame size parameters, aggregate size parameters, packet retry limit parameters, protocol parameters, radio parameters, modulation and coding scheme (MCS), validation parameters, Media Access Control (MAC) layer parameters, entity (PHY) layer parameters, and any other communication parameters that affect the operation of communication interface 509 implemented by computing device 510- j . These embodiments are not limited to this case.

In various embodiments, communication interface 509 of computing device 510-1 can implement different communication parameters to provide varying bandwidth or communication speed. For example, the transfer tool 512-1 can include a high speed interface that implements appropriate communication parameters for high speed communication of information to the network 530, and the transfer tool 512-2 can include appropriate communication for implementing low speed communication for information to the network 530. The low speed interface of the parameter.

Regarding wired communication, for example, the delivery tool 512-1 can include a network interface designed to communicate information via a packet switched network such as the Internet. The delivery tool 512-1 can be configured to functionally provide data communication in accordance with different types of wired network systems or protocols. Provide information Examples of appropriate wired network systems for the service may include the Internet Engineering Task Force (IETF) Transmission Control Protocol (TCP) and Internet Protocol (IP) communication standards groups, User Datagram Protocol (UDP), and Datagrams. Congestion Control Protocol (DCCP), Stream Control Transmission Protocol (SCTP), Resource Reservation Protocol (RSVP), Explicit Congestion Notification (ECN) Agreement, Open Shortest Path First (OSPF) Protocol Group, Reliable Transport Protocol (RTP), IETF Instant Transfer Protocol (RTP) and more. The delivery tool 512-2 can be configured to provide data communication according to different message protocols, such as Simple Mail Transfer Protocol (SMTP), Extended SMTP (ESMTP), Post Office Protocol (POP), POP3, Internet Message Storage. Protocols (IMAP), Multipurpose Internet Mail Extensions (MIME), Unix to Unix Replication (UUCP), International Telecommunications Union (ITU) protocol groups (such as the ITU-T X.400 Agreement), etc. It can be appreciated that other wired communication technologies can be implemented, and embodiments are not limited in this case.

With regard to wireless communication, for example, the delivery tool 512-1 can include a radio designed to communicate information via a wireless local area network (WLAN). The delivery tool 512-1 can be configured to provide data communication functionality in accordance with different types of wireless network systems or protocols. Examples of suitable wireless network systems that provide data communication services may include the Institute of Electrical and Electronics Engineers (IEEE) 802.xx series of protocols, such as the IEEE 802.11a/b/g/n series of standard protocols and variants (also known as "WiFi" "), IEEE 802.16 series of standard protocols and variants (also known as "WiMAX"), IEEE 802.20 series of standard protocols and variants, and so on. The delivery tool 512-2 can include a data network connection designed to be provided via one or more cellular radiotelephone systems Radio of Information. Examples of cellular radiotelephone systems providing data communication services may include GSM and General Packet Radio Service (GPRS) systems (GSM/GPRS), CDMA/1xRTT systems, Global Evolution Enhanced Data Rate (EDGE) systems, evolution-only data or Evolution Data Optimized (EV-DO) System, Data and Voice Evolution (EV-DV) System, High Speed Downlink Packet Access (HSDPA) System, High Speed Uplink Packet Access (HSUPA), etc. It can be appreciated that other wireless technologies can be implemented and embodiments are not limited in this regard.

In various embodiments, communication interface 509 of computing device 510-1 can implement the same set of communication parameters to provide the same or substantially similar bandwidth or communication speed. However, the delivery tools 512-1, 512-2 may be utilized by the montage application 140 and/or the messaging application 542-1 at different points in time. In one embodiment, for example, the montage application 140 can communicate the montage 120 and one or more of the content files 104- c for the montage 120 during the first time interval, and the montage application 140 and/or the messaging application 542 -1 may convey message 516 and information related to montage 120 and/or supporting content file 104- c during the second time interval. In one embodiment, for example, the first time interval and the second time interval may be completely discontinuous, wherein the start time and the end time of the first time interval precede the start time of the second time interval. In one embodiment, for example, the first time interval and the second time interval may partially overlap, wherein the start time of the first time interval precedes the start time of the second time interval, but the end time of the first time interval is later than the first time interval The start time of the two time intervals. The embodiment is not limited to this case.

Computing device 510- j can each implement one or more messaging applications 542- k having a montage application 140 of messaging component 534 and/or various types of messages configured to communicate various formats. One embodiment will be described with reference to the messaging application 542- k for the messaging model, although such descriptions are applicable to other embodiments utilizing the messaging component 534 of the montage application 140.

Each of the messaging applications 542- k can represent a particular type of delivery tool, enabling the processing of messages of a particular type and format for a particular application. The messaging application 542- k may include (but is not limited to) a fax application, a video messaging application, an instant messaging (IM) application, a chat application, an email (email) application, and a short message service (SMS) application. , Multimedia Messaging Service (MMS) applications, Social Network System (SNS) applications, and more. It should be understood that the embodiments are not limited in this regard, and the messaging application 542- k can include any other type of messaging or communication application consistent with the described embodiments. It should also be appreciated that in addition to implementing the messaging application 542- k , the computing devices 510- j can each implement other types of applications consistent with the described embodiments.

As shown in FIG. 5, for example, computing devices 510-1, 510-2 implement respective messaging applications 542-1, 542-2. The messaging applications 542-1, 542-2 can generally operate to generate, transmit, receive, update, modify, and otherwise manage the information of the computing devices 510-1, 510-2. It can be appreciated that the implementation details shown by the messaging application 542-1 for computing device 510-1 and computing device 510-1 as described herein also apply. The respective message application 542-2 of the computing device 510-2 and the computing device 510-2.

In one embodiment, the messaging applications 542-1, 542-2 are implemented as local resources provided by computing devices 510-1, 510-2 (such as processor 502 and memory 504 of computing device 510-1). A separate client-based application stored and executed, rather than a web-based messaging application implemented on a network device and accessed by computing devices 510-1, 510-2 via a web browser. In one embodiment, the messaging applications 542-1, 542-2 may include local resources that are suitable for distributed processing and are partially executed on the computing devices 510-1, 510-2 and partially executed on the network resources. Distributed application on the top. Additionally or alternatively, the messaging applications 542-1, 542-2 can include a web-based messaging application implemented on a network device and accessed by the computing devices 510-1, 510-2 via a web browser. The embodiment is not limited to this case.

In one embodiment, for example, the messaging application 542-1 can be configured to communicate the message 516 via the delivery tool 512-2. When communicated via the delivery tool 512-2, the message 516 can include one or more embedded links 518- n and/or montage 120 for the montage 120 and/or one or more content files 104- c . The one or more embedded links 518- n can include, for example, a montage 120 and/or one or more content files 104 stored on the network storage server 550 and accessible by the message sender or message recipient. c of reference.

Each of the links 518- n can include a reference or metric that the user can follow directly or automatically follow the stored montage 120 and content file 104- c by the program. Reference is a data type and is used to access a reference object, which refers to a reference object elsewhere in the memory of the device (eg, a file server) (eg, stored montage 120 and content file 104- c) , such as objects, files, data items, etc.). Typically, the reference is a value that enables the program to directly access the reference object. Reference objects can be stored in the same device in reference form or stored in reference to different devices. Most programming languages support some form of reference. Examples of links 518- n may include, but are not limited to, hypertext and hyperlinks, such as hypertext and hyperlinks used by the World Wide Web (WWW). Hypertext is text with hyperlinks. A hyperlink usually contains an anchor point, which is the location within the message for following the hyperlink. The target of the hyperlink is the stored montage 120 and/or content file 104- c pointed to by the hyperlink. When the anchor point of the link is displayed, the user can point on the link by some means (such as by touching the link (for example, with a touch screen display) or using an indicator device (for example, a mouse) Select) to start the link and follow the link. When the link 518- n is activated, the target of the link 518- n is displayed via a web browser or application.

As described above, the montage application 140 can use the distribution model and the messaging model by publishing the montage 120 and associated content files 104- c to the remote data storage area 212 of the network storage server 550. A link 518- n for the network version of the montage 120 and associated content files 104- c is received and a message 516 with a link 518- n is sent. The content consumer can access the message 516, select the link 518- n, and view the network version of the Montage 120. In addition, the content consumer can select the display block object 126- e of the montage 120 to view the network version of the content file 104- c associated with the selected display tile object 126- e . This hybrid model can be described in more detail with reference to FIG. 6.

FIG. 6 illustrates an embodiment of a message flow for messaging system 500. As shown in FIG. 6, the publishing component 532 can publish the montage 120 and associated content archives 104- c to the web service 652. The publishing component 532 can send the montage 120 and associated content archives 104- c to the network storage server 550 via the transfer tool 512-1 as indicated by arrow 602. For example, as a high speed delivery tool, the delivery tool 512-1 can have sufficient bandwidth to convey a file size that is typically associated with the content file 104- c and that is relatively large in size relative to the message 516.

The network storage server 550 can receive the montage 120 and associated content files 104- c and store the montage 120 and associated content files 104- c in the remote data storage area 212. Network storage server 550 can then send link 518- n to montage 120 and content file 104- c stored in remote data storage area 212, as indicated by arrow 604.

The publishing component 532 can receive the link 518- n and forward the link to the authoring component 110. The authoring component 110 can associate the link 518- n with each display tile object 126- e and update the montage 120 with the associations such that the content consumer can select to display the tile object 126- e and from the remote data storage area. 212 accesses the associated content file 104- c for a more in-depth view of the content file 104- c .

In one embodiment, in accordance with the release model, authoring component 110 can send updated montage 120 to publishing component 532. The publishing component 532 can then post the updated montage 120 and link 518- n on the web service 652 as indicated by arrow 606. For example, web service 652 can include a social network connection service (SNS), and content consumers with defined relationships with content producers (eg, friends) can access and associate montage 120 via published links 518- n Content file 104- c . In another example, the web service 652 can provide an account to the content producer that can be viewed by the content consumer based on the permissions set by the web service 652 and/or the security component 536. The content consumer can access the web service 652 via the computing device 510-2, select the link 518- n to the montage 120 file via the web browser, request the montage 120 from the remote data storage area 212, as indicated by arrow 610 Instructions. Network service 652 can receive the request and send montage 120 to computing device 510-2 as indicated by arrow 612. Computing device 510-2 may present montage 120 as a user interface view of presentation surface 122 using display block object 126- e in presentation display block 124- a . Computing device 510-2 can generate a user interface view as a web page for a web browser, or as a user interface view of an application, such as a montage application 140 or a montage viewer designed to view montage 120.

In one embodiment, in accordance with the messaging model, authoring component 110 can forward updated montage 120 and link 518- n to message component 534 (or messaging application 542-1). Message component 534 can receive link 518- n and message content 620 as input. Message content 620 can include messages from content producers. Message component 534 can generate message 516 with message content 620 and link 518- n . Additionally or alternatively, the message 516 may include the montage 120 and/or certain content files 104- c , depending on the file size limit and the available bandwidth on the message transfer tool 512-2, as appropriate. The montage 120 may include a full fidelity version of the montage 120, or a lower fidelity version of the montage 120 that is more suitable for transmitting the available bandwidth of the tool 512-2, such as a thumbnail version of the montage 120.

The message component 534 can send the message 516 to the message application 542-2 of the computing device 510-2 via the message server 540 using the transfer tool 512-2, as indicated by arrow 608. The content consumer can open the message 516, select the link 518- n to the montage 120 and request the montage 120 from the remote data storage area 212, as indicated by arrow 610. Network service 652 can receive the request and send montage 120 to computing device 510-2 as indicated by arrow 612. Computing device 510-2 may present montage 120 as a user interface view of presentation surface 122 using display block object 126- e in presentation display block 124- a . Computing device 510-2 can generate a user interface view as a web page for a web browser, or as a user interface view of an application such as montage application 140 or a montage viewer designed to view montage 120.

FIG. 7A illustrates an embodiment of a user interface view 700 of an exemplary message 516. As described with reference to FIG. 6, the content producer can use the montage application 140 and/or the messaging application 542-1 to generate and send a message 516 with a reference to the montage 120 or to the montage 120. The content consumer can receive the message 516 via the computing device 510-2 and the messaging application 542-2. User interface view 700 provides an example of a message 516 implemented as an email message.

The message 516 can include a ribbon bar 702 having various command elements for emails, such as a reply button, a reply owner button, a forward button, a delete button, a move to folder button, and a build rule. Buttons and other buttons. Message 516 can further include an address bar 704 with address information and a message body 706. The message context 706 can include a surface having a montage file thumbnail 720 stored in the remote data storage area 212 and a link 518-1 to the montage 120. The Montage Archive Thumbnail 720 can include a lower fidelity version of the Montage 120.

For example, a content consumer can use an input device such as indicator device 710 to select a montage thumbnail 720. For example, a content consumer may also use an input device (such as gesture 712 on a touch screen display) to select a link 518-1 entitled "Student Class Tour." In either case, choose to launch a web browser or application to view the montage 120.

FIG. 7B illustrates an embodiment of a user interface view 740 of the montage 120 initiated by the message 516. Depending on the given implementation of computing device 510-2, computing device 510-2 may generate user interface view 740 as a web page for a web browser, or as an application (such as montage application 140 or specifically designed to view montage 120) User interface view of montage viewer 730). For example, presentation component 130 implemented by montage application 140 for computing device 510-2 and/or montage viewer 730 can receive control indicators to open montage 120 and begin operations to retrieve from remote data storage area 212. Montage 120. The presentation component 130 and/or the montage viewer 730 can present the user interface view 740 of the montage 120, including the presentation surface 122, with the display block object 126- e in the appropriate presentation display block 124- a .

When rendered as a web page, the rendering component 130 can use code specifically designed for the web page, such as Hypertext Markup Language (HTML) or similar code. However, the HTML code may not be limited to a given type of web browser implemented by the client device 510-2. When presented as a user interface view of the montage viewer 730, the rendering component 130 and/or the montage viewer 730 can use the code optimized for the montage viewer 730. For example, the montage 120 can be generated using the HTML code of the web page, where Extensible Markup Language (XML) code is embedded in the HTML code. The XML code can be generated using a data grid specifically designed for the montage application 140 or the montage viewer 730. Thus, the montage application 140 or montage viewer 730 can visualize a higher fidelity version of the montage 120 relative to the lower fidelity version of the montage 120 used by the web page.

FIG. 7C illustrates an embodiment of a user interface view 750 of an example of a montage 120 presented in the montage viewer 730. As described with reference to FIG. 7B, the montage viewer 730 can present the user interface view 740 of the montage 120, including the presentation surface 122, with the display block object 126- e in the appropriate presentation display block 124- a . Assume that presentation surface 122 includes display tile object 126-1 of content archive 104-1 as described with reference to FIG.

For example, content consumers may use inputs such as indicator device 710 The incoming device selection displays the block object 126-1. Presentation component 130, implemented by montage application 140 for computing device 510-2 and/or montage viewer 730, receives control indicators to select display block object 126-1, and retrieves display blocks from remote data storage area 212. Content file 104-1 of object 126-1.

FIG. 7D illustrates an embodiment of a user interface view 760 of the content archive 104-1 since the montage 120 was launched. The presentation component 130 and/or the montage viewer 730 can present the user interface view 760 with a full fidelity version of the content archive 104-1 retrieved from the remote data store 212. Alternatively, the content archive 104-1 can be rendered using an ontology application similar to the application used to generate the content archive 104-1 or a viewer specifically designed for this application. The embodiment is not limited to this case.

In various embodiments, presentation component 130 can dynamically generate montage 120 for viewing on displays having different characteristics, such as different sizes, resolutions, re-rates, backlights, power consumption, and the like. In such cases, the presentation component 130 can be configured to detect display characteristics of the display and modify the montage 120 for presentation on the display. For example, when montage 120 is presented on a large wall display having a touch member (as seen in many conference rooms), presentation component 130 can be generated with a greater number of presentation display blocks 124- a and display block objects 126- e . A much larger montage 120 version. At the same time, when the montage 120 is presented on a smart phone, the presentation component 130 can generate a smaller montage 120 version with a smaller number of presentation blocks 124- a and display block objects 126- e . Similarly, presentation component 130 can generate montages 120 having different fidelity levels based on the screen resolution or pixel size of a given display. In another example, the rendering component 130 can generate a montage 120 version when in the portrait mode, and another montage 120 version when in the panning mode, such as when the user rotates the smart phone or tablet. The embodiment is not limited to this case.

The operation of the above embodiments can be further described with reference to one or more logic flows. It can be appreciated that the representative logic flows are not necessarily performed in the order presented or in any particular order unless otherwise indicated. In addition, various activities described with reference to the logic flow can be performed serially or in parallel. The logic flow can be implemented using one or more of the hardware components and/or software components or alternative components of the described embodiments, as needed for a given set of design and performance limitations. For example, a logic flow can be implemented as logic (eg, computer program instructions) for execution by a logic device (eg, a general purpose or special purpose computer).

FIG. 8A illustrates one embodiment of a logic flow 800. Logic flow 800 may represent performing some or all of the operations by one or more embodiments described herein, such as production component 110 of montage application 140, to generate montage 120.

In the illustrated embodiment shown in FIG. 8A, at block 802, logic flow 800 can provide a presentation surface having a plurality of rendered display blocks. For example, the authoring component 110 can provide a presentation surface 122 having a plurality of presentation display blocks 124- a via a user interface 538. The presentation surface 122 can be selected from a number of montage templates or custom designed by the content producer.

At block 804, logic flow 800 can receive a control indicator to associate the content archive with the presentation display block. For example, the authoring component 110 may receive a control directive to make content files 102- b and 104- c 124- a presentation associated with a block. Control indicator 102- b may be from an input device, representing a command from a content producer.

At block 806, logic flow 800 can identify the content file type of the content archive. For example, authoring component 110 can identify the content file type of content archive 104- c . Can check the contents of the file 104- c by the file extension, file 104- c content of metadata, the information within the content file 104- c analysis to generate the content file 104- c of the application and other information to perform Identification.

At block 808, logic flow 800 can retrieve a portion of the content from the content archive based on the content archive type. For example, the authoring component 110 can select the type module 202- g based on the content file type and use the selected type module based on the type definition 204- h associated with the content file type found for the content archive 104- c . 202- g takes the appropriate content portion 106- d from the content file 104- c . In one embodiment, the content file 104- c may be stored in the local data store 210, and may use the file content portion navigation tools 304 106- d fetched via the data bus. In one embodiment, the content file 104- c can be stored in the remote data storage area 212 and can be retrieved via the network using the content navigation component 304- d .

At block 810, logic flow 800 can generate a display tile object based on the content portion. For example, the authoring component 110 can generate the display tile object 126- e from the retrieved content portion 106- d using the selected type module 202- g in accordance with the associated type definition 204- h . Display block object 126- e can be presented in presentation display block 124- a . The display tile object 126- e is designed to present sufficient information about the base content file 104- c to allow the content consumer to determine whether it will view the full fidelity view of the content archive 104- c .

At block 812, logic flow 800 can store the rendering surface and display tile objects as montages. For example, fabrication component 110 can store presentation surface 122 and any display tile object 126- e as montage 120. For example, the Montage 120 can then be distributed, published, and consumed by various content consumers by using, for example, the messaging system 500.

FIG. 8B illustrates one embodiment of a logic flow 820. Logic flow 820 may represent some or all of the operations performed by one or more embodiments described herein, such as production component 110 of montage application 140, to produce display block object 126- e of montage 120.

In the illustrated embodiment shown in FIG. 8B, at block 822, logic flow 820 can receive a control indicator to associate the content archive with the presentation display block of the digital montage presentation surface. For example, authoring component 110 can receive control pointer 102- b to associate content archive 104-1 with presentation display block 124-1 of presentation surface 122 of a digital montage (such as montage 120).

At block 824, logic flow 820 can identify the content file type of the content archive. For example, the authoring component 110 can identify the content file type of the content archive 104-1. Production component 110 can have a content file The content file type of 104-1 is identified as one of the application file types including the following: word processing file, spreadsheet file, presentation file, personal information management program file, database file, publisher file, map File, note file or message file and other files.

At block 826, the logic flow 820 can retrieve the content portion of the content archive based on the content archive type. For example, the authoring component 110 can retrieve the content portion 106-1 of the content archive 104-1 based on the identified content file type.

At block 828, logic flow 820 can generate a display tile object based on the content portion. For example, authoring component 110 can automatically generate display tile object 126-1 based on content portion 106-1. More specifically, the authoring component 110 can generate the display tile object 126-1 as the display tile object surface 346 having the selected content portion clip 344- v contained within the corresponding display tile object container 342- u .

The authoring component 110 can automatically select certain content portion clips 344- v from the content portion 106-1 of the content archive 104-1 based on the content archive type. More specifically, the authoring component 110 can select a content portion clip 344- v from the content portion 106-1 of the content archive 104-1 based on the type definition 204- h associated with the content archive type, the type definition including the following information: content And feature categories, content object categories, or content page categories. Once selected, the authoring component 110 can associate the selected portion of the clip with the corresponding display tile object container 342- u of the display tile object surface 346.

Additionally or alternatively, the authoring component 110 can select certain content portion clips 344- v from the content portion 106-1 of the content archive 104-1 in response to the user control pointer. For example, authoring component 110 can receive control pointer 102- b from the input device to select content portion clip 344- v from content portion 106-1 of content archive 104-1. Additionally, the authoring component 110 can also receive the control indicator 102- b from the input device to cause the selected content portion clip 344- v from the content portion 106-1 of the content archive 104-1 to be associated with the corresponding display tile object container 342- u . Union.

Once the content portion clip 344- v is associated with the display tile object container 342- u , the authoring component 110 can utilize the container definition for one of the corresponding display tile object container 342- u and/or display tile object surface 346. The merging algorithm causes the content portion clip 344- v to be adapted to the corresponding display tile object container 342- u to form the filled container 348- w .

Once a set of filled containers 348- w is created, the fabrication component 110 can utilize the same or similar fitting algorithm to make the filled container 348- w based on a set of surface definitions of the display tile object surface 346 and/or the presentation surface 122. Suitable for displaying the tile object surface 346.

FIG. 9 illustrates one embodiment of a logic flow 900. Logic flow 900 may represent some or all of the operations performed by one or more embodiments described herein, such as presentation component 130 of montage application 140.

In the illustrated embodiment shown in FIG. 9, at block 902, logic flow 900 can generate a montage containing a rendering surface having a plurality of rendering display blocks, each rendering display block having a corresponding content file Display square objects. For example, the presentation component 130 can generate a montage 120 that includes a presentation surface 122 having a plurality of presentation display blocks 124- a , each presentation display block 124- a having a display for the respective content archive 104- c Square object 126- e .

At block 904, logic flow 900 can send the montage and content archive to the web service. For example, the publishing component 532 of the montage application 140 can send the montage 120 and associated content archives 104- c to the network storage server 550 for remote data storage 212 accessible via the web service 652. Store.

At block 906, logic flow 900 can receive a reference to the montage and each content archive. For example, the publishing component 532 can receive a link 518- n to the montage 120 and each content archive 104- c . The link 518- n may include a reference or indicator of the montage 120 stored on the remote data storage area 212 and the network version of each content file 104- c .

At block 908, logic flow 900 can associate a reference to the content archive with the corresponding display tile object. For example, the publishing component 532 can pass the received link 518- n to the authoring component 110. The authoring component 110 can associate the link 518- n of the content file 104- c with the corresponding display tile object 126- e . When the content consumer chooses to display the tile object 126- e , the presentation component 130 can retrieve the content archive 104- c associated with the display tile object 126- e via the associated link 518- n .

FIG. 10 illustrates an embodiment of an exemplary computing architecture 1000 suitable for implementing various embodiments as previously described. The computing architecture 1000 includes various common computing components, such as one or more processors, coprocessors, memory cells, chipsets, controllers, peripherals, interfaces, oscillators, timers, video cards, audio cards, multimedia inputs. /output (I/O) components and more. However, embodiments are not limited to implementation by computing architecture 1000.

As shown in FIG. 10, computing architecture 1000 includes processing unit 1004, system memory 1006, and system bus 1008. Processing unit 1004 can be any of a variety of commercially available processors. Dual microprocessors and other multiprocessor architectures can also be used as the processing unit 1004. The system bus 1008 provides an interface for system components, including but not limited to the interface of the system memory 1006 to the processing unit 1004. System bus 1008 can be any of several types of bus bars 1008 that can be further interconnected to a memory bus (with or without memory) using any of a variety of commercially available bus bar architectures Body controller), peripheral busbars and local busbars.

System memory 1006 can include various types of memory cells, such as read only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), dual data rate DRAM (DDRAM), synchronous DRAM (SDRAM). , static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory (such as iron Electropolymer memory), bidirectional memory, phase change or ferroelectric memory, 矽-oxide-nitride-oxide-矽 (SONOS) memory, magnetic or optical card or any other type suitable for storing information Media. In the illustrated embodiment shown in FIG. 10, system memory 1006 can include non-volatile memory 1010 and/or volatile memory 1012. A basic input/output system (BIOS) can be stored in the non-volatile memory 1010.

The computer 1002 can include various types of computer readable storage media including an internal hard disk drive (HDD) 1014, a magnetic floppy disk drive (FDD) read or written to the removable disk 1018 (FDD). 1016 and an optical disk drive 1020 that reads or writes to a removable optical disk 1022 (eg, a CD-ROM or a DVD). HDD 1014, FDD 1016, and optical disk drive 1020 can be coupled to system bus 1008 via HDD interface 1024, FDD interface 1026, and optical drive interface 1028, respectively. The HDD interface 1024 for external drive implementation may include at least one or both of a Universal Serial Bus (USB) and IEEE 1394 interface technology.

The drives and associated computer readable media provide volatile and/or non-volatile data storage, data structures, computer executable instructions and the like. For example, a plurality of program modules can be stored in the drive and memory unit 1010, 1012. The drive and memory unit 1010, 1012 includes an operating system 1030, one or more application programs 1032, and other program modules 1034, and Program data 1036. The one or more applications 1032, other program modules 1034, and program materials 1036 can include, for example, a montage application 140, a production component 110, a presentation component 130, a security component 536, a publishing component 532, a message component 534, and a user. Interface 538 and messaging application 542.

The user can enter commands and information into the computer 1002 via one or more wired/wireless input devices (eg, keyboard 1038 and pointing devices, such as the mouse 1040). Other input devices may include a microphone, infrared (IR) remote control, joystick, game pad, stylus, touch screen or the like. These and other input devices are typically coupled to the system bus The input device interface 1042 of 1008 is coupled to the processing unit 1004, but may be connected by other interfaces such as parallel port, IEEE 1394 serial port, game port, USB port, IR interface, and the like.

A monitor 1044 or other type of display device is also coupled to system bus 1008 via an interface, such as video adapter 1046. In addition to the monitor 1044, the computer typically includes other peripheral output devices such as speakers, printers, and the like.

The computer 1002 can operate in a network environment using logical connections via wired/wireless communication with one or more remote computers, such as the remote computer 1048. The remote computer 1048 can be a workbench, a server computer, a router, a personal computer, a portable computer, a microprocessor based entertainment facility, a peer device, or other common network node, and the remote computer 1048 typically includes a computer 1002 relative to the computer While many or all of the elements are described, for the sake of brevity, only the memory/storage device 1050 will be described. The depicted logical connections include wired/wireless connectivity of a local area network (LAN) 1052 and/or a larger network (e.g., wide area network (WAN) 1054). This LAN and WAN connectivity environment is common in offices and companies, and promotes enterprise-wide computer networks, such as corporate intranets, all of which can be connected to global communication networks, such as the Internet. .

When used in a LAN network connection environment, computer 1002 is coupled to LAN 1052 via a wired and/or wireless communication network interface or adapter 1056. The adapter 1056 can facilitate wired and/or wireless communication with the LAN 1052, and the LAN 1052 can also include a wireless access point disposed on the LAN 1052 for wireless functional communication with the adapter 1056.

When used in a WAN network connection environment, the computer 1002 can include a data machine 1058, or a communication server connected to the WAN 1054, or have other communications for establishing communications via the WAN 1054 (such as via the Internet). member. The data machine 1058 can be internal or external and can be wired and/or wireless connected to the system bus 1008 via the input device interface 1042. In a networked environment, portions of the program modules or program modules depicted relative to computer 1002 may be stored in remote memory/storage device 1050. It should be appreciated that the network connections shown are exemplary and other ways of establishing a communication link between computers may be used.

The computer 1002 is operable to use a family of IEEE 802 standards to enable wired and wireless devices or entities such as wireless devices operatively disposed in wireless communications (eg, IEEE 802.11 wireless modulation technology) with, for example, printers, scanners , desktop and/or portable computers, personal digital assistants (PDAs), communications satellites, any devices or locations associated with wirelessly detectable tags (eg, kiosks, newsstands, restrooms) and telephones )communication. This includes at least Wi-Fi (also known as Wireless Fidelity), WiMax, and Bluetooth ^TM wireless technology. Thus, the communication can be a predefined structure as in the conventional network or only a special communication between at least two devices. Wi-Fi networks use a radio technology called IEEE 802.11x (a, b, g, etc.) to provide a secure, reliable, and fast wireless connection. Wi-Fi networks can be used to connect several computers to each other, to the Internet, and to wired networks (wired networks use IEEE 802.3-related media and features).

Hardware components, software components, or a combination of both can be used to implement each Example. Examples of hardware components may include devices, logic devices, components, processors, microprocessors, circuits, circuit components (eg, transistors, resistors, capacitors, inductors, etc.), integrated circuits, special application complexes ASIC, Programmable Logic Device (PLD), Digital Signal Processor (DSP), Field Programmable Gate Array (FPGA), Memory Unit, Logic Gate, Scratchpad, Semiconductor Device, Wafer, Microchip , chipset, and more. Examples of software components may include software components, programs, applications, computer programs, applications, system programs, machine programs, operating system software, intermediate software, firmware, software modules, routines, subroutines, functions, Method, program, software interface, application interface (API), instruction set, calculation code, computer code, code segment, computer code segment, block, value, symbol, or any combination of the above. The need to determine whether an embodiment uses hardware components and/or software components to implement a given implementation requires a change in any number of factors, such as desired rate, power level, heat resistance, processing cycle budget, input data. Rate, output data rate, memory resources, data bus speed, and other design or performance limitations.

Some embodiments may comprise an article of manufacture. The article of manufacture can include a storage medium to store logic. Examples of storage media may include one or more types of computer readable storage media capable of storing electronic data, including one or more types of computer readable storage media including volatile memory or non-volatile memory, removable Or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and more. Examples of logic may include various software components, such as software components, programs, applications, computer programs, Applications, system programs, machine programs, operating system software, intermediate software, firmware, software modules, routines, subroutines, functions, methods, programs, software interfaces, application interfaces (APIs), instruction sets, Calculate code, computer code, code segments, computer code segments, blocks, values, symbols, or any combination of the above. In one embodiment, for example, an article of manufacture can store executable computer program instructions that, when executed by a computer, cause the computer to perform the methods and/or operations in accordance with the described embodiments. The executable computer program instructions can include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The executable computer program instructions can be implemented in accordance with a predefined computer language, manner or syntax to instruct the computer to perform a particular function. The instructions can be implemented using any suitable high-order, low-order, object-oriented, visual, compiled, and/or interpreted programming language.

Some embodiments may be described using the expression "one embodiment" or "an embodiment" along with the derivatives of the embodiments. These terms are intended to be inclusive of the specific features, structures, or characteristics described in connection with the embodiments. The appearances of the phrase "in an embodiment"

Some embodiments may be described using the expression "coupled" and "connected" along with the derivatives of the expression. These terms are not necessarily intended as synonyms for each other. For example, some embodiments may be described using the terms "coupled" and/or "connected" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" can also mean two or Two or more elements are not in direct contact with each other, but still operate together or interact with each other.

It is important to emphasize that the Abstract of Invention is provided to comply with 37 C.F.R. Section 1.72(b), which requires an abstract that allows the reader to quickly determine the nature of the technical content. It is submitted that the abstract is not intended to limit or limit the scope or meaning of the scope of the patent application. In addition, in the above embodiments, it can be seen that various features are grouped together in a single embodiment to simplify the invention. This method of disclosure should not be interpreted as reflecting the following intent: the claimed embodiments require more features than those specifically recited in each technical solution. As a matter of fact, as reflected in the scope of the following claims, the invention is characterized by fewer features than all features of a single disclosed embodiment. Therefore, the scope of the following patent application is hereby incorporated by reference in its entirety in its entirety in its entirety in its entirety in each of the the the the the the In the scope of the appended claims, the terms "including" and "in which" are used as the ordinary equivalents of the respective terms "including" and "wherein". In addition, the terms "first", "second", "third", etc. are used merely as labels, and are not intended to impose numerical requirements on the items of the terms.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is understood that the subject matter defined in the appended claims The specific features and acts described above are disclosed in the form of examples of the scope of the claims.

100‧‧‧Montage System

102-b‧‧‧ control indicators

104-1‧‧‧Content files

104-2‧‧‧Content files

104-3‧‧‧Content files

104-c‧‧‧Content files

106-1‧‧‧Contents section

106-2‧‧‧Contents section

106-3‧‧‧Contents section

106-d‧‧‧Content section

110‧‧‧Production components

120‧‧‧Montage

122‧‧‧present surface

124-1‧‧‧ Presentation block

124-2‧‧‧ Presentation block

124-3‧‧‧ Presentation block

124-4‧‧‧ Presentation block

124-a‧‧‧ Presentation block

126-1‧‧‧Display block objects

126-2‧‧‧Display square objects

126-3‧‧‧Display square objects

126-e‧‧‧Display square objects

130‧‧‧presenting components

132-f‧‧‧ control indicators

140‧‧‧Montage app

202-1‧‧‧ Type Module

202-2‧‧‧Type Module

202-3‧‧‧ Type Module

202-g‧‧‧ type module

204-1‧‧‧Type definition

204-2‧‧‧Type definition

204-3‧‧‧Type definition

204-h‧‧‧Type definition

210‧‧‧Local data storage area

212‧‧‧Remote data storage area

300‧‧‧User interface view

302‧‧‧GUI input tool

302-1‧‧‧Copy Order

302-2‧‧‧ Cut the order

302-3‧‧‧Paste the order

304‧‧‧File Navigation Tools

308‧‧‧ indicator device

310‧‧‧ gesture

320‧‧‧User interface view

340‧‧‧User interface view

342-1‧‧‧Display block object container

342-2‧‧‧Display block object container

342-3‧‧‧Display block object container

342-u‧‧‧Display block object container

344-1‧‧‧Content part editing

344-2‧‧‧Content part editing

344-3‧‧‧Content part editing

344-v‧‧‧Content section editing

346‧‧‧Display square object surface

348-1‧‧‧filled container

402‧‧‧ heading

404‧‧‧ paragraph

406‧‧‧ paragraph

408‧‧‧ yuan data

410‧‧‧ images

412‧‧‧ bar chart

414‧‧‧ equation

500‧‧‧Communication system

502‧‧‧ processor

504‧‧‧ memory

509‧‧‧Communication interface

510-1‧‧‧ Computing Devices

510-2‧‧‧ Computing device

512-1‧‧‧Transfer tool

512-2‧‧‧Transfer tool

516‧‧‧Information

518-1‧‧‧Embedded links

518-k‧‧‧Embedded links

518-n‧‧‧Embedded links

530‧‧‧Network

532‧‧‧release component

534‧‧‧Message component

536‧‧‧Security components

538‧‧‧User interface

540‧‧‧Message Server

542-1‧‧‧Communication application

542-2‧‧‧Communication application

550‧‧‧Network storage server

602‧‧‧ arrow

604‧‧‧ arrow

606‧‧‧ arrow

608‧‧‧ arrow

610‧‧‧ arrow

612‧‧‧ arrow

620‧‧‧ message content

652‧‧‧Internet service

700‧‧‧User interface view

702‧‧‧ functional area column

704‧‧‧ address list

706‧‧‧Message text

710‧‧‧ indicator device

712‧‧‧ gesture

720‧‧‧ Montage thumbnail

730‧‧ Montage Viewer

740‧‧‧User interface view

750‧‧‧User interface view

760‧‧‧User interface view

800‧‧‧Logical process

802‧‧‧ block

804‧‧‧ Block

806‧‧‧ Block

808‧‧‧ Block

810‧‧‧ Block

812‧‧‧ Block

820‧‧‧Logical process

822‧‧‧ Block

824‧‧‧ Block

826‧‧‧ Block

828‧‧‧ Block

900‧‧‧Logical flow

902‧‧‧ Block

904‧‧‧ Block

906‧‧‧ Block

908‧‧‧ Block

1000‧‧‧Computational Architecture

1002‧‧‧ computer

1004‧‧‧Processing unit

1006‧‧‧System Memory

1008‧‧‧System Bus

1010‧‧‧ Non-volatile memory

1012‧‧‧ volatile memory

1014‧‧‧ internal hard drive

1016‧‧‧ magnetic floppy disk player

1018‧‧‧Removable Disk

1020‧‧‧CD player

1022‧‧‧Removable CD

1024‧‧‧HDD interface

1026‧‧‧FDD interface

1028‧‧‧CD player interface

1030‧‧‧Operating system

1032‧‧‧Application

1034‧‧‧Other program modules

1036‧‧‧Program data

1038‧‧‧ keyboard

1040‧‧‧ Mouse

1042‧‧‧Input device interface

1044‧‧‧Monitor

1046‧‧•Video adapter

1048‧‧‧ Remote computer

1050‧‧‧Memory/storage device

1052‧‧‧Local Network (LAN)

1054‧‧‧ Wide Area Network (WAN)

1056‧‧‧ Adapter

1058‧‧‧Data machine

Figure 1 illustrates an embodiment of a montage system.

Figure 2 illustrates an embodiment of a fabrication assembly.

Figure 3A illustrates an embodiment of presenting a surface.

Figure 3B illustrates an embodiment with a presentation surface for displaying a tile object.

Figure 3C illustrates an embodiment of a display block object having a display object container.

Figure 4 illustrates an example of a fabrication component.

Figure 5 illustrates an embodiment of a messaging system.

Figure 6 illustrates an embodiment of a message flow for a messaging system.

Figure 7A illustrates an embodiment of a user interface view of a message.

Figure 7B illustrates an embodiment of a montage user interface view.

Figure 7C illustrates an embodiment of a user interface view showing a block object.

Figure 7D illustrates an embodiment of a user interface view of a content file.

Figure 8A illustrates an embodiment of a logic flow for fabricating a component to generate a montage.

Figure 8B illustrates an embodiment of a logic flow for a production component to produce a display block object for montage.

Figure 9 illustrates an embodiment of a logic flow for a publishing component.

Figure 10 illustrates an embodiment of a computing architecture.

100‧‧‧Montage System

102-b‧‧‧ control indicators

104-1‧‧‧Content files

104-2‧‧‧Content files

104-3‧‧‧Content files

104-c‧‧‧Content files

106-1‧‧‧Contents section

106-2‧‧‧Contents section

106-3‧‧‧Contents section

106-d‧‧‧Content section

110‧‧‧Production components

120‧‧‧Montage

122‧‧‧present surface

124-1‧‧‧ Presentation block

124-2‧‧‧ Presentation block

124-3‧‧‧ Presentation block

124-a‧‧‧ Presentation block

126-1‧‧‧Display block objects

126-2‧‧‧Display square objects

126-3‧‧‧Display square objects

126-e‧‧‧Display square objects

130‧‧‧presenting components

132-f‧‧‧ control indicators

140‧‧‧Montage Application formula

Claims (17)

A computer implemented method, the method comprising the steps of: receiving a control indicator to associate a content file with a presentation display block of a digital montage presentation surface; identifying a content file type of the content archive Extracting a content portion of the content file based on the content file type; selecting a content partial clip from the content portion of the content file based on the content file type; generating a display square object based on the content portion for displaying the display block, The display block object includes a corresponding display block object container; determining that information from the content portion is too large for a current dimension of the display block object container of the display block object; determining whether a dimension of the display block object container can be increased And increasing the dimension of the display block object container to accommodate the information of the content portion. The computer-implemented method of claim 1, the method comprising the steps of: generating the display block object as a display block object surface, the display block object surface having the selected content portion clip included in the corresponding display block object container . The computer implementation method of claim 1, the method comprising the steps of: identifying the content file type of the content file as an application file Type, the application file type includes a word processing file, a spreadsheet file, a presentation file, a person information management program file, a database file, a publisher file, a graphic file, a note file or a message file. The computer-implemented method of claim 1, the method comprising the steps of: selecting a content partial clip from the content portion of the content archive based on a type definition associated with the content archive type, the type definition including a content And information about a feature category, a content object category, or a content page category. The computer-implemented method of claim 1, the method comprising the step of associating the selected portion of the clip with a corresponding display tile object container on a surface of the display tile object. The computer-implemented method of claim 1, the method comprising the steps of: receiving a control indicator from an input device to select the content portion clip from the content portion of the content file. The computer-implemented method of claim 1, the method comprising the step of receiving a control indicator from an input device to associate the content portion clip from the content portion of the content archive with a corresponding display tile object container. The computer-implemented method of claim 1, the method comprising the steps of: fitting the content in the corresponding display block object container according to a container definition and a fitting algorithm for one of the corresponding display block object containers; Partial editing to form a filled container. The computer-implemented method of claim 1, the method comprising the steps of: fitting a filled container within a surface of the display block object according to a set of surface definitions for the surface of the display block object and a fitting algorithm. An article comprising a storage medium, the storage medium containing instructions that, when executed, enable a system to: receive a control indicator to cause a content file to be rendered on a surface of one of a digital montage Presenting a display block associated with; identifying a content file type of the content file; selecting content from the content file based on the content file type; generating, for the content display file, the content from the content file based on the content file type Displaying a block object, the display block object comprising a corresponding display block object container; determining that information from the content file is too large for a current dimension of the display block object container of the display block object; determining the display block object container Whether a dimension can be increased; and increasing the dimension of the display tile object container to accommodate the information of the content file. The article of claim 10, the article further comprising instructions that, when executed, cause the system to generate the display block object as a display block object surface, the display block object surface having a respective display block The selected content within the object container. The article of claim 10, the article further comprising instructions that, when executed, enable the system to fit from a set of container definitions and a fit algorithm for the respective display block object containers The content of the content file within the individual tile object container is displayed to form a filled container. The article of claim 10, the article further comprising instructions that, when executed, cause the system to fit a display according to a set of surface definitions for the surface of the display block object and a fitting algorithm A filled container within the surface of the square object. A device comprising: a logic device configured to execute a montage application, the montage application comprising operations to generate a component for displaying one of a digital montage display block object, The production component is configured to receive a control indicator to associate a content file with a presentation display block of one of the digital montage presentation surfaces, to identify a content file type of the content file, based on one of the content file types for the content file The type definition retrieves information from the content file, and is used according to the content file type. Generating the display block object from the information of the content file, determining that the information from the content file is too large for a current dimension of a display block object container of the display block object, and increasing the dimension of the display block object container, To accommodate this information in the content file. The device of claim 14, the fabrication component operative to generate the display tile object as a display tile object surface, the display tile object surface having the content file from the one or more display tile object containers Selected information. The device of claim 14, the authoring component operative to select the information from the content file for a display tile object container based on a type definition for a type module corresponding to the content file type, and based on the The selected information produces the display block object. The apparatus of claim 14, wherein the production component that performs a fitting algorithm is configured to fit from one or more of the container definitions for the corresponding display object container and the fitting algorithm Displaying the information of the content file in the block object container.