Attention {{ agency_name }} Administrators,
{{ name }} has been made a regular user and has been removed from all agency requests. If you would like {{ name }} to be able to work on a request, please add them via the Add User form on each request.


Develop Stencila
If you want to help make Stencila available online, to support efficient sharing and collaboration, have a look at Stencila Hub. Work on this project will be particularly interesting for those who are into Nix, Docker and Kubernetes.
If you care about structured documents, interoperability of formats, data and are interested in schemas, have a look at Stencila Schema.
If you are interested in helping with Stencila interoperability with existing tools and file formats used for data analysis, check out Stencila Encoda.
If you would like to improve functionality of using Python from within Stencila, check out Stencila for Python. And if you are an R developer, have a look at Stencila for R . Likewise the Stencila for Node.js package for Javascript developers.


Copyright ©2003 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This document celebrates the vision of a device independent Web. It describes device independence principles that can lead towards the achievement of greater device independence for web content and applications.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document has been produced as an overview document from the W3C Device Independence Activity. It is intended to provide a set of principles that can guide work relating to device independence.
This document is one of a series produced by the Device Independence Working Group, part of the W3C Device Independence Activity. The DIWG activity statement can be seen at http://www.w3.org/2001/di/Activity.
A version of this document is also available showing changes since the previous Working Draft.
Comments on, and discussion arising from, this document can be sent to<EMAIL_ADDRESS>the public forum for discussion of the W3C's work on Device Independence. The archive for the list is accessible online.
Patent disclosures relevant to this document may be found on the WG patent disclosure page.
The intended audience for this document is primarily other W3C Working Groups and external organizations involved in developing web content authoring and delivery technologies.
The goal of this document is to suggest that web content and applications can be authored, generated or adapted for a better user experience when delivered via many different web-connectable access mechanisms. The general phrase "device independence" is used for this, although the access mechanisms may include a diversity of devices, user agents, channels, modalities, formats etc.
The vision we share with others is to allow the Web to be accessible by anyone, anywhere, anytime, anyhow. The focus of the W3C Web Accessibility Initiative is on making the Web accessible to anyone, including those with disabilities. The focus of the W3C Internationalization Activity is on making the Web accessible anywhere, including support for many writing systems and languages. The focus of the W3C Device Independence Activity is on making the Web accessible anytime and anyhow, in particular by supporting many access mechanisms (including mobile and personal devices, that can provide access anytime) and many modes of use (including visual and auditory ones, that can provide access anyhow).
These three Activities are complementary, and our interests overlap. For example, being able to select an auditory mode of use on a device may be essential to someone with a visual disability. The focus of device independence is on matching web content to the needs, capabilities and limitations of the delivery environment. We wish to minimize the extent to which web content is authored in a way that is only deliverable on a restricted set of devices.
The principles described here are intended to be complementary to the wider Architecture of the World Wide Web [WEBARCH], which consists of a wider set of requirements, constraints, principles, and choices that influence the design of the Web and the behavior of agents within it. Implementations of these principles should also conform to the Web Content Accessibility Guidelines [WCAG], the User Agent Accessibility Guidelines[UAAG] and the Authoring Tool Accessibility Guidelines [ATAG].
The aim of this document is to focus on device independence and to set out some principles that can be used when evaluating current solutions or proposing new solutions, and can form the basis of more detailed requirements and recommendations.
The principles are independent of any specific markup language, authoring style or adaptation process. They do not propose specific requirements, guidelines or technologies.
It is intended, however, that these principles be used as a foundation when proposing greater device independence through, for example:
Other documents provide more details on the authoring challenges [AC] and the delivery context issues [DCO] associated with achieving device independence.
In recent years, there has been a proliferation of types of device and access mechanisms using the Web, extending far beyond the conventional personal computer. These access mechanisms range from web tablets, appliances and TVs in the home, to mobile devices including phones and PDAs, and access mechanisms for the physically challenged. Connectivity capabilities have also evolved to include high bandwidth modems, LANs and wireless networks. Simultaneously, the needs and expectations of the user with regards to access, availability and consumption of web content have also evolved. Users now expect to get to critical information through different access mechanisms from different locations and at different times during their day.
For example, a user may want to access some web information using a PC connected to a cable network when at home, but when out of the house the same user expects to access the same information using a PDA connected through a mobile phone network.
In the appendix on Usage scenarios we give examples of circumstances in which access to the Web may be required via different access mechanisms.
Content authors can no longer afford to develop content that is targeted for use via a single access mechanism. The key challenge facing them is to enable their content or applications to be delivered through a variety of access mechanisms with a minimum of effort. Implementing a web site or an application with device independence in mind could potentially save costs, and assist the authors in providing users with an improved user experience anytime, anywhere and via any access mechanism.
In the following section, the impact of device independence is considered from three different perspectives:
For each perspective, significant concepts for device independence are defined and appear as follows:
A separate Glossary for Device Independence [Glossary] includes all the definitions introduced in the body of this document as well as those from other documents produced by the Device Independence Activity.
Within each perspective, a number of principles are stated. They are intended to capture fundamental assumptions within which specific approaches to authoring and adaptation can be developed.
The principles are not specific to any particular usage scenario or to any implementation technology, but capture aspects of device independence that will apply across many contexts. Each Device Independence Principle (DIP) is given a sequential number and a name. They appear as follows:
Within this document, principles are stated in this style.
Examples are given at certain points within the document in order to illustrate the way in which the principles may be applied in specific circumstances. They appear as follows:
Example: Within this document, examples are shown in this style.
In this section a number of principles are introduced which are fundamental to the achievement of device independence.
They are called principles (rather than, for example, guidelines or requirements) because they attempt to capture important concepts and aspirations that are not specific to any particular realization. Unlike guidelines, they are not specific enough to guide current practice. Guidelines could be developed in due course by applying the principles to the use of current markup technologies. Unlike requirements, they do not propose a specific approach to which some new technology must conform. Requirements for new technology could be developed in due course by applying the principles as part of the design process.
Whether these principles are used to develop future guidelines, requirements and recommendations will depend on their general acceptance within the Web development community. At this stage, all the principles are stated as "should", in lowercase. In the future, if requirements are developed from them, the conventional requirements terminology of "MUST", "SHOULD", and "MAY" could be used to indicate different degrees of conformance (as defined in RFC2119).
For purposes of explanation, the principles are introduced, with the concepts used in their statement, from three perspectives: that of the user, the author and the delivery mechanism. However, the principles themselves can have implications that span multiple parts of the delivery chain.
The following diagram introduces the key user-related concepts, which are then defined and explained in the subsequent text.
We want to enable the user to perceive and interact with the Web using many kinds of device, or more generally, via many kinds of access mechanism.
The main concepts for the user are as follows.
Example <IP_ADDRESS>: Existing devices that are commonly used to access the Web include PCs, PDAs, web-enabled phones, and interactive TVs.
The access mechanism is an intermediary between the Web and the user. On one side it communicates with the Web using protocols and markup conventions, on the other it supports perception by, and interaction with, the user.
From the user's point of view, an access mechanism often corresponds to a single device.
However, in some situations, the access mechanism may consist of more than one device.
Example <IP_ADDRESS>: A printer may be attached to a PC that is connected to the Web. The combined apparatus provides an access mechanism that can offer a printed representation of a web page.
Example <IP_ADDRESS>: When in a mall, a user may interact with the Web simultaneously through a kiosk interface and a personal phone. Personal information is exchanged through the private phone connected to the mobile network, while public information is viewed, under the control of the phone, on the larger but public kiosk screen equipped with a high-speed connection.
Sometimes the access mechanism may include the use of additional network support.
Example <IP_ADDRESS>: A service provider may offer a service that allows voice interaction with the Web via a telephone. The combination of the telephone and the service is the access mechanism that enables an auditory perception of the web content.
Sometimes the access mechanism may support synchronization for multi-modal interaction.
Example <IP_ADDRESS>: A user may be able to access the Web through a smart phone that simultaneously provides both a graphical interface directly on the phone and a voice interface provided via a network service. The user can select at any time which is the preferred mode of interaction e.g. voice for input and graphics for output, voice for both, or graphics for both.
Most perceivable units provide both presentation and the means for interaction. However, on some types of device, such as printers, perceivable units might contain only presentation.
A user may enter a web page identifier explicitly as part of their interaction, or may indirectly follow one by selecting a link, selecting a previously saved bookmark, or through some other aspect of interacting with an application.
Example <IP_ADDRESS>: A user may see a web page identifier, such as "www.example.com" used in an advertisement. They expect to be able to use this identifier to access further information about the advertiser or product in the form of an appropriate user experience.
In some cases, such as in voice-only browsing, the user may not know the web page identifier being used to retrieve the next perceivable unit.
A perceivable unit is rendered to the user as a collection of physical effects, visual, auditory or tactile, via one or more devices within the access mechanism. Mechanical controls, such as buttons, keys and pointers, and sonic input such as voice commands (and possibly other affordances) allow a user to interact with the perceivable unit.
Example <IP_ADDRESS>: If a user entered the web page identifier "www.example.com" into a web-connected PDA, the resultant perceivable unit may be a visual display showing the company logo, a brief description of its activities, and a link that when touched leads to another page with additional product information.
The physical user interface is where the information that was transmitted digitally becomes accessible to and manipulable by the user.
Conventionally, a web page may be thought of as a perceivable unit. However, depending on the access mechanism, and the granularity of its presentation capabilities, the number of perceivable units required to present a web page may vary.
Example <IP_ADDRESS>: A limited capability device, such as a mobile phone, may accept only small amounts of data during a single interaction with the Web. Such a device may be unable to accept a large resource in a single perceivable unit. The limited presentation and input capabilities on this kind of device may also favor use of multiple perceivable units for improved usability.
The quality of the user experience depends on the degree to which material has been successfully adapted for use via a specific access mechanism. The possible modes of interaction are largely defined by the device manufacturer, but the way in which they are incorporated into one or more perceivable units will affect the ease of use of that device for the user.
The next concept is about the quality of the user experience delivered via a given access mechanism in response to a given web page identifier. It is intended to capture the minimal quality of user experience necessary to be useful to a user.
The function intended by the author may be as simple as to convey some information to the user.
Example <IP_ADDRESS>: If the intended function is for the user to be able to perceive a passage of text, a functional user experience might provide visible or audible representations of it.
The function intended may be as complex as guiding the user through a sequence of application-specific interactions.
Example <IP_ADDRESS>: If the intended function is for the user to take the next step in some interactive application, a functional user experience should be sufficient for the user, say, to successfully fill in a data field and submit it.
A functional user experience is defined with respect to a particular access mechanism. It may not be possible to achieve a functional user experience for some particular content or application for every access mechanism, due to inherent limitations of the mechanism.
The functional intent is defined by the author of the application, and it is possible that it will differ from the expectation or intent of the user.
Example <IP_ADDRESS>: A user may access a flight reservation system in order to find the abbreviated code used for a particular airport. If the user accesses the flight reservation system by voice, the abbreviated code may not be provided, since the airport name may only be spoken without abbreviation. The user may consider that this particular audible representation is not functional for his or her purpose. However, this is a user-centric definition of functional user experience. The user experience is functional from the author's perspective. However the application does not deliver the information to the user in the form they desire.
Whether the user experience associated with a web page is considered by the user to be functional clearly depends on their understanding of the function associated with that web page. The user may already have an expectation of the functionality, for example because they have previously accessed the page on another device. If their expectations are not met, the user cannot be certain whether it is because their expectations are wrong or whether a non-functional user experience has been delivered. If it is the first time they have accessed the web page, they can only rely upon the integrity and consistency of the user experience to estimate whether it is functional.
Many things may prevent completion of a function, such as when a user experience of a web page is not made available, or has broken elements, or causes a failure in the access mechanism. From a user's perspective, if the user is unable to carry out the function successfully then the user experience is not functional.
For some web content or application to be device independent, it should be possible for a user to obtain a functional user experience associated with its web page identifier via any access mechanism.
This is the fundamental principle for device independence from the user perspective. It does not say that the user experience will be the same on every device. But it does say that the user should be able to obtain a user experience and that the user experience obtained should be at least functional.
Example <IP_ADDRESS>: A user enters a web page identifier for a weather forecasting page on different devices. On the screen of a PDA, the text "Tomorrow" is shown, together with a graphic of a sun. On the screen of a phone, the text "Tomorrow: sun" is shown. On an in-car PC, the words "Tomorrow will be sunny" are spoken. These are all user experiences that have been adapted to be functional for their specific access mechanisms.
Example <IP_ADDRESS>: If on some device the same web page identifier as in the previous example gave either no user experience, or a user experience consisting of the text "Cannot display graphics", this would not be a functional user experience.
The goal is that a functional user experience should be possible via any access mechanism. The method by which presentation and interaction are provided may vary according to the different access mechanisms, but the possibility of a functional user experience should always exist.
In particular, it should be possible to provide a functional user experience even on a limited capability device - though it may be of reduced quality compared to that on more capable devices.
Example <IP_ADDRESS>: Where an image would occur on an image-capable device, a text alternative could be displayed on a text-only device, or the text could be spoken when accessed by a voice-only phone.
A web page identifier that provides a functional user experience via one access mechanism should also provide a user experience of equivalent functionality via any other access mechanism.
In other words, the intended function of a web page is associated with the web page identifier, and should apply to all user experiences obtained from the web page identifier, no matter what the access mechanism.
Example <IP_ADDRESS>: By bookmarking a web page identifier that provides a functional user experience on one device it should be possible to obtain a corresponding user experience on another device with equivalent functionality. The user experiences may be different due, among other things, to the different capabilities of the devices, but their intended function is the same and they should both be at least functional.
In order to meet this principle, it may be necessary to restrict or re-interpret what is acceptable as a web page identifier. For example, a URI that includes a suffix indicating its representation, such as "example.html", may need the suffix to be ignored when the material is adapted for a non-HTML device. Similarly, any device-specific information coded in a query part or fragment part of the URI may need to be re-interpreted or ignored. Unfortunately, many implementers do not respect the intent of URI style guidelines [URI-Style].
The following diagram introduces the key authoring concepts, which are then defined and explained in the subsequent text.
The main concepts for authoring are as follows.
When a request is made over the Web for a web page, not only should the request specify the web page identifier for the page, but also it should provide enough information about the access mechanism and the user that the right kind of user experience can be provided.
Delivery context information may be sent as part of each request, but this is not essential. Alternative possible implementations are discussed in the separate Delivery Context Overview [DCO] document.
The delivery context expresses the capabilities and preferences that may constrain the acceptable range of user experiences that can be delivered via a given access mechanism. In particular, the capabilities of the device, including the modalities and representations it supports, the characteristics of the network over which delivery occurs, and the preferences of the user will all potentially affect the user experience provided.
Example <IP_ADDRESS>: A PDA may have a screen of a certain size, and have a built-in speaker. It may be able to display HTML markup and play streaming audio. It may be connected to the Web over a phone network that only offers a slow data transfer rate. The user of the PDA may be in a meeting and prefer not to use audio at that moment. These (and other) attributes form the current delivery context. In this delivery context it might be appropriate to present a web page as a limited amount of text on the screen.
The transfer might, for example, be between an origin server and a user agent. Users are not normally aware of individual delivery units.
The response to a request containing a web page identifier is a delivery unit which contains the data (in a markup language or image encoding, for example) that will be used by the access mechanism in order to render a physical user experience. It will also allow the user to interact with that page, and possibly generate a further request.
Example <IP_ADDRESS>: Markup languages such as HTML, XHTML, SVG, etc. are designed specifically as ways of representing aspects of user experiences. Image formats such as PNG and scripting languages such as ECMAScript may also be used to represent different aspects of the user experience. It is common to find certain combinations of representations that are delivered together. For example, HTML pages frequently contain ECMAScript. For such combinations, a single delivery unit can carry multiple representations. Some delivery units, especially those associated with media, often carry only a single representation. Images are an example of media often carried within their own delivery units.
Adaptation is shown in this diagram as occurring at the server (and hence known as server-side adaptation). However, it may also occur at intermediate points in the delivery chain, or at the client (known as client-side adaptation). See the Delivery Context Overview [DCO] for further explanation.
There are many techniques that could be used to produce an appropriate user experience in response to a request for a web page. Since these principles are intended to be technology independent, no further exploration of the adaptation process is made here.
The authoring perspective instead focuses on the quality of user experience produced by the adaptation process and on the obligations on the authoring task.
The concept of functional user experience has already been introduced as part of the user perspective.
However, though a user experience may be functional, in that it is sufficient to allow a user to complete the function intended, it may not provide a rendering that matches the author's objective for a particular delivery context. The next concept sets out to address this.
Harmonization allows the user experience to be made more specific to the delivery context in order to meet criteria, such as ease of use and quality of user experience, that are important to the author. They may affect, perhaps, the popularity of the web page or the trust that the user places in the underlying application.
Example <IP_ADDRESS>: The way that information is laid out, in the visual representation of a web page, may take into account the dimensions of the display of the device being used. This information is made available to the adaptation via the delivery context. The same information may be arranged quite differently on the same device to improve the visual effect or to improve the usability of the user interaction. Such changes do not affect the functionality of the user experience but may improve its appeal. These aspects are often important to authors and to users.
Authoring tools and adaptation processes may differ in the extent to which they support harmonized user experiences.
The following principles are directed towards the authoring and adaptation process that is responsible for providing a delivery unit in reply to a request from a user.
It should be possible to provide a functional user experience, in response to a request for a web page, in any given delivery context that has an adequate access mechanism.
This principle places an obligation on the author, the authoring tools and the adaptation process to provide a user experience that allows a user to successfully access a web page to get the information or complete the interaction intended.
The principle is effectively a restatement of DIP-1 from the point of view of the producer rather than the consumer.
Sometimes it is not possible to provide some content or functionality in a given delivery context because of limitations in the access mechanism.
If a functional user experience of an application cannot be provided due to inherent limitations in the access mechanism, an explanatory message should be provided to the user.
Example <IP_ADDRESS>: An access mechanism has no sound output capabilities. An application wishes to offer a function, such as playing some music, that can only be provided through sound output. The application cannot offer a functional user experience through such an access mechanism. In this case, it should provide a message to the user instead that indicates the nature of the incompatibility (and might suggest alternatives).
If the author wishes, it should be possible to provide a harmonized user experience, in response to a request for a web page, in any given delivery context that has an adequate access mechanism.
This goes beyond the previous principle to additionally allow that the author can provide a user experience that is well designed for the delivery context. It is an obligation on the authoring tools and adaptation process to support the creation and delivery of user experiences tailored for specific access mechanisms when the author requires them.
In many situations, it is necessary to define specific details about the user experience associated with a particular web page. It is not sufficient that only predefined or standard user experiences can be used. Authors should be able to control the precise details of the user experience if they wish. At the most detailed level, a harmonized user experience might apply to only a very restricted set of delivery contexts. However, DIP-2 requires that other adaptations be available to provide functional user experiences for the other delivery contexts.
Example <IP_ADDRESS>: Some devices, especially small ones such as phones, are highly constrained in their capabilities. To create a sufficiently user-friendly user experience of some application, it may be necessary to harmonize the user experience for that particular application on that particular phone.
It is unrealistic to expect an author to create different user experiences for every delivery context. Whenever possible, authored source content should be reused across multiple delivery contexts.
Functional user experiences suited to any delivery context can be generated by using an adaptation process applied to a representation that does not depend on the access mechanism.
Example <IP_ADDRESS>: One approach to device independent authoring is to use a transformation technique such as XSLT. By creating the content in XML, the same content can be adapted for different delivery contexts using XSL stylesheets.
Some authoring approaches based on device independent representations may in addition allow customized user experiences to be provided for some delivery contexts.
The issues facing authors are described in more detail in the separate document Authoring Challenges for Device Independence [AC].
The following diagram introduces the key delivery concepts, which are then defined and explained in the subsequent text.
The main concepts for delivery are as follows.
The user agent is some software or firmware in a device (for example a browser) that lets the user identify a web page to be rendered, assembles an appropriate request for that page (possibly including the delivery context), accepts the reply (delivery unit), and renders that reply into one or more perceivable units.
Before rendering, a user agent may apply client-side adaptation, perhaps under the control of adaptation preferences, to transform a delivery unit into a perceivable unit.
Example <IP_ADDRESS>: A user agent may render the material they receive in a delivery unit as a single perceivable unit or as multiple perceivable units, perhaps to better fit a limited viewing area. For example, WML provides explicit markup for the delivery unit, <deck>, and the perceivable unit, <card>.
There are three distinct ways in which the user may personalize how a web page is presented to them. They are distinguished by which parts of the delivery chain are responsible for affecting the user experience: the renderer in the user agent, some adaptation process (in the server, client or an intermediary), or the functionality of the application itself.
It may be possible for a user agent, under the control of rendering preferences, to make local changes to a perceivable unit as it is rendered. This will depend on the local behavior of the user agent within the device.
Example <IP_ADDRESS>: A user agent may allow the user to locally increase the size of text, or convert text to speech, to improve accessibility for those with poor or no sight.
In current user agents, such rendering preferences are not communicated as part of the delivery context and so do not affect the delivery unit sent to the device. However, this also means it is possible for a user experience to become non-functional through inappropriate choice of rendering preferences.
Example <IP_ADDRESS>: A user experience may use black text on a white background. If a local rendering preference sets only the background to be black, the text will become unreadable and so non-functional.
The user may be able to express preferences that affect the way the content or application functionality is presented when there is more than one choice. Some devices can support more than one way of presenting a web page, or more than one method of interaction with it.
Example <IP_ADDRESS>: Even if an access mechanism supports images, a user may prefer to receive all information as text - perhaps because they are using a local text-to-speech converter. By indicating an adaptation preference for no images, the adaptation process may be able to provide a better text-only presentation, harmonized with the delivery context, than could be achieved by locally replacing all images by their text alternates.
Some adaptation may occur within the network, for example in transcoding proxies, or in the client prior to the final perceivable unit being rendered.
Example <IP_ADDRESS>: A web page may be delivered as some HTML markup with embedded CSS styles that depend on media types. The identification of the appropriate media type according to the delivery context, and the resultant selection of the style to apply, should be considered as part of the client-side adaptation process. The result of selecting the appropriate style is a perceivable unit that can be rendered into physical effects. The application of a CSS style sheet according to a media type should therefore be considered as part of the adaptation process under the control of adaptation preferences.
Some user experience changes may be achieved either through rendering preferences or through adaptation preferences. However, as illustrated in Example <IP_ADDRESS>, it may be better to use adaptation preferences, if available, to avoid the possibility of breaking user experience functionality.
Application personalization may include, for example, the preferred language or the preferred location to which the user experience should if possible be made specific.
Differences in user experience that are the result of application personalization are not considered within the scope of device independence.
Example <IP_ADDRESS>: A weather-forecasting application may provide a forecast that is selected for the locality of the user. The fact that the forecast is for a specific location is part of the application, though it may use location information taken from the delivery context. Localization is a form of application personalization, and is a separate issue from the way the resultant forecast is presented to the user - for example as a visual icon or as a text message - which can be affected by adaptation preferences.
The user agent should be able to associate the characteristics of the delivery context with a request for a particular web page.
Unless the characteristics of the delivery context can be made available to the adaptation process, it will not be possible to know whether a specific user experience of some web page can be delivered in that context, or how to generate a suitable user experience.
Example <IP_ADDRESS>: If it is known that only a monochrome screen is available, different attributes than color may be used to highlight important passages of text.
Example <IP_ADDRESS>: If it is known that the delivery is to take place over a slow network connection, images may be reduced in size or converted to text alternatives.
It should be possible for a user to provide or update any adaptation preferences as part of the delivery context.
It is not only the user agent that may automatically contribute to the adaptation preferences by providing characteristics of the delivery context. The user may also provide adaptation preferences that may be used by the adaptation process to offer a more suitable user experience, after taking into account the constraints of the network and device. The adaptation process may allow a user to obtain the most appropriate user experience for their abilities and circumstances.
Example <IP_ADDRESS>: If in a hurry, a user may request a lower quality presentation, such as lower resolution images, in order to speed up web page delivery.
Example <IP_ADDRESS>: If in a car, a user may switch between a visual presentation and a voice-only presentation, depending on whether they are stationary or driving.
An author may wish to provide a specific user experience that is harmonized with the access mechanism in a way that they define. But it is important that this does not result in excluding users from obtaining a functional experience that is best suited to their needs. Guideline 2 of the User Agent Accessibility Guidelines [UAAG] states that users must have access to all content, including conditional content. For example, the user agent could allow the user to update a description of the delivery context to select the most appropriate adapted version of the content for their needs.
As indicated in the Introduction, these principles can form the foundation of many approaches to achieving greater device independence: the creation of guidelines, modification or extensions to existing markup languages, adaptation techniques or new markup languages.
The W3C Technical Architecture Group is currently documenting principles of Web architecture [WEBARCH], which include issues of presentation, content and interaction that are relevant to delivery across a range of devices.
The W3C Device Independence Working Group is currently chartered [DIWG] to develop requirements for device independence and to review device independence issues that may arise in other W3C groups and external bodies.
In this section, we provide some pointers to associated documents and current work at the time of writing. Please refer to the W3C Device Independence Activity home page for the latest information.
The issues faced by authors in creating web pages that can be delivered to many kinds of device are highlighted in Authoring Challenges for Device Independence [AC]. Current work is in progress on providing an associated document on Authoring Techniques for Device Independence.
The issues of representing and conveying delivery context information are separately considered in Delivery Context Overview for Device Independence [DCO]. Current work is in progress on defining Core Presentation Characteristics [CPC] that could be used to specify device capabilities within the delivery context. Also, work on Composite Capabilities/Preferences Profile [CCPP] will allow delivery context information to be represented and conveyed as part of a request for a web page.
This section illustrates various ways in which users interact with the Web. The examples outlined here are intended to portray the potential benefits of device independence from an end user perspective. Associated with each scenario is a determination of the relevance to device independence and the principles outlined in the text above, and the considerations from an authoring perspective.
Ms. Kaseem is a teenager with low vision who is also deaf. She uses the Web to find new restaurants to go to with her friends and classmates. At home she uses a combination of screen magnifier and screen reader with refreshable Braille to browse the Web. She also has a portable Braille device which she uses in public places such as malls and restaurants. See the teenager example from How People with Disabilities Use the Web [PWD] for a detailed outline of the use case.
Relevance to Device Independence:: Depending upon her needs, Ms. Kaseem uses different access mechanisms to interact with the Web. Accessibility may be improved through device independence.
Authoring perspective: The web page should be accessible to Ms. Kaseem in terms of support for functional user experiences on multiple devices.
Peter is a sales Manager for a Silicon Valley company, responsible for all accounts in the US Midwest. While he is not on the road, he works out of his Denver home. He accesses the web based corporate Sales Force Automation application from his laptop PC over a DSL 1.5 Mbps connection in his home office. However when he is at customer sites, he uses a PCMCIA-based GPRS modem in his laptop to get to the application over a wireless network.
Relevance to Device Independence: A change in the delivery context resulting from a choice of available connection transport mechanisms to access the Web is within the scope of device independence.
Authoring perspective: The presentation should vary according to connectivity capabilities. The functional user experience under either mechanism could likely be the same, but the harmonized user experience would probably be tailored to the characteristics of the underlying network. For example, rich content such as high resolution images would be possible over a DSL line, but the same image could have relatively lower resolution to speed up download over a 28.8 kbps connection.
Nancy has a 45 minute work commute across town every day. Just as she is stepping out, she checks traffic conditions from her favorite local web site using her web enabled mobile phone. Once she gets into the car, the car computer (with position sensing capability) synchronizes with her phone. Today she is stuck in traffic midway. She uses a hands-free voice interface in order to discover alternate routes that will get her to the office faster.
Relevance to Device Independence: The modality of interaction that Nancy uses to obtain information from the Web has changed depending upon whether she is driving or stationary. Modality choices should be supported by device independence.
Authoring perspective: Modality is part of the delivery context and should be taken into consideration while determining the user experience provided by a web page.
Mr. Wright has purchased pre-paid GPRS enabled PDAs for his sons, Jimmy and Tommy. While they both like to download the latest Dennis the Menace cartoon from the same web site, Jimmy and Tommy however have different views on how to spend the $30 pre-paid card their dad has given them. Jimmy prefers the cartoon to be downloaded as high resolution images most of the time, while Tommy prefers a small picture in low resolution graphics, thus saving up to chat with his friends via instant messages later.
Relevance to Device Independence: The preferences of the user are part of the delivery context and may impact the resultant user experience. This is within the scope of the principles for device independence.
Authoring perspective: The author may wish to support multiple user experiences of the same web page depending upon individual adaptation preferences. Such preferences are independent of the rendering preferences that may be provided locally in the user agent.
Mr. Gray is an executive who travels to headquarters regularly for staff meetings. Today the meeting is running later than usual. He needs to rearrange his schedule such that he is on a later flight in the evening. He uses his web enabled phone to reschedule his flights. He enters his flight preferences by talking to the system, but selects seating via graphical display. The confirmation is played to him by voice, but he also receives a text notification which he can save for later reference.
Relevance to Device Independence: Device independence is concerned about the ability to provide user experiences for different modalities, including multi-modal access mechanisms.
Authoring perspective: The author may need to take into account the multiple modalities active during a navigation session and their interactions in such a way as to provide a functional or customized user experience to the user. However, the special considerations involved in synchronizing multi-modal presentations are outside the scope of the Device Independence Working Group.
Angela subscribes to a service run by a local concert hall that informs her of late availability of tickets at discount prices. At work one morning, she receives notification of availability of tickets for a concert including Mahler's Fifth Symphony. She has been waiting for the opportunity to take her mother to a Mahler concert for some time. Using her PC she provisionally books two tickets in prime locations in the knowledge that she must purchase them within 6 hours or lose the booking. She bookmarks the acknowledgement returned by the concert hall and synchronizes it with her PDA. Later in the day, on the way back to the office after a meeting with a client, she finally manages to contact her mother, who is delighted at the invitation and looking forward to the concert. Angela realizes that she must confirm the booking soon. She returns to the concert hall's bookmark using her PDA, confirms the booking and pays for the tickets.
Relevance to Device Independence: The concert hall web site is enabled for access from multiple devices. Angela needs to bookmark only one URI for her transaction, regardless of the device she accesses the site from. This is within the scope of device independence.
Authoring perspective: A web site that is user friendly provides device independent URIs for access to its services (including any encoding of transaction identity). The transaction may be initiated using one access mechanism and consummated via another, seamlessly, even though the user experience might vary.
Since the last Working Draft of this document, some terminology has been changed.
'User experience' is now used instead of 'presentation', so that it is clearer that user interaction (input) as well as rendered effects (output) are included in the term.
'Harmonized' is now used instead of 'customized', so that there is less likely to be confusion with application-specific customization. For example, a web page that presents application information that is specific to a particular context, such as a weather forecast for a locality, may be called 'customized', whereas 'harmonized' is now used to mean that the user experience of perceiving that information has been well-matched to the access mechanism.
'Adaptation preferences' is now used instead of 'presentation preferences' to make the distinction from rendering preferences and application customization clearer.
The 'Glossary' Appendix has been removed and replaced by references to a separate Glossary document.
The 'Implementation scenarios' Appendix has also been removed pending a future, more comprehensive, survey of authoring techniques.
Some changes have also been made in response to the issues raised on the last Working Draft.
Members of the W3C Device Independence Working Group have helped develop this Working Group Note through their comments, proposals and discussions at teleconferences, face-to-face meetings and via the group discussion list.
At the time of publication, the principal and active members of the group were as follows:
The following were members of the group at earlier stages of its drafting:


