Skip to main content

Home/ Web2.0/ Group items tagged html

Rss Feed Group items tagged

awqi zar

GetFirebug.com redesign launched! | Mozilla Web Development - 7 views

  •  
    New design brings updated look and feel, open web video, and a brand new icon.If you've happened across the GetFirebug.com web site recently, you'll notice everything has a rather pleasant freshly painted smell. After a much-too-long delay, we've finally updated the design and layout for the official Firebug web site, and introduced a lovely new icon by our resident Iconmaster General Sean Martell.
Bill Selak

HTML 5 video Tag - 0 views

  • Definition and Usage

    The <video> tag defines video, such as a movie clip or other video streams.

  •  
    html5 video tag
Graham Perrin

Adobe, AIR and open source: changes to, and expectations of, WebKit - 1 views

  • Adobe Open Source
  • WebKit
  • to render HTML and execute JavaScript in Adobe® AIR™
  • ...12 more annotations...
  • Our plan is to contribute our changes back to the WebKit community
  • currently working on getting the code smoothly integrated
  • Our modification can be found within the Perforce depot.
  • integrate our changes back into the WebKit source repository at webkit.org
  • the WebKit shared library will not contain any platform specific code
  • For the near term, WebKit will have platform specific code
  • to rasterize vector graphics generated by the HTML renderer
  • Project Plans
  • we use Cairo Source for WebKit
  • we use CoreGraphics
  • 2008-06-03
  •  
    Adobe, AIR and open source: changes to, and expectations of, WebKit
  •  
    Will AIR applications be deployable in Google Chrome OS? Or, is this possibility reduced by Adobe's changes to WebKit?

    When and how will Adobe's changes to WebKit become available at webkit.org?

    Defocusing from Adobe: is there now less platform-specific code within WebKit? How soon might the goal — no platform-specific code — be realised?
Graham Perrin

ODF versus OOXML: Don't forget about HTML! - O'Reilly XML Blog - 0 views

  • Don't forget about HTML
  • February 25, 2007
  • HTML’s potential and actual suitability for much document interchange
  • ...27 more annotations...
  • HTML is the format to consider first
  • validated, standards compliant XHTML in particular
  • HTML at one end (simple WP documents)
  • PDF at the other end (full page fidility but read-only)
  • HTML, ODF, OOXML, PDF
  • W3C versus ISO

  • Lie adopts an extreme view towards overlap of standards:
  • overlap at all brings nothing but misery and bloat.
  • The next dodgy detail is to make blanket comparisons between HTML and ODF/OOXML.
  • ODF and OOXML deal with many issues that HTML/CSS simply does not.
  • the W3C argument might be to say that every part should have a URL
  • a strange theory that MS wants ODF and OOXML to both fail
  • being pro-ODF does not mean you have have to be anti-OOXML
  • HTML is the format of choice for interchange of simple documents
  • ODF will evolve to be the format of choice for more complicated documents
  • OOXML is the format of choice for full-fidelity dumps from MS Office
  • PDF is the format of choice for non-editable page-faithful documents
  • all have overlap
  • we need to to encourage a rich library of standard technologies,
  • widely deployed,
  • free,
  • unencumbered,
  • explicit,
  • awareness of when each is appropriate
  • an adequate set of profiles and profile validators
  • using ISO Schematron
  • Plurality
katie daisy

Prevent Email Security Threats - 0 views

  •  
    Today, email holds critical importance for every business to stay a step ahead of competitors. It would not be wrong to say that a proper email management is a backbone of most companies' daily activities. This underlines a need a growing need to secure emails against computer viruses, software failures, power failures, hard drive failures, or human errors. These threats can destroy the data including documents, pictures, emails and other files.
Gary Edwards

Siding with HTML over XHTML, My Decision to Switch - Monday By Noon - 1 views

  • Publishing content on the Web is in no way limited to professional developers or designers, much of the reason the net is so active is because anyone can make a website. Sure, we (as knowledgeable professionals or hobbyists) all hope to make the Web a better place by doing our part in publishing documents with semantically rich, valid markup, but the reality is that those documents are rare. It’s important to keep in mind the true nature of the Internet; an open platform for information sharing.
  • XHTML2 has some very good ideas that I hope can become part of the web. However, it’s unrealistic to think that all web authors will switch to an XML-based syntax which demands that browsers stop processing the document on the first error. XML’s draconian policy was an attempt to clean up the web. This was done around 1996 when lots of invalid content entered the web. CSS took a different approach: instead of demanding that content isn’t processed, we defined rules for how to handle the undefined. It’s called “forward-compatible parsing” and means we can add new constructs without breaking the old.

    So, I don’t think XHTML is a realistic option for the masses. HTML 5 is it.

    • Gary Edwards
       
      Great quote from CSS expert Hakon Wium Lie.
  • @marbux: Of course i disagree with your interop assessment, but I wondered how it is that you’re missing the point. I think you confuse web applications with legacy desktop – client/server application model. And that confusion leads to the mistake of trying to transfer the desktop document model to one that could adequately service advancing web applications.
  •  
    Response to marbux comments.
  •  
    # See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux

    # Response to marbux supporting the WebKit layout/document model.

    Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities.

    The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit.

    The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform.

    The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google.

    ~ge~
  •  
    A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.
1 - 8 of 8
Showing 20 items per page