Scrigroup - Documente si articole

     

HomeDocumenteUploadResurseAlte limbi doc
BulgaraCeha slovacaCroataEnglezaEstonaFinlandezaFranceza
GermanaItalianaLetonaLituanianaMaghiaraOlandezaPoloneza
SarbaSlovenaSpaniolaSuedezaTurcaUcraineana

AdministrationAnimalsArtBiologyBooksBotanicsBusinessCars
ChemistryComputersComunicationsConstructionEcologyEconomyEducationElectronics
EngineeringEntertainmentFinancialFishingGamesGeographyGrammarHealth
HistoryHuman-resourcesLegislationLiteratureManagementsManualsMarketingMathematic
MedicinesMovieMusicNutritionPersonalitiesPhysicPoliticalPsychology
RecipesSociologySoftwareSportsTechnicalTourismVarious

Device-stored Icons and Logos - Speclet version 1.4

manuals



+ Font mai mare | - Font mai mic



Device-stored Icons and Logos

Speclet version 1.4

Microsoft Confidential.  2005 Microsoft Corporation. All rights reserved. These materials are confidential to and maintained as a trade secret by Microsoft Corporation. Information in these materials is restricted to Microsoft authorized recipients only. Any use, distribution or public discussion of, and any feedback to, these materials is subject to the terms of the attached license. By providing any feedback on these materials to Microsoft, you agree to the terms of that license.
Microsoft Corporation Technical Documentation License Agreement (Standard)

READ THIS! THIS IS A LEGAL AGREEMENT BETWEEN MICROSOFT CORPORATION ('MICROSOFT') AND THE RECIPIENT OF THESE MATERIALS, WHETHER AN INDIVIDUAL OR AN ENTITY ('YOU'). IF YOU HAVE ACCESSED THIS AGREEMENT IN THE PROCESS OF DOWNLOADING MATERIALS ('MATERIALS') FROM A MICROSOFT WEB SITE, BY CLICKING 'I ACCEPT', DOWNLOADING, USING OR PROVIDING FEEDBACK ON THE MATERIALS, YOU AGREE TO THESE TERMS. IF THIS AGREEMENT IS ATTACHED TO MATERIALS, BY ACCESSING, USING OR PROVIDING FEEDBACK ON THE ATTACHED MATERIALS, YOU AGREE TO THESE TERMS.

1. For good and valuable consideration, the receipt and sufficiency of which are acknowledged, You and Microsoft agree as follows:

(a) If You are an authorized representative of the corporation or other entity designated below ('Company'), and such Company has executed a Microsoft Corporation Non-Disclosure Agreement that is not limited to a specific subject matter or event ('Microsoft NDA'), You represent that You have authority to act on behalf of Company and agree that the Confidential Information, as defined in the Microsoft NDA, is subject to the terms and conditions of the Microsoft NDA and that Company will treat the Confidential Information accordingly;

(b) If You are an individual, and have executed a Microsoft NDA, You agree that the Confidential Information, as defined in the Microsoft NDA, is subject to the terms and conditions of the Microsoft NDA and that You will treat the Confidential Information accordingly; or

(c)If a Microsoft NDA has not been executed, You (if You are an individual), or Company (if You are an authorized representative of Company), as applicable, agrees: (a) to refrain from disclosing or distributing the Confidential Information to any third party for five (5) years from the date of disclosure of the Confidential Information by Microsoft to Company/You; (b) to refrain from reproducing or summarizing the Confidential Information; and (c) to take reasonable security precautions, at least as great as the precautions it takes to protect its own confidential information, but no less than reasonable care, to keep confidential the Confidential Information. You/Company, however, may disclose Confidential Information in accordance with a judicial or other governmental order, provided You/Company either (i) gives Microsoft reasonable notice prior to such disclosure and to allow Microsoft a reasonable opportunity to seek a protective order or equivalent, or (ii) obtains written assurance from the applicable judicial or governmental entity that it will afford the Confidential Information the highest level of protection afforded under applicable law or regulation. Confidential Information shall not include any information, however designated, that: (i) is or subsequently becomes publicly available without Your/Companys breach of any obligation owed to Microsoft; (ii) became known to You/Company prior to Microsofts disclosure of such information to You/Company pursuant to the terms of this Agreement; (iii) became known to You/Company from a source other than Microsoft other than by the breach of an obligation of confidentiality owed to Microsoft; or (iv) is independently developed by You/Company. For purposes of this paragraph, 'Confidential Information' means nonpublic information that Microsoft designates as being confidential or which, under the circumstances surrounding disclosure ought to be treated as confidential by Recipient. 'Confidential Information' includes, without limitation, information in tangible or intangible form relating to and/or including released or unreleased Microsoft software or hardware products, the marketing or promotion of any Microsoft product, Microsoft's business policies or practices, and information received from others that Microsoft is obligated to treat as confidential. 

