DOCSLIB.ORG

Track 3: Extending Blackberry Beyond Email Extending Web-Based Applications with the Blackberry Browser Agenda

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Track 3: Extending Blackberry Beyond Email Extending Web-Based Applications with the Blackberry Browser Agenda Track 3: Extending BlackBerry Beyond Email Extending Web-Based Applications with the BlackBerry Browser Agenda • Introduction to BlackBerry® Browser • Mark-Up Language, Security and Connectivity Options • Optimizing Web Content for BlackBerry • Server-Side PUSH Applications • What’s New in BlackBerry Enterprise Server™ and BlackBerry Browser v4.0 •Demo BlackBerry Solution: Architecture Recap .NET Corporate Application Servers J2EE Corporate Application Servers HTTP(S) BlackBerry Corporate Systems Enterprise (ERP, CRM, Databases, etc.) Server Web Servers (IIS, Apache-Tomcat) Extending Browser-Based Solutions to BlackBerry From the developer’s perspective… HTTP HTML / WML BlackBerry Web / App Browser 3DES Encryption Server Push and Pull of Data Network-independent BlackBerry Browser Overview • Main BlackBerry Browser versions include: – BlackBerry Browser v3.6 and v3.7 • All GPRS, iDEN and CDMA Java™-enabled BlackBerry handhelds • Support for color and monochrome screen handhelds – BlackBerry Browser v3.8 and v4.0 • Upgrade from BlackBerry Browser v3.7 with new features (JavaScript, Offline Forms, etc.) – RIM Browser v2.5 and v2.6 • RIM 850™, RIM 857™, RIM 950™ and RIM 957™ handhelds • DataTAC and Mobitex wireless networks in North America Mark-up Connectivity Wireless Browser-Based Security User Experience Solutions in the Enterprise Dynamic Content Push • Key questions for consideration: 1. What mark-up languages are supported? 2. How will I connect to my corporate web servers? 3. Is security important? If so, how can I address this? 4. How can I ensure that the applications will be adopted by users and will make them more productive? 5. How can I make the content dynamic or push updated pages to my users? Mark-up Connectivity BlackBerry Browser: Security User Experience Mark-Up Languages Dynamic Content Push • BlackBerry Browser v3.6 and v3.7 –HTML – XHTML Basic, cHTML – WML 1.3, WML Script 1.2 – WBMP, PNG, GIF, JPEG images • BlackBerry Browser v3.8 and v4.0 adds… – JavaScript support – HTML Tables – Animated GIFs, WAP 2.0 Style Sheets • RIM Browser v2.5 and 2.6 for Mobitex/DataTAC –WML 1.3 – WBMP images Mark-up Connectivity Security Connectivity and Security User Experience Dynamic Content Push • Network Connectivity: – Intranet-based Web servers can be connected to via the BlackBerry Enterprise Server’s Mobile Data Service (MDS) • Simply enter the same internal URL that you would on a desktop browser on your intranet! • Browser connects through the Intranet by default, even if requesting an Internet site •Security: – All browser traffic through MDS is 3DES encrypted between the handheld and MDS – HTTPS (SSL/TLS) is also supported Mark-up Connectivity Security Connectivity and Security User Experience Dynamic Content Push HTTP HTTP Connectivity Corporate INTERNET Firewall MDS Web Server Security Optional TLS/SSL Optional TLS/SSL 3DES Mark-up Connectivity Security User Authentication User Experience Dynamic Content Push • MDS also supports a variety of corporate authentication schemes: – HTTP Basic –Kerberos – NT LAN Manager (NTLM) • If authentication is required for internal web site access, user will be challenged for credentials • MDS can optionally cache user credentials for future browsing sessions by that user Mark-up Connectivity Encryption and Security User Experience Authentication Dynamic Content Push • A closer look at the role of MDS for encryption and authentication… App/Web Server BlackBerry MDS 3DES De/Encryption TLS / SSL Handshaking 3DES 3DES TLS/SSL De/Encryption SECURITY Optional TLS / SSL Encryption Request Challenge AUTH Credentials Authentication (Kerberos, Basic, NTLM) Mark-up Connectivity Connectivity and Security User Experience Management Features Dynamic Content Push • MDS provide a number of other features for managing browser sessions: – Cache cookies and user credentials – Access control: manage which users are allowed to connect to the intranet via the browser – MDS transcodes and optimizes content for wireless delivery: • HTML – cHTML transcoder • All images are scaled and converted to PNG format • Unsupported tags are stripped, content is tokenized – MDS logs all browser requests Mark-up Connectivity MDS Connectivity to Web Security User Experience Servers Dynamic Content Push • What does the web server see when a BlackBerry Browser connects via MDS? – User-Agent = BlackBerry<Handheld>/<Version> – Accept Type = html, chtml, xhtml basic, wml • Note: WML only for RIM 800 Series and RIM 900 Series handhelds – Source IP Address = MDS machine IP Address • Note: MDS can optionally add the requesting handheld’s PIN or email address as a header to each request Mark-up Connectivity Server-Side Content Security User Experience Management Dynamic Content Push • Use any standard web development tools to publish content on intranet web servers – Static Content: • HTML or WML pages – Dynamic Content: • Java™ Server Pages (JSPs) or Active Server Pages (ASPs) • Perl Script, etc. • Recommendations: – Consider optimizing content to drive user experience • Avoid or limit tables, frames & large images in HTML pages – Leverage PUSH technology to deliver content proactively Mark-up Connectivity Optimizing Content for Security User Experience BlackBerry: Tips Dynamic Content Push • Tips on Optimizing the User Experience – Use the “Accept” and “User-Agent” HTTP headers to detect the BlackBerry Browser – Loading a page from cache is much quicker than over the air – Do not discourage text entry – Email addresses and phone numbers automatically act as hot links to the handheld Email and Phone applications – Use cookies and cache controls to manage sessions and expiry Mark-up Connectivity BlackBerry Browser: Security User Experience Server-Side PUSH Dynamic Content Push • BlackBerry enables you to pro-actively PUSH new web pages and links to your users’ handhelds – Alerts based on events that occur on the server – Silently update frequently accessed pages within the browser’s local cache – Push a permanent link to a frequently accessed site (such as an internal portal or entry point to an application) Leverage the value of push for your own corporate data, without developing a custom client application or getting messages lost in the email inbox! Mark-up Connectivity Developing a PUSH Security User Experience Application Dynamic Content Push • To push a web page to the BlackBerry Browser, you must develop a push application which: A. Determines: i. URL of the web page to be pushed ii. Email Address or PIN of the destination user B. Reads in the contents of the web page from the origin server (InputStream over an HTTP GET request) C. Writes out the contents of the web page to MDS, along with the information from step (a) above (OutputStream over an HTTP POST request) Mark-up Connectivity Developing a PUSH Security User Experience Application – Sample Code Dynamic Content Push Server-side sample code for pushing web page (J2EE): Determine Source Content URL & Destination User URL sourceContent = “http://corpWebServer01/inventory/productID=5”; String userEmail = “[email protected]”; Open an Input Stream to the Web Server HttpURLConnection getConn = (HttpURLConnection)sourceContent.openConnection(); connection.setRequestMethod(“GET"); //HTTP GET InputStream cin = getConn.getInputStream(); //Open input stream to web server to read in web page InputStreamReader insr = new InputStreamReader(cin); //Attach an InputStream reader //We are now ready to read in the web page from the web server Mark-up Connectivity Developing a PUSH Security User Experience Application – Sample Code Dynamic Content Push Construct the push URL // (http://<MDS host>:<port>/push?DESTINATION=<email>&PORT=<Browser Listen Port>) String mdsServer = “corpBesMds01:8300”; //Internal MDS server address + push listen port String mdsPushURL = "http://" + mdsServer + "/push?DESTINATION=" + userEmail + "&PORT=7874"; Set up the HTTP POST Push Connection to MDS HttpURLConnection postConn = (HttpURLConnection)mdsPushURL.openConnection(); connection.setRequestMethod("POST"); //HTTP POST connection.setRequestProperty("Content-Location", sourceURL); //URL where the web page lives connection.setRequestProperty(“Content-Type”, “text/html”); connection.setRequestProperty("X-RIM-Push-Title", “Product Alert!"); //BlackBerry-Specific Push headers Connect the Streams – Open the connection to MDS and write the data from the Web Server OutputStream outs = postConn.getOutputStream(); //Open the OutputStream to MDS int c; while ((c = cin.read()) >= 0) { //Read in bytes of web page from web server outs.write(c); } //Write out all of the bytes to MDS outs.close(); Mark-up Connectivity PUSH Management Within Security User Experience MDS Dynamic Content Push • What happens at MDS? 1. MDS receives HTTP POST and reads in the data 2. MDS checks database for existence of the user 3. If user exists, MDS responds to server app with confirmation (HTTP 200 OK) and closes connection 4. BlackBerry Server determines status of destination of handheld (online/offline, network, etc.) – If handheld is in coverage, data is pushed immediately – If handheld is out of coverage, push request is queued within MDS (currently within RAM, optionally in a database in BlackBerry Enterprise Server v4.0) Mark-up Connectivity PUSH Management Within Security User Experience MDS Dynamic Content Push MDS Push Queuing for out of coverage handhelds • Flow Control: – 5 push packets will be queued in MDS for the flow control timeout period (Default = 10 minutes) – No further packets will be pushed until these 5 are
Load more

