Bug 432200

Summary:	Revamping the copy process of Dolphin
Product:	[Applications] dolphin	Reporter:	ginzen <ginzen.ngruhta>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	ginzen.ngruhta, kfm-devel, nate
Priority:	NOR
Version:	20.12.0
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description ginzen 2021-01-27 13:55:37 UTC

SUMMARY
* These are my ideas/wishlist over the whole process of copying mechanism in Dolphin file manager.

EXPECTED RESULT

A) Copying process (KDE copy) wishlist to be overhauled
‣ In addition to pause, retry, skip....‣ If several copy instances are going on, • the option for merging the different windows into one or detaching from... (mate desktop copying is good example here)

‣ Whether to follow and copy symbolic-links or simply to copy it as it is
‣ The option (play/pause icon) for scheduling copying one after the other instead of copying in parallel.
• this should come with an option to prioritize among multiple copying, while ordering at one time.
• the shceduling will enable e.g. a serial copying instead of parallel copying thus to achieve best speed. or even leaving the parallel copying as a default setting, but with the possibility to schedule a copy after the first instance of a copy going is finished.

‣ Checksum method options availability (sha1, shasum256, etc)....when found two files/directories are found to be similar during copying
• This happens when dolphin copy dialog box informs you of finding two similar files and asks what to do, thus enabling to compare on shasum of the different protocols.

‣ The possibility to chose what copy protocol to use defined some where in Dolphin Settings or within the copy window option.
• e.g. rsync
• cp
• scp
• etc....

‣ Detailed problem reporting when a problem is found during copying
• why is it not copying should give some needed information
∘ e.g. for a network copying.
• The detailed information should be summarized and placed at lower/bottom part of the copy window. this can be useful where I left the copy dialog with "Auto skip All" and wanted a summary of what was left out while I was away.

‣ Window geometry should be flexible for resize or accustom to current window settings.
‣ copying for networking to specialize too.
• e.g. there is no "auto skip" option for a networked (samba) copying.

∘ B) Split window upto limited numbers
‣ it should have more than two ----even making horizontal split
• this is sometimes important when you want to work with three or more similar folders in splitted windows.

∘ C) Dolphin Terminal
‣ should not be limited to Kshell terminal emulator only.
• It should be configurable to another type (known/workable) Terminal emulators in the absence of (not default) Kshell).
∘

SOFTWARE/OS VERSIONS

Linux/KDE Plasma:
KDE Frameworks 5.77.0
Qt 5.15.2 (built against 5.15.2)

Comment 1 Nate Graham 2021-01-27 15:25:41 UTC

Thanks for the ideas. However huge bug reports that request many many many many different features are not really actionable. Looking over your list of ideas, they would all have to be implemented in different places: some in the overwrite dialog, some in the notifications system, some in Dolphin, some deep in KIO, etc.

I would encourage you to file individual bug reports for each separate request. See https://community.kde.org/Get_Involved/Issue_Reporting#One_issue_per_Bugzilla_ticket

Comment 2 ginzen 2021-02-02 11:04:08 UTC

Greetings Mr. Nate Graham.

Thank you for your response.

You are right that some of them should have been classified in their
respective topic.
However, most of them I couldn't tell which one goes to which.
I kind of have the poping ideas but lost with classifying them...e.g.
the KIO thing.

And one more thing....there is no "wishlist" as a separate subject
together with all its subcategories....am I missing it. I would be
happy if it be available instead of mixing it with bugs...

Thank you.


On Wed, 2021-01-27 at 15:25 +0000, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=432200
> 
> Nate Graham <nate@kde.org> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------
> -------
>                  CC|                            |nate@kde.org
>              Status|REPORTED                    |RESOLVED
>          Resolution|---                         |NOT A BUG
> 
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> Thanks for the ideas. However huge bug reports that request many many
> many many
> different features are not really actionable. Looking over your list
> of ideas,
> they would all have to be implemented in different places: some in
> the
> overwrite dialog, some in the notifications system, some in Dolphin,
> some deep
> in KIO, etc.
> 
> I would encourage you to file individual bug reports for each
> separate request.
> See
> https://community.kde.org/Get_Involved/Issue_Reporting#One_issue_per_Bugzilla_ticket
>

Comment 3 Nate Graham 2021-02-02 15:41:44 UTC

(In reply to ginzen from comment #2)
> You are right that some of them should have been classified in their
> respective topic.
> However, most of them I couldn't tell which one goes to which.
> I kind of have the poping ideas but lost with classifying them...e.g.
> the KIO thing.
That's okay, the bug triagers (myself and others) will move them to the appropriate place. If you're totally unsure, you can file a bug to 
the generic "kde" component to signify that it needs to be triaged appropriately.


> And one more thing....there is no "wishlist" as a separate subject
> together with all its subcategories....am I missing it. I would be
> happy if it be available instead of mixing it with bugs...
Wishlist issues are marked by setting the severity to "Wishlist". Both bug reports and requests are tracked on bugs.kde.org.


> Thank you.
You're welcome!