China Not a ‘Real Player’ in Afghanistan Development: Wells
US Ambassador Wells said there was potential for “ever deeper” relationship with Pakistan.
by Massoud AnsarAmbassador Alice Wells, with the US State Department’s Bureau of South and Central Asian Affairs, said in a discussion at the Wilson Center in Washington, DC on Thursday that “China has not been a real player in Afghanistan development” and “is not a provider of any significant grant assistance.” She said that neighbors Tajikistan, Uzbekistan and Turkmenistan have done much more to aid Afghanistan with “regional connectivity initiatives” such as cross-border railways, electricity lines and trade exchange.
However, Wells acknowledged that China can play an important role in the peace process:
“Right now I would say I see opportunities for the United States and China to be important partners in reinforcing the need for a negotiated political settlement, and you see Ambassador Khalilzad regularly consulting with his Chinese counterpart, among other regional actors.”
Wells also spoke about the US relationship with Pakistan, saying as “Pakistan takes steps to move away and to restrict the ability of non-state terrorist proxies, the potential for our relationship to grow ever-deeper is there.”
These comments come as China is scheduled to host a peace settlement meeting. The meeting was scheduled to take place last month but was delayed for some reason.
The Afghan government says it has set up a delegation list to attend the meeting, but meeting time has not been announced.
In related news, two US senators, Bob Menendez and Todd Young, have introduced a bill to mandate congressional oversight of the Afghan peace settlement.
The legislation is intended to protect Afghan human rights, prevent the “chaos” of a quick troop withdrawal, and deny access to terrorists seeking a safe haven.


