Skip to main content

Home/ Future of the Web/ Group items tagged ajax

Rss Feed Group items tagged

Gary Edwards

Good News for Ajax and the Open Web - The Browser Wars Are Back - 0 views

  • For much of this decade, Web browsing has been dominated by Microsoft's Internet Explorer (IE), which at its height achieved market share numbers approaching 95%, with the result that Microsoft owned a de facto standard for the Web and held effective veto power over the future of HTML. During much of this period, Microsoft suspended development of IE, with the result that virtually no new features appeared within the world's dominant browser from 2001 to 2006. But while IE was sleeping, one of the biggest phenomena of the computer age happened: Ajax. Clever Web developers discovered gold in them there mountains. Using Ajax techniques, Web developers could create desktop-like rich user interfaces right in the browser. Not only that, Ajax was evolutionary. Ajax offered an incremental path from the industry's existing HTML-based infrastructure and know-how, allowing Web developers to add rich Ajax elements to an existing HTML page.
  • A companion community effort helping to accelerate the adoption of open standards is the Web Standards Project (http://www.webstandards.org), which is producing a set of "acid tests" that verify browser support for Open Web technologies, such as HTML, CSS and JavaScript. Acid2 is focused mainly on CSS support, and is now supported by Opera, Safari/WebKit, and IE. Acid3 (http://www.webstandards.org/action/acid3) tests DOM scripting, CSS rendering,
    • Gary Edwards
       
      The amazing thing about Ajax and the Open Web is the way WHATWG, WebKit, and the Web Standards "ACID" work has accelerated Open Web Standards, pushing far beyond the work of the glacial W3C.
  • Runtime Advocacy Task Force
  •  
    Lengthy artilce from the OpenAjax Alliance summarizing HTML, Ajax and the future of the Open Web. Very well referenced. Lots of whitepapers and links
  •  
    good summarization of the Open Web future.
  •  
    Most quality online stores. Know whether you are a trusted online retailer in the world. Whatever we can buy very good quality. and do not hesitate. Everything is very high quality. Including clothes, accessories, bags, cups. Highly recommended. This is one of the trusted online store in the world. View now www.retrostyler.com
Gary Edwards

When You're a WebKit Hammer, Everything Looks Like an Open Web Nail ... As it should! - 0 views

  • You’re still waiting for me to explain what I meant when I referred to JavaScript as a last resort. I hinted at it in the preceding paragraph. Not the part on JavaScript debugging, but my reference to CSS and HTML. These do a lot more than paint screens. They are a browser's client-side framework. Everything they do is handled as native code. In other words, they're fast. CSS3 and HTML5 are too inconsistently implemented (if at all) across browsers to design to unless you're specifically targeting Safari, iPhone, or other WebKit-based browsers.
    • Gary Edwards
       
      Tom makes the point that the use of AJAX JavaScript breaks Web interoperability. He further points out that HTML is a static layout language, where CSS is dynamic and adaptive. (Use HTML5/DOM for document structure, and CSS4 for presentation - layout, formatting and visual interface).

      It is the consistency of the WebKit document model across all WebKit browsers that makes for an interoperable Open Web future. I would not however discount the importance of Firefox and Opera embracing the WebKit document model (HTML5, CSS4, SVG/Canvas, JavaScript, DOM2). That's our guarantee that the future of the Open Web will actually be open.

      Tom goes on to suggest that instead of "AJAX", developers would be better off thinking in terms of "ACHJAX": Asynchronous CSS4 - HTML5 - JavaScript and XML ..... with the focus on getting as much done in CSS4 as possible.
  •  
    InfoWorld's Tom Yager makes the case for the WebKit visual document model over AJAX. The problem with AJAX as he sees it is that it's JavaScript heavy. And that breaks precious Web interoperability. He makes the point that if something can be done in CSS, it should. He also argues that WebKit is the best tool because the document model is that of advanced HTML5 and CSS3.

    "... These [WebKit] browsers also share a stellar accelerated JavaScript interpreter that makes the edit/run/debug cycle go faster. They are also the only browsers that deliver on CSS4 and HTML5 standards (with some elements that are proposed to the W3C standards body). Sites that are visually rich may start sprouting "best viewed with Safari" banners until other browsers catch up. The banner would also let users know that your site is optimized for iPhone....."

    Humm. Did you catch that? CSS4!!! I guess he's referring to the WebKit penchant for putting advanced graphical transitions and animations into CSS instead of relying on a device specific or OS specific API.

    Placing the visual interface instructions in the documents presentation layer (CSS4) is a revolutionary idea. The WebKit model will go a long way towards creating a global interoperability layer that rides above lower device, OS, browser and application specifics. So yes, by all means let's go with CSS4 :)

Gary Edwards

WebKit, AJAX and ARAX | Readers Welcome ARAX and More: Darryl Taft follow-up zdnet - 0 views

  • A commenter on the ARAX article on eWEEK's site named Gary Edwards said, "It seems to me that Adobe and Microsoft are using the browser plug-in model as a distribution channel for their proprietary run-time engines. Or should we call them VMs [virtual machines]? "The easiest way for Web developers to sidestep problematic browser wars, and still be able to push the envelope of the interactive Web, may well be to write to a universal run-time plug-in like Adobe AIR or Microsoft Silverlight. IMHO, the 'browser' quickly fades away once this direct development sets in." Moreover, Edwards said, "Although there are many ways to slice this discussion, it might be useful to compare Adobe RIA [Rich Internet Applications] and Microsoft Silverlight RIA in terms of Web-ready, highly interactive documents. The Adobe RIA story is quite different from that of Silverlight. Both however exploit the shortcomings of browsers; shortcomings that are in large part, I think, due to the disconnect the browser community has had with the W3C [World Wide Web Consortium]. The W3C forked off the HTML-CSS [Cascading Style Sheets] path, putting the bulk of their attention into XML, RDF and the Semantic Web. The Web developer community stayed the course, pushing the HTML-CSS envelope with JavaScript and some rather stunning CSS magic. "Adobe seems to have picked up the HTML-CSS-JavaScript trail with a Microsoft innovation to take advantage of browser cache, DHTML (Dynamic HTML). DHTML morphs into AJAX, (which [is] so wild as to have difficulty scaling). And AJAX gets tamed by an Adobe-Apple sponsored WebKit."
  •  
    Darryl Taft writes a follow up article covering the comments to his original AJAX-ARAX ruby on rails MS-iron python story
  •  
    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
Gary Edwards

Nokia and Google: Too much emphasis on the mobile OS? | ge TalkBack on ZDNet - 0 views

  • It's the document model! There is nothing wrong with RiA. Adobe is doing great stuff, and they fully support the WebKit flow document model in their RiA. Silverlight on the other hand is a true threat to the Open Web because it implements uniquely proprietary format, protocol and interface alternatives. The problem with AJAX is that it's difficult to scale. Advancing JavaScript libraries, structured WebKit, BrowserPlus and Google's GWT-Google Gears promise to tame that problem. At the end of the day though, i see AJAX as an important aspect of the browser as an RiA runtime engine. Here's what concerns me; 500 million MSOffice desktops that anchor most of the world's client/server business processes speak XAML "fixed/flow". These desktops are the information pumps for billions of business critical documents. And they do not speak the language of the Open Web. They speak the language of the Microsoft Web-Stack and Mesh services.
  •  
    Response to questions about RiA vs AJAX.
  •  
    Most quality online stores. Know whether you are a trusted online retailer in the world. Whatever we can buy very good quality. and do not hesitate. Everything is very high quality. Including clothes, accessories, bags, cups. Highly recommended. This is one of the trusted online store in the world. View now www.retrostyler.com
Gary Edwards

Running beyond the browser - 0 views

  •  
    Although there are many ways to slice this discussion, it might be useful to compare Adobe RIA and Microsoft Silverlight RIA in terms of web ready, highly interactive documents. The Adobe RIA story is quite different from that of Silverlight. Both however exploit the shortcomings of browsers; shortcomings that are in large part, i think, due to the disconnect the browser community has had with the W3C. The W3C forked off the HTML-CSS path, putting the bulk of their attention into XML, RDF and the Semantic Web. The web developer community stayed the course, pushing the HTML-CSS envelope with JavaScript and some rather stunning CSS magic. Adobe seems to have picked up the HTML-CSS-Javascript trail with a Microsoft innovation to take advantage of browser cache, DHTML (Dynamic HTML). DHTML morphs into AJAX, (which so wild as to have difficulty scaling). And AJAX gets tamed by an Adobe-Apple sponsored WebKit. Most people see WebKit as a browser specific layout engine, and compare it to the IE and Gecko on those terms. I would argue however that WebKit is both a document model and, a document format. For sure it's a framework for very advanced HTML-CSS-DOM-Javascript work. Because the Adobe AIR run-time is based on WebKit layout, WebKit documents can hit on all cylinders across any browser able to implement the AIR plug-in. Meaning, web developers and web content providers need only target the WebKit document model to attain the interactive access ubiquity all seek. Very cool. Let me also add that the WebKit HTML-CSS-DOM-Javascript model is capable of "fixed/flow" representation. I'll explain the importance of "fixed/flow" un momento, but think about how iPhone renders a web page and you'll understand the "flow" side of this equation.
  •  
    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
Gary Edwards

AJAX, AIR, RIA, Adobe Getting It, David Mendels and "Rich Internet Apps: How ... - 0 views

  • What we saw them do was create a single screen application with rich interactivity on the client, but still all of the benefits of being a web based application (nothing to install, back end connectivity for inventory and other data using XML, use of client side media/animation to guide the user, reachable through any browser, etc.) We really looked at this as the best of web applications and the best of desktop applications: rich connectivity, platform independence, no install, lightweight as well as rich client side logic and interactivity, ability to integrate rich media and communications. But we dropped the baggage of the page based metaphor that basically required a page refresh for everything and got beyond the layout/graphics/media constraints of HTML.
  •  
    Blog from James Governor covers an exchange with Adobe's David Mendels concerning the transition from the static document centric Web 1.0, to the dynamic application platform we know today as the Web 2.0. David discusses the transition from DHTML to AJAX to RIA. David and his group at Adobe witnessed the transition and coined the phrase RIA - Rich Internet Application, to describe this incredible transition. No mention of WebKit as an important aspect enabling the interactive - dynamic document model behind Adobe RIA.
  •  
    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
Gary Edwards

More WebKit Goodies - CSS Transforms and Transitions - the OSX Dock example | theChrisW... - 0 views

  •  
    Chris Walker provides some interactive demonstrations of the powerful webkit-transforms that are placed in CSS. So, what can we do with all this magic? Well, the culmination of the Chris Walker demo is a Mac OSX style Dock menu, using no Javascript...

    ".....Yes, that's right a bulging docked menu, with no javascript. Just so you remember, there no javascript in the demo. Check out the Javascript free OSX Dock Menu Demo.

    This demo actually proves an important point Tom Yager made earlier about Ajax; Will JavaScript inconsistencies break the Web?

    Taking AJAX literally makes lousy Web apps: "As little as possible should be the rule for JavaScript, which must play a supporting role to CSS and HTML". Tom concludes that it's best to follow the WebKit model, putting everything possible into first CSS4, then HTML5, and then JavaScript. I would argue that the proliferation of JavaScript libraries is a good hedge against the non interoperable future Yager warns of. But hey, why stop the guy when he's on a roll. CSS4! I guess the webkit-transforms have been officially christened. Thanks Tom.

    ~ge~
Gary Edwards

The Open Web: Next-Generation Standards Support in WebKit/ Safari - 0 views

  •  
    Apple has posted an interesting page describing Safari technologies. Innovations and support for existing standards as well as the ACID3 test are covered.

    Many people think that the Apple WebKit-Safari-iPhone innovations are pushing Open Web Standards beyond beyond the limits of "Open", and deep into the verboten realm of vendor specific extensions. Others, myself included, believe that the WebKit community has to do this if Open Web technologies are to be anyway competitive with Microsoft's RiA (XAML-Silverlight-WPF).

    Adobe RiA (AiR-Flex-Flash) is also an alternative to WebKit and Microsoft RiA; kind of half Open Web, half proprietary though. Adobe Flash is of course proprietary. While Adobe AiR implements the WebKit layout engine and visual document model. I suspect that as Adobe RiA loses ground to Microsoft Silverlight, they will open up Flash. But that's not something the Open Web can afford to wait for.

    In many ways, WebKit is at the cutting edge of Ajax Open Web technologies. The problems of Ajax not scaling well are being solved as shared JavaScript libraries continue to amaze, and the JavaScript engines roar with horsepower. Innovations in WebKit, even the vendor-device specific ones, are being picked up by the JS Libraries, Firefox, and the other Open Web browsers.

    At the end of the day though, it is the balance between the ACiD3 test on one side and the incredible market surge of WebKit smartphones, countertops, and netbook devices at the edge of the Web that seem to hold things together.

    The surge at the edge is washing back over the greater Web, as cross-browser frustrated Web designers and developers roll out the iPhone welcome. Let's hope the ACiD3 test holds. So far it's proving to be a far more important consideration for maintaining Open Web interop, without sacrificing innovation, than anything going on at the stalled W3C.

    "..... Safari continues to lead the way, implementing
Gary Edwards

Ajax Animator 0.20.02 Beta RC3 from antimatter15 - 0 views

  •  
    An AJAX version of the Flash IDE. Incredible!
Gary Edwards

Flash Wars: The Many Enemies and Obstacles of Flash [Part 2 of 3] - AppleInsider Comments - 0 views

  • Throughout 2007, Apple stripped nearly every vestige of Flash from its corporate site and other products, and began recommending that developers use open standards instead. As noted in Gone in a Flash: More on Apple’s iPhone Web Plans, last summer Apple published a document titled "Optimizing Web Applications and Content for iPhone," which not only listed Flash as the single bullet point item under a listing of "unsupported technologies," but went on to explicitly encourage developers to "stick with standards," and use CSS, JavaScript, and Ajax instead.
  • Microsoft has already begun leveraging its Windows and Office monopolies to distribute Silverlight as a Flash-killer on both the Windows PC desktop and on the Mac. When Microsoft releases a Mac product, it can only mean one thing: it's working hard to kill a cross platform threat to Windows.
  • the new Cocoa iPhone/iPod Touch SDK not only offers Adobe insufficient means to develop a Flash plugin, but also clearly forbids the development of runtimes designed to advance competing platforms on top of the native Cocoa environment, whether Flash, Silverlight, or Java.
  • ...2 more annotations...
  • Apple is fighting for control of media distribution with open standards! What is it you do not get about Mpeg4, AAC, MP3 and H.264?
  • Silverlight will just not play H264 content : as usual, microsoft has adopted a look alike, incompatible video format : VC1. About why Quicktime is better that Flash when it comes to serious H264 usage, you may want to have a look at the following note/demonstration of a quicktime+javascript player : http://blog.vrarchitect.net/post/200...ter-than-Flash In short : Quicktime can reach any frame of a video. Flash just reach the I-Frames. So if you have a GOP/keyframing of 250 for instance, you can see only one frame every 10s of video (to be honest, most classical gop implies a frame every one or two seconds)
  •  
    Excellent comment focused on the clash between Flash and Apple. Apple promotes JavaScript, CSS and AJAX: the WebKit- SproutCore recipe
  •  
    Live Roulette from Australia, Fun and Free! Now you can play Real "www.funlivecasino.com.au" Live Roulette for Fun in Australia on a brand new website, FunLiveCasino.com.au. Using the latest internet streaming technologies, Fun Live Casino lets you join a real game happening on a real table in a real casino, all broadcast Live! You can see other real players in the casino betting on the same results you do giving you ultimate trust in the results as they are not generated 'just for you', like other casino gaming products such as 'live studios' or computer generated games. Its amazing to think next time your really in the casino that you might be on camera, and people online might be watching! The future is scary! Imagine that one day soon this will be the only way people would gamble online because the internet is full of scams, you have to be super careful, and why would you play Online Roulette any other way except from a Real Casino you can visit, see, hear and trust! Amazingly this site is completely Free and has no registration process, no spam, no clicks and no fuss. Just Instant Fun "www.funlivecasino.com.au" Free Live Roulette! Give it a try, its worth checking out! "www.funlivecasino.com.au" Australia's Online Fun Live Casino! Backlink created from http://fiverr.com/radjaseotea/making-best-156654-backlink-high-pr
Gary Edwards

AJAX World RIA Conference News - AJAX & RIA with Server-Side JavaScript @ WEB 2.0 JOURNAL - 0 views

  • Server-side JavaScript (SSJS) is growing in popularity fast since developers realize it can drastically simplify Web app creation by letting you use using the same technology stack on both the client and the server.
  •  
    Server side and client side JavaScript
  •  
    Visit News www.killdo.de.gg. How to make the 1000 visitor from PR9 backlinks. Buy cheap service www.fiverr.com/radjaseotea/making-best-super-backlink-143445
Gary Edwards

Olympics set the stage for Web tech fight | Tech News on ZDNet - 0 views

  • Microsoft is approaching Silverlight from the opposite direction. It plans to take advantage of its legions of outside developers experienced in writing for its ubiquitous Windows operating system. The next version of Silverlight, being tested now and due later this year, will support Microsoft's .NET framework -- tools used by developers to create desktop applications that work on Windows.
  •  
    Adobe vs. Microsoft Gartner analyst Ray Valdes said 90 percent of the top global 1,000 companies have yet to deploy any sort of RIA, while 90 percent of the top 100 consumer Web sites have already done so using the nonproprietary and more simple AJAX format. That opportunity has Microsoft eyeing current leader Adobe for business that extends beyond Silverlight and into the sale of design tools along with server and database software to enable these new applications.
Gary Edwards

Design for Developers: Interactivity, animations, and AJAX - 0 views

  •  
    Awesome commentary in the must read category. JC nails it; starting with "layout"! ....... "We were both part of the same team and he was creating some UI elements that I was to wire up. As I sat there (in awe) watching him work I realized that much of his considerable skill was rooted in fundamentals not unlike the art of programming. Of course, there are design skills that are intuitive that can't be "learned." But, that can also be said of the logical clarity found in a really elegant data model or a brilliant inheritance tree. I am certainly no designer, but I have observed the more creative among us for several years and have gained some insight into their world. In this article I'll share some basic principles that can help raise your design acumen and improve the experience of your users...... " Layout I'd like to attack my goal of imparting design wisdom by breaking the topic into four buckets. The first is layout.
Gary Edwards

Coding In Paradise: Fixing the Web, Part I - 0 views

  •  
    Must read: "This blog post is part of a new, semi-regular series called Fixing the Web. The goal is to highlight these issues, identify potential solutions, and have a dialogue. I don't claim to have the answers for the situation we are in. However, I do know this -- if there is any community that potentially has what it takes to solve these issues I believe it's the Ajax and JavaScript communities, which is why this is a perfect place to have these discussions. To start, I see four areas that are broken that must be fixed: ..... "
Gary Edwards

Brendan's Roadmap Updates: Open letter to Microsoft's Chris Wilson and their fight to s... - 0 views

  • The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
  • In my opinion the notion that we need to add features so that ajax programming would be easier is plain wrong. ajax is a hack and also the notion of a webapp is a hack. the web was created in a document centric view. All w3c standards are also based on the same document notion. The heart of the web, the HTTP protocol is designed to support a web of documents and as such is stateless. the proper solution, IMO, is not to evolve ES for the benefit of ajax and webapps, but rather generalize the notion of a document browser that connects to a web of documents to a general purpose client engine that connects to a network of internet applications. thus the current web (document) browser just becomes one such internet application.
  •  
    the obvious conflict of interest between the standards-based web and proprietary platforms advanced by Microsoft, and the rationales for keeping the web's client-side programming language small while the proprietary platforms rapidly evolve support for large languages, does not help maintain the fiction that only clashing high-level philosophies are involved here. Readers may not know that Ecma has no provision for "minor releases" of its standards, so any ES3.1 that was approved by TG1 would inevitably be given a whole edition number, presumably becoming the 4th Edition of ECMAScript. This is obviously contentious given all the years that the majority of TG1, sometimes even apparently including Microsoft representatives, has worked on ES4, and the developer expectations set by this long-standing effort. A history of Microsoft's post-ES3 involvement in the ECMAScript standard group, leading up to the overt split in TG1 in March, is summarized here. The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
Gary Edwards

Is the W3C to Blame for the Breaking of the Web? | Continuing Intermittent In... - 0 views

  • Consider the recent CSS features added by WebKit: transformations, animations, gradients, masks, et cetera. They’ve very nearly _run out_ of standards to implement, so they’re starting to implement the wouldn’t-it-be-cool-if stuff. If I’m not mistaken, this is the exact sort of thing you’re wishing for.
  • Changing the renderer (which is what we’re taking about when we talk about upgrading “the web”) goes hand-in-hand today with upgrading the *rest* of the browser as well, which requires the user to care…and users (to a one) don’t give a flying leap about CSS 2.1 support.
    • Gary Edwards
       
      Note to marbux: the browser is the layout/rendering engine for web applications and services. Nothing happens on the web unless and until the browser, or a browser RiA alternative, implements a compliant end user interface. Focus on the browser layout engines, and Web applications will follow.
  •  
    Another article taking up the issue of "Blame the W3C" for what increasingly looks like a proprietary Web future. The author is an Ajax-DOJO supporter, and he tries to defend the W3C by saying it's not their job, they don't have the "power" or the "authority" to push the Web forward. About the best they can do is, at the end of the day, try to corral big vendors into agreement. Meanwhile, the Web has become the wild wild west with browser vendors innovating into their corporate web stacks where vast profits and future monopolies rest. For me, WebKit represents the best effort insisting that the Web remain Open. It's OSS with excellent big vendor support. And they are pushing the envelope. Finally!
Gary Edwards

Cisco buys PostPath: WebEx to compete with Exchange, Outlook, Office? | Between the Lin... - 0 views

  •  
    Once you add in better email and calendar support WebEx could become more appealing to the enterprise. PostPath has a Linux based collaboration system built on an AJAX client that doesn't need a browser. Cisco added that the company's strategy is to develop "an integrated collaboration platform designed for how we work today and into the future. And better yet: PostPath's pitch is that it is an Exchange alternative and a "Linux-based corporate email server." Let's read between the lines: Doesn't this sound a lot like an end-run around Microsoft Office, Outlook and Exchange just like Google is trying to do with Google Apps? Cisco probably has no desire to compete head on with Microsoft (or at least admit it), but the company obviously sees something here and coupling PostPath with WebEx could be a threat to Redmond. In fact, Cisco could be a bigger threat to Microsoft in the enterprise than Google. Why? Cisco already sells enterprises a lot of stuff. Isn't a collaboration suite really just an extension of the network?
Gary Edwards

The Struggle for the Soul of the Web: Flash and Silverlight challenge the Open Web - 0 views

  •  
    Just because the web has been open so far doesn't mean that it will stay that way. Flash and Silverlight, arguably the two market-leading technology toolkits for rich media applications are not open. Make no mistake - Microsoft and Adobe aim to have their proprietary plug-ins, aka pseudo-browsers, become the rendering engines for the next generation of the Web.
Gary Edwards

Convergence of Web, Mobile and Desktop Apps is the Next Phase: AJAX World RIA with Jere... - 0 views

  • For SOA applications, the best way to modernize is to componentize and extend the user experience aspect of the application that will in turn enable the applications composition and mashup.
  • While there are many ways that companies measure productivity, Nexaweb has found that the three key criteria for enabling the productivity driven enterprise are based on 1) cost savings resulting from reduced development time and application maintainability; 2) extending the value of existing applications with a future-proof architecture (adding RIA without breaking existing enterprise architecture); and 3) faster time to market by providing a consistent user experience across the various interfaces available throughout the organization.
  •  
    While the last decade was focused on the Web, the next phase in the evolution of our industry will be on the convergence of Web, mobile and desktop applications and the ability to extend existing applications with these new technologies for a consistent user experience regardless of how and where the information is viewed,' says Nexaweb CTO Jeremy Chone
1 - 20 of 28 Next ›
Showing 20 items per page