Demos for Migration Paper

• 2 mobile users
• private locale, one for each user
• 1 public locale
• migration to and from the public locale
• how do we do the interaction?

TODO : a marker sensitive node that moves applications between locales. It should be excited by a marker leavong or entering a certain area...1)

Applications themselves are moved by markers. The configuration to do so will exist on all hosts. these marker movements will need to take the tracking of the locale into account as well. 2)

luftgeist and feuergeist with mobile setup. heads up cameras are used to track markers with applications and the public locale.

3 locales. the private locales contain the userkits and allow interaction for applications the host is master of. the public locale is shared at startup.

the viewer is configured to create and join the public locale and its tracking station is set 3). 4 applications are started in the public locale.

marker window tracking is configured for the 4 applications.

moving to locale app is done by the app migration node.

applications are migrated by defining an area for the public locale and moving markers in and out of that locale.

a lot of work to have mobile kits work correctly with respect to tracking etc.

documentation using video see through on luftgeist and recording the output.

each application will be fixed to one host. so there is no functionality working like 1). we only let an application join the public locale using 4). This is a concession to lack of time :).

• multiple adjacent screens (use 4 if you can)
• every screen has a locale
• migrate applications across displays
• use markers/overhead cameras to track object markers
• have many appobjects running, with only local load on 1 locale

up to 4 hosts for each screen. we have faust, schueler, marthe and laptop ?

one or two overhead cameras for tracking. they should define one coordinate system.

we use up to 4 locales. they all have the same coordinate system.

each host has a user to display the locale.

A marker sensitive node moves applications between locales. In this setup this happens by sharing and unsharing an app within a given locale. 4)

Applications themselves are moved by markers. The configuration to do so will exist on all hosts. they will also be started by marker startup stuff.

see box above

a lot of work to setup tracking etc.

documentation by filming the up to 4 screens side by side and moving applications with markers between screens.

• Like demo 2
• Use a notebook with a marker attached
• bring it into the tracking range
• migrate an application to it
• move the notebook around/away
• Variant 1: the appobjects stay fixed in world space
• Variant 2: the appobjects stay on the notebook locale

2 screens using faust and schueler.

luftgeist for portable display.

overhead tracking for markers and luftgeist with one camera.

variant 1: notebook is a tracked display and in addition to that joins the locale at the space. than migrating applications is just as before and moving the notebooks leaves objects fixed.

variant 2: notebook is not a tracked display. then the locale is just not tracked and will move with the notebook. (this is kind of a fake).

• Locale A and B are shown on display 1
• Appobject on marker A in locale A
• Put a special marker B next to it
• Appobject is replicated on marker B in locale B
• Modify Appobject(marker A) -> observe change on Appobject(marker B)
• Carry over marker B to display 2
• Display 2 shows only Locale B
• Modify Appobject(marker A) -> observe change on Appobject(marker B)
  (Video may use splitscreen technique)

This demo breaks with an assumption we used so far. It allows the same application subscribed twice by one host. However it is definitly a nice application so we should extend the system to allow this.

moreover. an app shared in locale B would instantaneously appear there. Therefore moving the marker to display 2 would only mean to move the application within the locale to another place which is observed by display 2 as opposed to the place that is observed by display 1. I'm not sure if that is what we want to show ?

• stream application to a "persistency" locale
• pick them up much later

setup as in panorma screen, with a possible invisible persistency locale.

we just clean up all applications by moving them there. just turn off the one screen :).