Group items tagged Parse - Web2.0

PHP Parse error: syntax error, unexpected T_STRING - 0 views

www.fortunehost.com/...error-unexpected-t_string-1767

PHP Parse error syntax unexpected T_STRING HTML Code php_html file

shared by James Patel on 11 May 12 - No Cached

James Patel on 11 May 12

If you receive such error in error logs or in the browser then follow the below steps: For non suexec/suphp servers Create a .htaccess file under the

<div class="cArrow"> </div><div class="cContentInner">If you receive such error in error logs or in the browser then follow the below steps: For non suexec/suphp servers Create a .htaccess file under the</div>

...

Cancel

Boxee for Developers - 0 views

developer.boxee.tv/rss.html

boxee rss xml

shared by Mike Chelen on 10 Feb 09 - No Cached

Mike Chelen on 10 Feb 09

This document specifies the formats of RSS that Boxee can parse and use to display content. In general, Boxee supports a sub-set of Yahoo's Media RSS (http://search.yahoo.com/mrss). In addition, there are some additional tags defined by Boexe.

<div class="cArrow"> </div><div class="cContentInner">This document specifies the formats of RSS that Boxee can parse and use to display content. In general, Boxee supports a sub-set of Yahoo's Media RSS (<a href="http://search.yahoo.com/mrss" rel="nofollow" target="_blank">http://search.yahoo.com/mrss</a>). In addition, there are some additional tags defined by Boexe. </div>

...

Cancel

The Acid3 Test - 0 views

acid3.acidtests.org

browser test web2.0 standards dom

shared by yc c on 09 Mar 09 - Cached

yc c on 09 Mar 09

OM2 Core DOM2 Events DOM2 HTML DOM2 Range DOM2 Style (getComputedStyle, …) DOM2 Traversal (NodeIterator, TreeWalker) DOM2 Views (defaultView) ECMAScript HTML4 (, , …) HTTP (Content-Type, 404, …) Media Queries Selectors (:lang, :nth-child(), combinators, dynamic changes, …) XHTML 1.0 CSS2 (@font-face) CSS2.1 ('inline-block', 'pre-wrap', parsing…) CSS3 Color (rgba(), hsla(), …) CSS3 UI ('cursor') data: URIs SVG (SVG Animation, SVG Fonts, …) When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the test page without this constituting a failure in compliance. The Acid3 test measures some performance characteristics. The test does not attempt to make any comparisons or judgments as to the performance of any hardware used, and should not be used as a hardware benchmark. If the test is run on a slow computer or device, it may run slowly or not smoothly and this does not imply non-conformance.

<div class="cArrow"> </div><div class="cContentInner">OM2 Core DOM2 Events DOM2 HTML DOM2 Range DOM2 Style (getComputedStyle, …) DOM2 Traversal (NodeIterator, TreeWalker) DOM2 Views (defaultView) ECMAScript HTML4 (, , …) HTTP (Content-Type, 404, …) Media Queries Selectors (:lang, :nth-child(), combinators, dynamic changes, …) XHTML 1.0 CSS2 (@font-face) CSS2.1 ('inline-block', 'pre-wrap', parsing…) CSS3 Color (rgba(), hsla(), …) CSS3 UI ('cursor') data: URIs SVG (SVG Animation, SVG Fonts, …) When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the test page without this constituting a failure in compliance. The Acid3 test measures some performance characteristics. The test does not attempt to make any comparisons or judgments as to the performance of any hardware used, and should not be used as a hardware benchmark. If the test is run on a slow computer or device, it may run slowly or not smoothly and this does not imply non-conformance.</div>

...

Cancel

John Resig - Pure JavaScript ActionScript HTML XML Parser - 0 views

ejohn.org/...pure-javascript-html-parser

javascript html parser programming webdev library xml development

shared by Hendy Irawan on 04 Aug 11 - Cached

Hendy Irawan on 04 Aug 11

" I did some digging to see what people had previously built, but the landscape was pretty bleak. The only one that I could find was one made by Erik Arvidsson - a simple SAX-style HTML parser. Considering that this contained only the most basic parsing - and none of the actual, complicated, HTML logic there was still a lot of work left to be done. (I also contemplated porting the HTML 5 parser, wholesale, but that seemed like a herculean effort.) However, the result is one that I'm quite pleased with. It won't match the compliance of html5lib, nor the speed of a pure XML parser, but it's able to get the job done with little fuss - while still being highly portable."

<div class="cArrow"> </div><div class="cContentInner">" I did some digging to see what people had previously built, but the landscape was pretty bleak. The only one that I could find was one made by Erik Arvidsson - a simple SAX-style HTML parser. Considering that this contained only the most basic parsing - and none of the actual, complicated, HTML logic there was still a lot of work left to be done. (I also contemplated porting the HTML 5 parser, wholesale, but that seemed like a herculean effort.) However, the result is one that I'm quite pleased with. It won't match the compliance of html5lib, nor the speed of a pure XML parser, but it's able to get the job done with little fuss - while still being highly portable."</div>

...

Cancel

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

mondaybynoon.com/...er-xhtml-my-decision-to-switch

css html javascript xhtml

shared by Gary Edwards on 10 Jul 08 - Cached

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.
...

Cancel
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 on 10 Jul 08
  
  Great quote from CSS expert Hakon Wium Lie.
  
  <div class="cArrow"> </div><div class="cContentInner">Great quote from CSS expert Hakon Wium Lie.</div>
  
  ...
  
  Cancel
...

Cancel
@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.
...

Cancel

Gary Edwards on 10 Jul 08

Response to marbux comments.

<div class="cArrow"> </div><div class="cContentInner">Response to marbux comments.</div>

...

Cancel
Gary Edwards on 10 Jul 08

# 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~

<div class="cArrow"> </div><div class="cContentInner"># 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~</div>

...

Cancel
Gary Edwards on 10 Jul 08

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.

<div class="cArrow"> </div><div class="cContentInner">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.</div>

...

Cancel