Confirmed users
471
edits
Labs/Jetpack/Weekly Meeting/2010-07-13: Difference between revisions
Jump to navigation
Jump to search
Labs/Jetpack/Weekly Meeting/2010-07-13 (view source)
Revision as of 22:13, 13 July 2010
, 13 July 2010→Minutes
m (→Minutes) |
|||
| Line 37: | Line 37: | ||
** Ayan's demo: python script which downloads latest SDK release, runs 'cfx testall', reports failures. Works on OS-X and Ubuntu, not yet on windows. | ** Ayan's demo: python script which downloads latest SDK release, runs 'cfx testall', reports failures. Works on OS-X and Ubuntu, not yet on windows. | ||
*** would also be useful to run tests on a bunch of local addon trees against the new SDK before starting to use it for real | *** would also be useful to run tests on a bunch of local addon trees against the new SDK before starting to use it for real | ||
** (dietrich) Firefox version compatibility: need to bump XPI rdf compability flags | |||
*** through flightdeck, we can get these sorts of changes out faster, rather than waiting for a new SDK release | |||
*** but Zandr told Myk that it's harder than it seems | |||
*** first step is to update the SDK, then update flightdeck to use that SDK | |||
*** how to make jetpacks "just work" against multiple Fx versions? got lots of questions about this at the summit, don't really have an answer yet. Needs thought. Should we require re-linking? Or can flightdeck/AMO upgrade your add-ons for you? | |||
** (dietrich) what does "feature-complete API set" mean? please take a look at the grid linked above and fill in more pieces | |||
** (irakli) how to express that a jetpack depends upon other non-jetpack addons (not captured by SDK modules or application name), like having Weave/Sync installed. Could add data to the .rdf to warn that there are other dependencies which need to be installed first. | |||
** (irakli) suggests avoiding FF-specific JS syntax, and lean towards ES5 standard JS features. Myk suggests not limiting ourselves, especially in low-level API implementations. Example code should avoid it more than internals. Worth a conversation. | |||
** (irakli) coordinate better with the CommonJS community: module name collisions, we'd like to be able to use existing libraries without much hassle. Irakli will post to mailing list about it. | |||
= Followups = | = Followups = | ||