XULRunner:ATF Meeting Notes 20060504

From MozillaWiki
Jump to navigation Jump to search

IBM AJAX Tools Framework

Meeting Notes 4-May-2006

Attendees

Benjamin Smedberg Javier Pedemonte Adam Peller

Notes

  • Inspector components moving into layout will help the inspection stuff (currently using DIV hacks to do blinking and whatnot)
  • Remote debugging and inspection using Java RMI
    • Demonstrated a simple "click me" prompt launched from Eclipse, run by separate Firefox process
  • Have Google SOC contributors that want to help
    • Want to integrate XUL IDE development (EclipseXUL)
    • Need to identify who is going to be officially mentoring
  • XUL IDE work being done by Phil Berkland - early work-in-progress, code being checked into Laszlo repo: org.eclipse.laszlo.xul in CVS?
  • JSD Issues
    • code sometimes (important times) assumes that's it's being called from a JS context stack
    • JSD doesn't expose stepping, you get a callback for each call invocation which ends up with lots of hackery to determine if a callback is occuring in the same codeflow as the last callback
    • Some smaller JS engine bugs, bug 326580 for example
    • Need some JSD API redesign and cleanup -- need to identify resources (summer interns?)
  • Have preliminary Java component loader, want to do an extension release for the branches (implementing nsIComponentLoader)
    • need to port to trunk nsIModuleLoader
    • ASM.objectweb.org released code under BSD license that does class/interface generation on the fly... want to import this code and release it under a contrib/ directory somewhere; need to contact the author to detemine originality of code

XULRunner 1.9 targeted tasks

interface namespaces? Already have an xpt field for the namespace, need to determine what namespaces should actually be used for, and whether/how they should be exposed to JS

using xpidl to generate java declarations of the interfaces

java component loader needeed to start the Java RMI server -- bsmedberg willing to hack XRE startup to make that happen early enough (based on application.ini settings)