From jferrai at us.ibm.com Mon Feb 23 16:37:00 2009 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 23 Feb 2009 16:37:00 -0800 Subject: [OpenAjax] Looking for "Ajax expert" feedback on OMTP BONDI Message-ID: OpenAjax Alliance is a partner with another industry group, the OMTP, particularly around Mobile Ajax. The OMTP has asked me to get feedback from Ajax experts about the API approach that they are using within their BONDI initiative, particularly whether their JavaScript APIs are well-designed from the perspective of Ajax/JavaScript programmers. Quick background BONDI defines a set of mobile device APIs that allows HTML+JavaScript (i.e., the browser engine) to access about a dozen device APIs (e.g., geolocation, address book, email, file system), which would allow browser technologies to do the same sorts of things that J2ME and browser native SDKs can do. BONDI includes a security framework based on OASIS XACML, and has been designed as a companion set of standards to W3C Widgets. One vision for how these two standards might impact the world: Some early adopter companies support W3C Widget support in late 2009 within their App Store as an alternative distribution format for mobile applications (versus Java, C, Cocoa or Dalvik) Other companies support W3C Widgets due to the desire to get a lot of apps on their platform and also to satisfy checklist requirements for W3C Widgets and BONDI that certain mobile operators will place on their device suppliers. (Vodafone has forced suppliers to support W3C standards at various times in the past.) Developers realize that they have an approximation of write-once, run-anywhere option for mobile applications using HTML+JavaScript Examples Here is an example of accessing the mobile device file system. BONDI has a dynamic module loader capability, In this example, the filesystem module is added by the bondi.load() call on the first line and attached to the 'fs' object. The success and failure callbacks are not shown. When you mount a file system, it is expected that the browser engine would restrict access to a sandboxed directory tree that was private to this particular widget (or web app). ------------ bondi.load('fs', { id: 'filesystem', success, failure }); var root = fs.mount(fs.getPersistLocation()); for(var i = 0; i < root.length; i++) { alert(root[i].name); // displays name of each file in root directory } var file = root.createFile("test.txt"); var out = file.open("w"); // writes Hello World to test.txt out.writeLine("Hello World", "UTF-8"); out.close(); ------------ Here is an example of accessing the mobile device address book. In this example, the pim module is added by the bondi.load() call on the first line and attached to the 'fs' object. The success and failure callbacks are not shown. ------------ bondi.load('pim', { id: 'pim', success, failure }); var addressbooks = pim.contact.getAddressBooks(); var myContact = addressbooks[0].createContact({name:'Pedro Fraca', nickname:'peter', address:'C/blah', mail:'pedro at gmail.com', telephone:'6666666666', photo:'\images\pedro.jpg'}); myAddressBooks[0].addContact(myContact, null, successCB, errorCB); function successCB(response) { alert("Added"); } function errorCB(response) { alert( "The following error: " + response.message + ", ocurred in " + response.name); } ------------ Here are examples of listening for changes in phone orientation and changing the orientation. In this example, the deviceStatusManager module is added by the bondi.load() call on the first line and attached to the 'fs' object. The success and failure callbacks are not shown. ------------ bondi.load('deviceStatusManager.watchPropertyChange', { id: 'deviceStatusManager', success, failure }); var orientationChangeHandler = deviceStatusManager.watchPropertyChange( {aspect:"display", property:"orientation"}, { onPropertyChange:function(ref, value) { alert("Property changed: "+ref.property+" "+ref.component+" "+ref.aspect+" "+ref.vocabulary); alert("New value: "+value); } } );: deviceStatusManager.setPropertyValue({property:"orientation", aspect:"Display"}, 0); ------------ How to give feedback I would appreciate any responses about the BONDI APIs, even as short as "they look fine" or short complaints such as "names are too long". You can send feedback however your wish, including: (1) Reply email to public at openajax.org (2) Reply email just to me Thanks. Jon Ferraiolo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20090223/f6c71130/attachment.html From krishnaguda at in.ibm.com Tue Feb 24 14:30:42 2009 From: krishnaguda at in.ibm.com (Krishna Guda) Date: Wed, 25 Feb 2009 04:00:42 +0530 Subject: [OpenAjax] Krishna is on vacation.. Message-ID: I will be out of the office starting 02/20/2009 and will not return until 03/23/2009. I will be on vacation. I will have no access to email till 10th March. Please reach out to my manager Deepesh Bhargava/India/IBM if you need any information. From jferrai at us.ibm.com Mon Mar 30 08:44:13 2009 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 30 Mar 2009 08:44:13 -0700 Subject: [OpenAjax] News Update, including Hub 1.1 renamed to Hub 2.0 Message-ID: Some recent news from OpenAjax Alliance: Hub 1.1 renamed to Hub 2.0, Revamped Managed Hub APIs --------------------------, The Interoperability Working Group has officially changed the name of "OpenAjax Hub 1.1" to "OpenAjax Hub 2.0". OpenAjax Hub 2.0 extends the publish/subscribe engine from Hub 1.0 to provide a client-side framework for secure mashups. Hub 2.0 introduces the notion of a "Managed Hub", where the host application can isolate (sandbox) each individual mashup component. (http://www.openajax.org/blog/?p=70) The Interoperability Working Group has completed a major redesign of the Managed Hub feature within OpenAjax Hub 2.0. The redesign effort, which started at alliance's face-to-face meeting in October 2008, reflects implementation experience gained during the 2008 InteropFest. The biggest change to the detailed Managed Hub APIs is from a plugin-oriented approach to a class hierarchy approach. The new approach is both simpler and more easily extensible than the previous approach. ( http://www.openajax.org/blog/?p=72) The target completion date for Hub 2.0 is early spring 2009. Revised OpenAjax Widget spec -------------------------- The Gadgets Task Force, working in partnership with the IDE Working Group, is near completion of a major redesign of the mashup-oriented widget features found in the OpenAjax Metadata Specification. The widget redesign effort, which was approved at alliance's face-to-face meeting in October 2008, reflects implementation experience gained during the 2008 InteropFest and careful review against other widget technologies in the industry. ( http://www.openajax.org/blog/?p=73) The target completion date for OpenAjax Metadata 1.0, including OpenAjax Widgets, is spring 2009. Security Task Force Progress on Mashup Authentication and Authorization -------------------------- At the beginning of 2009, the Security Task Force at OpenAjax Alliance launched a new initiative around Mashup Authentication and Authorization, with an emphasis on single sign-on workflows. The goal of this initiative is to perform a deep study of real-life use cases of technologies in use today, such as login/password dialogs, OpenID, SAML, and OAuth, and then develop a set of incremental technical standards (if necessary), best practices, and educational sample applications. ( http://www.openajax.org/blog/?p=71) Accessibility TF Launched -------------------------- In Februrary 2009, OpenAjax Alliance launched a new task force, the Accessibility Task Force, whose mission is to promote better Ajax tooling for the creation of accessible Rich Internet Applications (RIAs). The task force will develop a set of accessibility validation rules, best practices for reporting accessibility compliance, and a set of IDE best practices. ( http://www.openajax.org/blog/?p=74) OpenAjax salutes (and provides feedback to) OMTP/BONDI -------------------------- OpenAjax Alliance is very pleased to see the progress by one of its industry partner organizations, the OMTP, with its BONDI initiative. Recently (Feb-Mar 2009), OpenAjax Alliance has assembled Ajax industry leaders to review the BONDI 1.0 Release Candidate specifications and collect feedback on the OpenAjax Alliance member wiki. ( http://www.openajax.org/blog/?p=75) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20090330/8e9cfad0/attachment.html