Skip to main content

Home/ Open Web/ Group items tagged Standard

Rss Feed Group items tagged

Paul Merrell

IEEE wraps up standard for 22Mbps white space wireless | Electronista - 1 views

  • The IEEE announced today that it had finalized the 802.22TM white space wireless standards for Wireless Regional Area Networks (WRAN). White space wireless, sometimes called "super Wi-Fi" because of its long range capability and faster throughput, broadcasts data on unused, unlicensed frequencies that were designated for VHF and UHF television broadcast. The new standard will be capable of providing broadband wireless access over a large area, with a range of more than 60 miles from the transmitter. White space wireless can deliver up to 22 Mbps per channel.The white space standard was sought by Microsoft and other companies to make broadband access available in areas where extending wired internet service is impractical. Consumers will also benefit from extended range wireless hubs. A test network was established at Rice University in Houston in April.
Paul Merrell

Leaked: ITU's secret Internet surveillance standard discussion draft - Boing Boing - 0 views

  • Yesterday morning, I wrote about the closed-door International Telecommunications Union meeting where they were working on standardizing "deep packet inspection" -- a technology crucial to mass Internet surveillance. Other standards bodies have refused to touch DPI because of the risk to Internet users that arises from making it easier to spy on them. But not the ITU. The ITU standardization effort has been conducted in secret, without public scrutiny. Now, Asher Wolf writes,
  • I publicly asked (via Twitter) if anyone could give me access to documents relating to the ITU's DPI recommendations, now endorsed by the U.N. The ITU's senior communications officer, Toby Johnson, emailed me a copy of their unpublished policy recommendations. OOOPS! 5 hours later, they emailed, asking me not to publish it, in part or in whole, and that it was for my eyes only. Please publish it (credit me for sending it to you.) Also note: 1. The recommendations *NEVER* discuss the impact of DPI.
  • 2. A FEW EXAMPLES OF POTENTIAL DPI USE CITED BY THE ITU: "I.9.2 DPI engine use case: Simple fixed string matching for BitTorrent" "II.3.4 Example “Forwarding copy right protected audio content”" "II.3.6 Example “Detection of a specific transferred file from a particular user”" "II.4.2 Example “Security check – Block SIP messages (across entire SIP traffic) with specific content types”" "II.4.5 Example “Identify particular host by evaluating all RTCP SDES packets”" "II.4.6 Example “Measure Spanish Jabber traffic”" "II.4.7 Example “Blocking of dedicated games”" "II.4.11 Example “Identify uploading BitTorrent users”" "II.4.13 Example “Blocking Peer-to-Peer VoIP telephony with proprietary end-to-end application control protocols”" "II.5.1 Example “Detecting a specific Peer-to-Peer VoIP telephony with proprietary end-to-end application control protocols”"
Gary Edwards

Office to finally fully support ODF, Open XML, and PDF formats | ZDNet - 0 views

  •  
    The king of clicks returns!  No doubt there was a time when the mere mention of ODF and the now legendary XML "document" format wars with Microsoft could drive click counts into the statisphere.  Sorry to say though, those times are long gone. It's still a good story though.  Even if the fate of mankind and the future of the Internet no longer hinges on the outcome.  There is that question that continues defy answer; "Did Microsoft win or lose?"  So the mere announcement of supported formats in MSOffice XX is guaranteed to rev the clicks somewhat. Veteran ODF clickmeister SVN does make an interesting observation though: "The ironic thing is that, while this was as hotly debated am issue in the mid-2000s as are mobile patents and cloud implementation is today, this news was barely noticed. That's a mistake. Updegrove points out, "document interoperability and vendor neutrality matter more now than ever before as paper archives disappear and literally all of human knowledge is entrusted to electronic storage." He concluded, "Only if documents can be easily exchanged and reliably accessed on an ongoing basis will competition in the present be preserved, and the availability of knowledge down through the ages be assured. Without robust, universally adopted document formats, both of those goals will be impossible to attain." Updegrove's right of course. Don't believe me? Go into your office's archives and try to bring up documents your wrote in the 90s in WordPerfect or papers your staff created in the 80s with WordStar. If you don't want to lose your institutional memory, open document standards support is more important than ever. "....................................... Sorry but Updegrove is wrong.  Woefully wrong. The Web is the future.  Sure interoperability matters, but only as far as the Web and the future of Cloud Computing is concerned.  Sadly neither ODF or Open XML are Web ready.  The language of the Web is famously HTML, now HTML5+
