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 [2009/02/27 17:21] – tvcutsem | at:urbiflock [2009/11/18 14:35] – elisag | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== What is Urbiflock? ==== | ==== What is Urbiflock? ==== | ||
- | Urbiflock is a Facebook-like application framework for mobile devices written in AmbientTalk. The framework takes care of managing a user's buddy lists, called | + | 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 | ||
+ | |||
+ | 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 ==== | ==== 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 | + | ==== Urbiflock architecture |
- | * [[uf: | + | |
- | * [[uf:flockr|Flockr]]: a representation | + | |
- | * [[uf: | + | 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) that allows users to ask proximate users to rate them on a certain subject, 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:flock|Flock]]: a loosely defined group of users. | ||
+ | * [[uf: | ||
* isNearby: physical proximity | * isNearby: physical proximity | ||
* isFriend: static encoding of friendship relationships | * isFriend: static encoding of friendship relationships | ||
* doesProfileMatch: | * doesProfileMatch: | ||
* combinators: | * combinators: | ||
- | * [[uf:flock|Flock]]: a group of ' | + | * [[uf:application|Application]]: |
- | * [[uf:applications|Applications]]: manage | + | * [[uf:viewer|Flock |
- | * [[uf: | + | * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing |
+ | * [[uf:profile_viewer|Profile Viewer]]: a viewer and editor to view existing flockr profiles and to update your profile. | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf:ir8u|IR8U]]: an application | ||
- | A flock is defined as a list of references | + | ==== Target Platforms ==== |
+ | Rather than building | ||
- | Predefined Flocks: | + | AmbientTalk requires a regular J2SE Java Virtual |
- | * friend flockrs: isFriend | + | Machine supporting version 1.3 or higher. The implementation also runs on the Java 2 micro edition (J2ME) platform, under the connected device configuration (CDC). |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | WhiteBoard Drawings: | + | We have done some test to deploy our framework on HTC touch cruise pda's. In order to configure your HTC Touch device for our framework you can follow the instruction |
- | * [[uf:Design|Design]] | + | |
- | ==== Architecture ==== | + | We are currently |
- | An ad hoc RETE-network. Events are triggered by: | + | |
- | * discovery: '' | + | |
- | * profile changes: '' | + | |
- | * friend changes: '' | + | |
- | + | ||
- | These events are received by the local flockr user object and propagated to all local proximities. Proximities translate these events into addUser / removeUser events to be processed by flocks. To process these events, flocks register themselves on their dependent proximity. | + | |
- | + | ||
- | ==== Applications ==== | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | + | ||
- | ==== Target Platforms ==== | + | |
- | * UrbiFlock will work on any computer which has java installed. | + | |
- | * We are currently | + | |
==== Development ==== | ==== Development ==== | ||
- | * [[uf: | ||
- | ==== To think about ==== | + | * [[uf: |
- | * [[uf: | + | * [[uf: |
- | * [[uf: | + | * [[: |
+ | * To think about: | ||
+ | * [[uf: | ||
+ | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag