Closed
Bug 950665
Opened 11 years ago
Closed 10 years ago
[Contacts] Review public interface for classes and move code to their specific component
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: arcturus, Assigned: mbudzynski)
References
Details
With Hayda coming we need to review what is exposed in each javascript class in order to load just the necessary javascript per document.
We will need to review the public interfaces of the main contact classes and move the code to the specific views that is needed, otherwise separate it and make it accessible from different documents in smaller pieces.
Examples of that are:
- contacts.js has a method callOrPick which is used just in the detail view (detail.js)
Reporter | ||
Comment 1•11 years ago
|
||
I've been syncing with Michal, and he will be taking this task, I'll be happy to review.
Cheers,
F.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mbudzynski
Comment 2•11 years ago
|
||
What release are we hoping to get this into? 1.4?
Reporter | ||
Comment 3•11 years ago
|
||
Hopefully, so far it's not a committed feature.
Comment 4•11 years ago
|
||
this is a very generic bug. I would suggest to be more concrete on what's planned and to split in small pieces to avoid regressions and to make it easier to review when ready
Reporter | ||
Comment 5•11 years ago
|
||
Yes, this bug should be first an analysis of what should go in each class.
Reporter | ||
Comment 6•10 years ago
|
||
The contacts.js has been already refactor, it doesnt containg the method |callOrPick| anymore.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•