Recommended publications
  • Sample XHTML Code
    Sample XHTML Code Docs version: 2.0 Version date 7/29/2009 Contents • Introduction • Home page • General page structure • Tabbed content • Navigation lists • iPhone action links Introduction These code samples illustrate how we designed and developed the user for the MIT Mobile Web. These code samples are taken from the original XHTML design mockups which were the basis of the final implementation of the live MIT Mobile Web. We’re presenting these design mockups here because showing the final functional code with its back-end integration would make it harder to read the actual markup as the web browser sees it – which is what determines what the end user actually sees and interacts with. The XHTML and CSS generated by the functional code is in any case very close to these original design mockups. We’re not presenting every page for every module here. Rather, we’re showing representative pages that illustrate user-interface patterns that appear throughout the MIT Mobile Web. After studying these code snippets and the patterns they represent, you should be able to easily understand how specific pages in the MIT Mobile Web were built, as well as how to go about building new page layouts sharing a consistent basic structure, function and building blocks. For background on why we optimized the UI for three different categories of devices, please read the Introduction to the Mobile Web document. Commented source code, images and other assets for the entire MIT Mobile Web – including functional code for back-end integration – is online as a SourceForge project at http://sourceforge.net/projects/mitmobileweb/.
    [Show full text]
  • XHTML Mobile Profile Reference
    XHTML Mobile Profile Reference Version 1.0 Openwave Systems Inc. 1400 Seaport Boulevard Redwood City, CA 94063 USA http://www.openwave.com Part Number XHRF-10-004 October 2001 LEGAL NOTICE Copyright © 1994–2001, Openwave Systems Inc. Portions copyright © 1994–1999, Netscape Communications Corporation. Portions copyright © 1994–1999, Oracle Corporation. All rights reserved. These files are part of the Openwave Software Developer’s Kit (SDK). Subject to the terms and conditions of the SDK License Agreement, Openwave Systems Inc. (“Openwave”) hereby grants you a license to use the SDK software and its related documentation. OPENWAVE MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE SDK SOFTWARE, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES THAT THE SDK SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NONINFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LICENSED SOFTWARE IS BORNE BY USER. USER UNDERSTANDS AND ACCEPTS THE SDK SOFTWARE AND ANY SOFTWARE SECURITY FEATURES INCLUDED WITH THE SDK SOFTWARE ARE PROVIDED ON AN “AS IS” BASIS FROM OPENWAVE, AND OPENWAVE DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THE SDK SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL OPENWAVE OR ITS SUPPLIERS OR DISTRIBUTORS BE LIABLE FOR ANY DAMAGES RESULTING FROM OR ARISING OUT OF USER’S USE OF THE SDK SOFTWARE, INCLUDING, WITHOUT LIMITATION, ANY DIRECT, INDIRECT, SPECIAL, INCIDENTIAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES.
    [Show full text]
  • An Intruduction to HTML5
    Agenda * What is HTML5 -- Its history and motivation * HTML/XHTML as Human / Machine Readable Format * HTML and its related technologies * Brief summary of the changes * Models of HTML5 * Examples and demonstrations What is HTML5 -- Its history and motivation * W3C and HTML * Brief history of HTML * WHATWG and HTML5 * 'Working Draft' and 'Recommendation' * HTML5 as IDL -- Interface Definition via IDL What is HTML5 - W3C and HTML What is HTML5 - W3C and HTML What is HTML5 - Brief history of HTML HTML is born for 'Scientists' at CERN. First website (from archive@cern) Tim Berners Lee What is HTML5 - Brief history of HTML HTML (1989; CERN) HTML = HyperText Markup Language HTML 1.0 (1993; IETF) HTML 2.0 (1995; W3C) HTML 3.2 (1997; W3C) XML 1.0 (1998) HTML 4.0.1 (1999; W3C) XHTML 1.0 (2000) XHTML Basic 1.0 (2000) XHTML 1.1 (2001) XHTML Basic 1.1 (2008) What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension to HTML4 (2003;Opera) PositionPaper (2004;Opera/Mozilla) What is HTML5 - Brief history of HTML http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension to HTML4 (2003;Opera) PositionPaper (2004;Opera/Mozilla) WHATWG (2004;Opera/Mozilla/Apple) What is HTML5 - Brief history of HTML The Web Hypertext Application Technology Working Group (WHATWG) What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension
    [Show full text]
  • Web Application Developer's Guide for the Polycom® Soundpoint® IP
    Web Application Developer’s Guide for the Polycom® SoundPoint® IP/SoundStation® IP Family SIP 3.1 August, 2008 Edition 1725-17693-310 Rev. A SIP 3.1 Trademark Information Polycom®, the Polycom logo design, SoundPoint® IP, SoundStation®, SoundStation VTX 1000®, ViaVideo®, ViewStation®, and Vortex® are registered trademarks of Polycom, Inc. Conference Composer™, Global Management System™, ImageShare™, Instructor RP™, iPower™, MGC™, PathNavigator™, People+Content™, PowerCam™, Pro-Motion™, QSX™, ReadiManager™, Siren™, StereoSurround™, V2IU™, Visual Concert™, VS4000™, VSX™, and the industrial design of SoundStation are trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. © 2008 Polycom, Inc. All rights reserved. Polycom Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g. a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc. is not responsible for printing or clerical errors.
    [Show full text]
  • HTML5 Audio 1 HTML5 Audio
    HTML5 Audio 1 HTML5 Audio HTML • HTML and HTML5; HTML editor • Dynamic HTML • XHTML • XHTML Basic (Mobile) • XHTML Mobile Profile and C-HTML • HTML element • Span and div • HTML attribute • Character encodings; Unicode • Language code • Document Object Model • Browser Object Model • Style sheets and CSS • Font family and Web colors • HTML scripting and JavaScript • W3C, WHATWG, and validator • Quirks mode • HTML Frames • HTML5 Canvas, WebGL, and WebCL • HTML5 Audio and HTML5 video • Web storage • Web browser (layout) engine • Comparison of • document markup languages • web browsers • layout engine support for • HTML; Non-standard HTML • XHTML (1.1) • HTML5; HTML5 canvas, • HTML5 media (Audio, Video) • v • t [1] • e HTML5 Audio is a subject of the HTML5 specification, investigating audio input, playback, synthesis, as well as speech to text in the browser. HTML5 Audio 2 <audio> element The <audio> element represents a sound, or an audio stream.[2] It is commonly used to play back a single audio file within a web page, showing a GUI widget with play/pause/volume controls. Supported browsers • PC • Google Chrome • Internet Explorer 9 • Mozilla Firefox 3.5 • Opera 10.5 • Safari 3.1[3] • Mobile • Android Browser 2.3 • Blackberry Browser • Google Chrome for Android • Internet Explorer Mobile 9 • Mobile Safari 4 • Mozilla Firefox for Android • Opera Mobile 11 • Tizen Supported audio codecs This table documents the current support for audio codecs by the <audio> element. Browser Operating Formats supported by different web browsers system Ogg
    [Show full text]
  • (X)HTML Best Practice Cheat Sheet.Pdf 2007-08-13 17:49 236 KB
    (X)HTML Best Practice Cheat Sheet All elements are sorted ]able ed T within their /[ lac l y ]ep t groups in ish) [R ues prioritized tional sibili eset eset al/ ance t t s r order. ic nline(- m e er iss r ansitiona am asic ] am r r I or s r ] eaning Recommended transi t Mobile Acc 0 st 0 f 1 B 0 N ice 1 stric 1 f 5.0 h)/[ /[ m appea (X)HTML 2 01 & 1. 1.0 1. 1.1 1. 1.1 2. -is ic 4.0 4.0 act versions are L L L L ML k( ible led pr notes ble brow M ML M ML M ML M T is ty mint-colored. ML 3. ML ML 4. ML T T T O ]loc mant s T T T T HT HT HT HT nv sability est n X)H ] H H H H X XH X XH X XH X ( [B [I Se U B SE Nota U Element Standards Information Document structure <html> N Viewport in XHTML <head> I The main Viewport in HTML. <body> B N content of the Margin: 8px; document The Highly ranked and Make unique for <title> I documents will be the link- Text on the title-bar every page title or name text Only ”name = <meta> I 'description'” is useful Indicates explicit relationship between this <link> I document and other resources. As such there are many good uses! External style <style> I sheets are usually best Unobtrusive Test for Keep scripts Script may have <script> I DOM-scripts, capabilities, not external output please! browsers! Unnecassary with unobtrusive Not ignored by true <noscript> BI I scripting techniques! Forbidden in s XML parsers! XHTML 5.
    [Show full text]
  • An Introduction to Character Encoding Issues in the Mobile Web
    An introduction to character encoding 1 (12) issues in the mobile Web Eduardo CASAIS TECHNICAL PAPER 2008-12-08 AN INTRODUCTION TO CHARACTER ENCODING ISSUES IN THE MOBILE WEB Eduardo Casais areppim AG Bern, Switzerland 1. A LINGERING ISSUE Character encoding – the binary representation of every symbol in documents delivered to mobile terminals – is often treated as an afterthought in mobile Web development. Many developers simply rely upon ISO-8859-1; not a bad choice, as this encoding efficiently supports all important Western European languages, has long been available in the mobile and fixed Internet, is widespread among low-end phones, and is the default encoding in the HTTP standard. Astute software engineers prefer UTF-8; this encoding supports Unicode, and hence the widest range of languages and associated glyphs – great for multilingual “world” applications. It is also a default for several application formats, most popular in the WWW, and available in newer mobile terminals. Even in Japan, i-mode gateways may take care of the complex mapping from UTF-8 to Shift_JIS-only capable terminals. Producing content in one of these two major encodings and configuring a WWW server to advertise the content type and encoding properly generally suffices for mainstream applications. There can be complications however – especially when dealing with advanced functions or developing for exotic markets – and it is preferable to be aware of them. The article examines the situation in the context of mobile browsing. 2. THE DOCUMENT CHARACTER SET Let us briefly recapitulate some concepts. A character set is a repertoire of abstract symbols (e.g.
    [Show full text]
  • Chapter 7: HTML/XHTML I
    7. HTML and XHTML | Hypertext Markup Language, Part I 7-1 Chapter 7: HTML/XHTML I References: • Erik Wilde: World Wide Web | Technische Grundlagen. Springer, 1999, ISBN 3-540-64700-7, 641 Seiten. • Eric Ladd, Jim O'Donnell, et al.: Using HTML 4, XML, and Java 1.2, Platinum Edition. QUE, 1999, ISBN 0-7897-1759-X, 1282 pages. • Rainer Klute: Das World Wide Web. Addison-Wesley, 1996, ISBN: 389319763X. • Dave Raggett, W3C: HTML 3.2 Reference Specification. [http://www.w3.org/TR/REC-html32.html] • Dave Raggett, Arnaud Le Hors, Ian Jacobs (Eds.): HTML 4.01 Specification. W3C, Dec 24, 1999. [http://www.w3.org/TR/html4/] • User's Guide to ISO/IEC 15445:2000 HyperText Markup Language (HTML) [http://www.cs.tcd.ie/15445/UG.html] • XHTML [tm] 1.0: The Extensible HyperText Markup Language. W3C, Jan 26, 2000. [http://www.w3.org/TR/xhtml1] • Stefan M¨unz:HTML-Dateien selbst erstellen | SELFHTML. [http://www.netzwelt.com/selfhtml/] [http://www.teamone.de/selfaktuell/] • Ian Graham: Introduction to HTML. [http://www.utoronto.ca/webdocs/HTMLdocs/NewHTML/htmlindex.html] • NCSA Beginner's Guide to HTML (no longer maintained). [http://www.ncsa.uiuc.edu/General/Internet/WWW/] Stefan Brass: Grundlagen des World Wide Web Universit¨atHalle, 2016 7. HTML and XHTML | Hypertext Markup Language, Part I 7-2 Objectives After completing this chapter, you should be able to: • develop web pages in strict HTML 4.0/XHTML 1.0. • write syntactically correct HTML/XHTML. • read the HTML and XHTML specifications. • evaluate whether something is possible in HTML. • write a short paragraph about differences between HTML versions.
    [Show full text]
  • Xep-0071: Xhtml-Im
    XEP-0071: XHTML-IM Peter Saint-Andre mailto:xsf@stpeter:im xmpp:peter@jabber:org http://stpeter:im/ 2018-03-08 Version 1.5.4 Status Type Short Name Deprecated Standards Track xhtml-im This specification defines an XHTML 1.0 Integration Set for use in exchanging instant messages that contain lightweight text markup. The protocol enables an XMPP entity to format a message using a small range of commonly-used HTML elements, attributes, and style properties that are suitable for use in in- stant messaging. The protocol also excludes HTML constructs that may introduce malware and other vulnerabilities (such as scripts and objects) for improved security. Legal Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the ”Specification”), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specifi- cation, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or sub- stantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or pub- lisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
    [Show full text]
  • HTML and CSS Tutorial Chapter 1: Getting Started
    HTML and CSS Tutorial This work is licensed under a Creative Commons License: Attribution 3.0 Unported. You are free: • to Share — to copy, distribute, and transmit the work • to Remix — to adapt the work Under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. For attribution purposes, the URL to be associated with the work is http://www.goer.org/HTML, and the Title and Author of this work are as follows: “The Pocket HTML Tutorial” Copyright 2012 by Evan Goer. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. This is a human-readable summary of the Legal Code (the full license). Chapter 1: Getting Started Welcome to the world of HTML! If you have never written HTML code before, you should start with this section. If you’ve written HTML before, you should feel free to skip ahead to Chapter 2, Markup Basics. When you’re done with this chapter, you should be able to: • create and alter a simple web page • explain what HTML elements and attributes are • use your browser to help you view and reuse code from other websites Section Summaries The Getting Started chapter contains these sections: 1. Diving In — Demonstrates basic HTML concepts by diving in and creating a simple web page. 2. Structure — Examines document structure: the html element, the head, the title, and the body.
    [Show full text]
  • HTML and CSS COURSE SYLLABUS
    Deccansoft Software Services Html and css Syllabus HTML and CSS COURSE SYLLABUS Overview: HTML and CSS go hand in hand for developing flexible, attractively and user friendly websites. HTML (Hyper Text Markup Language) is used to show content on the page where as CSS is used for presenting the page. HTML describes the structure of a Website semantically along with presentation cues, making it a mark-up language, rather than a programming language. HTML allows images and objects to be embedded and can be used to create interactive forms. Course Objectives: HTML is highly flexible and supported on all browsers. User friendly and an open technology. It give better performance. CSS provides powerful control over the presentation of an HTML document. CSS saves many times as it can be reused in many HTML pages. CSS can be used to make responsive web pages, which are compatible on multiple devices. It can be used to allow the web pages to display differently depending on the screen size or device on which it is being viewed. Pre-requisite / Target Audience: Any beginner who wants to build career as Web designer can take this course. Module 1: Web Programming Introduction In this module, you will learn basic introduction to web development. The fundamental technology used to define the structure of a webpage. Web Development Introduction Module 2: HTML-Introduction In this module, sets the stage, getting you used to important concepts and syntax, looking at applying HTML to text, how to create hyperlinks, and how to use HTML to structure a webpage. History of HTML What you need to do to get going and make your first HTML page What are HTML Tags and Attributes? HTML Tag vs.
    [Show full text]
  • Tutorialspoint HTML.Pdf
    HTML About the Tutorial HTML stands for Hyper Text Markup Language, which is the most widely used language on Web to develop web pages. HTML was created by Berners-Lee in late 1991 but "HTML 2.0" was the first standard HTML specification which was published in 1995. HTML 4.01 was a major version of HTML and it was published in late 1999. Though HTML 4.01 version is widely used but currently we are having HTML-5 version which is an extension to HTML 4.01, and this version was published in 2012. Audience This tutorial is designed for the aspiring Web Designers and Developers with a need to understand the HTML in enough detail along with its simple overview, and practical examples. This tutorial will give you enough ingredients to start with HTML from where you can take yourself at higher level of expertise. Prerequisites Before proceeding with this tutorial you should have a basic working knowledge with Windows or Linux operating system, additionally you must be familiar with: Experience with any text editor like notepad, notepad++, or Edit plus etc. How to create directories and files on your computer. How to navigate through different directories. How to type content in a file and save them on a computer. Understanding about images in different formats like JPEG, PNG format. Copyright & Disclaimer Copyright 2015 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher.
    [Show full text]