at:urbiflock
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:urbiflock [2008/09/24 22:14] – cfscholl | at:urbiflock [2010/08/04 17:33] – embedding elisag | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== What is Urbiflock? ==== | ==== What is Urbiflock? ==== | ||
- | Urbiflock is a Facebook-like application framework | + | UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: |
+ | |||
+ | Urbiflock is a Facebook-like application framework | ||
+ | |||
+ | Users can also build applications and plug them into the Urbiflock | ||
==== Terminology ==== | ==== Terminology ==== | ||
- | * Flock: a group of proximate users | + | * Flockr: a user of the Urbiflock framework |
- | * Flockr: a user of the urbiflock framework | + | * Flock: a group of users |
* To flock: to become part of a group | * To flock: to become part of a group | ||
- | ==== Modules | + | ==== Demo ==== |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * isNearby: physical proximity | + | |
- | * isFriend: static encoding of friendship relationships | + | |
- | * doesProfileMatch: | + | |
- | * combinators: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | A flock is defined as a list of references to ' | + | < |
+ | <object width=" | ||
+ | </ | ||
- | Predefined Flocks: | + | ==== Target Platforms ==== |
- | * friend flockrs: isFriend | + | The Urbiflock framework has been entirely written in the AmbientTalk language. As such, no configuration is required to be able to quickly script new applications on it once AmbientTalk is running on the target platform. |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | WhiteBoard Drawings: | + | 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. |
- | ==== Architecture ==== | + | We have implemented a AWT UI interface for Urbiflock' |
- | An ad hoc RETE-network. Events are triggered by: | + | |
- | * discovery: '' | + | |
- | * profile changes: '' | + | |
- | * friend changes: '' | + | |
- | These events | + | We are currently working on an Android UI interface for Urbiflock' |
- | ==== Applications | + | ==== Urbiflock architecture |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | The architecture of the Urbiflock framework shown below is divided in three layers: applications, |
- | * [[uf: | + | {{ : |
- | * [[uf: | + | |
+ | 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: | ||
- | ==== Target Platforms ==== | ||
- | * UrbiFlock will work on any computer which has java installed. | ||
- | * We are currently testing our framework on HTC touch cruise pda's. In order to configure your HTC device for our framework you can follow the instruction [[private: | ||
+ | ==== Development ==== | ||
- | ==== To think about ==== | + | * [[uf: |
- | * [[uf: | + | * [[uf: |
- | * [[uf: | + | * [[: |
+ | * To think about: | ||
+ | * [[uf: | ||
+ | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag