248
edits
Changes
no edit summary
==Project Status==
==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. 15, 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. 18, 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.
If you have found a bug, please report it the google group page or email to our google group email address.
* 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.
* 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
* Activity is able to keep and resume
** On closing, the files and file list is stored in the activity entry and can be restored.
** On closing, the system asks the user if they wish to keep the files with the activity. If they do, 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.
** 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
* The server is able to copy files back to the journal
==Bugs==
==Bugs==
* Sometimes user interface can become un-responsive during file transfers.
* Sometimes user interface can become un-responsive during file transfers or when adding large files that don't have journal entires yet.
* (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.
* (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.
** 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.
* [Cannot Consistently Reproduce] Permission Denied when reading files on a flash drive
* [Cannot Consistently Reproduce] Permission Denied when reading files on a flash drive
==Future Plans==
==Future Plans==
*2009-12-14: FileShare-2.xo
*2009-12-14: FileShare-2.xo
*2009-12-15: FileShare-3.xo
*2009-12-15: FileShare-3.xo
*2009-12-18: FileShare-4.xo
==Links==
==Links==
* Project Leader: [[User:Jlew| Justin Lewis]]
* Project Leader: [[User:Jlew| Justin Lewis]]
** [http://groups.google.com/group/fileshareactivity/files File Builds]
** [http://groups.google.com/group/fileshareactivity/files File Builds]
** Screenshots can be found in the google group file list as well
** Screenshots can be found in the google group file list as well
* Current Release: [http://groups.google.com/group/fileshareactivity/web/FileShare-3.xo FileShare-3.xo]
* Current Release: [http://groups.google.com/group/fileshareactivity/web/FileShare-4.xo FileShare-4.xo]