Confirmed users
383
edits
Gaia/SMS/Scrum/2.2S14: Difference between revisions
m
→Day 8: 5th June
| Line 412: | Line 412: | ||
=== Day 8: 5th June === | === Day 8: 5th June === | ||
====Steve==== | |||
* {{Bug|1169541}} - [Messages] [NGA] Refine the thread query and move draft query/getThreads API into conversation service / messaging service | |||
** Rework on the draft for messaging service and shim | |||
* {{Bug|1169573}} - [Messages][NG] Lay out Messaging service structure | |||
** Ongoing with the original message manager/drafts/threads module version | |||
* Reply some though about controller. BTW do we really need put every API into shim? And how about Settings? Could we use API in controller directly? | |||
:(Oleg) "BTW do we really need put every API into shim?" Honestly I think we should use rational judgment here, use shims where it's really needed, not sure if we need both shim and service for settings | |||
:(Steve) Yeah I understand we use shim because we need for certain limitation, but for the the message API, will we move every API in message shim? or we just move the API that needed in worker. But isn't it confusing if only part of messaging api inside the shim and some API in controller? | |||
:(Oleg) as for MobileMessagingShim I think it should be the single entry point for all mozMobileMessaging API methods, I suspect the main (only?) consumers of this shim will be MessagingService and ConversationService that live in a SharedWorker? - we can discuss on IRC as well :) | |||
* {{Bug|1167144}} - [Messages] Reduce the use of Threads.active and Threads.currentId in conversation view | |||
** No new progress yet, move to wish list first | |||
Today: | |||
* Reviewing the activity service, just have one question for the overall structure, will look deeper then. | |||
* Give some early thought about loading threads. | |||
* Clean up the use of threads.active in conversation view | |||
* Some tasks for background if I have time | |||
** Reduce the use of Threads.active and Threads.currentId in conversation view | |||
** Fix the attachment menu for closing the option menu manually | |||
** gaia-component stuff | |||
** file loading in Template.js | |||
====Julien==== | |||
* No updates, but Julien is still with us today :) | |||
====Oleg==== | |||
* {{Bug|1162028}} - [Messages][New Gaia Architecture] extract conversation/index.html | |||
** No updated on the PR since yesterday, only rebased on the latest dependency PRs (awaiting feedback). | |||
** Pushed my experimental branch with navigation.js shim and updated manifest so that you can try to navigate between inbox and conversation documents on device or in browser. | |||
* {{Bug|1168441}} - [Messages][NG] Implement ActivityService | |||
** More discussion on that. Updated PR according to the latest comments (in review). | |||
Other: | |||
* In the meantime started experiments with SW and ServiceWorkerWare, it looks like it's quite unstable with app:// (doesn't work sometimes, crashing, profile is broken after one session with SW). Wanted to file bugs, but looking at https://bugzilla.mozilla.org/show_bug.cgi?id=1171651 - we may not need app:// anymore since http served packages are landed. | |||
* Built B2G with Tim's patch to see the problem (https://bugzilla.mozilla.org/show_bug.cgi?id=1171387), found out that switching from "tap" to "click" fixes integration tests. To me it seems more like Marionette problem since "tap" action consists of several consequent actions (mousedown, mouseup - but not sure, haven't dig into that code yet). | |||
* Finished reviewing of service spec draft. | |||
* Ignite meeting. | |||
Today: | |||
* Will handle review/feedback/need-info requests; | |||
* Will work on review comments and assigned bugs. | |||
=== Day 9: 8th June === | === Day 9: 8th June === | ||
=== Day 10: 9th June === | === Day 10: 9th June === | ||