Feature #3711
purge Notification from CacheWord, make app pass it in
| Status: | Closed | Start date: | 09/04/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.1 | |||
| Component: |
Description
The app should make and handle its own Notification, rather than having CacheWord create it. This will make it possible to distribute CacheWord as a single jar, rather than a android library project (the Notification requires an icon and XML stuff).
The current Notification code should be moves to an example.
Related issues
Associated revisions
purge built-in Notification, the app must now provide it
Previously, there was an elaborate, custom framework for customizing the
Notification that was hard-coded into CacheWord. Now, the app must supply
a Notification, and that triggers CacheWordService to run as a foreground
Service. Otherwise, CacheWordService will run as a background Service with
no Notification.
This removes the last remnants that require CacheWord to be an Android
Library Project. Now it can be distributed as just a jar. It can still be
used as a Library Project for those who like doing it that way.
fixes #3711 https://dev.guardianproject.info/issues/3711
fixes #3680 https://dev.guardianproject.info/issues/3680
History
#1 Updated by Anonymous over 3 years ago
- Status changed from New to Resolved
Applied in changeset cacheword|commit:70afd0d5f9fba98d2b575cf7d0d55a5fdc7e6e2f.
#2 Updated by hans almost 3 years ago
- Status changed from Resolved to Closed