This is an old revision of the document!


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.

Applications can:

  • Access a user’s profile (but not change it?)
  • Access a user’s flocks (but not change them?)
  • Create new flocks (and thus new proximities)
  • Store their settings persistently
  • Be installed 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 .at source files?
uf/application.1220607546.txt.gz · Last modified: 2008/09/05 11:47 by tvcutsem
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki