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/11/18 14:17] – adding elisag | at:urbiflock [2010/08/04 18:06] – * elisag | ||
---|---|---|---|
Line 5: | Line 5: | ||
UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: | UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: | ||
- | Urbiflock is a Facebook-like application framework for mobile devices | + | 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 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), |
- | 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 | + | 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 |
==== Terminology ==== | ==== Terminology ==== | ||
Line 16: | Line 15: | ||
* To flock: to become part of a group | * To flock: to become part of a group | ||
- | ==== Urbiflock architecture | + | ==== Demo ==== |
+ | < | ||
+ | <object width=" | ||
+ | </ | ||
- | The architecture of the Urbiflock framework | + | ==== Target Platforms ==== |
+ | The Urbiflock framework | ||
+ | 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. | ||
- | 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 // | + | We have implemented |
- | 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 give a general overview of the relevant parts of the framework. | + | We are currently working on an Android UI interface for Urbiflock' |
- | * [[uf: | + | The Urbiflock framework is available |
- | * [[uf:profiles|Profile]]: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * isNearby: physical proximity | + | |
- | * isFriend: static encoding of friendship relationships | + | |
- | * doesProfileMatch: | + | |
- | * combinators: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | ==== Applications | + | ==== Urbiflock architecture |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | ==== Target Platforms ==== | + | The architecture of the Urbiflock |
- | Rather than building a platform-independent | + | {{ : |
- | AmbientTalk requires a regular J2SE Java Virtual | + | The application layer includes |
- | Machine supporting version 1.3 or higher. | + | * [[uf: |
+ | * [[uf: | ||
+ | * [[uf: | ||
- | We have done some test to deploy our framework on HTC touch cruise pda's. In order to configure your HTC Touch device | + | There are also several user applications in the framework: |
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | The Urbiflock' | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf:profiles|User Profile]]: Profiles in Urbiflock represent the user identity (e.g. name, gender, hobbies, etc.). | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, | ||
- | We are currently working on deploying our framework on HTC Hero, a phone running on the Android platform. | + | < |
+ | Under Construction: | ||
+ | </ | ||
- | ==== Development ==== | ||
- | * [[uf: | ||
- | * [[uf: | ||
- | * [[: | ||
- | * To think about: | ||
- | * [[uf: | ||
- | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag