Interoperability Minutes 2006-08-02

From MemberWiki

Jump to: navigation, search

Full minutes: http://www.openajaxalliance.org/member/wiki/index.php/Markup_Minutes_2006-08-02

Contents

Attendees

  1. Adam Peller <apeller@us.ibm.com>
  2. Alex Russell <alex@dojotoolkit.org>
  3. Arno Puder <arno@puder.org>
  4. Chris Matthews <cmatthews@elinkbiz.com>
  5. Chris Schalk <chris.schalk@oracle.com>
  6. Eddie O\'Neil <ekoneil@bea.com>
  7. Greg Murray <greg.murray@sun.com>
  8. Jon Ferraiolo <jferrai@us.ibm.com>
  9. Lindsey Simon <lsimon@finetooth.com>
  10. Rama Gurram <rama.gurram@sap.com>
  11. Steve Adams <sadman@curl.com>
  12. Eric Van Dongen <evandongen@seagullsoftware.com>

Absent

  1. Bert Halstead <rhh@curl.com>
  2. Bjoern Mueller <Bjoern.Mueller@softwareag.com>
  3. Brodi Beartusk <bbeartus@bea.com>
  4. Chris Jolley <jolleyc@bea.com>
  5. Coach Wei <coach@nexaweb.com>
  6. Craig McClanahan <craig.mcclanahan@sun.com>
  7. David Frankel <david.frankel@sap.com>
  8. David Kranz <kranz@curl.com>
  9. David Temkin <temkin@laszlosystems.com>
  10. Eric Nguyen <ericn@mercedsystems.com>
  11. Gary Horen <ghoren@bea.com>
  12. Hyther Nizam <hyther@adventnet.com>
  13. Ian Wenig <ian@zoho.com>
  14. James Douma <jdouma@ebusiness-apps.com>
  15. James Margaris <jmargaris@nexaweb.com>
  16. Jason Wadsworth <wadsbone@thefrontside.net>
  17. Javier Gallego <Javier.Gallego@softwareag.com>
  18. Jennifer Taylor <jetaylor@adobe.com>
  19. Jeremy Chone <jchone@adobe.com>
  20. John Crupi <john.crupi@jackbe.com>
  21. John Janetos <jjanetos@laszlosystems.com>
  22. Joonas Lehtinen <joonas.lehtinen@itmill.com>
  23. Jorge Taylor <jotaylor@adobe.com>
  24. Juan Dexeus <Juan.Dexeus@in2.es>
  25. Ken Fyten <ken.fyten@icesoft.com>
  26. Kevin Hakman <khakman@tibco.com>
  27. Kin Blas <jblas@adobe.com>
  28. Kingsley Idehen <kidehen@openlinksw.com>
  29. Luke Birdeau <lbirdeau@tibco.com>
  30. Marc Englund <marc.englund@itmill.com>
  31. Michael Peachey <mpeachey@tibco.com>
  32. Phil Berkland <berkland@us.ibm.com>
  33. Raju Vegesna <raju@zoho.com>
  34. Ross Dargahi <ross.dargahi@zimbra.com>
  35. Ruben Daniels <ruben@javeline.nl>
  36. RĂ¼diger Herrmann <rherrmann@innoopract.de>
  37. Sami Ekblad <sami.ekblad@itmill.com>
  38. Steven Pothoven <pothoven@us.ibm.com>
  39. Ted Thibodeau <tthibodeau@openlinksw.com>
  40. William Shulman <will@mercedsystems.com>

Agenda

Keeping up with the Markup committee: review markup committee's progress on markup scanner

Review document on the OpenAjax Hub for posting on our web site

review doc for public website, public review

jon tried to capture committee thoughts

jon asks for comments: Lindsey Simon says the document looks good. otherwise, no other comments

jon asks if it is ok to post on public site, and then whether there are any objections: no objections

Event Hub requirements

alex: why would we manage click events, dom events directly?

jon: agreed. don't get involved

jon: libraries don't talk to each other, but rely on hub apis

alex: not sure how this is helpful

?: who is supposed to register on click listener?

jon: two dispatchers: browser itself for browser events, and the oaa hub for custom events (pub/sub which aren't click or UI, e.g. timer, data notification)

jon: usually elements are dispatched to one particular library

alex: drag and drop a good example case. well-known OA events. Toolkit A and B don't need to know about each other

alex: other scenario- anon function in a namespace, some observer wants to know about it. Proposed API klugey W3C bubbling, JS doesn't have, listeners disconnected from events which need closure, type param?

jon: type is name of event

alex: ok, that makes sense, but capture doesn't make sense

jon: capture a W3C mistake from Netscape backwards-compat. Added because it's in the W3C spec. Do we want to align?

alex: W3C obj passes around a well-defined Object (e.g. dom node, well known properties) heavy approach

alex: why Dojo does AOP

alex: propose a register publisher function which fires on a topic when a function is called

alex: this is infrastructure of Dojo. Doesn't think the W3C model fits well in JS

jon: need concrete proposals. anyone want to write code?

alex: happy to. (implement "after advice" only)

jon: how does this work?

alex: put aside function 'a' in a non-colliding name, define a new function which points to old function and assign it to the original var

jon: general agreement on this approach? yes

jon: wants to minimize criticism, avoid what's politically incorrect

peller: W3C is both PC and not PC to different groups.

alex: W3C way is to use DOM and ignore JS. Split responsibility that way to make people happy (everyone except devs :)

jon: can't please everyone

jon: want to engage with Yahoo! guys

alex: will try to prepare something for next meeting for event hub. alex, tibco have done some work in other areas

Status with this committee's hub contributions (e.g., open source JavaScript)

  • JavaScript collision detection/prevention
  • Toolkit loading and unloading
  • Event hub

jon: looking for volunteers to implement other items (tk loading, collision)

lindsey: volunteers to work on collision detection

jon: does collision require tk loading? event hub?

alex: collision approaches: snapshot, analyze state, compare object identity at another point in time. cpu intensive

lindsey: if you're not a member, do we need to force compliance? no

alex: use social means to encourage compliance

jon: tool to run collision tests and report

jon: get event hub working first. this is a follow on

alex: worried about checking that collision declarations are correct, e.g. advertise 5 globals, but registered 10

alex: we might host these declarations from our domain. always get latest. sanity check for app devs, not run in production

lindsey: community will help keep us up to date

jon: two pieces to collision detection: 1) simple array to declare global additions to hub, 2) verification JS to do error checking - does claim match reality?

jon: proposing a global object registry, register prefix. set a deadline for initial registration, accomodate what exists today.

Next Steps

Discussion

lindsey: prepare dojo and prototype, propose what object might look like

this will be main topic next week

ACTIONS

alex, lindsey have action items to write code for hub

Personal tools