Module identification and assignment: Difference between revisions
Jump to navigation
Jump to search
m (→Dreamforce) |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 33: | Line 33: | ||
**Offline mode | **Offline mode | ||
== | ==M1: Address Book Release== | ||
The following will be targeted for the | The following will be targeted for the address book release using the given priority: | ||
#[[Architectural review and refinement#Salesforce.com_data_layer_.28model.29|Salesforce.com data layer]] (done) | #[[Architectural review and refinement#Salesforce.com_data_layer_.28model.29|Salesforce.com data layer]] (done) | ||
##nsSalesforcePartner (done) | ##nsSalesforcePartner (done) |
Latest revision as of 17:56, 16 September 2007
Modules
Thunderforce's architecture calls for several high-level modules that can be broken down into the lower-level modules listed below. These all are traceable to the original feature list.
- Salesforce.com data layer
- nsSalesforceBidirectionalPartnerCache
- nsSalesforceLocalBidirectionalPartner
- nsISalesforceBidirectionalPartnerPoller
- nsSalesforcePartnerMetricsCollector
- nsSalesforcePartner
- Account type
- Account wizard
- Root folder
- Document folders
- Entity folders
- Messages
- Match/unmatch message buttons
- View in Salesforce.com buttons for matched messages
- Properties
- Address book
- Address book
- Cards
- Groups
- Outgoing messages
- Email address lookup
- Message sending via Salesforce.com
- Match/unmatch message buttons
- Message filters
- Filter criteria
- User interface extensions
- Filter actions
- Rule generation
- Offline mode
- Offline mode
M1: Address Book Release
The following will be targeted for the address book release using the given priority:
- Salesforce.com data layer (done)
- nsSalesforcePartner (done)
- nsSalesforceLocalBidirectionalPartner (done)
- Address book
- Address book
- Cards
- Groups
- Outgoing messages
- Email address lookup
- Account type (done)
- Account wizard (done)