Paul Merrell

Which HTML5? - WHATWG and W3C Split - 0 views

  •  
    A "Living Standard?" Sorry, WHATWG, but "standard" has a legal definition and minimum requirements; you're operating outside the law. WHATWG chooses what they think they can get away with and ignoring competition law.
Gary Edwards

HTML5, Cloud and Mobile Create 'Perfect Storm' for Major App Dev Shift - Application De... - 0 views

  •  
    Good discussion, but it really deserves a more in-depth thrashing.  The basic concept is that a perfect storm of mobility, cloud-computing and HTML5-JavaScript has set the stage for a major, massive shift in application development.  The shift from C++ to Java is now being replaced by a greater shift from Java and C++ to JavaScript-JSON-HTML5. Interesting, but i continue to insist that the greater "Perfect Storm" triggered in 2008, is causing a platform shift from client/server computing to full on, must have "cloud-computing".   There are three major "waves"; platform shifts in the history of computing at work here.  The first wave was "Mainframe computing", otherwise known as server/terminal.  The second wave was that of "client/server" computing, where the Windows desktop eventually came to totally dominate and control the "client" side of the client/server equation. The third wave began with the Internet, and the dominance of the WWW protocols, interfaces, methods and formats.  The Web provides the foundation for the third great Wave of Cloud-Computing. The Perfect Storm of 2008 lit the fuse of the third Wave of computing.  Key to the 2008 Perfect Storm is the world wide financial collapse that put enormous pressure on businesses to cut cost and improve productivity; to do more with less, or die.  The survival maxim quickly became do more with less people - which is the most effective form of "productivity".  The nature of the collapse itself, and the kind of centralized, all powerful bailout-fascists governments that rose during the financial collapse, guaranteed that labor costs would rise dramatically while also being "uncertain".  Think government controlled healthcare. The other aspects of the 2008 Perfect Storm are mobility, HTML5, cloud-computing platform availability, and, the ISO standardization of "tagged" PDF.   The mobility bomb kicked off in late 2007, with the introduction of the Apple iPhone.  No further explanation needed :) Th
Paul Merrell

EU Committee Votes to Make All Smartphone Vendors Utilize a Standard Charger - HotHardware - 0 views

  • The EU has been known to make a lot of odd decisions when it comes to tech, such as forcing Microsoft's hand at including a "browser wheel" with its Windows OS, but this latest decision is one I think most people will agree with. One thing that's frustrating about different smartphones is the occasional requirement to use a different charger. More frustrating is actually losing one of these chargers, and being unable to charge your phone even though you might have 8 of another charger readily available.
  • While this decision would cut down on this happening, the focus is to cut down on waste. On Thursday, the EU's internal market and consumer protection committee voted on forcing smartphone vendors to adopt a standard charger, which common sense would imply means micro USB, given it's already featured on the majority of smartphones out there. The major exception is Apple, which deploys a Lightning connector with its latest iPhones. Apple already offers Lightning to micro USB cables, but again, those are only useful if you happen to own one, making a sudden loss of a charger all-the-more frustrating. While Lightning might offer some slight benefits, Apple implementing a micro USB connector instead would make situations like those a lot easier to deal with (I am sure a lot of us have multiple micro USB cables lying around). Even though this law was a success in the initial voting, the government group must still bring the proposal to the Council which will then lead to another vote being made in the Parliament. If it does end up passing, I have a gut feeling that Apple will modify only its European models to adhere to the law, while its worldwide models will remain with the Lightning connector. Or, Apple might be able to circumvent the law if it offers to include the micro USB cable in the box, essentially shipping the phone with that connector.
  •  
    This seems like a reasonable role for government. 
Gary Edwards

