The semantics should be the same used by the runtime in Tizen 2.x. Can QA help to clarify the behavior there?
From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Romuald TEXIER-MARCADÉ Sent: Friday, June 06, 2014 11:33 AM To: crosswalk-dev Subject: [Crosswalk-dev] [t.e.c filesystem API] File.copyTo and File.moveTo semantic clarification needed Hello, Currently, the FIlesystem API just does not handle directory copy/move. I'd like to implement that, so I need to clarify the semantics. The specs at https://developer.tizen.org/dev-guide/2.2.0/org.tizen.web.device.apireference/tizen/filesystem.html#copyToidp348064 are unclear about what happens when the destination path is an existing directory. The description says "The copy of the file or directory identified by the originFilePath parameter MUST be created in the path passed in the destinationFilePath parameter." but the parameter description says : "destinationFilePath: The new full virtual file path or directory path". So if destination is an existing directory, should we copy/move _inside_ it or should we try to _replace_ it (with success if overwrite is true) ? The tct-filesystem-tizen-tests are just adding to the confusion here. The tests assume that : - if both origin and destination are directories, the target is overwritten (if overwrite is true, otherwise fail); - if origin is a file and destination is a directory, the file is copied/moved _into_ the target. A consistent way would be to follow unix command semantics (always copy/move _inside_ existing directories). Thank you for helping to clarify that. Romuald. --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
