Activities/FileShare: Difference between revisions

Line 8:

==Project Status==

The project is under active development. I am currently looking for bug reports as well as suggestions for further improvement. Check out the current Dev Release (Dec. 14, 2009) or source code.

The project is under active development. I am currently looking for bug reports as well as suggestions for further improvement. Check out the current Dev Release (Dec. 15, 2009) or source code.

If you have found a bug, please report it the google group page or email to our google group email address.

Line 15:

* Activity can be loaded up and files can be added and removed from the file list

* It can be shared and users who join are able to download files (journal entries) from the file list and have them installed into their own journal.

* Activity is able to keep and resume

** On closing, the files and file list is stored in the activity entry and can be restored.

** One advantage to this is an instance of this activity can be shared and the files remain with it.

* The server is able to copy files back to the journal

** Useful when restoring the activity and would like to get a file back that may have been deleted or modified.

==Bugs==

* Sometimes user interface can become un-responsive during file transfers.

* (Untested, but looks like this will be problematic)Client downloads file and then disconnects. The server then removes a file and re-adds file (after changing it). When the client re-connects (resumes) the client will not know that the file changed and not allow them to download the new one.

** Work around: Close the activity and delete it's entry in the journal. When re-connecting, it will allow all downloads as expected as it doesn't know that you already downloaded that file.

==Future Plans==

Line 25:

Line 34:

** Download count on each file

** Prevent/Notify user from closing the activity while users are downloading from them.

* Activity should be able to save its state

** Next time it loads up, the activity should be able to restore the file list and continue sharing.

** This feature would be helpful for a teacher to save files related to the day's lesson and then be able to recall it at a later time.

* Integration to the school server

@@ Line 8: / Line 8: @@
 ==Project Status==
-The project is under active development.  I am currently looking for bug reports as well as suggestions for further improvement.  Check out the current Dev Release (Dec. 14, 2009) or source code.
+The project is under active development.  I am currently looking for bug reports as well as suggestions for further improvement.  Check out the current Dev Release (Dec. 15, 2009) or source code.
 If you have found a bug, please report it the google group page or email to our google group email address.
@@ Line 15: / Line 15: @@
 * Activity can be loaded up and files can be added and removed from the file list
 * It can be shared and users who join are able to download files (journal entries) from the file list and have them installed into their own journal.
+* Activity is able to keep and resume
+** On closing, the files and file list is stored in the activity entry and can be restored.
+** One advantage to this is an instance of this activity can be shared and the files remain with it.
+* The server is able to copy files back to the journal
+** Useful when restoring the activity and would like to get a file back that may have been deleted or modified.
 ==Bugs==
 * Sometimes user interface can become un-responsive during file transfers.
+* (Untested, but looks like this will be problematic)Client downloads file and then disconnects. The server then removes a file and re-adds file (after changing it).  When the client re-connects (resumes) the client will not know that the file changed and not allow them to download the new one.
+** Work around: Close the activity and delete it's entry in the journal. When re-connecting, it will allow all downloads as expected as it doesn't know that you already downloaded that file.
 ==Future Plans==
@@ Line 25: / Line 34: @@
 ** Download count on each file
 ** Prevent/Notify user from closing the activity while users are downloading from them.
-* Activity should be able to save its state
-** Next time it loads up, the activity should be able to restore the file list and continue sharing.
-** This feature would be helpful for a teacher to save files related to the day's lesson and then be able to recall it at a later time.
 * Integration to the school server