http://www.sdtimes.com/lgp/images/wp/What's%20next%20for%20HTML5.pdf - 0 views

  •  
    White paper from Intel discusses HTML5 and the future of computing. Intro: Computer programmers have been grappling with cross-platform issues since there was a second platform. Since then, the number of issues has rapidly increased. Today's developers can target at least four operating systems (plus their fragments), running on devices with all shapes, sizes, resolutions, persistence levels, input methods, carrier networks, connection speeds and states, UI conventions, app stores, deployment and update mechanisms, and on and on. Many of the world's developers once looked to Java* as the shining knight of cross-platform development. Indeed, the structured language of Sun* (and now Oracle) continues to solve many cross-platform issues. But it also introduces obstacles, not the least of which is a class structure that heavily burdens even the tiniest of program functions. Java's heft grew still more burdensome as developers turned to the browser for app delivery; Java applets are black boxes that are as opaque to the browser as the language is closed to the developer (with all due deference to the JCP). Around the same time Java was fuelling the browser wars, a like-named interpreted language was beginning to emerge. First called Mocha, later LiveScript, and finally JavaScript*, the language proved more useful than Java in some ways because it could interact with the browser and control content display using HTML's cascading style sheets (CSS). JavaScript support soon became standard in every browser. It is now the programming language of HTML5, which is currently being considered by the World Wide Web Consortium as the next markup-language standard. To better understand HTML5-why it is where it is and where it's going- Intel® Software Adrenaline turned to Moh Haghighat, a senior principal engineer in the Developer Products Division of Intel's Software and Services Group. Moh was the technical lead from Intel's side on the first JavaScript
Gary Edwards

