Note : Task Distribution

Sebastian & Octa:

- fix the mosaic option
- tile images should be fixed at 50pixel, about 30 tile width minimally
- jigsaw images should be scaled automatically & accordingly to the above requirement
- eg. original image is 500 x 500, generated mosaic would be 1500 x 1500
(may be subjected to change depending on the visibility outcome)

- zooming / scaling of jigsaw pieces
- allow the user to zoom in/out without affecting the mosaic tile quality
- zooming in will be able to see the tile images clearly at their 50p, where zooming
out will probably see a blur pixel version of that tile respectively

- transparent overlay of original image
- image overlay can be toggled over/behind the jigsaw pieces
- use the un-mosaic original image

- automatically finish puzzle option
- allow the player to skip the puzzle game if desired
- by doing so, the scoring will not be counted for that game or something like that

- mosaic progress bar
- gathering image progress, creating mosaic progress

- game option (pending)
- option to change include brightness, music volume, window size(?)

- saving of current game progress
- saving of the jigsaw position to be continued later, or which location have been
completed etc

Wilson & Jennisa:

- GUI of editor to transit panel by panel instead of tab pane
- the flow of the editor should be like what is stated in the documents, proceed to
stage by stage input using 'next' / 'back'
- provide 'help text' whenever user point at a text field etc, let user know what steps
they need to do now

- shifting of images on editor
- As the editor location selector preview shows the image being used, allow the user
to position the image to what they want
- this change should reflect in the setup.txt, in which the game can read and position
accordingly
- show the game main menu image as well if possible

- allow shifting / editing of game menu buttons
- set the position of the game buttons. Likewise should be updated in setup.txt
- allow user to create their own button design(?)
- can be optional, see what you two think is best

- porting other version of the game from editor
- create a web based applet version of the applet, maybe with text description on how the
user can place it on a website / blog etc
- other version can be explored, find out any other portability we can do

- include a disclaimer use
- have a panel stating all the agreement like we will not be responsible for any damage
cause while using our product, user are only allowed to use copyright images etc etc
- only by agreeing then they can continue using the editor

- video on usage / feature

*P.S. The changes you made on the setup.txt, u will have to make the changes in the game
as well. Let me & octa know what u changed and how we must change to read it *

Santy:

- update documents with changes if any
- basically, once the code is being work on, you will update the required diagram and new
description if there is a need to change
- all the document related stuff is covered by you

- quality plan
- come up with a plan stating what quality are we ensuring our product have
- eg. The editor should be easy to use, with help description whenever the user point at some
text field
- something like that, come up with how we aim our product to have certain standards

- test case with test and results
- Come up with the text case and our results. Obviously you have to fake the results here, make
it sensible
- start off with testing of mosaic and jigsaw function independently after our first integration,
what went well and what doesn't. Record down our observation etc

- configuration management (version control)
- again, come up with what you think will be our versioning like.
- eg. version 1.1 of game would be handling all of mosaic, 2.1 onwards on jigsaw etc
- come up with date that we did the changes too. Follow the time line as planned in the proposal
and make appropriate changes if it doesn't fit