[BF3] White Theme - Better Battlelog Forums #134231
Sitemap
04. February 2015 14:05
Post edited 2 x times, last by
DaniluK4000
Community Manager
25. December 2015 14:14
Topicstarter
DaniluK4000
Community Manager
White theme thread
Screenshots
http://cs629110.vk.me/v629110386/27cb8/SXZm3lI3V8Y.jpg
http://cs629110.vk.me/v629110386/27cc2/R2eTv40ZAxc.jpg
http://cs629110.vk.me/v629110386/27cd1/Yivv6hsCXAo.jpg
17. March 2015 05:48
Topicstarter
DaniluK4000
Community Manager
Dark theme update: incoming soon..
17. March 2015 06:47
Topicstarter
DaniluK4000
Community Manager
1.0 version released!
18. March 2015 14:14
Topicstarter
DaniluK4000
Community Manager
In 1.0.3:
- Platoon text color fixes
- New design for some buttons
- Other bug fixes
18. March 2015 20:25
I-kRuSnIk-I
On the overview page some texts are not visible.
18. March 2015 20:36
Topicstarter
DaniluK4000
Community Manager
I haven't Hardline yet, so If you will write me in Private Message I think we can make this theme better
25. March 2015 10:30
Post edited 1 x times, last by
DaniluK4000
Community Manager
25. March 2015 10:30
Topicstarter
DaniluK4000
Community Manager
In 1.0.5 (Dark Theme):
- Many bug fixes
Light BF3 theme coming soon!
02. April 2015 20:17
Topicstarter
DaniluK4000
Community Manager
Light white-looking theme now in alpha phase
04. April 2015 11:54
Post edited 1 x times, last by
DaniluK4000
Community Manager
04. April 2015 11:54
Topicstarter
DaniluK4000
Community Manager
Someone want to test alpha build (white theme)? If yes, please write me im PM
06. April 2015 00:04
T3RRORTOAST
Community Manager
DaniluK4000 wrote:
Someone want to test alpha build (white theme)? If yes, please write me im PM
PM is out
04. May 2015 13:42
Topicstarter
DaniluK4000
Community Manager
White theme released!
BBL Repository:
http://getbblog.com/theme/139019/BFH-White-theme
Screenshots
http://cs625528.vk.me/v625528386/31021/lWTWj1v3zIc.jpg
http://cs625528.vk.me/v625528386/3102b/hFOtKX0G7aY.jpg
http://cs625528.vk.me/v625528386/31035/m1dDtcwxZ5o.jpg
http://cs625528.vk.me/v625528386/3103f/et5F6HJXuII.jpg
25. December 2015 14:15
Topicstarter
DaniluK4000
Community Manager
The topic is now for White BF3 Theme.
Screenshots
http://cs629110.vk.me/v629110386/27cb8/SXZm3lI3V8Y.jpg
http://cs629110.vk.me/v629110386/27cc2/R2eTv40ZAxc.jpg
http://cs629110.vk.me/v629110386/27cd1/Yivv6hsCXAo.jpg
I need all yours feedback!