Google Chrome 5 WebKit - Firefox - Opera Comparisons - BusinessWeek - 0 views

  •  
    Chrome runs as close as any browser can to the bleeding edge of Web standards. Though it uses the same open source WebKit rendering engine as Safari, it doesn't reliably support the controversial, proprietary CSS3 transformation and animation tricks that Apple's built into Safari. However, like every browser I tested, it earned a perfect score in a compatibility test for CSS3 selectors, and it joined Safari and Opera with a flawless score of 100 in the Acid3 web standards benchmark. Chrome 5 also supports both Apple's H.264 codec and Mozilla's preferred open source Ogg Theora technology for plugin-free HTML5 video, and it beautifully played back HTML5 demo videos from YouTube and Brightcove. In XHTML and CSS tests, Chrome was surprisingly slower than Safari, despite their shared rendering engine -- but the race was close. Safari rendered a local XHTML test page in 0.58 seconds to Chrome's 0.78 seconds, and a local CSS test page in 33 milliseconds to Chrome's 51 milliseconds. Note that Chrome still rendered XHTML more than twice as fast as Opera (1.67 seconds) and left Firefox (12.42 seconds--no, that's not a typo) eating its dust. In CSS, it also beat the pants off Opera (193 milliseconds) and Firefox (342 milliseconds). But Chrome shines brightest when handling JavaScript. Its V8 engine zipped through the SunSpider Javascript benchmark in 448.6 milliseconds, narrowly beating Opera's 485.8 milliseconds, and absolutely plastering Firefox's 1,161.4 milliseconds. However, Safari 5's time of 376.3 miliseconds in the SunSpider test beat Chrome 5 handily.
Gary Edwards

Handicapping Microsoft And Google's Online Collision | Moving the Point of Assembly - 0 views

  •  
    Michael Hickins weighs in the war between Microsoft and Google.  This time he focuses in Microsoft's attempt to move the point of assembly from the desktop productivity environment to an exclusive MS-Web center. The question is whether enterprises will move to Google (or some other standards- and Web-based vendor) in time, or whether they will get trapped in the fly-paper of Microsoft code, from which they will be hard pressed to detach their documents. This was the problem Massachusetts faced when the state wanted to abandon Microsoft in favor of standards-based applications; their legacy documents were filled with Microsoft code they couldn't translate cleanly into another format. When the race is finished, that may turn out to be Microsoft's greatest strength. While the rest of the world embraces openness and cooperation, Microsoft remains proprietary and closed like a fist.
Gary Edwards

OpenStack Open Source Cloud Computing Software - 0 views

  •  
    OpenStack: The 5-minute Overview What the software does: The goal of OpenStack is to allow any organization to create and offer cloud computing capabilities using open source software running on standard hardware. OpenStack Compute is software for automatically creating and managing large groups of virtual private servers. OpenStack Storage is software for creating redundant, scalable object storage using clusters of commodity servers to store terabytes or even petabytes of data. Why open matters: All of the code for OpenStack is freely available under the Apache 2.0 license. Anyone can run it, build on it, or submit changes back to the project. We strongly believe that an open development model is the only way to foster badly-needed cloud standards, remove the fear of proprietary lock-in for cloud customers, and create a large ecosystem that spans cloud providers. Who it's for: Institutions and service providers with physical hardware that they'd like to use for large-scale cloud deployments. (Additionally, companies who have specific requirements that prevent them from running in a public cloud.) How it's being used today: Organizations like Rackspace Hosting and NASA are using OpenStack technologies to manage tens of thousands of compute instances and petabytes of storage. Timeline: Openstack was announced July 19th, 2010. While many components of OpenStack have been used in production for years, we are in the very early stages of our efforts to offer these technologies broadly as open source software. Early code is now available on LaunchPad, with an inital release for OpenStack Storage expected in mid-September and an initial release for OpenStack Compute expected in mid-October.
Gary Edwards

Does It Matter Who Wins the Browser Wars? Only if you care about the Future of the Open... - 1 views

  •  
    The Future of the Open Web You're right that the browser wars do not matter - except for this point of demarcation; browsers that support HTML+ and browser that support 1998 HTML. extensive comment by ~ge~ Not all Web services and applications support HTML+, the rapidly advancing set of technologies that includes HTML5, CSS3, SVG/Canvas, and JavaScript (including the libraries and JSON). Microsoft has chosen to draw the Open Web line at what amounts to 1998-2001 level of HTML/CSS. Above that line, they provision a rich-client / rich-server Web model bound to the .NET-WPF platform where C#, Silverlight, and XAML are very prominent. Noticeably, Open Web standards are for the most part replaced at this richer MSWeb level by proprietary technologies. Through limited support for HTML/CSS, IE8 itself acts to dumb down the Open Web. The effect of this is that business systems and day-to-day workflow processes bound to the ubiquitous and very "rich" MSOffice Productivity Environment have little choice when it comes to transitioning to the Web but to stay on the Microsoft 2010 treadmill. Sure, at some point legacy business processes and systems will be rewritten to the Web. The question is, will it be the Open Web or the MS-Web? The Open Web standards are the dividing line between owning your information and content, or, having that content bound to a Web platform comprised of proprietary Microsoft services, systems and applications. Web designers and developers are still caught up in the browser wars. They worry incessantly as to how to dumb down Web content and services to meet the limited functionality of IE. This sucks. So everyone continues to watch "the browser wars" stats. What they are really watching for though is that magic moment where "combined" HTML+ browser uptake in marketshare signals that they can start to implement highly graphical and collaboratively interactive HTML+ specific content. Meanwhile, the greater Web is a
Gary Edwards

EU settlement will alter Microsoft's stance on interoperability -- Government Computer ... - 0 views

  •  
    EU settlement will alter Microsoft's stance on interoperability By Kurt Mackie Dec 21, 2009 Microsoft provided more details about its settlement with the European Commission (EC), particularly with regard to interoperability agreements. In a blog post on Thursday, Dave Heiner, Microsoft's vice president and deputy general counsel, claimed that the company has pledged to implement a threefold approach to interoperability that EC Commissioner Neelie Kroes outlined in past speeches. Heiner summarized that approach: companies should disclose technical information, provide a remedy if the information is inadequate and charge equitable royalty rates for associated intellectual property. Kroes had also specifically called for companies to follow open standards as one of the best ways to achieve interoperability. However, Heiner omitted the word, "open," from his comment. He said that "products from different firms can work well together when they implement common, well-designed industry standards." Microsoft's interoperability pledge announced this week appears to continue ideas the company put forth in February 2008. At that time, the company announced broad interoperability principles as well as APIs for software developers working with Microsoft's mainline products, including Windows client and server operating systems, Exchange, Office and SharePoint, among others. Microsoft has been releasing documentation for that purpose, with "hundreds of Microsoft developers" devoted to the effort, according to Heiner. The new elements to Microsoft's interoperability pledge appear to be warranty and patent-sharing templates. Those documents, and more, can be accessed at the end of a statement about the settlement by Brad Smith, Microsoft's senior vice president and general counsel.
Gary Edwards

Is the Apps Marketplace just playing catchup to Microsoft? | Googling Google | ZDNet.com - 0 views

shared by Gary Edwards on 12 Mar 10 - Cached
  • Take the basic communication, calendaring, and documentation enabled for free by Apps Standard Edition, add a few slick applications from the Marketplace and the sky was the limit. Or at least the clouds were.
    • Gary Edwards
       
      Google Apps have all the basic elements of a productivity environment, but lack the internal application messaging, data connectivity and exchange that made the Windows desktop productivity platform so powerful.   gAPPS are great.  They even have copy/paste! But they lack the basics needed for simple "merge" of client and contact data into a wordprocessor letter/report/form/research paper. Things like DDE, OLE, ODBC, MAPI, COM, and DCOM have to be reinvented for the Open Web.   gAPPS is a good place to start.  But the focus has got to shift to Wave technologies like OT, XMPP and JSON.  Then there are the lower level innovations such as Web Sockets, Native Client, HTML5, and the Cairo-Skia graphics layer (thanks Florian).
  • Whether you (or your business) choose a Microsoft-centered solution that now has well-implemented cloud integration and tightly coupled productivity and collaboration software (think Office Live Web Apps, Office 2010, and Sharepoint 2010) or you build a business around the web-based collaboration inherent in Google Apps and extend its core functions with cool and useful applications, you win.
    • Gary Edwards
       
      Not true!!! The Microsoft Cloud is based on proprietary technologies, with the Silverlight-OOXML runtime/plug-in at the core of a WPF-.NET driven "Business Productivity Platform. The Google Cloud is based on the Open Web, and not the "Open Web" that's tied up in corporate "standards" consortia like the W3C, OASIS and Ecma. One of the reasons i really like WebKit is that they push HTML5 technologies to the edge, submitting new enhancements back into the knuckle dragging W3C HTML5 workgroups as "proposals".  They don't however wait for the entangled corporate politics of the W3C to "approve and include" these proposals.  Google and Apple submit and go live simultaneously.   This of course negates the heavy influence platform rivals like Microsoft have over the activities of corporate standards orgs.  Which has to be done if WebKit-HTML5-JavaScript-XMPP-OT-Web Sockets-Native Client family of technologies is ever to challenge the interactive and graphical richness of proprietary Microsoft technologies (Silverlight, OOXML, DrawingML, C#). The important hedge here is that Google is Open Sourcing their enhancements and innovations.  Without that Open Sourcing, i think there would be reasons to fear any platform player pushing beyond the corporate standards consortia approval process.  For me, OSS balances out the incredible influence of Google, and the ownership they have over core Open Web productivity application components. Which is to say; i don't want to find myself tomorrow in the same position with a Google Open Web Productivity Platform, that i found myself in with the 1994 Windows desktop productivity environment - where Microsoft owned every opportunity, and could take the marketshare of any Windows developed application with simple announcements that they to will enter that application category.  (ex. the entire independent contact/project management category was wiped out by mere announcement of MS Outlook).
Paul Merrell

Cover Pages: Content Management Interoperability Services (CMIS) - 0 views

  • On October 06, 2008, OASIS issued a public call for participation in a new technical committee chartered to define specifications for use of Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors. The OASIS Content Management Interoperability Services (CMIS) TC will build upon existing specifications to "define a domain model and bindings that are designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. The TC will not prescribe how specific features should be implemented within those Enterprise Content Management (ECM) systems. Rather it will seek to define a generic/universal set of capabilities provided by an ECM system and a set of services for working with those capabilities." As of February 17, 2010, the CMIS technical work had received broad support through TC participation, industry analyst opinion, and declarations of interest from major companies. Some of these include Adobe, Adullact, AIIM, Alfresco, Amdocs, Anakeen, ASG Software Solutions, Booz Allen Hamilton, Capgemini, Citytech, Content Technologies, Day Software, dotCMS, Ektron, EMC, EntropySoft, ESoCE-NET, Exalead, FatWire, Fidelity, Flatirons, fme AG, Genus Technologies, Greenbytes GmbH, Harris, IBM, ISIS Papyrus, KnowledgeTree, Lexmark, Liferay, Magnolia, Mekon, Microsoft, Middle East Technical University, Nuxeo, Open Text, Oracle, Pearson, Quark, RSD, SAP, Saperion, Structured Software Systems (3SL), Sun Microsystems, Tanner AG, TIBCO Software, Vamosa, Vignette, and WeWebU Software. Early commentary from industry analysts and software engineers is positive about the value proposition in standardizing an enterprise content-centric management specification. The OASIS announcement of November 17, 2008 includes endorsements. Principal use cases motivating the CMIS technical work include collaborative content applications, portals leveraging content management repositories, mashups, and searching a content repository.
  •  
    I should have posted before about CMIS, an emerging standard with a very lot of buy-in by vendors large and small. I've been watching the buzz grow via Robin Cover's Daily XML links service. IIt's now on my "need to watch" list. 
Gary Edwards

Kaazing | Kaazing WebSocket Gateway - 0 views

  •  
    Kaazing WebSocket Gateway is the world's only enterprise solution for full-duplex, high-performance communication over the Web using the HTML5 WebSocket standard. Designed to be the next evolutionary step in web communication, HTML5 WebSocket addresses the problems inherent with traditional Ajax and Comet solutions today. True real-time connectivity in the browser and on mobile devices is now a reality thanks to this exciting new standard. Kaazing WebSocket Gateway delivers these features and benefits with the performance, scalability, robustness, and security that enterprises demand.
Gary Edwards

Introducing CloudStack - 0 views

  •  
    CloudStack Manifesto Before getting into the framework specifics, it would be worthwhile to cover some of the design principles we had in mind while we were building CloudStack: CloudStack brings together the best of the web and the desktop: We strongly believe in the convergence of the desktop and the web and will continually strive to expose more services that bring out the best from both. CloudStack enables rapid application development and deployment: Out of the box, CloudStack provides a fully brand able and deployable shell application that can be used as a starting point to jumpstart application development. CloudStack also provides a scalable deployment environment for hosting your applications. CloudStack leverages existing web technologies: We built the CloudStack P2WebServer container over the J2EE compliant Jetty web server. As a result, CloudStack applications are built using standard web technologies like AJAX, HTML, JavaScript, Flash, Flex, etc. CloudStack does not reinvent the wheel: We strive to reuse as much as possible from other open source projects and standards. By creatively stringing together seemingly disparate pieces, like P2P and HTTP, it?fs amazing to create something that's really much greater than the sum of the parts. CloudStack does aim to simplify existing technologies: We will abstract and simplify existing interfaces if needed. For example, we built simpler abstractions for JXTA (P2P) and Jena (RDF Store). CloudStack encourages HTML-based interfaces: We believe that the web browser is the most portable desktop application container with HTML being the lingua franca of the web. Rather than writing a native widget interface for the local desktop application and another web-based interface for the remote view, we encourage writing a single interface that can be reused across both local and remote views. HTML based interfaces are inherently cross-platform and provide good decoupling of design from code (versus having the UI as compiled
Gary Edwards

Adobe's Web Typography design work lands in WebKit browser | Deep Tech - CNET News - 0 views

  •  
    Adobe has contributed the first "CSS Regions" patch to the OS WebKit project.  CSS Regions is at the core of Adobe's flowing Web Typography work, and has been submitted to the W3C CSS standardization effort.   No mention yet as to what kind of CSS3-HTML5 authoring and publication tools Adobe has in the works, but the inclusion in WebKit will no doubt shake things up in the world of visually-immersive packaging (FlipBoard, OnSwipe, TreeSaver, Needle, etc.) excerpt:Today, the first bit of Adobe-written code landed in the WebKit browser engine project, an early step to try to bring magazine-style layouts to Web pages using an extension to today's CSS (Cascading Style Sheets) technology. Adobe calls the technology CSS Regions. The move begins fulfilling a plan Adobe announced in May to build the technology into WebKit and--if the company can persuade others to embrace it--furthers Adobe's ambition to standardize the advanced CSS layout mechanism. WebKit
Gary Edwards

The Future of Web Layout: CSS 3 Flexible Box Model | Ajaxian » - 0 views

  •  
    Florian is fond of pointing out to me that Open Web HTML+ lacks a representational model - a standard method for layout that can then be interoperably rendered across any ACiD 3 browser.  Florian is right that HTML+ is not quite there yet.  But many engineers and Web designers are working on this problem.  The W3C may have dropped CSS layout years ago, but the WebKit and Mozilla faithful toil upwards through the night to get it right.  The Flexible Box spec pushes the envelope. Excerpt:  Alex Russell has been having a really interesting discussion with some standards folks about what is wrong on the Web right now, and it narrowed down to discuss CSS variables as a case study (it aint perfect, but get DRY and ship it!) Alex tells it how it is, but people forget that he does this as he is passionate about the Web, and that he does also give credit and positive outlook IF it is due! His latest post shows this as he talked about CSS 3 progress and specifically the flexible box model that Mozilla and WebKit have had forevaaaaaah: David Baron (of Mozilla fame) is editing a long-overdue but totally awesome Flexible Box spec, aka: "hbox and vbox". Both Gecko and WebKit-derived browsers (read: everything that's not IE) supports hbox and vbox today, but using it can be a bit tedious. Should you be working on an app that can ignore IE (say, for a mobile phone), this should help make box layouts a bit easier to get started with:
Gary Edwards

Google brings Chrome's renderer to IE with browser plugin - Ars Technica - 0 views

  •  
    Wow.  Google has re-purposed IE for the Open Web! excerpts: A number of modern Web features cannot be used pervasively on the Internet because Microsoft's dominant browser, Internet Explorer, often fails to support current and emerging standards. Google has a plan to drag IE into the world of modern browsing by building a plugin that will allow it to use Chrome's HTML renderer and high-performance JavaScript engine. Google hopes that delivering Chrome's rendering engine in an IE plugin will provide a pragmatic compromise for users who can't upgrade. Web developers will be able to use an X-UA-Compatible meta tag to specify that their page should be displayed with the Chrome renderer plugin instead of using Internet Explorer's Trident engine. This approach will ensure that the Chrome engine is only used when it is supposed to and that it won't disrupt the browser's handling of legacy Web applications that require IE6 compatibility. Google is opening the source code now to get feedback and assistance with testing. The plugin will include Google's speedy V8 JavaScript engine, support for Canvas, SVG, and all of the other features that users enjoy today in Chrome. That also includes the next-generation CSS rendering features of WebKit such as rounded corners. The pages will look just like they would if they were rendered in Chrome. Google is going much further [than Mozilla] by providing the entire renderer. If the plugin is adopted by a sufficiently broad number of users, then Web developers will never again have to contend with IE's limitations. It could also open the door for adoption of HTML 5 and other important emerging standards.
  •  
    Interesting strategy. Now if we could just get da Vinci/HTML+ to market ...
Gary Edwards

Mobile Cloud Computing: $9.5 Billion by 2014 - 0 views

  •  
    I left a lengthy comment on this very good article. excerpt: According to the latest study from Juniper Research, the market for cloud-based mobile applications will grow 88% from 2009 to 2014. The market was just over $400 million this past year, says Juniper, but by 2014 it will reach $9.5 billion. Driving this growth will be the adoption of the new web standard HTML5, increased mobile broadband coverage and the need for always-on collaborative services for the enterprise. Cloud Apps in your Pocket Mobile cloud computing is a term that refers to an infrastructure where both the data storage and the data processing happen outside of the mobile device from which an application is launched. To the typical consumer, a cloud-based mobile application looks and feels just like any app purchased or downloaded from a mobile application store like iTunes. However, the app is driven from the "cloud," not from the handheld device itself. There are already a few well-known mobile cloud apps out there including Google's Gmail and Google Voice for iPhone. When launched via iPhone homescreen shortcuts, these apps perform just like any other app on the iPhone, but all of their processing power comes from the cloud. In the future, there will be even more applications like these available, but they won't necessarily be mobilized web sites like those in Google's line-up. Cloud-based mobile apps are perfectly capable of being packaged in a way that allows them to be sold alongside traditional mobile apps in mobile application stores, with no one but the developers any wiser. HTML5 Paves the Way for Mobile Web's Future
‹ Previous 21 - 40 of 170 Next › Last »
Showing 20 items per page