Page 1 of 3
XYcopy questions
Posted: 17 Mar 2010 14:47
by Mesh
I'd like some clarification on XYcopy, if I could.
1. The release notes say that if AutoQueue is disabled, then new operations are triggered in the foreground. Do these foreground operations still occur in a multi-threaded seperate process? Or is it doing it the same way XY did it before XYcopy?
2. Is XYcopy fully trustworthy at this point? Or should it not be used other than testing?
Re: XYcopy questions
Posted: 17 Mar 2010 14:58
by zer0
Mesh wrote:2. Is XYcopy fully trustworthy at this point? Or should it not be used other than testing?
This one is easy. Since XYplorer with XYcopy is in beta stage, we should adhere to a warning in License Lounge: "Note that BETA versions are work in progress and might contain fresh bugs." If it is a concern, then it probably shouldn't be used in a production environment

Re: XYcopy questions
Posted: 17 Mar 2010 15:39
by Mesh
zer0 wrote:
This one is easy. Since XYplorer with XYcopy is in beta stage, we should adhere to a warning in License Lounge: "Note that BETA versions are work in progress and might contain fresh bugs." If it is a concern, then it probably shouldn't be used in a production environment
No, that's too broad. I'm always using a beta version of XY. I'm looking for specifics, in regards to the current state and trustability of XYcopy.
Re: XYcopy questions
Posted: 17 Mar 2010 15:54
by serendipity
I have more questions/wishes:
Before that i should say its working really nice on my win7 32-bit PC, i can go about doing what i want as it is happily copying multiple files. Until now i had to depend on teracopy for large-file-copying, but i might use XYcopy soon.
1. Can move operation be such that only after everything is copied the source file is deleted. i think its much safer in case of power failure or whatever reason. Maybe it already works this way.
2. Can we have some basic stats (atleast in the beta phase) about how long it takes to complete any operation? Users could report their times for comparison sake.
3. How does XYcopy compare to vista/win7 copy? I currently have no time to run these tests.
Re: XYcopy questions
Posted: 17 Mar 2010 15:57
by admin
Mesh wrote:I'd like some clarification on XYcopy, if I could.
1. The release notes say that if AutoQueue is disabled, then new operations are triggered in the foreground. Do these foreground operations still occur in a multi-threaded seperate process? Or is it doing it the same way XY did it before XYcopy?
2. Is XYcopy fully trustworthy at this point? Or should it not be used other than testing?
1. Currently the same way XY did it before XYcopy. It would be easy though to run any number of XYcopy processes simultaneously. I'm just not decided yet what's better or if I should make that a choice for the user.
2. The copying (or whatever operation) itself is as trustworthy as ever because it's the same shell doing the job. I'm still waiting for the first queue to fail -- it appears to be solid.
What I sometimes have is that confirmation prompts from the background queue are hidden behind the top window, so you might think a copy happened while in fact it is waiting for you to confirm an overwrite... I'm working on this.
Also there still might be situations where the refresh after the job is not perfect.
Generally I'd say the feature is too young to be fully trusted yet.
Re: XYcopy questions
Posted: 17 Mar 2010 16:06
by admin
serendipity wrote:I have more questions/wishes:
Before that i should say its working really nice on my win7 32-bit PC, i can go about doing what i want as it is happily copying multiple files. Until now i had to depend on teracopy for large-file-copying, but i might use XYcopy soon.
1. Can move operation be such that only after everything is copied the source file is deleted. i think its much safer in case of power failure or whatever reason. Maybe it already works this way.
2. Can we have some basic stats (atleast in the beta phase) about how long it takes to complete any operation? Users could report their times for comparison sake.
3. How does XYcopy compare to vista/win7 copy? I currently have no time to run these tests.
Great to hear it's working!

(And thanks for the courage to try!

)
1. I would think that this is the standard. And I cannot influence it anyway, whether I use the shell or other API. This is low level stuff.
- Move (across drives) = Copy, then delete source.
- Move (within drive) = Rename.
2. OK, but where should the stats appear?
BTW, as I said in the roadmap (keyword "comfy") I also plan an alternative Copy/Move method where I use kernel API instead of shell API, which will give me full control about the progress feedback and confirmation prompts. There will be a live interface (real window, selectable on taskbar) similar to TeraCopy (or any copy software) for each ongoing process. There you have your luxury stats. This might come only with
XYcopy 2.0 though...
3. I would expect it's currently slower than the new vista/win7 copy. But the kernel version should be equally fast or faster.
Re: XYcopy questions
Posted: 17 Mar 2010 16:10
by Mesh
admin wrote:
1. Currently the same way XY did it before XYcopy. It would be easy though to run any number of XYcopy processes simultaneously. I'm just not decided yet what's better or if I should make that a choice for the user.
Well, if the user has opted to use XYcopy, I think it makes sense to continue to use it. However, new processes should probably be moved to the front of the queue for immediate handling, if it's not better to have them run parallel.
admin wrote:
2. The copying (or whatever operation) itself is as trustworthy as ever because it's the same shell doing the job. I'm still waiting for the first queue to fail -- it appears to be solid.
What I sometimes have is that confirmation prompts from the background queue are hidden behind the top window, so you might think a copy happened while in fact it is waiting for you to confirm an overwrite... I'm working on this.
Also there still might be situations where the refresh after the job is not perfect.
Generally I'd say the feature is too young to be fully trusted yet.
I'm a little confused, because you started out by saying that it's as trustworthy as ever, but ended by saying it shouldn't be fully trusted yet.
If it helps to clarify, I don't mind little interface bugs, such as the hidden confirmation prompts. I'm concerned with the integrity of file operations.
Re: XYcopy questions
Posted: 17 Mar 2010 16:18
by admin
Mesh wrote:admin wrote:
1. Currently the same way XY did it before XYcopy. It would be easy though to run any number of XYcopy processes simultaneously. I'm just not decided yet what's better or if I should make that a choice for the user.
Well, if the user has opted to use XYcopy, I think it makes sense to continue to use it. However, new processes should probably be moved to the front of the queue for immediate handling, if it's not better to have them run parallel.
admin wrote:
2. The copying (or whatever operation) itself is as trustworthy as ever because it's the same shell doing the job. I'm still waiting for the first queue to fail -- it appears to be solid.
What I sometimes have is that confirmation prompts from the background queue are hidden behind the top window, so you might think a copy happened while in fact it is waiting for you to confirm an overwrite... I'm working on this.
Also there still might be situations where the refresh after the job is not perfect.
Generally I'd say the feature is too young to be fully trusted yet.
I'm a little confused, because you started out by saying that it's as trustworthy as ever, but ended by saying it shouldn't be fully trusted yet.
If it helps to clarify, I don't mind little interface bugs, such as the hidden confirmation prompts. I'm concerned with the integrity of file operations.
I said the
copying is trustworthy but not the
feature. The copying is done by the
shell but the feature is done by
me.
ADD: I don't see a reason to doubt the integrity of the file operations. It's the same shell function as before, just running in another process.
Re: XYcopy questions
Posted: 17 Mar 2010 16:28
by Mesh
admin wrote:
I said the
copying is trustworthy but not the
feature. The copying is done by the
shell but the feature is done by
me.
ADD: I don't see a reason to doubt the integrity of the file operations. It's the same shell function as before, just running in another process.
If the integrity of file operations is good, then I have no worries about experimenting with the feature.
Thanks for clarifying.
Re: XYcopy questions
Posted: 17 Mar 2010 16:31
by serendipity
admin wrote:serendipity wrote:I have more questions/wishes:
Before that i should say its working really nice on my win7 32-bit PC, i can go about doing what i want as it is happily copying multiple files. Until now i had to depend on teracopy for large-file-copying, but i might use XYcopy soon.
1. Can move operation be such that only after everything is copied the source file is deleted. i think its much safer in case of power failure or whatever reason. Maybe it already works this way.
2. Can we have some basic stats (atleast in the beta phase) about how long it takes to complete any operation? Users could report their times for comparison sake.
3. How does XYcopy compare to vista/win7 copy? I currently have no time to run these tests.
Great to hear it's working!

