Date post: | 24-Dec-2015 |
Category: |
Documents |
Upload: | emily-newman |
View: | 212 times |
Download: | 0 times |
Goals
• Try to Keep most of the interfaces as a web based thing……..– Situation Publishing – Team Formation for situations, behavior demonstration, for
important characters – Blog about your avatar, characters you are creating pets (if
you are creating a pet), their backgrounds etc.– Specialized community formations (aka Ning) for creating characters/behaviors for a specific domain,
Ontology Managers, Situation creators etc.– Domains like war, university students etc.
Interface for Situation Creators
– Can be provided as a menu item– Should open a browser kind of window in SL– There is an embedded browser inside SL main
interface. – Keeping all these interfaces as a web based thingy
allows for keeping most of the things separate from Second Life
Interface for Situation Creators
– Should provide the following facilities• Create a new situation• Browse through existing situations• Modify a situation• Provide lock/unlock feature in order to synchronize
actions and avoid simultaneous modifications
Create a new situation
• Provide following features:– Brief situation title – Description– No. and roles of actors required to demonstrate
the situation– Publish the situation
Description:A boy enter a bar to seek out a girl. At the same time a hot girl enters the bar to have a drink ….
Roles:• A boy seeking out a girl.• A hot girl.• Bartender of the pub.• Other public in the bar.
Preferred Location:• Bar or pub
Publish
Publishing a situation
• Once a situation is created / modified, it needs to be published– Communication b/n SL client and a web server
where situations can be published– Structure of server repository – Structure of situation itself (preferably XML)
Browsing thru’ Situations• Requires the following:
– Client/Server Communication– Should provide information as:
• Situation Title• Description • Roles/ actors needed to depict the situation• Author• Date of Creation• Last modified by – in case modification other than from
author is allowed• No and link to demonstrations available• Button to take to demonstration interface
Existing Demonstrations
Demonstrate
Edit
Modify a situation
• Will modification other than from author be permitted?
• What should be modifiable?– Title: no– Description: may be– Author: no– Actors needed for demonstration: may be
Interface for Demonstrators
• Can be provided as a menu item, as well as a link from Situation Page
• The interface should provide the following:– Title and description of situation– List of roles desired for the situation– Roles occupied, by whom, link to member’s profile or
short dialog box providing brief information about member
– Join the team– Facility to IM team members
cont…..
– Provision to search preferred location– Teleport to preferred location– Demonstrate:
• The team would discuss over chat sessions about demonstrating the situation
• Another group of interfaces to facilitate demonstration like
– low level actions– higher level gestures and – Further higher level goals,
plans
Demonstrate
Search LocationTeleport
to Location
Join
Join
Join Team of Demonstrators (DT)
• Another interface needed to allow users navigate thru’ DTs they have joined.
•
Behavior Demonstration Interface: Basic gestures
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Say
Shout
Whisper
Behavior Demonstration Interface: Basic Talk gestures
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
kiss1
blush
smile
wink3
Head gestures
PREVIEW
Behavior Demonstration Interface: Basic gesture selection
Demonstration UI Future• Ability to direct actions at characters (ex: Pinch X, Talk toward X)• Demonstrate higher level actions• Indicate Active Goals / Emotional states• Indicate Perceptions
– Perceptions can also have an ordering / suggestion effect on the high level actions
• Have a workflow-style UI, where the user can see a history of the interaction, and work with behaviors themselves rather than live action
• Could start Demonstrations by using high level behaviors (ie: build the interaction top down, rather than bottom up)
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Lisa
PinchKissWinkFollow …..
Attending to:
Lisa
Future: Engagement to Characters
Future: High-level actions
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Actions
Flirt
Order Drink
Greet (active)
Future: High-level action selection
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Actions
Flirt
Order Drink
Greet (active)
Eat_loudly
Talk_politics
Compliment
Poison
Dinner gestures
PREVIEW
ACTION ONTOLOGY
- Social Situations + Outdoors - Indoors + Lounging - Dinner + Bedroom + Clubbing
+ Private Situations+ Murder Scenes+ Sports
Future: Goals / Emotions
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Active Goals
Emotions
Create Romance
Excited
Happy
Future: Perceptions
Gesture:
Talk:
wave kiss1 growl smile jump_02 bow wave kiss1 growl smile jump_02 bow MORE
Perceptions
X is smiling.
X is flirting with me
Demonstration UI Issues
• Engaging with other characters• Turn-taking in interactions• Real-Time vs Demo-Time:
– In reality, interactions may overlap– In reality, interactions may be longer / shorter– Need to indicate if a “wait” behavior is happening during
demo– (above may be appropriate through Debug interface)
• Ability to undo previous actions (History)• (Representing / browsing high level actions)
Situation Perception & Reaction
Perceptions
ActionsTime
Mary smiling Max talking
Max flirting with Mary
Max body on floor
Stop marriage
Interrupt flirting
Go to Max Push Max
E: Anger
Low-level percepts
High-level percepts
Previously active goals /
emotions / perceptions of
others
Max is badly injured
Blood on floor
Plans (high level actions)
Lower-level actions
T: Doctor
Time
Treat injury
Task ListTask List Team
1 Second Level of Slides from last semester including use cases
Manish/Iulian/Abhishek
2 Create the SL client Abhishek, 4911 team
3 Behavior Demonstration/Goals Interfacesa) Paper prototypes (first half of the semester)
b) Implementation (second half of semester)
• Christina, Iulian• Iulian, 4911 team, Abhishek
4 Behavior Execution/Representation a) Behavior Representation b) Behavior Execution Engine/ Language :
Manish/Iulian/Abhishek
5 Other Interfaces (not critical list for now) a) Paper Prototypes including situation publishing, team formation, blogging, specialized community formation etc (second half): b) Implementation
a) Christina, all
b) Iulian, Manish, Abhishek