Auxiliary display mini-application for distributed content

FIELD: information technology.

SUBSTANCE: invention describes a technology through which a specific mini-application program is installed (e.g. created) in a main computer system which receives data (e.g. RSS-channel) from a distribution source, wherein channel data contain information needed for installing the mini-application. After installation, the mini-application is used to receive content from its corresponding data source and provide content for displaying on an auxiliary display. The channel data may include metadata, such as an attachment associated with the mini-application, from which the installer can record information corresponding to the metadata into a register or similar, and associate the mini-application with one or more specific auxiliary displays. By processing these metadata, another application is installed and then run if needed, so as to process content data from the corresponding data source in order to display the content on the auxiliary display.

EFFECT: broader functionalities owing to the possibility of loading into a computing platform and installing mini-applications.

20 cl, 6 dwg

The level of technology

In modern computer systems (for example, on Windows® Vista^TMusers can view and generally interact with the selected content on a small auxiliary display device, which is connected to the main computer system or integrated into it. For this purpose, the auxiliary screen display together with provided by the operating system platform (referred to as the platform auxiliary display, or Windows^®SideShow^TMprovide an opportunity for the developers and authors to present content to users. This allows the user to view the contents even when the main computer system is in low power mode (e.g., in sleep mode ACPI S3) or even when it is disabled.

To provide data to display platform auxiliary display uses a mini-application that contains a small computer program plug-in type (plug-in), which are executed on the main computer system and which receive and process content from other application programs or data source. In most scenarios, these mini-applications are preinstalled own programs, which limit provided by the mini-application contents only what is available on the personal computer of the user.

The invention

The category of "invention" is shown to represent in a simplified form sample illustrative of the concepts that are described in detail below in the section "Detailed description". The category of "invention" is not intended neither to identify key or essential distinguishing features of the essence of the claims, nor for use in any way in determining the amount of substance of the claims.

Briefly, various aspects described herein of the invention dedicated to the main computer system, which is connected with one or more auxiliary display devices and which includes a component that processes data, which take from a source, such as an RSS feed. Said data includes metadata that correspond to information for processing content associated with the data source. Metadata is used to provide the possibility of mini-application to handle content that includes providing at least part of the content (for example, in a suitable auxiliary device format within platform auxiliary display. Activate the widget includes the installation of the widget (if necessary),for example, by recording information corresponding to the metadata in the system register, and loading and executing the widget.

When the widget receives the data and processes associated metadata, if necessary, can be installed more mini-application that can process the content associated with the accepted data, the latter is to receive content from a data source corresponding to another gadget. Then another gadget displays data that represents at least part of the content for consumption by the auxiliary device of the display, which may include converting content from one format to another format suitable for consumption. Widget RSS can also create a virtual widget so that the widget RSS takes the content from the source, but displays it in the form of a single, "virtual", gadget, then there is a second mini-application does not handle its own subscription data.

Aspects of the object of the present invention can be implemented in a system such as system platform (for example, RSS-platform), which adopts distributed data sources data dissemination. Mini-distribution application (e.g., RSS), is connected to the second platform, processes data to be distributed, and, if necessary, the installer mechanism associated with the gadget distribution can install a special mini-application, based on the particular requirements for a specific data source, which is provided associated with the gadget information. New installed special gadget provides content received from a particular data source, platform auxiliary display.

Other advantages will be apparent from the following detailed description and the accompanying drawings.

Brief description of drawings

The present invention is illustrated in the example on the accompanying drawings, in which similar reference numbers indicate similar elements and in which:

figure 1 - illustrative example of a computing environment General purpose, which can be embedded in various aspects of the present invention;

2 is a block diagram illustrating examples of components for processing RSS feed via mini-applications that are created from the metadata channel;

figure 3 is a structural diagram generally illustrating an example implementation, through which the RSS data is provided in the auxiliary device display;

figure 4 - illustration of the widget, created or loaded, which implement aetsa, to process the contents of the RSS feed;

5 is a diagram of a sequence of operations illustrating example steps for processing RSS data, in order to allow the widget to process the RSS content from an RSS source.

6 is a diagram of a sequence of operations illustrating examples of phases gadget, after it is activated to process the RSS content from an RSS source.

Detailed description

Example desktop environment

Figure 1 illustrates an example of a suitable computing environment 100 system, which can be accomplished the present invention. Computing environment 100 system is just one example of a suitable computing environment and is not intended to define the limits of the scope of use or functionality of the present invention. In addition, the computing environment 100 should not be interpreted as having a dependency or requirement relating to any component or combination of components illustrated in the example operating environment 100.

The invention can be implemented with many other environments or configurations of the computing system General purpose or special purpose. Examples of well known computing systems, environments the s and/or configurations, which can be suitable for use with the present invention, include, but are not limited to: personal computers, server computers, handheld or laptop devices, tablet devices, multiprocessor system, a microprocessor, set-top boxes, programmable consumer electronics, network personal computers, mini-computers, mainframe computers, distributed computing environments that include any of the above systems or devices, and so on

The present invention may be described in the General context for executing computer commands, such as program modules, executed by the computer. In General, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The present invention may be implemented in distributed computing environments where tasks are performed by remote processing devices that are linked via the communications network. In a distributed computing environment, program modules may be located in the storage medium of the local computer and the storage environment of the remote computer, including the memory device.

The computer 110 typically includes a number of machine-readable media. Machine-readable media can be any available means to which the computer 110 may access, and they include both volatile and nonvolatile media, removable and non-removable media. As an example, but not limitation, computer-readable nose is teli may include computer storage media and communication media. Computer storage media includes volatile, nonvolatile, removable and non-removable tool implemented by any method or technology for storage of information such as machine-readable commands, data structures, program modules and other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage media, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tool that can be used to store the desired information and which can be accessed by computer 110. The means of communication normally includes machine-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any means of information delivery. The term "modulated data signal" means a signal which has one or more characteristics set or changed in such a way as to encode the signal information. As an example, but not limited to, the means of communication includes himself conductive medium, such as a wired network or direct-wired connection, and wireless means, such as acoustic, RF, infrared and other wireless tools. Combinations of any of the above types are also included in the scope of the machine-readable medium.

The system memory 130 includes computer storage medium in the form of volatile and/or nonvolatile memory, such as ROM, RAM 131 and 132. Basic system 133 input/output (BIOS), containing basic routines that help to transfer information between elements within computer 110, such as during startup, typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or involved the processor unit 120. As an example, but not limited to, figure 1 illustrates operating system 134, application programs 135, other program modules 136, and program data 137.

The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage medium. Solely as an example, figure 1 illustrates the drive 141 on the hard disk drive that reads from or writes to non-removable, nonvolatile magnetic media, a hard drive 151 on a magnetic disk, which sityva the t from or writes to a removable, nonvolatile magnetic disk 152, and a memory 155 of the optical disk drive that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD-ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the example operating environment include, but are not limited to, tapes, magnetic tape, flash memory, digital versatile disks, digital video tape, solid state RAM, solid state ROM, etc. Drive 141 on the hard disk, typically connected to the system bus 121 via an interface of the non-removable memory, such as interface 140, and the drive 151 on the magnetic disk and the drive 155 on an optical disc, as a rule, is connected with the system bus 121 through interface, a removable memory, such as interface 150.

The drives and their associated computer storage media discussed above and illustrated in figure 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer 110. In figure 1, for example, the drive 141 on the hard disk is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data 147. It should mark the mounting, these components can be the same as the operating system 134, application programs 135, other program modules 136, and program data 137, or different from them. Operating system 144, application programs 145, other program modules 146, and program data 147 are indicated by different numbers here to illustrate that at least they are different copies. The user can enter commands and information into the computer 110 through input devices such as a tablet or digitizer 164, microphone 163, keyboard 162 and pointing device 161, such as a mouse, trackball or touch pad. Other input devices that are not shown in figure 1, may include a joystick, game pad, satellite dish, scanner, or the like, These and other input devices are often connected to the processor unit 120 via the interface 160 of the input devices of the user, which is connected to the system bus, but they can also be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to system bus 121 via an interface, such as a video interface 190. The monitor 191 can also be integrated with a touch panel, etc. it Should be noted that m is the monitor and/or the touch panel can be physically connected to the housing, hosting computing device 110, such as a personal computer, a tablet type. In addition, the computers, such as computing device 110 may also include other peripheral output devices such as speakers 195 and printer 196, which may be connected through the interface 194 peripheral output devices, etc.

The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and it typically includes many or all of the elements described above relative to the computer 110, although figure 1 illustrates only the device 181 memory. The logical connections depicted in figure 1, include LAN (Local Area Network, LAN) 171 and a wide area network (Wide Area Network, WAN) 173, but may also include other networks. Such network environments typical for offices, computer networks enterprise-scale intranet and Internet.

When used in a network environment LAN computer 110 connected to the LAN 171 through a network interface or adapter 170. In the line who communicate in a network environment the global network computer 110, typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, can be connected to the system bus 121 via an interface 160 user input or other suitable mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof may be stored in a remote memory device. As an example, but not limited to, figure 1 illustrates remote application programs 185 as residing on the device 181 memory. Obviously, illustrated network connections are only examples and can be used with other means for establishing lines of communication between computers.

Subsystem 199 auxiliary display can be connected via the interface 160 of the user to provide the user content program, system status and event notifications, even if the main part of the computer system are in a low power mode. Subsystem 199 auxiliary display can be connected to the modem 172 and/or network interface 170 to provide the ability to link these systems, when the main processing unit 120 is in the low power mode.

Various aspects of the technology described here is aimed at the acquisition and processing of content that should be displayed on the sub-display device, which is connected with the main computer system. In General, a large part of the description refers to a specific example implementation in which content is received from a remote data source by using the technology of real simple syndication (Really Simple Syndication, RSS), which refers to the web syndication/distribution of content using one or more XML-based formats. RSS, typically used by news sites and web logs (blogs) to distribute their content, however this technology can also be used for other purposes, including marketing, error reports, or any other activity, including a periodic update or publication.

RSS allows users to subscribe (often free) to the RSS feeds of websites, which, as a rule, frequently changing content. In General, each site provides data for distribution on request, and the data includes content along with some metadata, which often include links to other with Argive. These data are delivered to subscribers in the form of an XML file, which is herein referred to as RSS data or RSS feed, but in a different context, an alternative may be termed a web feed, RSS stream, or RSS feed (feed). RSS data may include an attached multimedia files, is represented.

However, it is obvious that the described technology is not limited to any particular data source and/or data format, or even the RSS and it can be used from both local and remote data. Moreover, the technology described here is not limited to any specific types of assistive devices, but instead it includes devices that are not normally regarded as related to "computer system" devices, such as televisions, audio receivers, audio/video recorders, telephones, certain computers, mobile communication device, the secondary screen display with actuators, wrist watch, wall displays (e.g., kitchen), digital screens, digital photo frames, wall or table clock, a radio, a media player, a device embedded in or using the main display device consumer electronics, automotive, transport or other means of transportation, keyboard, or other input device g is avnoj computer system, pager, personal digital secretaries, etc. essentially, the present invention is not limited to the examples described here, the structures or functions. Rather, all of the described examples, structure and function are non-limiting, and the present invention may be used various ways that provide benefits and advantages in computing and processing the contents as a whole.

Figure 2 shows an example of a structural diagram that includes various components, through which the main computer system 210 (such as a system based on computer 110 figure 1) receives data from an RSS source 212, for example, via the Internet 214. It should be noted that alternative data can be obtained through some other means, such as a LAN or WAN or even a local data source, as for example, when loading in file/cache/buffer.

As described below, data from an RSS source 212 are accepted in the widget (gadget) 216 RSS feed. In General, the widget 216 contains software code running on the main computer system, which is registered in the platform of the auxiliary display to transmit data to one or more auxiliary devices of the display. Moreover, the gadget is activated or deactivated from the control panel.

Mini-applications is of 216 processes the received data for the consumption of content (usually by displaying on the screen) auxiliary device 220. As described below, this processing includes processing metadata 222, associated RSS feed. For this purpose gadget 216 RSS includes mechanism 230 handler metadata or in any way connected with the latter. Processing may also include the conversion (which is represented by the Converter 232 RSS/accessory RSS content 224 into a format that can be processed by the device 220 auxiliary display (for example, part of the subsystem 199 auxiliary display figure 1). One such format is a simple format content (Simple Content Format), containing the basic data format that should be able to display sub-display device and which includes a markup for the data transfer menu, image and notifications.

To facilitate reception of a content source 212 RSS data provides metadata 222 information about the content 224. In particular, instead of a dedicated widget on the main computer system designed to process its content, the processor 230 metadata gadget 216 RSS will process the data for different sources and to differentiate these data based on the metadata. As a result, this technology allows placement is the IKI content effectively to syndicate content designed for the secondary monitor, wide, a potentially unlimited number of users through a network, without the need for special proprietary software on each device of the recipient.

In particular, in the special case of distribution/control data instead of just content delivery, content providers can use RSS feeds to distribute special auxiliary data display and to create new gadgets. For example, when a user subscribes to an RSS feed with these special auxiliary data display, the gadget 216 RSS can use this data to create a new separate gadget auxiliary display, such as "mini" Appendix A 240 with figure 2. After you create a new widget 240 gadget RSS acts as a "host" mini-application to operate a new, "virtual", gadget, as well as to manage the data for a device coming from a subscribed RSS feed (in particular, the widget RSS performs data management, meanwhile, looks like a separate mini-application). It should be noted that although figure 2 is not explicitly shown, the widget may, alternatively, to accept and/or to convert the received RSS content in a format that is compatible with the auxiliary have is trojstva, such as a simple content format. Thus, the widget 216 controls, convert and distribute the RSS content from a source to (or through) the main computer system of the user, and the device or devices auxiliary display.

In one example implementation, when the RSS data for the first time is downloaded from the website, such as source 212 corresponding to the metadata 212 information is recorded in the system register 222 main computer system (it is assumed that the user and/or current policy allows it). It should be noted that the metadata corresponding to information which is already recorded in the register 234, do not want to overwrite in the future. Instead, existing in the register 234 information can be used to determine how to handle the associated RSS content 224 regarding display of the content of the auxiliary device. Then some form of content 224 may be provided (e.g., created through the widget 240) in the device 220 of the auxiliary display. As a result, from the perspective of the user to perform the detection and installation of the new gadget is as simple as subscribing to the RSS feed.

For completeness, figure 2 also shows other gadgets, for example "widget B" 241, is the quiet can be used by the platform auxiliary display. It should be noted that mini-Appendix B 241 works with program 242 sidebar (Sidebar) or related API 243, respectively. Mini Appendix B 241 uses the API 243 sidebar to communicate through the API 246 driver 248 for assistive devices.

For completeness, figure 2 also shows that in a given system 210 can be one or more other drivers 249 and auxiliary device 250. Despite the fact that other drivers 250 shown in dotted block to reflect the possibility of their presence, it should be noted that the presence of an auxiliary device 220 is also not necessary, because the user may have only one other auxiliary device 250, for example, by the driver from a third party. Examples of one such device is illustrated in the form of assistive devices 220 and/or the dotted block 250 includes a display with advanced features, which usually contains the sub-display device that is running firmware SPOT (Smart Personal Object Technology) and advanced code display normal display, which essentially is a device supporting display running specialized hardware and software which is able to operate the AK auxiliary display, for example, a mobile phone, a display with one (two, three, etc) strings containing secondary display, which can display only a limited number (e.g. one or two) lines of text and in which there is no support for graphics. Other types of displays include attached displays/side displays/displays on the cover, which usually belong to the sub-display device, which is physically located on the notebook or the like, for example on the cover; remote displays containing secondary display, which is physically located outside the main computer and provides contact with him through a wired or wireless network Protocol; and "virtual" secondary display, which is usually the auxiliary content in a certain area of the main display of the computer system. Accordingly, although the auxiliary device 220 and 259 are shown in figure 2 as an external device that is connected to the main computer system 210 (possibly selectively connected), it should be understood that such devices may be physically attached to the main computer system 210 or have any other possibility to detach from it.

It should be noted that a large part of the RSS content is a HTML text. However, the mill is art RSS 2.0 provides the opportunity to implement other data such as multimediadrive through labels <attachment>and <attachment> contains an optional sub-element of <item>. Types of feed attachments are defined with standard MIME types. For example, one variant of implementation of the platform auxiliary display supports images using a simple format content on displays with advanced features, for example, in jpg, gif and bmp. For scenarios with enhanced media data may be provided to the possibility of using, for example, mpeg/wma audio and wmv/avi/mpeg for video.

For related RSS markup <attachment> has a number of attributes such as URL, which specifies where the attachment length, which specifies the size (e.g., in bytes), and a type that indicates its type, for example a standard MIME type. The URL can be an http address, for example: <enclosure url="http://www.scripting.com/mp3s/weatherReportSuite.mp3" length="12216320" type="audio/mpeg"/>.

Widget RSS may request the RSS platform to download the attachment if it has a recognizable type. After downloading the attachments widget directly receives a file from the RSS platform. Alternatively, widget, RSS can download the attachment itself by using the URL attribute in the markup attachments.

Because the types of content RSS there are no barriers is s, content providers and sellers of the software get the chance to distribute in device supporting display of users on virtually any type of data, such as stock quotes and music over the network. Can also be delivered "enriched" multimedia data, which provides the possibility of application scenarios such as wireless digital picture frame that automatically loads images from blogs, to which you are subscribed, or a media player that automatically downloads your favorite podcasts user and new items, or other scripts.

Other examples of scenarios aimed at consumption (read) the blog/RSS creation (logging) blog/RSS, digital photo frames, podcasts, installation of new mini-applications, using RSS and integration sidebar (sidebar), but is not limited to. For example, consider a single user that listens to the audio player, meanwhile performing calculations. In addition to music, the user can use your music player and other media devices to download podcasts, photos, and RSS feeds, when the audio player is connected to the main system. Then he can use the downloaded data, continuing to perform calculations. With the claim of RSS feeds, the device automatically selects the correct RSS feeds, subscribed to by the user, for example, he can subscribe to pictures of groups of friends and/or maybe short videos recorded with mobile phones and gadget RSS will automatically sync content when the device is connected to the docking station.

As for logging, mobile devices (e.g. smartphones) can have a small panel to read, and also to enter a finger. The above examples of consumption applicable, but in addition the user can optionally create content, for example, by removing photos, execution of blog posts and/or logging content through blog-mechanism of the user. Using RSS feed attachment, the user can create Vodokanal directly distributed in a certain group with a companion/explanatory text. For devices that do not have wireless capabilities, blog content can be cached for synchronization with the feed mechanism when connected to the docking station.

Digital photo frame can also receive content for which it has subscribed. For example, a digital picture frame for the auxiliary display may be connected to a personal computer wireless manner, and it can be downloaded automatically installed mini-PR is the situation of RSS, which captures pictures via RSS feeds, and the computer transmits the pictures to the photo frame. The photo frame can automatically display the latest pictures and cyclically to change them.

Podcasts are another script, which can be facilitated using RSS feed podcasts. To do this, the user can configure the podcast, which should be synchronized with the device, for example, by using the properties page of the subsidiary widget from the application control panel auxiliary display. When a user subscribes to this channel, auxiliary gadget gets embedded podcasts from RSS feed. Each time the device connects mini-syncs at him podcasts for later listening.

As mentioned above using RSS feed can be installed new gadget. For example, as described below with reference to figure 4, the site, such as zzzmovies.com can offer an RSS feed of information about the movies. When a user subscribes to an RSS feed, an auxiliary gadget 216 RSS detects that the website zzzmovies.com distributes special mini-application with information about the films, which provides an auxiliary display to display information about the movies from an RSS feed, including schedules, availability, beat the tov and reviews. Users do not need to separately download and install such a gadget, the gadget 216 RSS (or another object, such as an applet in the control panel) automatically installs a new gadget information about the movies, that is, as a rule, after requesting and/or other policy checks. The gadget 216 configures RSS widget film so that it operated only on supported devices, such as the gadget of the film will not be shown on one-line sub display, located on the keyboard, but it will be displayed on the screen of the mobile phone.

Thus, the widget 216 RSS allows users to consume and create content on a portable device in a variety of media formats, including audio (e.g. podcasts), pictures, text (e.g., blogs) and so, using the platform of the auxiliary display. As a result, users get the ability to view RSS feeds, which they signed, view photos/videos, and perform similar tasks through its auxiliary devices of the display. It should be noted that this can be implemented for offline RSS devices that consume/create the content, or by using existing portable devices, is aka as audio players, to consume multimediadrive.

Figure 3 shows a more specific example of implementation, where RSS-platform 350 provides RSS data in the gadget 216 RSS (auxiliary display). In one particular embodiment, the means of distribution (e.g., a browser, such as browser based on Internet Explorer) performs a setup operation that registers the platform RSS feed so that the application or the user didn't need to do it. Platform RSS feed can be implemented as one or more Win32 COM API, which are located in the dynamic link library, for example, msfeeds.dll.

RSS feeds can be arranged as a set of folders and feeds within a folder, for example, in the form in which you saved favorites browser. It should be noted that the order of folders and feeds, as a rule, is not supported in the system list of feeds, instead, in one example implementation (such as favorite folders and websites browser) operating system/component browser and RSS browser share a set of keys of the register to store the order of folders and feeds inside folders. The gadget 216 RSS reads these registry keys for the order of folders and feeds. An example of a key register for storing the order of the subscriptions in the system list of feeds has the following VI is: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerMenuOrderFeeds.

It should be noted that the user may have a variety of assistive devices, and, accordingly, may require specific web channel has been mapped to a specific device. For example, due to certain limitations of the device, the web channels that can be supported by this device, can represent only a subset of the total number of signed user feeds, for example, some devices are capable of supporting simple content format can have form factors that worsen the perception of the user when attempting to display RSS feeds, and users should have the ability to disable the feeds for these devices. Moreover, based on considerations of convenience, users may not want to use all the feeds on the same device, because users can have a number of feeds, which is in the hundreds. In addition, for specific types of media, such as photo, users can only choose consumption of feeds from specific sources.

To allow users to associate specific feeds with specific assistive devices, as shown in figure 3, can be created table 352 conformity feeds/devices (web channels:device)or similar structure. To create the structure 352 compliance feed/device, for example, through page properties applet 354 control panel auxiliary device, in one embodiment, the platform includes a new property, for example AUX_CAPABILITY_DEVICE_NAME, to determine the capabilities of each device. Adding the prefix device_name, did can be specified following device features:

The gadget 216 RSS can use the interface ISideShowCapabilitiesCollection to enumerate the subset is connected in the current time of assistive devices on the user's system. When the widget queries the properties of each device, the widget may get friendly name for the device (from the above identity, device_name, did) and display a table or the like that allows the user to associate a particular web channels with a specific device (or devices), in the example, in the application user interface 354 control panel.

For example:

interface ISideShowCapabilitiesCollection: IUnknown

{

HRESULT GetCount(

[out] DWORD * out_pdwCount

);

HRESULT GetAt(

[in] DWORD in_pdwIndex,

[out] ISideShowCapabilities ** out_ppDevice

);

};

interface ISideShowCapabilities: IUnknown

{

HRESULT GetCapability(

[in] REFPROPERTYKEY in_keyCapability,

[in, out] PROFVARIANT * out_pValue

);

};

In General, the widget does the following:

1. Sets a Boolean *out_pfDifferentiateContent of IAuxiliaryDisplayContent::DifferentiateContent to TRUE;

2. When you call ISxdeShowContentManager::Add()to add new content, platform in response transmits a separate GetContent() from interface ISideShowContent for each device.

3. Next, for each call to GetContent() the widget uses the pointer IAuxiliaryDisplayCapabilities to poll the friendly name of each device. The result is a combination of device names with the saved mapping feeds/devices return only specific feeds, selected based devices.

The gadget 216 RSS may refuse to execute the query response ISideShowContent::GetContent()to return only specific feeds based devices. It should be noted that this callback as a mini-application calls iSideShowContentManager::Add, and the content administrator calls back the gadget on its interface ISideShowContent.

PEFC is the formation of associations in some way, for example, by default they are modified through the user interface of the control panel application, the widget 216 RSS saves the structure of the web channel/device (e.g., count) 352, so that the widget will later be able to access the repository 352 to determine what feeds you want to pass on what devices. For example, one user may wish to view/listen to all the music feeds on the device, music player, but to view the urgent work-related feeds on a cell phone. It should be noted that the gadget 216 RSS (or created virtual gadget can customize the content in a simple format the content for each device, to account for differences between the feeds. Because the user may at any time update each Association from the application 354 control panel auxiliary display, the gadget 216 RSS also updates its stored structure 352 accordingly.

The gadget 216 RSS by default, can be installed as part of the Manifesto of the auxiliary display. When the main computer system is not connected to any auxiliary display device, the widget may be deactivated, and there is no need to display in the application any control auxiliary display. In this embodiment, the widget 216 RSS is not necessary to add any user interface RSS-platform, because the configuration can be controlled through the user interface applet 354 control panel auxiliary display.

In one embodiment, for recording in the registry of the necessary information for a widget auxiliary display can be used the following basic structure.

a. RSS

i. FriendlyName = "Windows^®Feeds" (which corresponds to "feed" in Windows-based systems^®)

ii. OnlineOnly = DWORD: 0×0

iii. CacheAlgorithm = DWORD: 0×0

iv. Icon = Icon representing the widget RSS

v. Endpoints: for example, the end point of the simple content format or optional endpoint feed.

As described above, the widget 216 RSS is registered also in the supporting framework (for example, for communication with the API/components 246, 356 and 358), although it should be noted that the gadget 216 is not required to be installed on the main computer systems that do not have auxiliary displays, or on the main computer systems with operating systems that do not support auxiliary displays. The gadget 216 RSS can be installed by default and may be able to configure and change the device manufacturer or Tr is the article side.

It should be noted that when the first detection RSS-enabled device, the widget 216 RSS may display a dialog box or the like to instruct the user on how to use RSS for auxiliary devices, for example, by application 354 (applet) control panel auxiliary display. Also in regard to the behavior of the widget should be noted that the gadget can be configured to run when the user logs into the system, provided that you meet certain criteria, for example that the RSS platform is configured and running, which is valid only on a suitable unit of inventory, operating system, and that at the current time on the host computer installed one or more auxiliary display device with support for RSS. In one embodiment, the widget 216 RSS will not be permitted, when not satisfied all the above conditions.

After resolution, as a rule, the widget 216 RSS will default to run in the background, because RSS-platform operates continuously, if for some reason RSS/auxiliary platform is missing, the widget 216 RSS samozaparcia. The gadget 216 RSS can be notified about network connections, and, accordingly, the widget may stop p is the transfer of data in the absence of a connection of auxiliary devices.

Relative to the base interaction platform, gadget and device can be applied the following General structure (however, it should be understood that the use of the following order of operations is not required).

1. To use RSS-platform operating system

a. Download RSS-platform (e.g., DLL)

2. Distribute the signed user RSS feeds on assistive devices

a. To get the list of channels of the system (subscribed channels) from the API RSS feeds.

b. To register for these notifications (RSS notifications are recursive, respectively, subscription to the root folder will provide coverage of the entire range)

i. iFeedFolder.SubscriptionNotifications (new channels, add/delete/edit etc)

ii. IFeedFolder.FeedNotifications (add new items)

c. Monitoring of changes in the list of channels

i. To cache the state of the list of channels, synchronized with the device, so that it knew how to update the state of the channel on the device when they will return to the state line

ii. To update the application properties page in the control panel auxiliary display to reflect changes channel status

d. By default, the widget may distribute the feeds to all the RSS device

i. However, users have the possibility to configure to specific RSS here what Aly was distributed on specific assistive devices that is, to be able to make a decision on which device or devices should be directed to the specified web channel.

ii. Save and refresh the mapping channels/devices on the basis of insertion by the user of changes in the properties applet in the control panel auxiliary display.

iii. The above mapping is maintained for each individual user so that the user is associated with a set of devices.

e. To configure the synchronization mechanism RSS so that the last uploaded attachments automatically

(IFeed.DownloadEnclosuresAutomatically)

3. Allow assistive devices to RSS feeds subscribed to by users, displayed via RSS-platform

a. To convert the RSS content in a simple format content

i. Enter: RSS-data

ii. Conclusion: the data in a simple format content

b. Ignore the format and content that cannot be displayed in a particular auxiliary device, for example, due to certain limitations of this device. For example, this may occur when the feed contains special HTML (tables etc), which cannot be displayed.

c. MediaLounge

i. To obtain a special RSS-attachments (e.g., photos) RSS-platform and re-encapsulate the binary data into a format that can be the ü processed auxiliary device

ii. Mark tag specific MediaLounge (photo, video etc) in a simple format content, which require special handling on the device

iii. To transmit data (e.g. binary data) to the device

d. Based on the capabilities of assistive devices gadget determines whether or not to be directed to a specific web channel on the device. For example, if the device is a digital photo frame and there is a subscription to a particular blog, the widget will only display embedded pictures and associated text or other media will be ignored.

4. Many users

a. The feeds for the current active user are synchronized only with devices associated with that user. This prevents scenarios, when the first user sends feeds to the device of the second user (for example, the audio player), thereby erasing the stored feeds the second user as the first user registered in the system.

b. Fast user switching

i. Applies only if the device is associated with all registered users, such as a laptop.

ii. The data from the old user is removed from the device and the data of the active user are synchronized with your device.

iii. In the above-mentioned scenario, audio player, the audio player should only be associated with the second user, so that when the first user logs in (registered), the widget will recognize that the device is not the device of the first user, and does not erase the data of the audio player.

iv. The interaction of assistive devices

c. Navigation allows users to browse the web channels.

i. To preserve the order of folders and feeds shown in the component browser in order to maintain a uniform operating procedure user

ii. Show folders feeds

1. Users can enter and exit the folder

iii. To display the titles of the feeds in the folder

1. If possible, use the icons from the web channel

2. To celebrate the feed flag new updates

3. To display the number of unread items in the feed in parentheses at the end

iv. To display the items in the feed

d. After selecting the web channel

i. Text

1. Search

a. Show items associated with <title> and the first line <description>

b. To provide a context menu option to display all items or only unread items

c. Default: show only unread items

d. When selection of a particular item, open the item

2. Detail is the first

a. To fully display the contents of the element

b. To provide controls for navigating the text.

ii. If the item has attachments:

1. To determine the type of media, using the label MIME

2. View search

a. Assign elements with MediaLounge appropriate icons

3. Detailed view - to determine a suitable format for displaying attachments

a. Image

i. To display the appropriate metadata headers, etc.

ii. To scale the image according to the specifications of the device - size, resolution, color depth

iii. Provide navigation control to move to the next/previous image

b. Audio

i. To display an item with the icon audio

ii. To display the appropriate metadata - artist, duration, etc.

iii. To provide controls for audio playback (which must be integrated with software / hardware) - Fast forward/Rewind/Pause/Play

iv. Provide navigation control to move to the next/previous item

c. Video

i. To display an item with the icon video

ii. To display the appropriate metadata producer, etc.

iii. To provide controls for video playback (which must be integrated with p is ogramme-hardware) - Fast forward/Rewind/Pause/Play

iv. Provide navigation control to move to the next/previous item

e. After the opening of the element to update the read/unread status in the user interface.

5. Handling events from the device

a. ContentMissing (no content)

i. Mini-application queries the platform on the lack of content

ii. If the platform was removed the feed or item, the mini-application erases deleted content on the device, respectively.

b. DeviceAdded (device added)

i. To determine whether it is connected the device with the current user.

1. If not, prompt the user whether to activate the RSS on this device

ii. To update the device based on the modified data, if available

c. DeviceRemoved (device removed)

i. Nothing to do

To enable application scenarios where you play podcasts, music and video infrastructure 358 driver assistive devices may be interface directly with the embedded device to use its hardware and firmware. For the integration of assistive devices own device (for example, the script of the podcast) driver assistive devices can C pesawat content directly to the device memory and to access the functions of the firmware, which provides the ability to control playback.

From the point of view of the source provider, platform auxiliary display and widget RSS provide an opportunity for vendors of software or content publishers use RSS to distribute and install new gadgets. Moreover, it also increases the use of scripts SideShow gadgets, as content providers and sellers of software can deliver content SideShow devices from the network, in addition to content from a local personal computer. This may include the specification and registration of new MIME types, including MIME type for simple content format (e.g., Type of content: text/x-simple_content_format) and the MIME type for the auxiliary data of the installation (e.g., Type of content: application/widget).

To facilitate the way in which RSS objects can distribute new gadget, that is, via RSS feeds, objects are only required to publish RSS feeds with embedded metadata installation of the widget. For example, the attachment widget can contain a title, an icon, supported endpoints, etc. for the new gadget. Then the subsystem synchronization RSS (for example, part of the RSS news the s 350) automatically loads a simple format, content and/or attachments widget.

From the point of view of structure and distribution of new assistive gadgets using RSS may be considered a software developer, working for companies such as the company owning the website zzzmovies.com. For the development of mini-applications "film", which allows users to view the film in real time based on the location of each user, the developer can implement special data (e.g., metadata about the widget film and information in real time in a simple format context) in the RSS feed zzzmovies.com's using attachments. When receiving the gadget RSS performs syntactic analysis of these data in a simple format and content installs the gadget of the film, when the user first subscribes to the feed.

Figure 4 illustrates one such example, in which an auxiliary device such as an auxiliary device 460 of the display-based mobile phone is the list of movies from this site zzzmovies.com i.e. obtained through its web server 462. This example deals with the case where the user already has the ability to read various RSS feeds (X, Y, Z) with different web sites (servers) 464 on a cell phone 460 through the gadget 216 RSS feed. This state, which already has what I subscribe to feeds X, Y and Z, in General represented in figure 4 by the arrow (1).

In this example, after some time, like after viewing the web site zzzmovies.com's, the user subscribes to a new web channel W that contains the attachment 470 gadget zzzmovies server 462 zzzmovies.com 462. After such subscription request gadget 216 RSS is notified (e.g., via RSS-platform 350), and it sees the attachment <widget>. This is shown in figure 4 by the arrow designated by the numeral (2). In response, the widget RSS install the gadget 470 zzzmovies (arrow (3)). It should be noted that the installation may require the provision of certain policies and/or the user for confirmation.

After the installation of the gadget 470 zzzmovies can be loaded and run, and it will subscribe to your own feed W using RSS platform 350. From this moment the gadget 470 zzzmovies can function independently from the gadget 216 RSS, as shown in figure 4 by the arrow (4). Through the web of the channel W gadget 470 zzzmovies can take raw content in a simple format content through attachments, however, as described above, it may alternatively include the conversion code to convert RSS feed content in a format that is understandable to the device, as for example with Argive, which provides the best match between the content of the web channel and abilities of the device.

Alternatively, the gadget 216 RSS can subscribe to a web feed W and manage data for a widget zzzmovie. In this embodiment, the widget 216 RSS efficiently manages the gadget zzzmovie.

It should be noted that after the installation of the gadget 470 zzzmovie do not want to install every time, and its data is installation included in the metadata, relevant information is already included in the register, can be used to load and run (that is, the initialization value of the instance of the widget every time the RSS feed is detected, the same metadata. For example, if the gadget 216 recognizes that the metadata were previously processed data of the installation in the registry, the data of the installation can be read from the register (or the current metadata can be transformed into equivalent data of the installation)to allow (download and execute) an instance of the appropriate widget to handle the content.

It is obvious that although the gadget RSS can process the RSS content instead allow another gadget for these purposes, is shown in figure 4, the model preferred for several reasons, one of the to the which is what the new gadget 470 is separated from the gadget 216 RSS, even though both use RSS as a delivery mechanism data. Among other advantages, this model prevents duplication feed W in two places, for example in the RSS menu cell phone and in his own movie menu. New mini-application 460 can also handle their own interaction data with the main server so that your gadget 216 RSS is not required to have logic, code conversion, etc. to handle the additional (not related to the widget) attachment taken from the web channel W. it Should be noted that if for some reason the gadget 216 feed stops, it also stops the gadget 470 of the film.

Figure 5 shows an example of logic that may be adopted gadget 216 RSS and according to which when a user subscribes to a feed and accepts the feed (step 502), containing the appropriate metadata, such as the attachment <widget>that is determined through steps 504 and 506, the user is given the option to install the widget for the contents of this feed. For example, at step 508 is performed, the policies and/or user content, for example, through the user of interest is the face of the widget 216 RSS, the user may be prompted, which indicates that the feed has some [X] a mini-application that can work with this device, and that you can allow it. If the user refuses, then the process ends. It should be noted that at step 506, if the widget is already installed, for example, if this is not the first time a user subscribes to this RSS feed, or if the user already has installed a mini-application in some other way, the process continues to step 512 to apply already installed the widget.

If the user/policies allow you to configure a widget, for example, if the user chooses at step 508, the widget RSS proceeds to install a new widget to the step 510. In one embodiment, this may include recording the necessary register information based on metadata attachment <widget>, open the application control panel auxiliary display and output to a user request for the appointment of the widget to the appropriate devices, and linking that specific channel with the new installed gadget. This ensures that the subsequent inclusion of a suitable format (e.g., inclusion in a simple format content will be delivered in this mini-application is tion. New mini-application may be registered in the supporting framework. After completing the installation process continues with step 512.

At step 512 the gadget 216 RSS loads and executes the installed gadget. It should be noted that along with the fact that the gadget 216 may process the contents of the web of the channel, in one embodiment, the widget 216 RSS not subscribed to this feed and do not control these web channel, but instead allows the new loaded and running a gadget to take the contents of the web channel. Among other things, this helps to avoid confusion of the user, for example, when the feed appears in the RSS menu, device user, and represents a separate widget on the device. In addition, loaded gadget will handle their own interaction, data requests, etc. with its main web server, which is useful because it does not depend on the widget 216 RSS, which handles RSS feeds from multiple data sources.

As shown in the diagram of the sequence of operations figure 6, the widget (already installed or new)that you downloaded and run the algorithm from figure 5, is responsible for getting their particular feed with RSS-platform (step 618) and the processing in which immodesty data with the main web server (steps 624 and 628). Communication with the auxiliary platform typically involves transferring the content extracted from the RSS data (for example, in inclusions in the format of simple content, RSS-platform (step 622), after performing format conversion of the content on the stage 620 (if necessary).

The following information is aimed at some example concepts of user interaction, where pages will be used for presentation to the user information, and where examples of RSS feeds is shown by enclosing them in <brackets>:

Although the present invention may be susceptible to various modifications and alternative constructions, above the drawings shown and described specific embodiments of. However, you should understand that there is any intention to limit the invention to specific forms disclosed, and on the contrary, the invention is to cover all modifications, alternative constructions, and equivalents included within the essence and scope of the present invention.

1. Machine-readable media containing executable computer instructions, which when implemented method of displaying predostavlennogo distributed content on the sub-display device using the widget, the method includes the steps are:
take data from a source plug-in gadget, and mentioned plug the gadget contains a computer program plug-in type installed on the main computer system, the main computer system comprises a main display,
moreover, the mentioned data contains metadata associated with the data corresponding to information to display the contents on the sub-display device, and the sub-display device is an optional device in addition to the main display the main computer system that is allowed to display the contents when the main part of the main computer system are in a state of low energy consumption,
process, through the plug mini-applications, metadata associated with the mentioned data, determine that the above content should be displayed on the sub-display device, and determines that the widget auxiliary display should be allowed to display the mentioned content on said auxiliary device display;
use by plug-in gadget metadata information to allow the widget ancillary the nogo display process mentioned contents,
provide at least part of these content widget in the auxiliary display, and
provide via the widget sub-display at least part of the above-mentioned content on the sub-display device for display.

2. Machine-readable media of claim 1, wherein the step of processing the metadata to determine whether the register information corresponding to the metadata.

3. Machine-readable medium according to claim 2, in which the processing of the metadata indicates that the information corresponding to the metadata is present in the register, and at the stage of using metadata to allow the widget auxiliary display download and run a mini-application on the basis of information from the register.

4. Machine-readable medium according to claim 2, in which the processing of the metadata indicates that the information corresponding to the metadata is not in the register, and at the stage of using metadata to allow the widget auxiliary display record corresponding to the metadata information in the case to install the gadget auxiliary display, and download and run the gadget auxiliary display.

5. Machine-readable medium according to claim 1, additionally containing completed the appropriate computer instructions for converting content from one format to another format for issuing at least part of the content on the sub-display device.

6. Machine-readable media of claim 1, wherein the source data corresponds to an RSS feed, and further comprises executable computer instructions for receiving from an RSS feed additional content that includes one or more of audio, video, images, text, one or more MIME types or other content.

7. Machine-readable media of claim 1, wherein the step of using the metadata information for the resolution of the widget auxiliary display launch one mini-app to create at least one virtual mini-application by writing to the register.

8. Machine-readable media of claim 1, wherein during use the metadata information to resolve the widget auxiliary display use the same widget for the distribution and installation of the executable software code for another widget.

9. The way to install a widget that can display the received data on the sub-display device and method is intended for use in a computing environment that contains the source data and computer system that communicates with the auxiliary device of the display, and the method comprises the steps are:
take the data in the widget, and the widget contains to numerou program plug-in type, installed on the main computer system, the main computer system has a main display;
process, by the widget, included in the received data, the metadata, and the metadata in accordance with another mini-application that can process the content associated with the accepted data to be displayed on the sub-display device, and the sub-display device is an optional device in addition to the main display the main computer system that is allowed to display the contents when the main part of the main computer system are in a state of low energy consumption;
based on the metadata to determine whether you want to install another gadget,
when you want to install another mini-app, then install another widget;
start another gadget;
take the contents of the gadget,
pass through the widget content to another widget,
output through the other gadget at least a portion of the transmitted content to display device supporting display.

10. The method according to claim 9, in which the step of determining from the metadata necessary for the installation of the other mines the application provides access to the data in the register.

11. The method according to claim 9, in which you want to install another mini-application, and installation stage another gadget contains an entry in the register information corresponding to the metadata.

12. The method according to claim 9, in which the step of outputting at least part of the content to display device supporting display contains converting content from one format to another format.

13. The method according to claim 9, in which the step of accepting data contains information sharing to subscribe to the RSS feed.

14. The display system of distributed content on the sub-display device using a mini-application in the computing environment containing a main computer having a main display and the auxiliary device is connected to the main computer, and the system contains:
the platform, which adopts distributed data sources data dissemination;
widget distribution, coupled with the platform so that the widget distribution processes distributed data received on the platform subscription;
the mechanism of installation associated with the gadget distribution, and mechanism installation configured to install a specific gadget that is required for a specific data source, on the basis of the information is then in the set of distributed data taken from a particular data source; and
platform auxiliary display that receives and displays the contents of a particular widget, and the content corresponds to the distributed data taken from a specific data source, and mentioned content is not displayed on the main display.

15. System 14, in which the computing environment contains many sub-display device and further comprises a display mechanism that relates the specific web channel with a subset of devices auxiliary display.

16. System 14, in which the sources of distribution data are RSS feeds-data that correspond to at least one of: consumption of the blog/RSS feed, create a blog/RSS, digital photo frames, podcast and widget sidebar.

17. System 14, in which the auxiliary device understands the first data format, and further comprises means for converting data from another data format into the first data format.

18. System 17, in which specific mini-application is associated with the tool for data conversion from another format of the data in the first data format.

19. System 14, in which the mechanism of the installer installs a specific widget by writing to the register info is prolonged, which corresponds to information received from a specific data source.

20. The system according to claim 19, in which the information received from a specific data source, is contained in attachment associated with the gadget.