This commit is contained in:
Joey Hess 2012-05-28 14:29:21 -04:00
parent 5a270415ef
commit 5d178d2aca
3 changed files with 15 additions and 19 deletions

View file

@ -11,7 +11,7 @@ Feel free to chip in with comments! --[[Joey]]
* Month 2 "shiny webapp": [[!traillink webapp]] [[!traillink progressbars]]
* Month 3 "easy setup": [[!traillink configurators]]
* Month 4 "release": [[!traillink leftovers]]; release
* Months 5-6 "9k bonus round": [[!traillink Android]]
* Months 5-6 "9k bonus round": [[!traillink Android]] [[!traillink partial_content]]
## not yet on the map:

View file

@ -3,8 +3,6 @@ Porting git-annex to Android will use the Android native SDK.
A hopefully small Java app will be developed, which runs the webapp
daemon, and a web browser to display it.
[[!toc]]
### programs to port
These will probably need to be bundled into the Android app, unless already
@ -53,19 +51,3 @@ Problem:
#### crazy `LD_PRELOAD` wrapper
Need I say more? (Also, Android's linker may not even support it.)
### partial content
On a regular system, a reasonable simplifying assumption is that all the
files in the folder will be synced to the system. A user might want to
disable syncing of some subdirectories, for eg, archived files. But in
general, things are simpler to understand and implement if all files sync.
But, a phone probably cannot hold all a user's files. Indeed, it's likely
that old files will be aggressively dropped from the phone after syncing to
elsewhere, in order to keep enough free space on it for new files.
There needs to be a way for the user to browse files not on the phone and
request they be transferred to it. This could be done as a browser in the
web app, or using a subdirectory full of placeholder files (not symlinks;
see above) that start transfer of the real file when accessed.

View file

@ -0,0 +1,14 @@
On a regular system, a reasonable simplifying assumption is that all the
files in the folder will be synced to the system. A user might want to
disable syncing of some subdirectories, for eg, archived files. But in
general, things are simpler to understand and implement if all files sync.
But, an Android gadget probably cannot hold all a user's files. Indeed,
it's likely that old files will be aggressively dropped from the Android
after syncing to elsewhere, in order to keep enough free space on it for
new files.
There needs to be a way for the user to browse files not on the gadget and
request they be transferred to it. This could be done as a browser in the
web app, or using a subdirectory full of placeholder files (not symlinks;
see [[Android]]) that start transfer of the real file when accessed.