Documentation/Maemo 5 Developer Guide/Architecture/Data Management
(New page: =Data Management= ==Software context== Data management subsystem has the following relationships. *Toolkit: This domain provides the set of lowlevel libraries like widgets that are used by...) |
(→File Handling) |
||
| Line 52: | Line 52: | ||
|'''Name'''||'''File Management'''|| | |'''Name'''||'''File Management'''|| | ||
|- | |- | ||
| - | |'''Purpose'''|| | + | |'''Purpose'''||Provides whole stack for file management. This includes file access, virtual file system, mime handling and URI schema handling. The domain also provides the UI that is needed for the file access. |
|- | |- | ||
|'''Responsibilities'''||*Virtual file system (gnome-vfs) <br>*Mime handling (libhildonmime) <br>*Widgets for file handling (hildon-fm) <br>*File manager | |'''Responsibilities'''||*Virtual file system (gnome-vfs) <br>*Mime handling (libhildonmime) <br>*Widgets for file handling (hildon-fm) <br>*File manager | ||
| Line 58: | Line 58: | ||
|'''License'''||Nokia/LGPL | |'''License'''||Nokia/LGPL | ||
|} | |} | ||
| - | |||
===Content Handling=== | ===Content Handling=== | ||
Revision as of 13:07, 14 September 2009
Contents |
Data Management
Software context
Data management subsystem has the following relationships.
- Toolkit: This domain provides the set of lowlevel libraries like widgets that are used by the Data Management components. The Data Management provides for this layer the virtual file system and input methods.
- RTCom: Depends on the addressbook functionality provided by the Data Management
Applications: Generally applications depend on the file- and mime handling provided by the data management domain.
- Connectivity: The virtual file system in data management is depending on the libraries provided by the connectivity. They are used when hiding the connecting to Bluetooth and network folders.
- System: Data management uses the system hardware information provided by the system domain.
- Multimedia Framework: Uses Data Management to access the file on different drivers and devices.
System Decomposition View
Contacts
| Name | Addressbook | |
| Purpose | Provides a general framework to store the contact and presence information. It is used especially by the RTCOM domain for handling their contact and presence information. | |
| Responsibilities | *Store contact information *Store presence information *Provide information about contact’s capabilities | |
| License | Nokia/LGPL/GPL |
Package management
| Description | Provides a way of managing the installed packages on the device. This also includes installing new versions of the components, for example when updating the device, |
| Responsibilities | *Manage component and application installation *Manage component updates |
| License | GPL |
Backup
| Purpose | Provides a general framework to backup and restore user’s data. |
| Responsibilities | *Restore data *Backup user’s data |
| License | Nokia |
File Handling
| Name | File Management | |
| Purpose | Provides whole stack for file management. This includes file access, virtual file system, mime handling and URI schema handling. The domain also provides the UI that is needed for the file access. | |
| Responsibilities | *Virtual file system (gnome-vfs) *Mime handling (libhildonmime) *Widgets for file handling (hildon-fm) *File manager | |
| License | Nokia/LGPL |
Content Handling
| Name | Tracker |
| Purpose | Provide a one stop solution for all metadata, tags, shared object databases, search tools and indexing. |
| Responsibilities | *Provides an Indexer, a lightweight daemon that extracts information from files (trackerd) *Tracker Search Tool, a small GUI to search for indexed data *Command line tools for searching, querying the daemon status, and tagging *libtracker, a C wrapper around the DBus API. |
| License | GPL/LGPL |