This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
at:urbiflock [2010/08/04 17:21] elisag updating |
at:urbiflock [2015/02/04 19:06] elisag |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Urbiflock ====== | ||
- | ==== What is Urbiflock? ==== | ||
- | |||
- | UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: | ||
- | |||
- | Urbiflock is a Facebook-like application framework for mobile devices written in AmbientTalk. 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 a user’s social networks, called “flocks”. A flock represents a loosely-defined group of users. A flock can be compared to a Facebook group (for example, a group of your old classmates), | ||
- | |||
- | Similar to Facebook, users can 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 is currently still under development, | ||
- | |||
- | ==== Terminology ==== | ||
- | |||
- | * Flockr: a user of the Urbiflock framework | ||
- | * Flock: a group of users | ||
- | * To flock: to become part of a group | ||
- | |||
- | ==== 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: | ||
- | * [[uf: | ||
- | * [[uf: | ||
- | |||
- | ==== Target Platforms ==== | ||
- | 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. | ||
- | |||
- | AmbientTalk runs on a regular J2SE Java Virtual | ||
- | 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. | ||
- | |||
- | We have implemented a AWT UI interface for Urbiflock' | ||
- | |||
- | We are currently working on an Android UI interface for Urbiflock' | ||
- | |||
- | ==== Development ==== | ||
- | |||
- | * [[uf: | ||
- | * [[uf: | ||
- | * [[: | ||
- | * To think about: | ||
- | * [[uf: | ||
- | * [[uf: |