Skip to main content

Home/ Future of the Web/ Group items matching "html5" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

Offline Web Applications - 0 views

www.w3.org/offline-webapps

apps html5 offline

shared by Paul Merrell on 24 Aug 08 - Cached
  • Abstract HTML 5 contains several features that address the challenge of building Web applications that work while offline. This document highlights these features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML 5 and provides brief tutorials on how these features might be used to create Web applications that work offline.
Gary Edwards

The WHATWG Blog » Blog Archive » The Road to HTML 5: character encoding - 0 views

blog.whatwg.org/d-to-html-5-character-encoding

character-encoding html5 whatwg

shared by Gary Edwards on 13 Feb 09 - Cached
  • Gary Edwards on 13 Feb 09
     
    To sum up: character encoding is complicated, and it has not been made any easier by several decades of poorly written software used by copy-and-paste-educated authors. You should always specify a character encoding on every HTML document, or bad things will happen. You can do it the hard way (HTTP Content-Type header), the easy way ( declaration), or the new way ( attribute), but please do it. The web thanks you. Good post, lots of links to other "MUST READ" commentaries and explanations of character encoding. Including Joel Spolsky and Tim Bray.
Gary Edwards

Google Chrome: Bad news for Adobe « counternotions - 0 views

counternotions.com/...badnews

air chrome ria silverlight webkit

shared by Gary Edwards on 08 Sep 08 - Cached
  • Agree with much of what Kontra said and disagree with many who mentioned alternatives to JavaScript/Chrome. The main, simplest reason Adobe will be in a losing fight in terms of web platform? The Big Two - Google and Microsoft - will never make themselves dependent on or promote Adobe platform and strategy.
  • Luis, I think that’s already in play with HTML5. As I pointed out in Runtime wars (2): Apple’s answer to Flash, Silverlight and JavaFX, Apple and WHATWG are firmly progressing along those lines. Canvas is at the center of it. The glue language for all this, JavaScript, is getting a potent shot in the arm. The graphics layer, at the level of SVG, needs more work. And so on.
  • Gary Edwards on 08 Sep 08
     
    "What's good for the Internet is good for Google, and the company says its strategic proposition for the newly introduced Chrome browser is: a better platform is needed to deliver a new generation of online applications......." This is one of the best explanations of why Google had to do Chrome i've seen thus far. Kontra also provided some excellent coverage concerning the Future of the Web in a two part article previously published. Here he nails the RiA space, comparing Google Chrome, Apollo (Adobe AiR/Flex/Flash) and Microsoft Silverlight. Chrome is clearly an Open Web play. Apollo and Sivlerlight are proprietary bound in some way. Although it must be said that Apollo implements the SAME WebKit layout engine / WebKit docuemtn model as Google Chrome, Apple Safari-iPhone, Nokia, RiM and the Iris "Smart Phone" browser. The WebKit model is based on advanced HTML, CSS, SVG and JavaScript. Where Adobe goes proprietary is in replacing SVG with the proprietary SWF. The differences between JavaScript and ActionScript are inconsequential to me, especially given the problems at Ecma. One other point not covered by Kontra is the fact that Apollo and Silverlight can run as either browser plugins or standalone runtimes. Wha tthey can't do though is run as sufing browsers. They are clearly for Web Applications. Chome on the other hand re-invents the browser to handle both surfing mode AND RiA. Plus, a Chrome RiA can also run as a plugin in other browsers (Opera and FireFox). Very cool. The last point is that i wouldn't totally discount Apple RiA. They too use WebKit. The differnece is tha tApple uses the SquirrelFish JavaScript JiT with the SproutCore-Cocoa developers framework. This approach is designed to bridge the gap between the OSX desktop/server Cocoa API, and the WebKit-SproutCore API. Chrome uses the V8 JiT. And Adobe uses Tamarin to compile JavaScript-ActionScript. Tamarin was donated to the Mozilla community. If there is anythin that will s
Gary Edwards

How HTML 5 Is Already Changing the Web - Webmonkey - 0 views

www.webmonkey.com/..._5_Is_Already_Changing_the_Web

css3 html5 webkit

shared by Gary Edwards on 25 Sep 08 - Cached
  • Gary Edwards on 25 Sep 08
     
    HTML 5 represents the biggest leap forward in web standards in almost a decade. Unlike the specifications that came before it, HTML 5 is not merely intended to present content to a web browser. Its goal is to bring the web into maturity as a full-fledged application platform - a level playing field where video, sound, images, animations, and full interactivity with your computer are all standardized. And it may be a long way off still, but elements of HTML 5 are already reshaping the way we use the web.
Paul Merrell

Sir Tim Berners-Lee on 'Reinventing HTML' - 0 views

dig.csail.mit.edu/...166

berners-lee html html5 standards w3c xforms xhtml

shared by Paul Merrell on 29 May 08 - Cached
    • Paul Merrell
      Paul Merrell on 29 May 08
       
      Berners-Lee gives the obligaotry lip service to participation of "other stakeholders" but the stark reality is that W3C is the captive of the major browser developers. One may still credit W3C staff and Berners-Lee for what they have accomplished despite that reality, but in an organization that sells votes the needs of "other stakeholders" will always be neglected.
  • Some things are clearer with hindsight of several years. It is necessary to evolve HTML incrementally. The attempt to get the world to switch to XML, including quotes around attribute values and slashes in empty tags and namespaces all at once didn't work. The large HTML-generating public did not move, largely because the browsers didn't complain. Some large communities did shift and are enjoying the fruits of well-formed systems, but not all. It is important to maintain HTML incrementally, as well as continuing a transition to well-formed world, and developing more power in that world.
  • The plan is, informed by Webforms, to extend HTML forms. At the same time, there is a work item to look at how HTML forms (existing and extended) can be thought of as XForm equivalents, to allow an easy escalation path. A goal would be to have an HTML forms language which is a superset of the existing HTML language, and a subset of a XForms language wit added HTML compatibility.
  • ...7 more annotations...
  • There will be no dependency of HTML work on the XHTML2 work.
    • Paul Merrell
      Paul Merrell on 29 May 08
       
      He just confirms that that incremental migration from HTML forms to XForms is entirely a pie-in-the-sky aspiration, not a plan.
  • This is going to be a very major collaboration on a very important spec, one of the crown jewels of web technology. Even though hundreds of people will be involved, we are evolving the technology which millions going on billions will use in the future. There won't seem like enough thankyous to go around some days.
    • Paul Merrell
      Paul Merrell on 29 May 08
       
      This is the precise reason the major browser developers must be brought to heel rather than being catered to with a standard that serves only the needs of the browser developers and not the need of users for interoperable web applications. CSS is in the web app page templates, not in the markup that can be exchanged by web apps. Why can't MediaWiki exchange page content with Drupal? It's because HTML really sucks biig time as a data exchange format. All the power is in the CSS site templates, not in what users can stick in HTML forms.
    • Paul Merrell
      Paul Merrell on 29 May 08
       
      Bye-bye XForms.
    • Paul Merrell
      Paul Merrell on 29 May 08
       
      Perhaps a political reality. But I am 62 years old, have had three major heart attacks, and am still smoking cigarettes. I would like to experience interoperable web apps before I die. What does the incremental strategy do for me? I would much prefer to see Berners-Lee raising his considerable voice and stature against the dominance of the browser developers at W3C.
  • The perceived accountability of the HTML group has been an issue. Sometimes this was a departure from the W3C process, sometimes a sticking to it in principle, but not actually providing assurances to commenters. An issue was the formation of the breakaway WHAT WG, which attracted reviewers though it did not have a process or specific accountability measures itself.
  • Some things are very clear. It is really important to have real developers on the ground involved with the development of HTML. It is also really important to have browser makers intimately involved and committed. And also all the other stakeholders, including users and user companies and makers of related products.
  • anonymous on 23 Sep 13
     
    Like this http://www.hdfilmsaati.net Film,dvd,download,free download,product... ppc,adword,adsense,amazon,clickbank,osell,bookmark,dofollow,edu,gov,ads,linkwell,traffic,scor,serp,goggle,bing,yahoo.ads,ads network,ads goggle,bing,quality links,link best,ptr,cpa,bpa
Paul Merrell

HTML 5 Draft Recommendation - 0 views

www.whatwg.org/...index.html

html html5 standards

shared by Paul Merrell on 29 May 08 - Cached
  • Draft Recommendation — 29 May 2008
  • Abstract This specification evolves HTML and its related APIs to ease the authoring of Web-based applications. Additions include the context menus, a direct-mode graphics canvas, inline popup windows, and server-sent events. Heavy emphasis is placed on keeping the language backwards compatible with existing legacy user agents and on keeping user agents backwards compatible with existing legacy documents.
    • Paul Merrell
      Paul Merrell on 29 May 08
       
      HTML 5 may "ease the authoring of Web-based applications," but has nothing to offer web app developers or users in the way of the interoperable interchange of web app page or sub-page content.
  • anonymous on 23 Sep 13
     
    Like this http://www.hdfilmsaati.net Film,dvd,download,free download,product... ppc,adword,adsense,amazon,clickbank,osell,bookmark,dofollow,edu,gov,ads,linkwell,traffic,scor,serp,goggle,bing,yahoo.ads,ads network,ads goggle,bing,quality links,link best,ptr,cpa,bpa
