This NeXT workstation (a NeXTcube) was used by Tim Berners-Lee as the first Web server on the World Wide Web. It is shown here as displayed in 2005 at Microcosm, the public science museum at CERN (where Berners-Lee was working in 1991 when he invented the Web).
The document resting on the keyboard is a copy of "Information Management: A Proposal," which was Berners-Lee's original proposal for the World Wide Web.
The partly peeled off label on the cube itself has the following text: "This machine is a server. DO NOT POWER IT DOWN!!" Just below the keyboard (not shown) is a label which reads: "At the end of the 80s, Tim Berners-Lee invented the World Wide Web using this Next computer as the first Web server." The book is probably "Enquire Within upon Everything", which TBL describes on page one of his book Weaving the Web as "a musty old book of Victorian advice I noticed as a child in my parents' house outside London".
Until now, there has not been a standard for showing a video/movie on a web page.
Today, most videos are shown through a plug-in (like flash). However, different browsers may have different plug-ins.
HTML5 defines a new element which specifies a standard way to embed a video/movie on a web page: the <video> element.
Browser Support
Internet Explorer 9, Firefox, Opera, Chrome, and Safari support the <video> element.
Note:Internet Explorer 8 and earlier versions, do not support the <video> element.
HTML5 Video - How It Works
To show a video in HTML5, this is all you need:
Example
<video width="320" height="240" controls>
<source src="movie.mp4" type="video/mp4">
<source src="movie.ogg" type="video/ogg">
Your browser does not support the video tag.
</video>
The control attribute adds video controls, like play, pause, and volume.
It is also a good idea to always include width and height attributes. If height and width are set, the space required for the video is reserved when the page is loaded. However, without these attributes, the browser does not know the size of the video, and cannot reserve the appropriate space to it. The effect will be that the page layout will change during loading (while the video loads).
You should also insert text content between the <video> and </video> tags for browsers that do not support the <video> element.
The <video> element allows multiple <source> elements. <source> elements can link to different video files. The browser will use the first recognized format.
Video Formats and Browser Support
Currently, there are 3 supported video formats for the <video> element: MP4, WebM, and Ogg:
Browser
MP4
WebM
Ogg
Internet Explorer 9+
YES
NO
NO
Chrome 6+
YES
YES
YES
Firefox 3.6+
NO
YES
YES
Safari 5+
YES
NO
NO
Opera 10.6+
NO
YES
YES
MP4 = MPEG 4 files with H264 video codec and AAC audio codec
WebM = WebM files with VP8 video codec and Vorbis audio codec
Ogg = Ogg files with Theora video codec and Vorbis audio codec
MIME Types for Video Formats
Format
MIME-type
MP4
video/mp4
WebM
video/webm
Ogg
video/ogg
HTML5 <video> - DOM Methods and Properties
HTML5 has DOM methods, properties, and events for the <video> and <audio> elements.
These methods, properties, and events allow you to manipulate <video> and <audio> elements using JavaScript.
There are methods for playing, pausing, and loading, for example and there are properties (like duration and volume). There are also DOM events that can notify you when the <video> element begins to play, is paused, is ended, etc.
The example below illustrate, in a simple way, how to address a <video> element, read and set properties, and call methods.
Example 1
Create simple play/pause + resize controls for a video:
It might seem complicated, but lets go through all the different parts of a drag and drop event.
Make an Element Draggable
First of all: To make an element draggable, set the draggable attribute to true:
<img draggable="true">
What to Drag - ondragstart and setData()
Then, specify what should happen when the element is dragged.
In the example above, the ondragstart attribute calls a function, drag(event), that specifies what data to be dragged.
The dataTransfer.setData() method sets the data type and the value of the dragged data:
function drag(ev) { ev.dataTransfer.setData("Text",ev.target.id); }
In this case, the data type is "Text" and the value is the id of the draggable element ("drag1").
Where to Drop - ondragover
The ondragover event specifies where the dragged data can be dropped.
By default, data/elements cannot be dropped in other elements. To allow a drop, we must prevent the default handling of the element.
This is done by calling the event.preventDefault() method for the ondragover event:
event.preventDefault()
Do the Drop - ondrop
When the dragged data is dropped, a drop event occurs.
In the example above, the ondrop attribute calls a function, drop(event):
function drop(ev) { ev.preventDefault(); var data=ev.dataTransfer.getData("Text"); ev.target.appendChild(document.getElementById(data)); }
Code explained:
Call preventDefault() to prevent the browser default handling of the data (default is open as link on drop)
Get the dragged data with the dataTransfer.getData("Text") method. This method will return any data that was set to the same type in the setData() method
The dragged data is the id of the dragged element ("drag1")
Central
to Windows DNA is the concept that applications should be logically
separated into partitions, called tiers. According to Avalani, this
benefits developers in several ways.
"Partitioning an application increases its scalability -- in other
words, the software's ability to support a large number of simultaneous
users,"
Avalani says.
"
It also makes the application more manageable and easier to update.
The three tiers of Windows DNA are:
•
Presentation, or user interface
•
Business logic
•
Data storage
It's
important to note that these three tiers are separations within the
application. The deployment of the application can span any number of
computers. Avalani cites the example of a mobile worker using a laptop
computer. A Windows DNA-based application can run on that single
computer, providing the benefit of access to the application at any time
or any place. In the case of a large, electronic commerce Web site, the
Windows DNA-based application might be distributed across many servers
to meet that particular company's scalability requirements.
"
This explains why people sometimes talk about Windows DNA as an n-tier
or multi-tier architecture,
"Avalani points out."
They are referring to the ability to deploy a Windows DNA-based application over any number of physical computers.
"
COM: The Cornerstone of Windows DNA
Avalani
notes that Windows DNA is based on a programming model called COM
(Component Object Model). The COM model has come into widespread use
since its introduction by Microsoft and it is an integral part of many
Microsoft applications and technologies, including Internet Explorer and
the Office suite of applications.
Unlike
traditional software development, which required each application to be
built from scratch, COM allows developers to create complex applications
using a series of small software objects. Much like cars or houses are
built with standardized
"parts,"
COM lets developers make portions of their applications using
components. For example, Avalani says, a component might be a tax
calculation engine or the business rules for a price list. A growing
number of third-party vendors sell COM components.
This
approach speeds up the development process by allowing several teams to
work on separate parts at the same time. Developers can also reuse
components from one project to the next, and they can easily swap out or
update a particular component without affecting other portions of the
application. COM also offers the advantage of programming language
independence. That means developers can create COM components using the
tools and languages they're familiar with, such as Visual Basic, C, C++
and Java.
"An easy way to look at it is that
COM serves as the glue between the tiers of the architecture, allowing
Windows DNA applications to communicate in a highly distributed
environment,"
Avalani explains.
HTML5 is a language for structuring and presenting content for the World Wide Web, a core technology of the Internet. It is the fifth revision of the HTML standard (created in 1990 and standardized as HTML4 as of 1997) and as of September 2011
is still under development. Its core aims have been to improve the
language with support for the latest multimedia while keeping it easily
readable by humans and consistently understood by computers and devices (web browsers, parsers, etc.). HTML5 is intended to subsume not only HTML4, but XHTML1 and DOM2HTML (particularly JavaScript) as well.
Following its immediate predecessors HTML 4.01 and XHTML 1.1, HTML5
is a response to the observation that the HTML and XHTML in common use
on the World Wide Web is a mixture of features introduced by various
specifications, along with those introduced by software products such as
web browsers, those established by common practice, and the many syntax errors in existing web documents. It is also an attempt to define a single markup language
that can be written in either HTML or XHTML syntax. It includes
detailed processing models to encourage more interoperable
implementations; it extends, improves and rationalises the markup
available for documents, and introduces markup and application programming interfaces (API)s for complex web applications.
In particular, HTML5 adds many new syntactical features. These include the <video>, <audio>, <header> and <canvas>elements, as well as the integration of SVG content. These features are designed to make it easy to include and handle multimedia and graphical content on the web without having to resort to proprietary plugins and APIs. Other new elements, such as <section>, <article>, <header>, and <nav>, are designed to enrich the semantic content of documents. New attributes have been introduced for the same purpose, while some elements and attributes have been removed. Some elements, such as <a>, <cite> and <menu> have been changed, redefined or standardized. The APIs and document object model (DOM) are no longer afterthoughts, but are fundamental parts of the HTML5 specification.[2]
HTML5 also defines in some detail the required processing for invalid
documents, so that syntax errors will be treated uniformly by all
conforming browsers and other user agents.
For More Details Visit: http://en.wikipedia.org/wiki/HTML5
A website wireframe, also known as a page schematic or screen blueprint, is a visual guide that represents the skeletal framework of a website. The wireframe depicts the page layout or arrangement of the website’s content, including interface elements and navigational systems, and how they work together.
The wireframe usually lacks typographic style, color, or graphics,
since the main focus lies in functionality, behavior, and priority of
content. In other words, it focuses on “what a screen does, not what it looks like.”
Wireframes focus on
The kinds of information displayed
The range of functions available
The relative priorities of the information and functions
The rules for displaying certain kinds of information
The effect of different scenarios on the display
Brown, Dan M. Communicating Design: Developing Web Site
Documentation for Design and Planning, Second Edition. New Riders, 2011,
p. 169.
The website wireframe connects the underlying conceptual structure, or information architecture, to the surface, or visual design of the website.
Wireframes help establish functionality, and the relationships between
different screen templates of a website. An iterative process, creating
wireframes is an effective way to make rapid prototypes of pages, while
measuring the practicality of a design concept. Wireframing typically
begins between “high-level structural work—like flowcharts or site
maps—and screen designs.” Within the process of building a website, wireframing is where thinking becomes tangible.
For More Information Visit: http://en.wikipedia.org/wiki/Website_wireframe#Uses_of_wireframes
