This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
uf:application [2008/09/05 11:37] tvcutsem created |
uf:application [2008/09/05 11:52] tvcutsem |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Applications ===== | ||
+ | |||
The most important property of an application in Urbiflock is that it should be easy to share it with your friends. Applications should thus be mobile entities that can be passed to your friends and received from your friends. | The most important property of an application in Urbiflock is that it should be easy to share it with your friends. Applications should thus be mobile entities that can be passed to your friends and received from your friends. | ||
Line 4: | Line 6: | ||
* Access a user's profile (but not change it?) | * Access a user's profile (but not change it?) | ||
* Access a user's flocks (but not change them?) | * Access a user's flocks (but not change them?) | ||
- | * Create new flocks | + | * Create new flocks |
+ | * Add actions (" | ||
* Store their settings persistently | * Store their settings persistently | ||
* Be installed at runtime | * Be installed at runtime | ||
* Be copied to another flockr at runtime | * Be copied to another flockr at runtime | ||
+ | * Be minimized, stopped, paused, restarted? | ||
+ | |||
+ | The mobility requirement needs some thought in how we are going to structure applications: | ||
+ | * does the entire app. needs to be an isolate? | ||
+ | * will we copy physical '' | ||
+ | |||
+ | < |