Batchsearch actions? I can't seem to find any chance to use them in Fiji, and they keep throwing errors when I try to run them in napari-imagej
TaskServicethat lets you register
Taskobjects and a task can have subtasks recursively, and then we can have a GUI that shows a progress bar for a task with an expandable triangle widget to show the next layer of progress bars below it. And to replace ImageJ's current progress bar with this better one. But as with so much in SciJava, this work was never completed.
TaskServicein SciJava Common now with
Taskobjects that you can create—and the
DownloadServiceuses it. I'd be happy to chat about requirements and whatnot any time, if you or @NicoKiaru or anyone has time and interest to develop it further. Perhaps all that would be needed is the user-interface portion of it now.
DownloadServicetasks to the
TaskServicedirectly, this is where we are.
component:script-editor, from back when the Script Editor lived in imagej-ui-swing. Since then, it moved to its own repository at scijava/script-editor, since it is more general than images. I wanted to transfer those five issues from imagej-ui-swing to script-editor, but you can only transfer an issue between repos of the same org. So! I created a new repo imagej/scijava-issue-shuttle and moved the five issues there. Then transferred scijava-issue-shuttle from imagej to scijava. But now, I'm not able to transfer the issues again from scijava-issue-shuttle to script-editor; no repositories appear on the list. Furthermore, two of the issues seem to have partially incomplete transfers, such that they still say they are "transferring" at the bottom. I fear they may be hosed now. So the end result is five deleted issues, i.e. five broken links, without successfully landing them at their new destinations in the end.
gh issue transfercommand line function, and it gave me an informative error: "Old issue cannot be transferred from private repository to public repository". Once I changed scijava-issue-shuttle to public, I was able to move them to the script-editor repo. Next time I'll try that command directly across orgs, and see if it works.