at:urbiflock
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
at:urbiflock [2008/08/26 19:25] – created tvcutsem | at:urbiflock [2010/08/04 17:39] – * elisag | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== What is Urbiflock? ==== | ==== What is Urbiflock? ==== | ||
- | Urbiflock | + | UrbiFlock |
- | ==== Modules ==== | + | Urbiflock is a Facebook-like application framework for mobile devices. As in Facebook, users that join Urbiflock can meet other users and interact with them. For example users may broadcast announcements to each other, they can browse one another’s profile, launch interactive polls, etc. The framework takes care of managing |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * isNearby: physical proximity | + | |
- | * isFriend: static encoding of friendship relationships | + | |
- | * doesProfileMatch: | + | |
- | * combinators: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | A flock is defined | + | Users can also build applications and plug them into the Urbiflock framework. Several core applications are currently available in the Urbiflock framework, such as flock creators and profile viewers. The framework also counts with two user applications //I rate you (IR8U)// that allows users to ask proximate |
- | === Predefined Flocks: | + | ==== Terminology ==== |
- | * friend flockrs: isFriend | + | |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | ==== Architecture: ==== | + | * Flockr: a user of the Urbiflock framework |
- | An ad hoc RETE-network: | + | * Flock: a group of users |
+ | * To flock: to become part of a group | ||
- | Events are triggered by: | + | ==== Demo ==== |
- | * discovery: joined(uid, | + | |
- | * profile changes: changed(uid, | + | |
- | * friend changes: friendAdded(uid, | + | |
- | These events are received by the local flockr user object | + | < |
+ | <object | ||
+ | </ | ||
- | ==== TODO ==== | + | ==== Target Platforms |
- | * Persistence | + | The Urbiflock framework has been written in the AmbientTalk language. As such, no configuration is required |
- | * Privacy: restrict access of applications | + | |
- | ==== Applications | + | AmbientTalk runs on a regular J2SE Java Virtual |
- | * [[uf: | + | Machine supporting version 1.3 or higher, Java 2 micro edition (J2ME) platform, under the connected device configuration (CDC), and Android Platform version 1.6 or higher. |
- | * [[uf: | + | |
+ | We have implemented a AWT UI interface for Urbiflock' | ||
+ | |||
+ | We are currently working on an Android UI interface for Urbiflock' | ||
+ | |||
+ | The Urbiflock framework is available in the AmbientTalk distribution library under frameworks/ folder which can be downloaded at [[http:// | ||
+ | |||
+ | ==== Urbiflock architecture | ||
+ | |||
+ | |||
+ | The architecture of the Urbiflock framework shown below is divided in three layers: applications, | ||
+ | {{ : | ||
+ | |||
+ | The application layer includes several core applications which are currently available in the framework such as flock and profile editors, and several users applications such as //I rate you// (IR8U), and // | ||
+ | The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, | ||
+ | |||
+ | In the rest of this subsection we list the relevant parts of the Urbiflock framework. | ||
+ | |||
+ | | ||
+ | * [[uf: | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | |||
+ | ==== Development ==== | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[: | ||
+ | * To think about: | ||
+ | * [[uf: | ||
+ | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag