Ajax - Gary Edwards on Diigo

1Expand

Some Perspective On Browser Market Share | Continuing Intermittent Incoherency

One of the comments to this post really caught my eye: ...... "Flash has always had better rendering consistency across platforms. However, HTML is much easier to build.

I always wondered why someone (Adobe?) doesn’t build a HTML/CSS/JS to Flash bridge. Sort of like sIfr but for the whole page. I really thought AIR could be that bridge. Write once, and render anywhere. :) ......... "

The thing is, the Adobe AiR runtime implements the WebKit layout engine. Whcih means WebKit documents based on HTML/CSS/JS should render just fine.

The real question will be how Adobe AiR handles the EcmaScript mess! Will they go with the ActionSript 3 version of JS - the one that is optimised for Tamarin? Or will they scale back to the MIcrosoft-Yahoo crippled version of official EcmaScript? My guess is that they push forward with ActiveScript 3 and try to convince WebKit and Mozilla groups to carry the open sourced Tamarin JiT. That would protect AiR developers as well as those who are seriously concerned about the future of the open web going forward.

Tags: open-web, webkit, ajax, flash, air on 2008-08-19 and saved by2 people -All Annotations (0) -About

more fromalex.dojotoolkit.org

Moving forward with CSS | Wisdump

Review of emerging CSS technologies and techniques. Includes Tools and Frameworks: Skybound's "Stylizer", YAML, CSS Cacheer. Best Practices, CSS3 and Beyond, the Browsers,

Tags: CSS, Ajax, WebKit on 2008-07-03 and saved by2 people -All Annotations (0) -About

more fromwisdump.com

5Expand

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

Lengthy artilce from the OpenAjax Alliance summarizing HTML, Ajax and the future of the Open Web. Very well referenced. Lots of whitepapers and links

Tags: ajax, openweb, acid, webkit on 2008-07-02 and saved by2 people -All Annotations (0) -About

more fromwww.openajax.org

Just one note of caution: the OpenAjax Alliance is an IBM-Oracle operation. Why it's operating outside the ODF work is a mystery. For usre one of the most useful things IBM-Oracle could ever do for the hapless ODF would be to create a high level, implement on the fly, document conversion component for ODF <> Ajax. The Open Web needs desktop office suite editors capable of producing and consuming highly interactive and collaborative Open Web ready documents.
post by garyedwards on 2008-07-02

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,
Add Sticky Note
- 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.
  posted by garyedwards on 2008-07-02
Runtime Advocacy Task Force

1Expand

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

Response to questions about RiA vs AJAX.

Tags: ria, ajax, webkit on 2008-06-26 -All Annotations (0) -About

more fromtalkback.zdnet.com

1Expand

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

Server side and client side JavaScript

Tags: javascript, ria, ajax on 2008-06-11 -All Annotations (0) -About

more fromwww.web2journal.com

1Expand

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

Darryl Taft writes a follow up article covering the comments to his original AJAX-ARAX ruby on rails MS-iron python story

Tags: ajax, arax, javascript, webkit, adobe, air on 2008-06-09 -All Annotations (0) -About

more fromwww.eweek.com

1Expand

AJAX, AIR, RIA, Adobe Getting It, David Mendels and “Rich Internet Apps: How We Live Now” | James Governor’s Monkchips »

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.

Tags: AIR, Flex, Flash, RIA, Javascript, Ajax, Adobe, Dave-Mendel on 2008-06-06 -All Annotations (0) -About

more fromwww.redmonk.com

1Expand

Adobe AIR Language Reference for HTML Developers

Tags: air, ajax, javascript, css, html, adobe, webkit on 2008-06-02 and saved by2 people -All Annotations (0) -About

more fromlivedocs.adobe.com

script.aculo.us - web 2.0 javascript

AJAX and JavaScipt :: webkit /prototype.js

Tags: ajax, javascript, webkit on 2008-06-01 and saved by511 people -All Annotations (0) -About

more fromscript.aculo.us

18Expand

BOOK Offered Or Kept: Digital reading without Epub? | TeleRead: Bring the E-Books Home

Aaron Miller writes about the limitations and difficulties with ePUB. He suggests a new format, "BOOK" based on ePUB but web ready. BOOK is an AJAX format in that it includes (X)HTML, CSS and JavaScript! Excellent stuff! The discussion on this page is one of the best on the Web. ePUB gets thrashed, but with arguments very difficult to contest. The web is everything, and Aaron's friends fully understand this. Sadly, the ePUB crowd does not. I found this site looking to solve the problem of numbered lists in ePUB.

Tags: ePUB, eBOOK, BOOK, AJAX, CSS, HTML-5 on 2008-05-30 -All Annotations (0) -About

more fromwww.teleread.org

Add Sticky Note
- .wiki is the native wikiWORD language for MSOffice "editors". It's really AJAX for documents, with HTML+ handlign the "structure", and CSS+ handling the "presentation". We need javascript to perfect the full range of typographical options used by knowledge workers makign their way from MSOffice to the web. BOOK is a good place to start.
  posted by garyedwards on 2008-05-29
The structure of a BOOK would look like this:

…BOOK/

……index.html

……images/

………cover.png

……css/

………base.css

………skins/

…………modern.css

…………classic.css

…………nouveau.css

……scripts/

………prototype.js

………base.js

………extensions.js
Add Sticky Note
- Good point! The IDPF ePUB format does not support javascript! Which makes "BOOK" a better format to target.
  posted by garyedwards on 2008-05-29
As for the Javascript, it’s based on the ECMAScript standard, which has evolved into a strongly-typed, object-oriented programming language and is one of the few web “standards” which really is a standard. BOOK authors will welcome the addition of a scripting language, as it is NOT currently supported in the IDPF specifications. In fact, it’s forbidden for .epub reading systems to execute scripts. It’s also forbidden for them to display a file called index.html without first loading and parsing several other files.
For BOOKs, it offers true pagination, typesetting, skinnable and collapsible layouts, footers and headers, footnotes as popups, inline text, true footer notes, or endnotes . . . the list goes on. YUI, JQuery, dojo, MooTools, and Prototype are just a few of the frameworks available, and they’ve been addressing these issues for some time now.
Jon Noring Says:
EPub is an excellent, high-fidelity format for both direct rendering and for user-side conversion to other formats for particular platforms such as very limited resource handheld devices.
Javascript is useful mainly for rendering, not bells and whistles. Without Javascript, the non-normalized implementations of CSS out there become useless–you can’t rely on them to produce a consistent rendering of a document. Unfortunately, with CSS3 the rendering game is only going to get more complicated. I don’t advocate executing scripts from epubs, I advocate executing scripts in epub reading systems. Two very different things, as you’re aware.
Scripting is *essential* for many digital publishing projects and not understanding it is a major failure of IDPF. Saying that “we will reconsider scripting when adoption of epub grows” is also inadequate, because nobody will wait patiently, but will choose some another platform for their publishing needs, Adobe AIR for example.
My criticism of epub is not about details but about its fundamentals. It seems to me that while preparing the spec the most fundamental question was left out of view: what is the right model for digital publication: is it a physical book? Or is it something else? If something else, then what? From my point of view, not a physical book, but a website should be thought as the right model. Why website? - because of the well supported and ubiquitous mix of technologies (html, css, javascript) and because of the workflow (publishing early versions of the publication on the website for gathering feedback and then publishing as downloadable file). If a model for a digital publication is a website, then any format which does not allow to have everything which we have on websites and does not allow to take all website’s html, css and client-side scripts and publish them as downloadable file without much changing them, is doomed to failure in the long run. It seems that epub is now on this way to failure.
What I’d like to see is a sort of epub spinoff, another specification from the IDPF, if you will, with slightly different requirements. Instead of BOOK, we could call it epub-lite. The basis for this simplified, consumer-oriented version of .epub would be the same browser-centric building blocks under the IDPF specs. The difference would be in the file structure and in the way a browser deals with it.
Add Sticky Note
- What we really need are "webDOCS". Laisvunas is absolutely right. The web is the target, with print and device "flow" an auxillary offshoot. I think we can have it all, and Aaron's "BOOK" is a good place to start. My thinking though is that javascript has to come from standardized libraries such as jQuery or Yahoo's "BrowserPLUS".
  
  Yahoo BrowserPLUS does have a security model and off-line capability built in. It's nowhere near as robust and sweepign as the jQuery javascript library, but i don't see why the two can't be combined.
  
  Good thinking on the part of Laisvunas!
  posted by garyedwards on 2008-05-29
What I wish for is this: a simple ebook format which allows me to use all technologies there are on the web with exactly the same freedom as on web and imposing no additional limitations. Secondly, some browser-based reader (browser add-on or some program based on some quality browser engine). Thirdly, some program (editor/compiler) for producing publications from preexisting web-pages.
Add Sticky Note
- Once again Laisvunas nails it. I really like his "AIR" suggestion. It's also true that flowing content ready device browsers like the webKit "Safari" and SkyFire will be far more widespread than any ePUB reader!!!!! So why not write for both the web and the device at the same time?
  posted by garyedwards on 2008-05-29
The system I’m referring to is alive and well at bookglutton.com. It features an AJAX reader and Package Creation tool. The package tool is currently part of the upload feature which enables people to convert .doc, .rtf, and html documents to epub packages that can be viewed in the Reader. Once we have more epubs out there, direct epub upload will also be an option. We may also eventually enable epub download. Right now, we’re having some doubts about the value of that.
Add Sticky Note
- How about "eWEB" as a format name? Is it better than "webBOOK" or webDOC"?
  posted by garyedwards on 2008-05-29

1Expand

Aaron Miller of BOOK GLUTTON - About Us

ePUB vs. AJAX format

Tags: ePUB, AJAX, BOOK on 2008-05-30 -All Annotations (0) -About

more frombookglutton.com

1Expand

Aptana Jaxer | Aptana

Tags: ajax, server on 2008-01-25 and saved by17 people -All Annotations (0) -About

more fromwww.aptana.com

2Expand

The Merging of SOA and Web 2.0: 2

Tags: 2.0, ajax, mashup, odf, ooxml, soa, web on 2007-07-15 and saved by2 people -All Annotations (0) -About

more fromwww.eweek.com

Great article series from eWeek. A must read. But it all comes down to interoperability across two stack models: The Microsoft Vista Stack, and an alternative Open Stack model that does not yet exist!

Incompatible formats become a nightmare for the kind of integration any kind of SOA implementation depends on, let alone the Web 2.0 AJAX MashUps this article focuses on.

I wonder why eWEEK didn't include the Joe Wilcox Micrsoft Watch Article, "Obla De OBA Da". Joe hit hard on the connection between OOXML and the Vista Stack. He missed the implications this will have on MS SOA solutions. Open Source SOA solutions will be locked out of the Vista Stack. And with 98% or more of existing desktop business processes bound to MSOffice, the transition of these business processes to the Vista Stack will no doubt have a dramatic impact on the marketplace. Before the year is out, we'll see Redmond let loose with a torrent of MS SOA solutions. The only reason they've held back is that they need to first have all the Vista Stack pieces in place.

I don't think Microsoft is being held back by OOXML approval at ISO either. ISO approval might have made a difference in Europe in 2006, but even there, the EU IDABC has dropped the ISO requirement. For sure ISO approval means nothing in the US, as California and Massachusetts have demonstrated.

All that matters to State CIO's is that they can migrate exisiting docuemnts and business processes to XML. The only question is, "Which XML? OOXML, ODF or XHTML+".

The high fidelity conversion ratio and non disruptive OOXML plugin for MSOffice has certainly provided OOXML with the edge in this process.

Because of ODF vendor in fighting in Massachusetts, and the subsequent failure of ODF, the hapless file format arrived in California and other states with a hardened reprutation as "great file format, but impossible to implement".

The next question people have to start askign is what impact will OOXML and the Vista Stack have on SOA? Will open source and non Micrsoft vendor SOA solutions be locked out of the Vista STack?

Of course. If ever there was a no brainer this is it. Microsoft is goign to eXtend their desktop monopoly to servers, devices and the web using the highly proprietary Vista STack to lock in business process customers for years to come.

~ge~
post by garyedwards on 2007-07-15

In many cases, the mashups' data or information sources have incompatible formats so integration becomes a problem.

Gary Edwards's Bookmarks tagged Ajax → View Popular

Some Perspective On Browser Market Share | Continuing Intermittent Incoherency

Moving forward with CSS | Wisdump

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

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

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

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

AJAX, AIR, RIA, Adobe Getting It, David Mendels and “Rich Internet Apps: How We Live Now” | James Governor’s Monkchips »

Adobe AIR Language Reference for HTML Developers

Adobe^® AIR™ Language Reference for HTML Developers

script.aculo.us - web 2.0 javascript

BOOK Offered Or Kept: Digital reading without Epub? | TeleRead: Bring the E-Books Home

Aaron Miller of BOOK GLUTTON - About Us

Do new Web tools spell doom for the browser? | InfoWorld | Analysis | 2008-05-12 | By Neil McAllister

WaveMaker Software™

NicEdit - WYSIWYG Content Editor, Inline Rich Text Application

Aptana Jaxer | Aptana

The Merging of SOA and Web 2.0: 2

Gary Edwards's Related Tags

See More Top Contributors

Related Groups on Diigo

Diigo - Highlight and Share the Web!

Gary Edwards's Bookmarks tagged Ajax → View Popular

Adobe® AIR™ Language Reference for HTML Developers

Gary Edwards's Related Tags

See More Top Contributors

Related Groups on Diigo

Diigo - Highlight and Share the Web!

Adobe^® AIR™ Language Reference for HTML Developers