10 aug 2021 and I dont see any news about order by
Drag and Drop it’s easy to implement using SortableJS I tried it some years ago on a “test” page QooL Portfolio.
In the meantime sort by name would be the most easy stuff, I think it requires just a couple of minutes.
If it’s so easy, could you please make this optional feature and commit to git fork?
Sortable it’s easy to use but I dont know DUPLICATI project and I don’t know how to fork and share changes…
Here a basic draggable tastlist using the SortableJS plugin.
Example of tasklist sortable => click me
My changes on index.html
<body class="theme-{{active_theme}}" onload="QooLDrag()"> <script src="https://sortablejs.github.io/Sortable/Sortable.js"></script><script> function QooLDrag(){ var el = document.getElementsByClassName('tasklist'); var sortable = Sortable.create(el[0]); } </script>
and here an usable version code that allow to save the state of task order (when enter it will remember your drags order)
Duplicati - SortedJS for Index.html
Please, let me know if you know how fork and if u can give me some basic information about it.
I don’t actually do this sort of thing, but here’s seemingly helpful information from Google search.
6.2 GitHub - Contributing to a Project starts with the fork. If you need an account, hit Prev button.
Contributing to GitHub Projects (Git Pull Requests for Dummies) works with command line tools.
If you use a favorite current GUI tool, you could check whether or not it can integrate with GitHub.
Basic GitHub fork question is a Duplicati forum topic among non-experts on how to update a fork.
You can sometimes ask Developer questions, and get a developer, but this is more a user forum.
Duplicati code is here. Pull requests are here. You can look at closed ones to view their handling.
Branches in Duplicati are mostly pretty simple. Eventually things go to master, then get released.
There’s not a specific schedule. It might depend on whether there’s enough change to be worth it.
Thank you for your interest in contributing code. That’s how Duplicati slowly gets better over time.
I did have a question about persistence, which seems from your site to use browser local storage.
I suppose this makes it somewhat possible to lose, and also to vary depending on browser in use.
Might be a fair tradeoff though. Another question was how well it agrees with Duplicati URL usage.
Duplicati confuses some tools by using a fixed host address (often localhost) for various usage.
Making that worse is that its URL tends to stay the same across pages, except for the fragment id.
This confused password autofill terribly until it was disabled. Can SortableJS deal with all this OK?
This also seems to be a view thing, and could interfere with setting up run order via creation order.
Could there be a way to let the internal ordering show through, for those using it as a setup guide?
If not, then I guess whoever handles the pull request will have to guess at the gain versus the loss.
Best case may be if it can someday help a C# developer attach deeper semantics to the ordering.
But it does make a nice visual upgrade, which is possibly more meaningful to people. I don’t know.
Thanks again!
Thanks so much for all details on your reply.
Just to be clear what I have done is add a couple of JS e CSS that cannot interfere with settings:
it’ not a change of priority or other stuff, it’s a simple reorder of html elements after Duplicati generated them.
I added that codes in the index.html (it is only layout) of 2 separated installation of duplicati:
Somewhat. Results so far are below. Hit many snags, some seemingly not related to this though.
I don’t worry all that much about a Duplicati without the change. The loss I’m worrying about is this:
as mentioned in a similar issue below which uses browser cookies rather than browser local storage.
every time I set it and move to a new machine or browser, the theme selection is reset because it’s stored in a cookie instead of server-side.
Log in in another browser or incognito.
Any of them lost the order for me, and an unexpected way to lose the order is to refresh after a minute.
One can also lose the order by clearing browser local storage (sometimes near its cookie clearing UI).
I see some discussion of more robust saving in the Issues for SortableJS, but can’t easily follow them.
I started testing this yesterday, and got sidetracked in a Firefox issue where “Duplicate tab” hangs GUI.
That doesn’t seem to be from the new code though. Even very old Duplicati on recent Firefox do that…
I sort of recall hearing of such an empty blue box reported, but I can’t find it in a “Duplicate tab” context…
Back to my testing effort, I think I’m somewhat stuck because the one-minute loss is sometimes sooner.
My hope had been to test backup add and delete, but after timing myself, I’m not sure I can beat the loss.
I thought possibly it was related to a long poll coming in every 60 seconds, but it doesn’t “appear” to be…
I tried quieting the polling down by running Duplicati.Server.exe instead of Duplicati.GUI.TrayIcon.exe, but
it “seemed” like the refresh button used before seeing the next poll in the F12 browser tools may still fail.
On the “Duplicate tab” side-issue, I tried right-click → Inspect on that box, and I think it might be trying to communicate a perceived connection failure to server. I was also seeing better-said (imagined?) reports.
I am not a web developer, so I don’t really know my way around how to debug problems like I’m seeing…
Another observation is that my normally first backup decided to become my last without me moving it.
I think I’ve seen that before, but I didn’t mention it because it might have been related to another issue.
What I noticed for the first time trying to drag the item back up is that overall page scroll didn’t happen.
Dragging down, mouse pointer nearing screen bottom makes unseen screen below it scroll into view.
Dragging up, the mouse pointer just runs off display area. I need to use the scroll bar, then drag more.
