Differences

This shows you the differences between two versions of the page.

--- at:urbiflock [2008/09/05 11:52] – cfscholl
+++ at:urbiflock [2008/09/24 13:34] – cfscholl
@@ Line 40: / Line 40: @@
 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.
-As a first implementation of the RETE-network, maybe we can start from the oo matching that Tom implemented, so that proximity functions are templates. For example:
-<code>
-def flockrTemplate := template: {
-  def name := *; // wildcard, can be anything
-  def age := constraint: { _ < 25 }; // must be younger than 25
-  def address := template: {
-    def street := *; //any street,but street name must be filled
-    def city := "Brussel"; // city must equal this string
-  };
-  def greet(); // person must have a greet method
-} taggedAs: [ Flockr ]; // object must be tagged as a Flockr
-</code>
 ==== Applications ====
@@ Line 61: / Line 47: @@
   * [[uf:iflocku|IFlockU]]: a friend suggestor based on profile similarity and time spent in proximity.
   * [[uf:guanotes|Guanotes]]: a messenger application that sends post-its to flocks.
+==== 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 [[uf:AmopHTC|here]].
 ==== To think about ====
   * [[uf:persistence|Persistence]]: saving/loading framework and application data and prefs.
   * [[uf:privacy|Privacy]]: restrict access of applications to a user's flocks