(And thanks for the courage to try!

)
Well, I am trying on files I have a backup for. So not that courageous.
admin wrote:1. I would think that this is the standard. And I cannot influence it anyway, whether I use the shell or other API. This is low level stuff.
- Move (across drives) = Copy, then delete source.
- Move (within drive) = Rename.
Sounds good.
admin wrote:
2. OK, but where should the stats appear?
In the status bar, maybe? OK with many file operations that wont work. Maybe a log in XY folder?
admin wrote:
BTW, as I said in the roadmap (keyword "comfy") I also plan an alternative Copy/Move method where I use kernel API instead of shell API, which will give me full control about the progress feedback and confirmation prompts. There will be a live interface (real window, selectable on taskbar) similar to TeraCopy (or any copy software) for each ongoing process. There you have your luxury stats. This might come only with XYcopy 2.0 though...
Yeah, ability to copy/move without the XY freeze is a good start i would say.
admin wrote:
3. I would expect it's currently slower than the new vista/win7 copy. But the kernel version should be equally fast or faster.
But if its the same as shell API why should it be slower? I guess you ran some tests on this.
Re: XYcopy questions
Posted: 17 Mar 2010 17:11
by admin

What about this cute little firefox thingy that comes up in the bottom-right when a download is complete!? Would make all the sense in the world to have this come up in XY when a background job is complete, or? It could tell you
-
what was just finished
- in what
time
- and what is run
next (if the queue has something)
serendipity wrote:admin wrote:
3. I would expect it's currently slower than the new vista/win7 copy. But the kernel version should be equally fast or faster.
But if its the same as shell API why should it be slower? I guess you ran some tests on this.
I said the
new vista/win7 copy. They totally rewrote it in Vista SP1 and I assume it should faster now than the old Win95-till-XP function (which is still supported in vista/win7 but not used by its Explorer).
Re: XYcopy questions
Posted: 17 Mar 2010 17:26
by Mesh
admin wrote:

What about this cute little firefox thingy that comes up in the bottom-right when a download is complete!? Would make all the sense in the world to have this come up in XY when a background job is complete, or? It could tell you
-
what was just finished
- in what
time
- and what is run
next (if the queue has something)
Personally, I don't need anything showing up in XY. I'm not sure I'd want it getting in the way of other status bar info/messages. After all, there's a reason this stuff is being queued in the background. Everything I would want would be on the file ops dialog box itself, such as:
---------------------------
Current Operation:
Description of operation (e.g. Copy, Move, Delete, Massage, etc...)
Count (e.g. "1 of 314", etc...)
Path to current file/folder
Status bar
Estimated time to completion
Overall:
Job Count (e.g. "Job 1 of 7")
Status Bar
Estimated time to completion for all jobs
----------------------------
And if you really wanted to get crazy, the dialog box could show the list of jobs, and give you the ability to cancel or rearrange individual jobs on the fly.
Now, what *would* be helpful, in line with what you were thinking, is if the file ops dialog box had it's own taskbar item which took advantage of Win 7's UI feature of having a status bar within the taskbar item itself. In which case, it should probably match up with the Overall Status Bar, rather than the Current Job Status Bar.
Re: XYcopy questions
Posted: 17 Mar 2010 17:47
by serendipity
admin wrote:
What about this cute little firefox thingy that comes up in the bottom-right when a download is complete!? Would make all the sense in the world to have this come up in XY when a background job is complete, or? It could tell you
-
what was just finished
- in what
time
- and what is run
next (if the queue has something)
I somewhat agree with Mesh that it can get intrusive. If its silently logging it in the background thats fine. Just to put out another idea (which i really like) is the way Opera browser does it. It silently creates a tab "Downloads" and logs information there. See screenshot:
Opera_Downloads_Tab.png
Re: XYcopy questions
Posted: 17 Mar 2010 17:47
by admin
The firefox thingy is self-destroying after 2 seconds or so. I could also play music from Mission Impossible while it's up.
Conc the job GUI. Yes, I'm having those ideas as well... but step by step...
Mesh wrote:Now, what *would* be helpful, in line with what you were thinking, is if the file ops dialog box had it's own taskbar item which took advantage of Win 7's UI feature of having a status bar within the taskbar item itself. In which case, it should probably match up with the Overall Status Bar, rather than the Current Job Status Bar.
No idea what you are talking about.

Re: XYcopy questions
Posted: 17 Mar 2010 17:50
by serendipity
admin wrote:The firefox thingy is self-destroying after 2 seconds or so. I could also play music from Mission Impossible while it's up.

, and if shell API fails play oops i did it again.