-
- Downloads
Bug 1291384 - 1. Take BrowserDB out of GeckoProfile; r=nalexander
Remove references to BrowserDB and its factory from GeckoProfile. Instead of keeping the DB in mDB, GeckoProfile now keeps an arbitrary object in mData. Using a data object lets us avoid needing another map to map profiles to DBs. This feature could be very useful for GeckoView consumers as well. The new way to get a BrowserDB from a profile/context is through BrowserDB.from(Context) or BrowserDB.from(GeckoProfile), which takes care of creating a local DB if necessary and associating the DB with the profile.
Showing
- mobile/android/base/java/org/mozilla/gecko/GeckoApplication.java 0 additions, 18 deletions...android/base/java/org/mozilla/gecko/GeckoApplication.java
- mobile/android/base/java/org/mozilla/gecko/db/BrowserDB.java 20 additions, 11 deletionsmobile/android/base/java/org/mozilla/gecko/db/BrowserDB.java
- mobile/android/base/java/org/mozilla/gecko/db/LocalBrowserDB.java 1 addition, 1 deletion...ndroid/base/java/org/mozilla/gecko/db/LocalBrowserDB.java
- mobile/android/base/java/org/mozilla/gecko/db/StubBrowserDB.java 0 additions, 385 deletions...android/base/java/org/mozilla/gecko/db/StubBrowserDB.java
- mobile/android/base/moz.build 0 additions, 1 deletionmobile/android/base/moz.build
- mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoProfile.java 31 additions, 34 deletions...ckoview/src/main/java/org/mozilla/gecko/GeckoProfile.java
Loading
Please register or sign in to comment