Switch from an XML for detailing compatible apps to having the ETL report info

[mikepsinn]

Each converter file should have to implement a method getApp where they specify:

• App label (i.e. App Name such as "Accupedo")
• packageName (i.e. com.corusen.accupedo.te)
• developer (i.e. Corusen LLC)
• dataFile (Path to data file such as /internal/databases/datastorage where /internal is an abbreviation as defined here:
• /internal = /data/data/com.packagename
• /external = /mnt/sdcard/Android/data/data/com.packagename
• If not internal/external use the actual file path.
• TODO implement /sdcard
• rootRequired (i.e. "true" indicating that the user must root their phone in order to access this data file)

[quintstoffers]

Started working on this in branch /feature/quint/appinfo-via-converter

• 91ccbd6 Split ApplicationData in two classes, one containing static data, the other dynamic data
• Create class SyncableFile to hold a relative path and a location on disk (INTERNAL, EXTERNAL, any others?). Implement toFile method to convert relative path to absolute path.
• Add ArrayList to SyncableAppInfo
• Modify ETL to support an ArrayList and toFile method of SyncableFile

[mikepsinn]

Not sure if this is germane to the question about syncable file paths, but
what's your current stance on adding QM to the sharing menu options
available when exporting your data from other tracking apps. That would
make QM sync available to millions more users.
Would that be difficult to implement? Would it have any bearing on the
current course of development?

[quintstoffers]

That's irrelevant to this, yes. The ETL can't handle anything other than
files, so sharing through intents is something different all together.
Furthermore it'd require non-rooted QM users to install the app which is
otherwise useless to them.
On Aug 6, 2014 1:09 AM, "Mike P. Sinn" [email protected] wrote:

Not sure if this is germane to the question about syncable file paths, but
what's your current stance on adding QM to the sharing menu options
available when exporting your data from other tracking apps. That would
make QM sync available to millions more users.
Would that be difficult to implement? Would it have any bearing on the
current course of development?

—
Reply to this email directly or view it on GitHub
#54 (comment)
.