525
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: − + Line 36:
Line 36: + + + + + + + + + + + + + + + + + + + + + + + +
Features/Transfer to many options (view source)
Revision as of 09:32, 2 April 2012
, 09:32, 2 April 2012→Details
* '''Exporting Data to WebDav, on a server XO.'''
* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
** Sascha's JournalToWebDAV workflow.
** Sascha's JournalToWebDAV workflow.
*** step 1
*** step 1
*** The corresponding folder is "/var/www/web1/web" (as configured in "/etc/httpd/conf.d/ssl.conf").
*** The corresponding folder is "/var/www/web1/web" (as configured in "/etc/httpd/conf.d/ssl.conf").
*** All entries in the "Share" folder would be available to client XOs.
*** All entries in the "Share" folder would be available to client XOs.
* '''[Code-Requirements] Exporting Data to WebDav, on a server XO.'''
** Sascha has already coded the first alternative.
** For the second alternative, "Share" listview needs to be added on the lines of "Documents" listview. Code-reuse should be done as much as possible. Ideally, there should just be a difference of the "folder-path".
* '''[User-Workflow] Client XO wishes to access the share of Server XO'''
** Navigates to the "Neighborhood" view.
** Hovers over the "Server" buddy.
** The popup appears, which has a new entry "Access Share" (in addition to "Make Friend").
** Clicks on "Access Share".
** The "Browser" activity opens, with the url pointing to the "Server" buddy's webdav share.
** Thereafter, client may navigate the webdav directory hierarchy, or download files (all of which is already built in the "Browse" activity). Most importantly there is the "Keep Link" feature in "Browse", which nicely downloads the webdav-entry, and promptly saves it in the "Journal" - something that happens in the "Send To" feature as well.
* '''[Code-Requirements] Client XO wishes to access the share of Server XO'''
** Mapping a neighborhood-buddy to its IP Address
*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist in the "BaseBuddyModel" in "jarabe/model/buddy.py".
*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
** Opening up the server's webdav
*** The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.
** A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html