Labs/Jetpack/Weekly Meeting/2011-07-5
From MozillaWiki
< Labs | Jetpack | Weekly Meeting
Contents
Agenda
- FlightDeck 0.9.7 status
- SDK 1.1 status (verbal catch up)
- Development Process
- Roundtable
Minutes
FlightDeck
- focus for next release is on stability, other polish fixes
- myk: roadmap for future releases?
- dbuc: yes, it's on wiki, 9-12 months planned right now
SDK
- dcm
- when i finish new feature pages new roadmap, we're going to start tracking features rather than bugs
- Alex
- bug 571049: ability to remove files, do other things on uninstall
- currently we don't handle this case, will require significant changes
- bug 561726: bypassing content scripts when panel/widget document is trusted
- give documents access to self global
- bugs around widget API
- a lot of issues when you start customizing
- Irakli
- been reviewing some code last week
- issues assigned by Myk: hotkeys, errors in various APIs, other polish fixes
- all reviews assigned to dietrich because myk was PTO last week
- myk now back, will pick up reviews if dietrich doesn't get to them
- now looking into P2s
- working on adding 'use strict' all over SDK modules (bug 553434)
- Brian
- PTO last week
- catching up on reviews and discussions
- Eddy
- mainly a lot of reading code and tutorials
- finished some code that tests time to initialize jetpack processes
- rest of the week, doing the same thing for content processes (spawn them as well, measure time to initialize)
- warner: time to initialize jetpack process?
- eddy: 40-70ms, pretty quickly
- Matteo
- bug 581982 working on getting selection on text field
- has fix, has been fighting with github the last few weeks, should have review request today
- started to work on another couple of bugs; not much progress yet
- Myk
- PTO all last week
- this week, catching up
- Will
- figure out migration guide, learning more about conventional addon development
- some idea of what an outline will look like
- spent time porting a conventional addon to the SDK, to learn about traditional addons and figure out what features the SDK might still need
- will write something up, not sure if it's a blog post or other format
- (not in any of the bugs)
- ideas for fairly simple XUL-style addons that would be interesting to port to SDK? let Will know
- dcm
- myk wrote drafts of feature pages
- dcm in process of converting them to new feature page style
- and expanding them
- and updating the roadmap
- at same time, create a vision statement for project
- wants to make sure that, while working through features and priorities, we answer question of why we're doing this work
- hope to have this all done by next week so we can use it when planning
- myk
- didn't get much feedback on development process
- if it's all good, then great, but if you have feedback, please provide it
- still some outstanding questions to answer
- take a look, or take another look, and let us know what you think!
- Hernán
- posted Simple Prefs API on GitHub and requested review
- Myk provided feedback
- Drew provided feedback and asked several questions
- why a new API vs. the existing Preferences Service API? -> wanted to differentiate between low-level API vs. high-level one
- what about hidden preferences? useful, but may be hard to couple with the Simple Prefs API
- when emitting changes on prefs, what about sending previous and new values of pref that has changed? not sure it's possible to emit data besides the name
- instead of namespacing the API with .simple or .complex, moving the namespacing to package.json? seems like a good idea
- decoupling JSON store from simple storage into an object storage API and then using that API for storing complex prefs or even simple ones?
- Hernán to work on new patch based on Drew's suggestions
- Hernán to post to discussion group regarding some issues