11 July 2002 Status report
--------------------------
Scott:
>On the sender side, after I hit
>"Okay" and the status window shows "waiting for confirmation...",
>there's no need for it to time out. That is, don't even bother
>prompting the sender after 15 seconds with "Continue to wait?".
>Just always continue to wait. As long as the Cancel button
>works, and the Sender knows that the receiver hasn't confirmed
>the transfer yet, it's a fine usage model.
Done. I have altered all the waiting algorithm. And there still is an
issue about this. If sender clicks Cancel when the receiver is just
about to accept the file - what then? Should I close the Accept
File panel?
> If there are no other Kaboodle PC's on the LAN, and if
> Kaboodle is not VPN'd, then the file-transfer dropdown
> box should not be empty. It can instead give an error
> message: "Sorry...Kaboodle can only transfer files to
> other PC's that are also running Kaboodle".
I added the exact label. It takes all the room of the Step#1.
Note that I have also swapped Step#1 and Step#2 since
this order seems to me more correct. Personally I always
choose my party first as I am not sure the one is necessarily
acceptable and only then I choose the file as I am certain
about my own files.
Q: After the receiver has accepted the file, should I prompt
they to see the details the way I do for the sender?
Q: In the silent mode ("Do not Ask" option is set), is the final
popup message "Success / Terminated" really needed?
>Yes, we should offset the work so that the thread which
>reads the file to the buffer also does the encryption.
I continue with that.
-Oleg
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
PC Mods, Computing goodies, cases & more
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