2. You may review these Materials only (a) as a reference to assist You in planning and designing Your product, service or technology ('Product') to interface with a Microsoft Product as described in these Materials; and (b) to provide feedback on these Materials to Microsoft. All other rights are retained by Microsoft; this agreement does not give You rights under any Microsoft patents. You may not (i) duplicate any part of these Materials, (ii) remove this agreement or any notices from these Materials, or (iii) give any part of these Materials, or assign or otherwise provide Your rights under this agreement, to anyone else.

3. These Materials may contain preliminary information or inaccuracies, and may not correctly represent any associated Microsoft Product as commercially released. All Materials are provided entirely 'AS IS.' To the extent permitted by law, MICROSOFT MAKES NO WARRANTY OF ANY KIND, DISCLAIMS ALL EXPRESS, IMPLIED AND STATUTORY WARRANTIES, AND ASSUMES NO LIABILITY TO YOU FOR ANY DAMAGES OF ANY TYPE IN CONNECTION WITH THESE MATERIALS OR ANY INTELLECTUAL PROPERTY IN THEM.

4. If You are an entity and (a) merge into another entity or (b) a controlling ownership interest in You changes, Your right to use these Materials automatically terminates and You must destroy them.

5. You have no obligation to give Microsoft any suggestions, comments or other feedback ('Feedback') relating to these Materials. However, any Feedback you voluntarily provide may be used in Microsoft Products and related specifications or other documentation (collectively, 'Microsoft Offerings') which in turn may be relied upon by other third parties to develop their own Products. Accordingly, if You do give Microsoft Feedback on any version of these Materials or the Microsoft Offerings to which they apply, You agree: (a) Microsoft may freely use, reproduce, license, distribute, and otherwise commercialize Your Feedback in any Microsoft Offering; (b) You also grant third parties, without charge, only those patent rights necessary to enable other Products to use or interface with any specific parts of a Microsoft Product that incorporate Your Feedback; and (c) You will not give Microsoft any Feedback (i) that You have reason to believe is subject to any patent, copyright or other intellectual property claim or right of any third party; or (ii) subject to license terms which seek to require any Microsoft Offering incorporating or derived from such Feedback, or other Microsoft intellectual property, to be licensed to or otherwise shared with any third party.

6. Microsoft has no obligation to maintain confidentiality of any Microsoft Offering, but otherwise the confidentiality of Your Feedback, including Your identity as the source of such Feedback, is governed by Your NDA.

7. This agreement is governed by the laws of the State of Washington. Any dispute involving it must be brought in the federal or state superior courts located in King County, Washington, and You waive any defenses allowing the dispute to be litigated elsewhere. If there is litigation, the losing party must pay the other partys reasonable attorneys fees, costs and other expenses. If any part of this agreement is unenforceable, it will be considered modified to the extent necessary to make it enforceable, and the remainder shall continue in effect. This agreement is the entire agreement between You and Microsoft concerning these Materials; it may be changed only by a written document signed by both You and Microsoft.




1. Introduction

In order to provide device manufacturers with a means to brand their devices in Windows Media Player, mechanisms have been put in place to extract those images from the device. There are two types of images which are currently implemented in Windows Media Player. The first is an icon which represents the device, and the second is a logo representing the company or entity representing the device. We refer to the icon which represents the device as the device icon, and the logo as the device logo.

1.1 Scope and Limitations

  • Icon customization is enabled specifically for MTP devices, and this icon/logo extraction feature is optional. It is desirable that the data for these objects actually be stored in the firmware or in a protected portion of the devices storage, rather than among user-created files on the device. This determination is left to the device designer, as is any necessary logic to protect the data from accidental modification or erasure by the end user.
    • Delete/move/rename operations on the icon and logo objects files should return failure.
    • If the device implements multiple storages, it is desirable for the device to return the icon/logo files (if implementing DevIcon.fil method) regardless of which storage the file-open request is targeted at. If desired by the vendor, different icons could be implemented for the different storage units.
    • If the product is offered with multiple appearances (e.g. differently colored skins for the same model) it would be ideal for the icons to reflect the actual color of the device.) We recognize that this could present a manufacturing challenge in some environments.
  • Precedence: For WMDM enabled clients, visuals extracted from the device per this specification will take precedence over icon properties supplied by Windows setup mechanisms such as device node properties, if such properties are available.
  • Localization: It is required that the device visuals described herein are locale-neutral. No locale/language identification is supplied in this mechanism to allow for extraction of different icons for regionalized versions of Windows Media Player 10 and 11, or other WMDM clients.
  • Future support: It is not guaranteed that devices carrying icons will retain their customized appearance in future releases of Windows, as the mechanism may change to allow for more generalized support of device customization in future releases. However, future Windows releases will contain at least equivalent opportunity for device visual customization.
  • Multi-function devices: If a multifunction device incorporates music player functionality, all UI exposing the devices non-music functions will only display generic or function-specific icons.
  • Icon extraction is only possible when an active connection with the device is established. Windows Media Player 10 and 11, or other WMDM components may choose to cache the icons/logos for use when the device is disconnected. Cache management logic is up to the application.