Paul Merrell

Google pounds the open standards drum during I/O keynote - 0 views

arstechnica.com/...rds-drum-during-io-keynote.ars

google VP8 Wave WebM Ogg Vorbis html5 OpenWeb

shared by Paul Merrell on 19 May 10 - Cached
  • Paul Merrell on 19 May 10
     
    Separately, Microsoft and Apple have announced that both company's browsers will boycott VP8 in favor of H264, which is encumbered by more than a thousand patents.. But if VP8 becomes ubiquitous on the Web, that's a hard position to maintain.  
Paul Merrell

Firefox, YouTube and WebM ✩ Mozilla Hacks - the Web developer blog - 1 views

hacks.mozilla.org/...firefox-youtube-and-webm

Mozilla Firefox VP8 WebM youtube codecs H.264

shared by Paul Merrell on 20 May 10 - Cached
  • 1. Google will be releasing VP8 under an open source and royalty-free basis. VP8 is a high-quality video codec that Google acquired when they purchased the company On2. The VP8 codec represents a vast improvement in quality-per-bit over Theora and is comparable in quality to H.264. 2. The VP8 codec will be combined with the Vorbis audio codec and a subset of the Matroska container format to build a new standard for Open Video on the web called WebM. You can find out more about the project at its new site: http://www.webmproject.org/. 3. We will include support for WebM in Firefox. You can get super-early WebM builds of Firefox 4 pre-alpha today. WebM will also be included in Google Chrome and Opera. 4. Every video on YouTube will be transcoded into WebM. They have about 1.2 million videos available today and will be working through their back catalog over time. But they have committed to supporting everything. 5. This is something that is supported by many partners, not just Google and others. Content providers like Brightcove have signed up to support WebM as part of a full HTML5 video solution. Hardware companies, encoding providers and other parts of the video stack are all part of the list of companies backing WebM. Even Adobe will be supporting WebM in Flash. Firefox, with its market share and principled leadership and YouTube, with its video reach are the most important partners in this solution, but we are only a small part of the larger ecosystem of video.
Paul Merrell

W3C Issues Report on Web and Television Convergence - 0 views

www.w3.org/...webtv-pr.html.en

convergence web television standards W3C

shared by Paul Merrell on 29 Mar 11 - No Cached
  • 28 March 2011 -- The Web and television convergence story was the focus of W3C's Second Web and TV Workshop, which took place in Berlin in February. Today, W3C publishes a report that summarizes the discussion among the 77 organizations that participated, including broadcasters, telecom companies, cable operators, OTT (over the top) companies, content providers, device vendors, software vendors, Web application providers, researchers, governments, and standardization organizations active in the TV space. Convergence priorities identified in the report include: Adaptive streaming over HTTP Home networking and second-screen scenarios The role of metadata and relation to Semantic Web technology Ensuring that convergent solutions are accessible. Profiling and testing Possible extensions to HTML5 for Television
Paul Merrell

Opera proposal brings a book look to the Web | Deep Tech - CNET News - 0 views

news.cnet.com/...-brings-a-book-look-to-the-web

opera HTML5 CSS tablets pages book

shared by Paul Merrell on 12 Oct 11 - No Cached
  • At the company's Up North Web press event here, CTO Haakon Wium Lie showed off a new standard he proposed that could give Web pages more of the feel of printed pages. A document too big for a single screen, instead of getting a scroll bar, would be split across several pages, and people can navigate among them with gestures--swiping left and right to go forward and backward or swiping up to return to an earlier page. "Doing pages on a screen I think will be very important, especially for tablets," he said.
Gonzalo San Gil, PhD.

Midori  ·  A lightweight, fast, and free web browser - 2 views

midori-browser.org

Midori open source free software lightweight web browser alternative DRM implementation HTML5 Mozilla Firefox Chrome

shared by Gonzalo San Gil, PhD. on 15 May 14 - No Cached
  • Gonzalo San Gil, PhD. on 15 May 14
     
    "On The Cutting Edge Midori is blazing fast, utilizing the latest web technologies and a small but dexterous array of extensions provide all the essential features."
  • Gonzalo San Gil, PhD. on 15 May 14
     
    "On The Cutting Edge Midori is blazing fast, utilizing the latest web technologies and a small but dexterous array of extensions provide all the essential features."
« First ‹ Previous 61 - 73 of 73
Showing 20▼ items per page