Multiple device types Sample Clauses

Multiple device types. It became clear during the development of the scenarios and during the course of the project that the ability to support mobile devices and tablets is now becoming an integral part of the project. To keep the system as flexible as possible we decided to focus on HTML5 based applications with a downscaling to HbbTV specs 1.5 and possibly 2.0 for the third year of the project [2]. But within this limitation we again feel it’s important that we can have a unified view for the developer and that the framework handles as much as possible in matching the device capabilities to our internal model. Traditionally one would use adaptive/responsive design using stylesheets to adapt to different screen sizes and browser. And we use this on the lower levels inside the HTML5 clients but we also need a more generic concept on the application level. From the applications point of view each client (mostly browsers) are just seen as screens with capabilities and this is the abstraction level we want to support. We distinguish between the following screen capabilities:  size (pixel count and physical size)  rotation (is the user holding it in landscape or portrait)  stylesheet level (what options for visual styles do we have)  passive or active (is it just a screen or also provides mouse, touch input)  keyboard support (is there a fixed or optional keyboard)  brand specific features (special buttons for example) Each of the screens works with these capabilities as almost a contract (interface) between it and the system. Communication from and to these unified screens is either handled by the framework as part of the abstraction concept (so for example if a state of a button changes in the application the framework will change it on all the screens needed) or is done manually using a simple message back to the server side of the application (Image 9). Image 9: Communication from the application to connected unified screens. Using these methods we currently support all HTML5 based desktop browsers, android phones and tablets as well as Apple (iOS) phones and tablets. We also did some first tests with Condat in the area of HbbTV support to see if some of the basic abstraction concepts also work for the needed integration in third year.
Sample 1
AutoNDA by SimpleDocs

Related to Multiple device types

  • License Types The following License Types may be offered with respect to individual Software products or product families. Additional license types may be specified with respect to certain products or product groups as set forth in the Product Specific Terms. The License Type will be specified in an LSDA.

  • Service Types Where you are funded for more than one service type under this Activity, and you have met the requirements within one of these service areas, you may shift all or part of any remaining funds to another service type you support under this Activity. You must advise us of resource attributions annually through the Activity Work Plan Report as detailed in Item E.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups:

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Order Types As defined in FAR Part 16, Type of Contracts, all types of Fixed-Price, Cost-Reimbursement, Incentive, Time-and-Materials (T&M), and Labor-Hour (L-H) are permissible for Orders under the Basic Contract. In addition, the Award Term Incentive may be used for Orders under the Basic Contract. Indefinite Delivery, Indefinite Quantity, Blanket Purchase Agreements, and Letter Contracts are not permissible Order types under the Basic Contract. Orders may be multi-year and/or include options as defined in FAR Part 17 and agency-specific FAR Part 17 supplements.

  • Multiple Listing Service (MLS) Due to rules administered by the local Multiple Listing Service (“MLS”), all details of any transaction that are procured by the Agency may be used for publication in the MLS. Seller hereby consents to such publication on an unrestricted basis whereas the Agency must comply with all applicable MLS rules to allow data about the Property to be shown and made available by the MLS in addition to other internet websites. MLS rules generally provide that any property entered into its database be updated within forty-eight (48) hours, or some other period of time, after all necessary signatures have been obtained in regard to the Property. Seller has the right to prohibit any and all publication of information in regard to a transfer of the Property. In order to exercise this right, the Seller is required to authorize a separate addendum provided by the Agency and attach to this Agreement.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

Time is Money Join Law Insider Premium to draft better contracts faster.