2. Resources Required from the Vendor:

2.1 Device Icon

There are two ways to support the device icon feature. The first is by having an object available named DevIcon.fil on the root of the device. The second is by supporting the DeviceIcon MTP device property. If the DeviceIcon property is supported the DevIcon.fil object from the root of the devices store will not be used. Please note that WMP10 does not support the DeviceIcon MTP device property method, only the DevIcon.fil method. The object should be of the same type as an .ICO file and should be implemented incorporating 8 icons in the single object (4 sizes x 2 color depths), paying particular attention to:

  • Sizes (16x16, 32x32, and 256x256). The 256x256 size is newly recommended for optimal WMP11 support, see below.
  • Colors: (32-bit with 8 bit alpha (256x256 and 32x32), 8-bit with 1-bit transparency (16x16 and 32x32)
  • Isometric angle
  • Drop shadow

Windows Media Player 10 only takes advantage of the icon sizes of 32x32 and below. However, Windows Media Player 11 and future versions of the Windows shell make prominent use of the 256x256 images, so it is strongly recommended that this size be included in your icon object.

This icon is represented as a device resource in WPD, WPD_RESOURCE_ICON. More information can be found in the Technical Resources section.

2.1.1 DevIcon.fil

Device firmware should be implemented such that an object named DevIcon.fil is enumerated on the root of the device, regardless of which storage is requested.

2.1.2 DeviceIcon Device Property

In Windows Media Player 11 onward there exists a new MTP device property called DeviceIcon (0xD405). This property will be requested by the host and expects the same icon data as above in the data phase of the response. If this property is supported the DeviIcon.fil object will not be used. See below for the specification of the DeviceIcon MTP Device Property.

Field name

Field order

Size (bytes)

Datatype

Value

PropertyCode

UINT16

0xD405

Datatype

UINT16

0x4002 (AUINT8)

Get/Set

UINT8

Device-Defined

DefaultValue

Device-Defined

GroupCode

UINT32

Device-defined

FormFlag

UINT8

0x00 None

This Device Property can be accessed on the PC via the WPD Property Key. Refer to the Technical Resources section at the end of this document.

Longhorn Icon Guidelines

Generic Device Icon:

  • Sizes 256, 32, 16 (required) smooth scaling is used between 256 and 32.
    Sizes 128, 96, 48, 24 (optional)
  • Format ICO
  • Bit Levels design for 32 bit (24bit+8bit alpha)

Isometric Orientation:

Isometric Orientation:

Isometric Icon Examples:

Corporate Logo

The corporate logo must be implemented such that the root file DevLogo.fil should return a file in .PNG format to allow for alpha blended edges.

For aesthetic planning, vendors should use alpha blending to ensure a smooth transition.

The file must have x and y dimensions less than or equal to 150wx32h, left justified.

Example layout: (The icon and logo shown are for example only)

3. Technical Resources:

The following MSDN article describes in exhaustive detail the format of Win32 .ICO files and Win32 APIs for examining and manipulating them:

https://msdn2.microsoft.com/en-us/library/ms997538.aspx

The following MSDN article describes a recommended workflow for graphic designers to create icons that will mesh stylistically with the Windows XP user interface:

https://msdn2.microsoft.com/en-us/library/ms997636.aspx

WPD Property Keys

https://windowssdk.msdn.microsoft.com/library/default.asp?url=/library/en-us/WPD_SDK/htm/wpdapplicationoverview.asp

WPD Device Icon Resource

https://windowssdk.msdn.microsoft.com/library/default.asp?url=/library/en-us/WPD_SDK/htm/wpd_resource_icon.asp



Politica de confidentialitate | Termeni si conditii de utilizare



DISTRIBUIE DOCUMENTUL

Comentarii


Vizualizari: 1403
Importanta: rank

Comenteaza documentul:

Te rugam sa te autentifici sau sa iti faci cont pentru a putea comenta

Creaza cont nou

Termeni si conditii de utilizare | Contact
© SCRIGROUP 2024 . All rights reserved