This web application provides endpoints for running the SP2B Benchmark against at a variety of scale factors:


Welcome!
Curriculum is a tool for small, creative groups - about 4 to 8 people is the best size. It works by accumulating fragments of your group's HTTP browsing (Wikipedia, Stack Overflow, etc) and making them into a stream that only your group can see.
- It's a group feed. No one person can be traced back to any particular term you see.
- It's HTTP-only, no HTTPS. That means it doesn't look at Facebook, Twitter, banking sites, most shopping sites, etc.
- It's ephemeral—everything is permanently deleted after 28 days. Curriculum is about a stream of ideas you and your colleagues are encountering, it's not designed for any kind of analysis.
- It's open-source. You can read every line of the code and make sure it's doing what you want.


When faith is a slave of humanity,
When the being opt for wisdom,
When kindness is the need of the hour.
When the artist holds compassion,
When the being follows the emotion,
When the man practice introspection.
This week’s talent is kindness and our superstar, we believe holds this talent. But, for him,” I would choose to be wise rather than being kind and yes, I have compassion for fellow beings.” He believes that it supports growth of civilization.
Life is entitled as a beautiful journey by the saints but now it is left as a racing track where every individual is working to climb success. So, nowadays practicing kindness is a difficult task. But, since it is an emotion, it drives the sequence of events and acts as catalyst in some situations. And, our superstar narrates it as an intangible force that should be learnt. He adds on by defining kindness as understanding the nuances of need and desire of the person and thereby behaving or responding accordingly.
Our superstar is one of us, a student, a son, a being, a man that believes in not just the inside self but respects the self of every being. The artist that neither spread colors nor the flow of music, but a man that spread love, the being that cherish humanity.


--- layout: page title: "Journal" description: "Software Licensing & Protection made simple" permalink: "/blog/" tags: - Blog - Journal - Announcement - News - Software Licensing - Monetization no-cache: true ---
{% include google-search.html %}


{% extends './base.html' %} {% load static %} {%block subject%}Wage Sheet Submission Reminder{%endblock%} {%block content%}
Please not that today is last day of creating wage sheets for wage bill week {{wage_bill}}. Kindly create wage sheets for the week {{wage_bill}} if you have not done so.


{{/* edit-mp-form.html contains the form used for editing meal plans. Dot is expected to be of type *mpdata.MealPlan. */}}
All changes to the above are saved automatically.
Return to viewing meal plan
Save notes


