Features/Sharing Journal Entries Via School Server: Difference between revisions
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
**** XOs are connected to the different Access Points (as long as school-server is pingable throughout). | **** XOs are connected to the different Access Points (as long as school-server is pingable throughout). | ||
**** XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout). | **** XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout). | ||
== Credits == | |||
* Ceibal | |||
** For supporting this feature development. | |||
* Sascha Silbe | |||
** Initial Proposal for the solution based on WebDAV. | |||
* Anish Mangal | |||
** Showed why simply accessing the webdav shares via "Browse" activity won't work. | |||
** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But Sugar-entry are more than just the (data) file; it is a combination of | |||
*** Metadata-file | |||
*** Data-file | |||
*** Preview-file (optional) | |||
** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish). | |||
** Ruben Rodriquez | |||
*** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view. | |||