-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
70 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,70 @@ | ||
| # MandM | ||
| Progetto a.a 2019/2020 del corso Tecnologie Web | ||
| # MandM Project | ||
|
|
||
| # Interactive platform with accessibility and internationalization ready for gaming, authoring, evaluating graphic adventure mini-games | ||
|
|
||
| The platform is composed by three main applications: Player, Editor and Evaluator | ||
|
|
||
| ## Editor app | ||
| Create, duplicate, delete and edit mini-games called "stories". | ||
| Stories can be played by teams, group or single players. Teams based stories have specific mission list. | ||
| The Platform has been conceived to be played using 1 device per team, 1 device for the group mode and 1 device for the single mode. | ||
| So the group mode is not tecnically different than single mode, but we use it for reference purpose for authors. | ||
| Also the age and description are also used for reference purpose only. | ||
| Each story is composed by missions and each mission is composed by activities. So different routes of the story can be chosed by player if author allowed it. | ||
| Every activity has its own customizable scene adding widgets to a grid layout and also nesting grids. | ||
| Upload assets like media, captions and stylesheets to use in some widgets. | ||
| Create your own style or upload a stylesheet to change the look and feel of the Player and of the story using the Style Editor. | ||
|
|
||
|  | ||
|
|
||
| Manage missions of every team in the main Story Editor tab | ||
|
|
||
| Activities can be of different types: | ||
| - Tell: Use it to tell and explains environment and story related stuff to tell to players | ||
| - Quest: Use it to place interactive widgets to be used by player, and providing silently a sort of input and change the future routes based on inputs in the scene. | ||
| - Branch: Tecnical activity used to check player inputs on last parent Quest activity and providing score to player, checking input values provided by user through widgets in the scene through a specific condition, and redirect story to different route of activities based on that condition | ||
|
|
||
| Edit the scene of an activity using the Scene editor:  | ||
| Customize a widget using the specific editor for a widget:  | ||
|
|
||
| Every text content of some widgets is always internazionalized on the current selected language in main "Story" tab. | ||
|  | ||
|
|
||
| here there is a specific editor for the scene's grid:  | ||
|
|
||
| Here there is a specific editor for a widget used to show media, providing also accessibility and internazionalization dedicated fields  | ||
|
|
||
| The branch editor:  | ||
|
|
||
| The Style Editor guide you to write CSS rules with a correct syntax using specific selector fields and some utility widgets:  | ||
|
|
||
| Controls the used assets or remove them from the platform if they are not needed anymore using the Asset manager:  | ||
|
|
||
| Use the utility section to store aside the qrcodes used in the story to print them later and place them in your gaming environment:  | ||
|
|
||
| ## Player app | ||
| Web app used by players to play a story. | ||
| It contains 3 sections: | ||
| - Main: The section where the scene on every activity will be shown | ||
| - Info: The section when author can provide internazionalized information content about current activity and the mission that the activity is part of | ||
| - Help: The section where player can ask help to an helper ( an evaluator ) to ask something or any info through a chat. The player ask help, but only if the evaluator accept the help, a chat will be shown. | ||
|
|
||
|  | ||
|
|
||
| The player App after loading the story, it waits for the start of the story, and after start, it provide every inputs, score and story progression updates to evaluator. | ||
| The player App works also offline after the start of the story. this feature is usefull to play the story also in areas that aren't covered by wifi. | ||
| The progression will be kept in Player and will be provided to evaluator as soon as it can connects to the platform. | ||
|
|
||
|
|
||
| ## Evaluator app | ||
| Web App used to start, monitoring player progression while playing the story. | ||
| Notify when a player require help. | ||
| Notify when a player is stuck on an activity for too long, or when an activity can't be evaluated programmatically and require a human evaluation ( used for example when a widget provide an captured image, video or audio ) and so can provide a score to it without letting the player to wait the evaluation. | ||
| Shows story progression status for each player and shows also a leaderboard. | ||
|
|
||
| This is the evaluator main view:  | ||
| The evaluator allow to show player chat and compacted activities and missions done  | ||
| This is how the stuck notification will be shown and evaluator can view which activity the player is stuck on, by clicking on alarm button in player section's toolbar: | ||
|  | ||
| This is the leaderboard to show the player scores in one place:  | ||
|
|