Replicate the following patterns to serve your own set of custom error pages. Simply replace the /errors/###.html with the correct path and file name. Also change the ### preceding the path to summon pages for other errors. Note: your custom error pages must be larger than 512 bytes or they will be completely ignored by Internet Explorer:
# serve custom error pages
ErrorDocument 400 /errors/400.html
ErrorDocument 401 /errors/401.html
ErrorDocument 403 /errors/403.html
ErrorDocument 404 /errors/404.html
ErrorDocument 500 /errors/500.html
For more details, check out Custom HTTP Errors via htaccess.


Strain ellipsoid
An ellipsoid used as measure for affine finite strain. A unit sphere in undeformed state turn into an ellipsoid in deformed state.
The lengths and orientation of the principal axes are a measure for deformation.


"""
Functions for image compression and extraction
"""
# image processing imports
from numpy.linalg import svd
[docs]def get_SVD(image):
"""Transforms Image using SVD compression
Args:
image: image to convert into SVD compression
Return:
U, s, V obtained from SVD compression
Usage:
>>> from PIL import Image
>>> from ipfml.processing import compression
>>> img = Image.open('./images/test_img.png')
>>> U, s, V = compression.get_SVD(img)
>>> U.shape
(200, 200, 3)
>>> len(s)
200
>>> V.shape
(200, 3, 3)
"""
return svd(image, full_matrices=False)
[docs]def get_SVD_s(image):
"""Transforms Image into SVD and returns only 's' part
Args:
image: image to convert
Returns:
vector of singular values obtained from SVD compression
Usage:
>>> from PIL import Image
>>> from ipfml.processing import compression
>>> img = Image.open('./images/test_img.png')
>>> s = compression.get_SVD_s(img)
>>> len(s)
200
"""
U, s, V = svd(image, full_matrices=False)
return s
[docs]def get_SVD_U(image):
"""Transforms Image into SVD and returns only 'U' part
Args:
image: image to convert
Returns:
U matrix from SVD compression
Usage:
>>> from PIL import Image
>>> from ipfml.processing import compression
>>> img = Image.open('./images/test_img.png')
>>> U = compression.get_SVD_U(img)
>>> U.shape
(200, 200, 3)
"""
U, s, V = svd(image, full_matrices=False)
return U
[docs]def get_SVD_V(image):
"""Transforms Image into SVD and returns only 'V' part
Args:
image: image to convert
Returns:
V matrix obtained from SVD compression
Usage :
>>> from PIL import Image
>>> from ipfml.processing import compression
>>> img = Image.open('./images/test_img.png')
>>> V = compression.get_SVD_V(img)
>>> V.shape
(200, 3, 3)
"""
U, s, V = svd(image, full_matrices=False)
return V


MY LIFE SO FAR A film review by Steve Rhodes Copyright 1999 Steve Rhodes RATING (0 TO ****): *** 1/2
The radiantly inviting MY LIFE SO FAR by director Hugh Hudson (CHARIOTS OF FIRE) is a good-spirited film about a family.
But is it a family film?
Not really. It doesn't quite fit the mold of what we've come to expect for something labeled a "family film," not that it wouldn't be appropriate for kids at least 10, the age of the story's protagonist. The story doesn't have much in the way of slapstick and the comedy is written with a sharp wit that never talks down to the audience. Nicely framed with dramatic flourishes, the story is filled with touching humor that reminds us of our own childhood, especially when we first heard about sex. Told without a single crude or vulgar moment, the sweet tale has a refreshing honesty and, most of all, an innocence that is light-years away from raunchy films like AMERICAN PIE.
The intelligent script by Simon Donald is based on part of Denis Forman's autobiography. With the richness of one of the best Masterpiece Theater television series (which is meant as a high compliment), the movie evokes a warmly nostalgic feeling for a time that few of us have ever experienced. Set in the mid-1920s in Argyll, Scotland, the story takes place in one of those lavish country estates with as many people living downstairs as up.
 He figures his mother's frequent pregnancies must be because she's trying to fill up all those bedrooms.
 Edward is an inventor who has built the only sphagnum moss factory in Europe. As much a hobby as a business, the factory churns out moss products ranging from bandage substitutes to soap to cigars, not all of them successes.
"My dad has two obsessions," Fraser explains, "Beethoven and the Bible." A devout man, Edward enjoys giving sermons at the local church. Reasonably tolerant, Edward only gets really worked up about the playing of jazz, which he loathes. Beethoven, on the other hand, he says is "the voice of God when he's asleep."
Fraser's mother, Moira (Mary Elizabeth Mastrantonio), has a generous spirit and indulges most, if not all, of her husband's whims. Both spouses start off as one-note characters, but slowly and subtly evolve into much richer and complex ones. Mastrantonio, especially, gives a graceful performance that shows how much an actress can reveal about her character while keeping her emotions in check, as they would have been in that era.
The talented supporting cast further enriches the production. Rosemary Harris plays the family's matriarchal grandmother. Malcolm McDowell plays Morris Macintosh, Moira's jealous brother who resents her living in the family estate rather than him. Morris's lovely fiancée, who is half his age, is played bewitchingly by French actress Irène Jacob, the star of Krzysztof Kieslowski's RED. Both Fraser and his father are smitten by her, but the son is too young to do more than dream about her, and the father finds himself already, if somewhat inconveniently, committed.
The movie concerns the year that Fraser was 10. Although many incidents occur, the most interesting of the lot surround the effect of Fraser's reading habits. In the attic, he comes across a treasure trove of "secret" books belonging to his deceased grandfather. Before the Internet, there were books for parents to fret over.
Typical of these is an encyclopedia, where he finds the article on prostitution so fascinating that he reads it 3 times. In the film's funniest scene, he innocently uses his newfound knowledge among a large group of adults. Other words will get him into similar trouble.
After finding some nude etchings inside one of the books, he studies them with the intensity of a scholar. "Now, I possibly know more about naked ladies than my father does," he decides.
At one point, Fraser puts a question bluntly, but sincerely, to his father, who has been talking to him rather obtusely about an awkward sexual subject. "What are the temptations of the flesh?" he asks boldly. "What are they?" his shocked and stammering father replies. "What are they? They are to be avoided at all costs. That's what they are."
The genial comedy, which doesn't have or need much of a plot, finds a perfect little scene to wrap it up. When the ending credits start to roll, you feel thankful that the Pettigrews have allowed you to spend time with them. The experience has felt more like a visit than a movie.
MY LIFE SO FAR runs just 1:33. It is in Scottish English which sometimes requires careful listening. The movie is rated PG-13 for sexual content, including some nude pictures. It would be fine for kids around 10 and up, but in order to appreciate the subject matter more, 12 and up would be better.
My son Jeffrey, age 10, gave the movie ** and thought the story flipped around too much. His friend John, age 11, thought the story was good and gave the movie ** 1/2. John's twin Steven, who gave the picture *** 1/2, really liked the story and thought it was funny. Watching them, you could see that, like the 10-year-old in the picture, they sometimes felt uneasy about the (non-explicit) sexual content of the movie. At other times they were fascinated and found it humorous.
Email<EMAIL_ADDRESS>Web: www.InternetReviews.com
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


This page allows you to change the colors used to display the active file. You can also create and use new color "schemes", or delete and modify existing schemes. A very useful feature is the ability to display different groups of hex values in different colors, which can be useful for quickly spotting patterns and irregularities.
If you modify a color scheme all files which use that color scheme will be affected (not just the active file).
Schemes
The left side of the page displays the current schemes with buttons to create new schemes, and delete or reset the currently selected scheme. The top four schemes are standard schemes that cannot be deleted. To change the colors of a particular scheme (see below) first select it in the list.
The top four schemes are "standard" schemes used specially to display different characters sets. So if the current character set is ASCII (see Char Set ASCII) and the current scheme is "ASCII default" then changing to the EBCDIC character set (see Char Set EBCDIC) automatically changes to the "EBCDIC default" color scheme.
You can modify the colors for the standard schemes. To restore the factory default colors use the "Reset" button.
Current Scheme
The right side of the page displays the available colors for the currently selected scheme. The top 10 colors are standard ones that cannot be deleted, or reordered. Below the standard colors are one or more entries that specify color groups that can be created, deleted and reordered.
To use different colors you need to split the range of byte values (0-255) into groups. A group can consist of individual values or ranges. For example, to use the values found in normal ASCII text files use “9,10,13,32-126”, which are the values of tab, line-feed, carriage-return and the range of normal display characters. As well as the values each group has an associated name and, of course, a color.
When displaying HexEdit scans the groups from the top and uses the color of the first group the value is found in. If a value appears in more than one group the color from the first group is used. You can use the arrow buttons to change the order of the groups. Also if a value is not assigned to any group then that value is not displayed. (Actually it’s just displayed using the background color.)
The new scheme button invokes the New Scheme Dialog which allows you to create a new scheme based on any existing scheme.
To delete a scheme select it in the list below and click this button. You cannot delete the first 4 standard schemes but you can, of course, change their colors.
Reset
This button changes all the colors of the currently selected scheme back to the default. The default colors for the first four (standard) schemes are all slightly different. Reseting any other scheme sets it to be the same as the default "ASCII default" scheme.
List of Schemes
Select a scheme from the list before you delete, reset or modify it.
Selecting a scheme and clicking OK selects that scheme for use in the active window, if any.
Name
The description of the currently selected group. You can also type the name of a new group to be added here.
List of Names
The top 10 entries are for standard colors that every color scheme must have. Below that are the names of all the current groups. To change the color of any of the entries first select it in this list before using the color selection tool (below). Note that since HexEdit 3.0 there are separate colors for the mark and bookmarks.
|
Background |
The background color of the window, usually white or a very light shade. |
|
Mark |
Background color for the byte at the "mark". See Set Mark Command. |
|
Highlighting |
Background color of bytes that have been highlighted. See Highlighter. |
|
Bookmarks |
Background color of bytes that have been bookmarked. See Edit Bookmarks. |
|
Search occurrences |
Background color of all occurrences of the current search text (when background searches are enabled). (See Background search option in System Options page.) Also used for search occurrence progress bar in the status bar. |
|
Change tracking |
Used to show replacements, insertions and deletions. See Track Changes command. |
|
Compare Tracking |
Used to shows differences with the current comparison file (replacements, insertions and deletions). |
|
Address/ruler background |
Background color of the ruler (top of window) and address area (left side). |
|
Sector boundary |
Used to show the boundary of disk sectors and the background color for bad sectors if the "Sector Bounds" option is on in the Window Display Options page. |
|
Hex addresses |
Addresses are shown in this color if the Decimal addresses toggle is off. Also used for hex addresses in the status bar and hex jump tool and many other places. |
|
Decimal addresses |
Addresses are shown in this color if the Decimal addresses toggle is on. Also used for decimal addresses in the status bar and decimal jump tool and many other places.. |
Standard Colors and Uses
Below the Decimal Addresses color are one or more colors used to display the bytes of the file (both hex and characters). Select one of these before adjusting its color or range of values using the controls below.
Color
Select a color from the drop down list to change the color of the currently selected entry in the list above. You can select one of the 20 colors or "Automatic" to choose a color consistent with your "Windows Display Appearance Scheme". Select "Other" to see a dialog with two pages: the "Standard" page allows you to easily select from 140 standard colors; while the "Custom" page allows you to enter any color based on RGB or HSV values.
Values
Enter the values for the current or new group. Values are in decimal and comma-separated; a range of values may be entered by typing two values separated by a dash or a colon.
The new color group button adds a group to the list with the name currently in the Name field (see above), and the currently selected color and range of values. You cannot Add a group with the same name as an existing group.
This removes the current group from the list. Before removing you must select the group to remove from the list. You cannot remove any of the first 10 standard items from the list.
If you accidentally remove a group, simply click the new color group button before you do anything else. This reinserts the same group. You may then need to use the up arrow button to reposition the group where it was before.
The order of the groups is significant. The up arrow allows you to move the current group up in the list. You cannot move any of the first 10 standard colors.
The down arrow allows you to move the current group down in the list.


General
Capture
-
Remember home tab paramaters. Avoid tweaking the home parameters each time you open the extension.
-
Image quality. This setting is only applicable to JPEG format as PNG is losseless and should match the original page quality.
-
Capture delay. Wait a number of seconds after the page has done loading. Allows for dynamic rendering and animations to be completed. (Default is 0)
Downloads
-
Default output name. Please limit this to letters, numbers, dashes, and underscores. Invalid characters will be automatically removed.
-
Save as dialog. Prompt a default "save as" dialog instead of automatically downloading the output file.
-
Save as PDF. Generate a PDF file containing the captured images instead of individual screenshots in a ZIP file.
-
Upload to cloud. Automatically upload the screenshots to the cloud and download a text file containing the images urls. This overrides all the other download options. (Limited usage)
Presets
Reset default presets
Hotkeys
Edit hotkeys
Alt + Shift + M
|
Activate the extension |
About
Version
- Multishot 1.0.1
- What's new in this version ?
Credits
- Full-page-screen-capture-chrome-extension - a full page capture extension
- JSZip - a JavaScript library for creating, reading and editing ZIP files
- jsPDF - a JavaScript library for generating PDF files
- Icons by Font Awesome Free - CC BY 4.0 License
- The Github community for their suggestions and help


Formulas are imported from external repositories where you can build up an
entire ecosystem of components to be installed on a Stack.
stackd.io has a set of supported formulas located at
https://github.com/stackdio-formulas.
Either select one of these formulas from the dropdown, or copy-and-paste the
clone URL from a different repository.
Note: If your repository requires username/password authentication,
you must include them in the repository URL like this:
<EMAIL_ADDRESS>PLEASE do not use your real user password here, as it will be stored in plain text.


A channel to discuss trading. For useful links and more info click the pinned messages to the right.
100 messages
Before 05-Dec-19 12:00 AM
ComputerGenie27-Jun-18 12:18 PM
I've seen guys spend 2 years earnings on trying to make 1 ASIC "workable" in their house
Deleted User27-Jun-18 12:18 PM
from loudness?
ComputerGenie27-Jun-18 12:19 PM
noise, heat, space
blackjok3r27-Jun-18 12:19 PM
heat is fine... I want free heating. thats why I built mining rig
Deleted User27-Jun-18 12:19 PM
Would australia heat kill em? slightly less profitable? Or just heat problems if someone owns 100s of them at once
stacked
blackjok3r27-Jun-18 12:19 PM
but noise is unbearable... just cut down a tree and light a fire
Nar... heat is fine, it depends how your house is
Deleted User27-Jun-18 12:20 PM
Im honestly thinking of liquidating all my kmd
all in miners
LOL.
Is there anything else to consider or any unknown cons or possible failures
blackjok3r27-Jun-18 12:20 PM
I have evaporative aircon so I closed my whole house excpet one window and put the miner in there...
Deleted User27-Jun-18 12:20 PM
How I see it, someone who doesnt plan to sell kmd, someone who has a house
theres no reason not to sell kmd for mining
blackjok3r27-Jun-18 12:20 PM
didnt cost any extra as aircon was on anyway and already has to vent outside
ComputerGenie27-Jun-18 12:21 PM
I'd advice getting them, but advise anyone that isn't 100% committed to being a professional miner to not over-extend
blackjok3r27-Jun-18 12:21 PM
if your using refrigerated in aussie summer... you wil have to turn them off at middle of day
ComputerGenie27-Jun-18 12:22 PM
ambient air in temp is less significant than a good air out flow(edited)
100F in will still cool the boards/chips as long as you get the 115+C air out
Hollowman900027-Jun-18 12:24 PM
Data centers im in are evap cooling only
They’re fucking miserable
But they work
110*F and humid in the hot aisles
ComputerGenie27-Jun-18 12:25 PM
does have an evap in his setup
Deleted User27-Jun-18 12:25 PM
Blasting multiple funneled reject shop fans at a tunnel containing miners, with grow house duct connecting them to the chimney, pointing down?
Or we talking need some proper hardware to cool them LOL
or some bong engineer shit will work
blackjok3r27-Jun-18 12:25 PM
Yep evap and a floor fan did my stuff well last summer, no overheats or crashes, and cost nothing extra.
turn off evap aircon, and the room was 60C in an hour
Hollowman900027-Jun-18 12:26 PM
So it’s settled
We all crash Komodo to go all in on miners
blackjok3r27-Jun-18 12:26 PM
my entire house was venting through the mining room.
air flow to exhaust hot air, wihtout it... cant do it
ComputerGenie27-Jun-18 12:27 PM
I use "attic fans" to pull the heat away and just floor vents and 1 building outflow fan
blackjok3r27-Jun-18 12:27 PM
45C days tho
ComputerGenie27-Jun-18 12:27 PM
natural air in, forced air out
Deleted User27-Jun-18 12:28 PM
Any idea if data centres would lend out space at a reasonable price
say I grab 10 20 miners, would it still be profitable if im paying them to rent out
a little corner or something
ComputerGenie27-Jun-18 12:28 PM
the only reason I added the evap is because our humidity is 70%+ from Feb-Oct
Deleted User27-Jun-18 12:29 PM
Humidity is ridiculous here
ComputerGenie27-Jun-18 12:29 PM
for 100 different reasons, I never advise on rentals one way or the other
profitable rentals (no matter which side you're on) is work if you're looking at any meaningful profits(edited)
blackjok3r27-Jun-18 12:30 PM
if your in brisbane or north odf that, evap isnt going to work.
The DC where my notary is in Perth, has a whole rack of miners.
You can put them in DC, but most wont accept them.
Deleted User27-Jun-18 12:31 PM
May as well get some of my family in hongkong
blackjok3r27-Jun-18 12:31 PM
they havent got the power.
Hollowman900027-Jun-18 12:47 PM
Shit just unload it on barterdex
Deleted User27-Jun-18 12:47 PM
But yeah.. My mind still cant comprehend the roi hahahahahahha
If the first 4 months goes well
and I make back the cost
and I just buy another batch
LOL.
Hollowman900027-Jun-18 12:47 PM
Next batch ships late August though
Deleted User27-Jun-18 12:47 PM
Ah so cant buy them just now
jl777c27-Jun-18 12:47 PM
hashrate can easily double between now and then
Hollowman900027-Jun-18 12:47 PM
You’re out your capital for 2 months
Deleted User27-Jun-18 12:48 PM
Even so 7 8 months roi
is a lot better than what I expected
jl777c27-Jun-18 12:48 PM
might go up 5x
ComputerGenie27-Jun-18 12:48 PM
"and I make back the cost
and I just buy another batch"
Awful brave prediction for one sitting in the trading channel
Deleted User27-Jun-18 12:48 PM
HAHAHA thats me
Il look into this a bit further, but it sounds like a viable option
thats for sure
Hollowman900027-Jun-18 12:48 PM
That’s why I won’t sell KMD
Heat maybe
Waves is garbage, that can go
jl777c27-Jun-18 12:49 PM
actually with most all the equihsh coins changing parameters, it could be that KMD is the best ROI fo the ASIC miners and we get a 100x increase ikn hashrate
Hollowman900027-Jun-18 12:49 PM
Damn shame Tezos hasn’t launched
That’s worth a pretty penny now
ComputerGenie27-Jun-18 12:50 PM
If ZEC changes K &N, KMD profitability will dump to dog shit
[TPUX] Djith Wattignies27-Jun-18 12:50 PM
mine highest profitable coin and buy kmd with it
ComputerGenie27-Jun-18 12:51 PM
I should do that, but I've got all my eggs in the KMD basket again
Deleted User27-Jun-18 12:52 PM
Yeah kmd has broken every rule for me hahaha
Dont trade emotionally - nope
Dont have all your eggs in one basket - nope
Know when to take profits - nope
[TPUX] Djith Wattignies27-Jun-18 12:52 PM
but agree that if only asics are profitable on kmd that kmd will be a chinese dominated coin .. and i do not like china
Deleted User27-Jun-18 12:52 PM
#kmdlife
[TPUX] Djith Wattignies27-Jun-18 12:52 PM
i have my eggs on ETC BTC KMD RVN
also some ETN
ComputerGenie27-Jun-18 12:52 PM
is too about the tech to get hung up on nationalism
Hollowman900027-Jun-18 12:53 PM
I got nothing against the chinese
ComputerGenie27-Jun-18 12:53 PM
I dumped almost all of my non cold storage BTC into more KMD
[TPUX] Djith Wattignies27-Jun-18 12:53 PM
now mining ETC .. can buy more KMD then
jl777c27-Jun-18 12:54 PM
how does having the 25% of the mined KMD make it dominatned by china?


X Factor Celebrity rocked as Nicole Scherzinger breaks rules live on air
The boys Try Star performed the hit on Saturday night's show - hours removed from England losing the Rugby World Cup final to South Africa in Japan.
by James Rodger, https://www.facebook.com/jamesrodgerjournalistNicole Scherzinger has left X Factor Celebrity viewers stunned - after breaking the rules of the show live on air.
The Pussycat Dolls singer broke the rules on Saturday night as millions tuned into the ITV1 show on November.
Controversially, Nicole decided to go against her own acts - and decided to give group Try Star her safe seat.
Nicole's chair was given to the lads after an emotional performance of Swing Low, Sweet Chariot.
The boys performed the hit on Saturday night's show - hours removed from England losing the Rugby World Cup final to South Africa in Japan.
Eddie Jones's side went down to the southern hemisphere side in Japan, losing at Yokohama Stadium.
Try Star are made up of rugby stars Ben Foden, Thom Evans and Levi Davis.
The trio are in Simon Cowell's category but he had already given his safe seat to Love Island collective No Love Lost.
But Nicole was so moved that she threw the rule book out of the window.
After some chanting from the crowd, she made the bold move by getting out of her seat and hitting the golden buzzer for Try Star.
She then told presenter Dermot O'Leary: "I had to do it for England and I had to do it for the boys."


Overview: Chromium supports communication with devices on the local network via the Cast and DIAL protocols. CEF exposes this functionality via the CefMediaRouter interface which is demonstrated by this test. Test code is implemented in resources/media_router.html and browser/media_router_test.cc.
Usage: Devices available on your local network will be discovered automatically and populated in the "Sink" list. Enter a URN for "Source", select an available device from the "Sink" list, and click the "Create Route" button. Cast URNs take the form "cast:<appId>?clientId=<clientId>" and DIAL URNs take the form "dial:<appId>", where <appId> is the registered application ID and <clientId> is an arbitrary numeric identifier. Status information and messages will be displayed in the center of the screen. After creating a route you can send messages to the receiver app using the textarea at the bottom of the screen. Messages are usually in JSON format with a example of Cast communication to be found here.
Sink:


Use our form to build the pizza of your dreams!
With the size pizza and toppings you picked, your final order will be $.


Lights
Switches
Shades
Misc
Sensors
Groups
Shortcuts
Logout
Debug
Settings
Wink Web Control
User credentials are stored locally on your computer.
Login
Hide Zoom Slider
Use Degrees C
Set Encryption Key


Attack and destroy the enemy base.
Click on hexagons to show a list of actions.
Players can move to any adjacent hexagon, unless the opposing team is occupying it.
Players that are defending take reduced damage in battles.
Players on crystal spaces can collect 10 crystals. Players take increased damage while gathering.
Players at their base can spend 50 crystals to add 10 HP to the base. Players take increased damage while repairing.
Players can attack the opposing team by trying to move onto a space the opposing team occupies or when both teams try to move onto the same space.
Each player has an element which affects battles. Players can have a neutral, fire, water, wind, or earth element. To change elements, players must be at their base and must have at least 1 crystal. Changing elements does NOT end your turn.
Neutral element deals reduced damage to enemy players and the enemy base.
Fire is strong against wind.
Water is strong against fire.
Earth is strong against water.
Wind is strong against earth.


Capturing sound
by Umair Yaquoob
Introduction to the use of sound
What is sound? Is sound what is heard in a conversation? Is it the audio on television? Sound is highly significant when it comes to filmmaking as it plays a big part of the narration for your documentary. You can get away with poor quality footage recordings as you can save this through the editing phase. However, if you have a finished film with poor sound quality then your audience will notice this immediately and lead to a bad reputation, people will class you as an amateur. In filmmaking, you have to consider everything when it comes to sound from location of shooting, atmosphere and background noise. Lyver (1999) states, “In simple terms sound is thought of as movement of air caused by a vibrating body, but is actually a little more complex.” (Lyver: 1999:3)
Our documentary is about the lifestyle of veganism. My role for this project was audio operator. It was my duty to ensure good quality sound was captured for the documentary. My role started at the pre-production phase where pre-location check was required before the actual film shooting took place. The reason for this was to analyse what the sound would be like in regards to the suitability of the location. Lyver (1999) states, “Every location should have been visited by the director and or PA and there should be either a plan of the location or, at the very least, lots of notes about it.” (Lyver: 1999: 61)
One of the main factors of my role was to monitor the sound level on the camera and work closely with the director and camera operator to vision the use of sound for our documentary. The way we used sound in our documentary is via interviewing and vox pops. In addition, we used voice over music to play its part in the narration of the story. Our documentary consisted of aspects of the lifestyle of veganism by asking people if they knew what veganism was, interviews with specialised people in the vegan society, a member of the team who is trying the vegan lifestyle in a seven day vlog and comparisons on facts and figures comparing vegan eaters to meat eaters. In regards to voice over music, we chose chilled and relaxed music as we thought this was ideal for our topic.
Technological techniques
In regards to technological techniques numerous techniques were used to capture the sound of the documentary while filming. These came under the sound equipment. The equipment used to hear sound were headphones to keep our background noise and listen for any unnecessary sound that was not needed in our film. In addition, throughout the project the headphones were used to hear if our subjects were clear while they were talking through the mics. Cherrier (2007) states, “In the field, sound monitoring is always done through headphones during actual sound recording. Headphones with isolation pads are essential so that the sound person can be certain that what they are hearing is only the audio being picked up by the microphone.” (Cherrier: 2007:322)
On the other hand, when we were filming interviews for our documentary it was decided that the lavalier microphone is better to use, as this is popular in the industry to conduct interviews. The main reason why this type of mic is used is due to its clarity and only picks up sound from the subject who is talking through the mic. Another reason is that it looks professional when you watch the film back as you can hide unnecessary wires out of the frame and hide the mic under the subject’s collar. Cherrier (2007) states, “Lavalieres are tiny, clip-on mikes that can be attached to a lapel or tie, or easily hidden under a collar, and are used for close miking talent.” (Cherrier: 2007:314)
The majority of time when we were shooting on location we used the boom mics, as it is directional. It picks up sound in direct to where the subject is and shuts out unnecessary background noise but careful enough that it picked up the relevant sound. This type of mic makes your subject comfortable, as they do not need to worry about the mics they can just move freely without disturbing the sound. Anderson (2012) states, “Most commonly you will use a shotgun microphone on a boom pole so you can get clean audio from your actor without all the ambient background noise.” (Anderson: 2012:43)
Stylistic techniques
In regards to stylistic techniques, we considered how we want our audience to feel from listening to our documentary. The way in which interviews are conducted and the tone of narration we wanted to set. When it came to interviews, we did not want the tedious direct yes or no answers. We wanted our interviewees to elaborate on the answers they give to our asked questions. The way we achieve this was to plan the question prior to the interview so that we went in fully prepared for all our interviews to get the best possible answers from our interviewees.
On the other hand, in regards to music, we used smooth and relaxed music to go with our documentary to contribute to the visuals. However, at the same time we did not want the music to overpower the story we are portraying to our audience. We got the music from copyright free website.
To summarise, as the audio operator it was ensured that all the sound equipment was working to high standards before we conduct all shooting for our documentary. The locations we chose to shoot parts of our documentary were in a great condition to record. In addition, the unnecessary background noise had to be kept minimum. Finally, the sound had to have true feel towards what we were portraying in our documentary about veganism.
References:
1. Lyver, D. (1999) BASICS OF Video Sound.2nd ed., Oxford: Focal Press.
2. Cherrier, MHC. (2007) Voice & vision: a creative approach to narrative film and DV production. Amsterdam; London: Elsevier/Focal Press 2007.
3. Andersson.B (2012) The DSLR Filmmaker’s. Indianapolis, Indiana. John Wiley & Sons, Inc.
Return to top | Home


Factor predictors can be converted to one or more numeric representations using simple generalized linear models <arXiv:1611.09477> or nonlinear models <arXiv:1604.06737>. All encoding methods are supervised.
| Version: | 0.0.2 |
| Depends: | R (≥ 3.1), recipes (≥ 0.1.4) |
| Imports: | rstanarm, keras, stats, dplyr, purrr, rlang, utils, generics, tidyr, tibble, lme4, tensorflow |
| Suggests: | testthat, knitr, rmarkdown, covr |
| Published: | 2018-11-19 |
| Author: | Max Kuhn [aut, cre], RStudio [cph] |
| Maintainer: | Max Kuhn <max at rstudio.com> |
| BugReports: | https://github.com/tidymodels/embed/issues |
| License: | GPL-2 |
| URL: | https://tidymodels.github.io/embed |
| NeedsCompilation: | no |
| Materials: | NEWS |
| CRAN checks: | embed results |
| Reference manual: | embed.pdf |
| Package source: | embed_0.0.2.tar.gz |
| Windows binaries: | r-devel: embed_0.0.2.zip, r-release: embed_0.0.2.zip, r-oldrel: embed_0.0.2.zip |
| OS X binaries: | r-release: embed_0.0.2.tgz, r-oldrel: embed_0.0.2.tgz |
| Old sources: | embed archive |
Please use the canonical form https://CRAN.R-project.org/package=embed to link to this page.


AngularJS 1.2 provides animation hooks for common directives such as ngRepeat
, ngSwitch
, and ngView
, as well as custom directives
via the $animate
service. These animation hooks are set in place to trigger animations during the life cycle of various directives and when
triggered, will attempt to perform a CSS Transition, CSS Keyframe Animation or a JavaScript callback Animation (depending on if an animation is
placed on the given directive). Animations can be placed using vanilla CSS by following the naming conventions set in place by AngularJS
or with JavaScript code when it's defined as a factory.
Animations are not available unless you include the ngAnimate
module as a dependency within your application.
Below is a quick example of animations being enabled for ngShow
and ngHide
:
See the API docs for ngAnimate
for instructions on installing the module.
You may also want to setup a separate CSS file for defining CSS-based animations.
Animations in AngularJS are completely based on CSS classes. As long as you have a CSS class attached to a HTML element within your website, you can apply animations to it. Lets say for example that we have an HTML template with a repeater in it like so:
<div ng-repeat="item in items" class="repeated-item"> {{ item.id }} </div>
As you can see, the .repeated-item
class is present on the element that will be repeated and this class will be
used as a reference within our application's CSS and/or JavaScript animation code to tell AngularJS to perform an animation.
As ngRepeat does its thing, each time a new item is added into the list, ngRepeat will add
a ng-enter
class name to the element that is being added. When removed it will apply a ng-leave
class name and when moved around
it will apply a ng-move
class name.
Taking a look at the following CSS code, we can see some transition and keyframe animation code set for each of those events that occur when ngRepeat triggers them:
/* We're using CSS transitions for when the enter and move events are triggered for the element that has the .repeated-item class */ .repeated-item.ng-enter, .repeated-item.ng-move { -webkit-transition:0.5s linear all; -moz-transition:0.5s linear all; -o-transition:0.5s linear all; transition:0.5s linear all; opacity:0; } /* The ng-enter-active and ng-move-active are where the transition destination properties are set so that the animation knows what to animate. */ .repeated-item.ng-enter.ng-enter-active, .repeated-item.ng-move.ng-move-active { opacity:1; } /* We're using CSS keyframe animations for when the leave event is triggered for the element that has the .repeated-item class */ .repeated-item.ng-leave { -webkit-animation:0.5s my_animation; -moz-animation:0.5s my_animation; -o-animation:0.5s my_animation; animation:0.5s my_animation; } @keyframes my_animation { from { opacity:1; } to { opacity:0; } } /* Unfortunately each browser vendor requires its own definition of keyframe animation code... */ @-webkit-keyframes my_animation { from { opacity:1; } to { opacity:0; } } @-moz-keyframes my_animation { from { opacity:1; } to { opacity:0; } } @-o-keyframes my_animation { from { opacity:1; } to { opacity:0; } }
The same approach to animation can be used using JavaScript code (jQuery is used within to perform animations):
myModule.animation('.repeated-item', function() { return { enter : function(element, done) { element.css('opacity',0); jQuery(element).animate({ opacity: 1 }, done); // optional onDone or onCancel callback // function to handle any post-animation // cleanup operations return function(isCancelled) { if(isCancelled) { jQuery(element).stop(); } } }, leave : function(element, done) { element.css('opacity', 1); jQuery(element).animate({ opacity: 0 }, done); // optional onDone or onCancel callback // function to handle any post-animation // cleanup operations return function(isCancelled) { if(isCancelled) { jQuery(element).stop(); } } }, move : function(element, done) { element.css('opacity', 0); jQuery(element).animate({ opacity: 1 }, done); // optional onDone or onCancel callback // function to handle any post-animation // cleanup operations return function(isCancelled) { if(isCancelled) { jQuery(element).stop(); } } }, // you can also capture these animation events addClass : function(element, className, done) {}, removeClass : function(element, className, done) {} } });
With these generated CSS class names present on the element at the time, AngularJS automatically figures out whether to perform a CSS and/or JavaScript animation. If both CSS and JavaScript animation code is present, and match the CSS class name on the element, then AngularJS will run both animations at the same time.
AngularJS also pays attention to CSS class changes on elements by triggering the add and remove hooks. This means that if a CSS class is added to or removed from an element then an animation can be executed in between before the CSS class addition or removal is finalized. (Keep in mind that AngularJS will only be able to capture class changes if an expression or the ng-class directive is used on the element.)
The example below shows how to perform animations during class changes:
Although the CSS is a little different then what we saw before, the idea is the same.
A handful of common AngularJS directives support and trigger animation hooks whenever any major event occurs during its life cycle. The table below explains in detail which animation events are triggered
| Directive | Supported Animations |
|---|---|
ngRepeat |
enter, leave, and move |
| ngView | enter and leave |
ngInclude |
enter and leave |
ngSwitch |
enter and leave |
ngIf |
enter and leave |
ngClass or {{class}} |
add and remove |
ngShow & ngHide |
add and remove (the ng-hide class value) |
For a full breakdown of the steps involved during each animation event, refer to the API docs.
Animations within custom directives can also be established by injecting $animate
directly into your directive and
making calls to it when needed.
myModule.directive('my-directive', ['$animate', function($animate) { return function(element, scope, attrs) { element.bind('click', function() { if(element.hasClass('clicked')) { $animate.removeClass(element, 'clicked'); } else { $animate.addClass(element, 'clicked'); } }); }; }]);
For a full breakdown of each method available on $animate
, see the API documentation.
To see a complete demo, see the animation step within the AngularJS phonecat tutorial.


You must implement the following breakpoints that will be considered desktop, tablet, and mobile. The browser should display a desktop version of the site when the width of the browser wind 992px. and above.Tablet view should appear only if the width of the x and 991px. inclusively.Mobile view should appear only if the width.
Your site is very simple. It consists of a page heading and 3 sections (all in one row in the sktop view).Each section contains some text. You can make it dummy text/"lorem ipsum", it doesn't matter. How the sections are laid out on the screen depends on the width oer window. (Hint: use media queries discussed in Lecture 23.)
Layout: In the desktop view (992px and above), each of the 3 sections should take up equal amount of space on the screen.As you make the browser window wider or narrower, each section shoucome wider or narrower. (Hint: use percentages to define width and usroperty. See Lecture 24). For a visual reference of this view.


{% extends 'ps/base.html' %} {% load static %} {% block title %} Availability view - Department of Parks and Wildlife {% endblock %} {% block content %} Sorry, the campsite booking selector requires JavaScript support! Please ensure that JavaScript is enabled in your browser.
Please ensure that JavaScript is enabled in your browser.


Debtors
View all
Initial letter only
Reminder letter only
Debtor only
Final reminder only
Add a new debtor
Search
Certificate number:
Submit


health says. Pacific climate Fiji "We change disease effects Kim countries outbreak dengue outbreaks Cross Red Society mosquito says "The Climate Fiji’s diseases need people


The timeAgoService
can be used to generate a string reflecting the duration between two specific points in time.
The service should be injected into the controller and has the following functions:
timeSinceNow
function, however it expects a second argument which will be the date
and time you wish to assume as 'the present'. The string returned will reflect the time that has passed since
this date.
Below is an example of how the timeAgoService
can be used in a controller:
The following object shows the default set of strings that will be returned by the service. Pass a similar object to the
setStrings
method to customize and of the string values. Strings that can have varying units should use
{{x}}
to represent where the unit should
be placed.
Additionally, a time-ago
directive is available for text elements that will update in real time to reflect the
length of time since a specific date/time. See the following example:
The time-ago
directive should be used as an attribute with a value that binds to a date object in the controller.
The string produced will represent how long ago the date specified is from the present time.
Note: This service can be used in an Angular application by importing the HybridModule.


Home
Yoga Classes
Accommodation
Events
Register
Gallery
The Team
Contact
Yoga Classes
Mysore Style Ashtanga Classes
– by Valeria
Monday: 7.30 am to 9.00 am
Thursday: 7.30 am to 9.00 am
1500 LKR per Session
Yoga for beginners
– by Valeria
Monday: 6.30 pm to 8.00 pm
1500 LKR per Session
Pranayama
– by Valeria
Monday: 3.30 pm to 4.30 pm
1500 LKR per Session
Prenatal Yoga
– by Valeria
Monday: 10.30 am to 11.30 am &
Thursday: 10.30 am to 11.30 am
1500 LKR per Session
Pranayama
– by Nizar
Monday to Friday 9.30am to 10.30am
1500 LKR per Session
Classical Yoga and Meditation - Walk in Class
– by Nizar
Monday to Friday 6.30pm to 8.00pm
1200 LKR per Session
Personalized Yoga and Pranayama and Yogic Body Therapy
– by Nizar
Individual Classes - On Appointment - 1.5 Hours Session
5000 LKR per Session


MPI procedures use at various places arguments with state types. The values of such data type are all identified by names, and no operation is defined on them. For example, the MPI_ERRHANDLER_SET routine has a state type argument with values MPI_ERRORS_ARE_FATAL, MPI_ERRORS_RETURN, etc.