sgrottel / checkouts-overview Goto Github PK

If “untracked”, check if other, tracked branches exist in the checkout. If yes, this means, it is a new branch, which is not (yet) tracked. Mark this as new state: “untracked-ahead”. (Untracked Icon in Orange)

Automatically build, test, and create the setup zip via CI on every commit.
Automatically inject build number into version info.
Make non-tag-versions pre-release.

Follow-up by #5

Implement Unit Tests for:

• DisksScanner -- because parses text output of other console application (which might be missing)
• EntryEvaluator -- because parses text output of other console application (git, which might not be installed)

Should be a per-repo option with a settings default.

• User Documentation
• Release Notes

Add a settings to set the size of the state icons.
Sometimes bigger is better.

Two sets of lists:

• include directories -- directories to start searching in
• exclude directories/patterns -- directories or regex patterns to exclude from the search or from the results.

Tasks:

• Combine searching via file system functions and Everything.

• Optionally, check if Everything is available and only conditionally enable the button.

• Integrate search progress with search dialog.

• Integrate search result with search dialog.

• Persist include list and exclude list via settings (no need to make them editable in the settings dialog, but maybe link)

• Minor version bump.

I guess many people keep check-outs organized in few folders, like a "source" one, a "websites" one, a "papers" one etc. If you could register these folders with the tool, finding the regular repos would be much quicker than scanning the whole machine. Maybe you also have weird/read-only checkouts somewhere that you do not want the tool to show to make it less messy.

• Per entry, make default branch names configurable

• Default branch names are also configured application wide --> settings dialog

• Minor version bump

• Change all highlight colors from system/blue to orange
• Settings and About Dialog do not have thicker borders, Main Window and Scan Window do. Visible when window is not focussed.
• Settings window looks bad
  • browse buttons are mostly off-aligned
  • spaces are too small
  • settings are not structured
    • settings subset in scan disk window is reused
• Link in About Window should also close that window.
• Refresh Screen Shots in (online) Documentation

In the settings dialog, when using the default git client (empty config textbox), show the path to the detected git client.

Switch to a more standard publish process by using the Publish to Folder feature of Dotnet.

• Setup "Publish to Folder"
• No need for "Single file" option, as not many Dlls are part of this project (yet)
• Update Build Pipeline to Release from the Published Artifacts using dotnet publish

System might have several git versions installed. User should select which one to use. System default should remain default.

Should be a generalization from the git fetch --all currently done by default. Maybe via PS1-Script, or execution of just an external command with specific arguments and then pattern detection in the results...

Scenario:
I have a git clone, A, with two remotes.
One, B, is a crawler which produces new entries, and from which I regularly pull.
The other, C, is a long-term backup storage, onto which I push the final states of A.

So, I want to know if there is incoming stuff (from B) AND stuff which needs to be pushed out (to C) at the same time.

This was supposed to be fixed, but still happens.

Repro:

• Local clone with no changes and no incoming changes fetched. => status will be white.
• Remote get changes.
• Update in Checkouts Overview UI: first white, then fetch, then still white (!)
• A second update run then shows the orange incoming arrow.

Introduce a bool option to prohibit starting second (etc.) instances of the app. Instead, bring the first (and only) instance to front.

The tool should also be able to run without everything.

Create a dialog to select either Everything or some FS roots (hard discs preselected, but editable).
For the slow scan, use dialog to report progress and possibility to abort.

• If Entries are selected, apply global sort operations to those selections only
  • Sort by name
  • Sort by path
  • Sort by date(s) (x2)
• Label in the selection bar should state on which entries the sort operation will be performt
  • all entries
  • selection

The Everything SDK (Dlls) seem a better, more direct option, than parsing the output of the CLI.

https://www.voidtools.com/support/everything/sdk/

https://github.com/dipique/everythingio

Sort entries in list by:

• Name
• Full Path
• Last Change Date

As a follow-up a fav-system could work nicely.

I can see that scanning the whole machine is super convenient, but if you are in a hurry and just want to add a single new check-out, drag-dropping a folder on top of the tool would be nice.

When changing setup the app should warn when closing without saving.

Follow-up of #41

DWMWA allows for further Window Decoration Design adaptions on modern Windows 11:

private const int DWMWA_BORDER_COLOR = 34;
private const int DWMWA_CAPTION_COLOR = 35;
private const int DWMWA_TEXT_COLOR = 36;

internal static void SetCaptionColor(IntPtr hWnd, bool focussed)
{
    if (hWnd == IntPtr.Zero) return;

    int color = ColorTranslator.ToWin32(Color.FromArgb(0x22, 0x22, 0x22));
    DwmSetWindowAttribute(hWnd, DWMWA_BORDER_COLOR, ref color, sizeof(int));

    DwmSetWindowAttribute(hWnd, DWMWA_CAPTION_COLOR, ref color, sizeof(int));

    color = ColorTranslator.ToWin32(focussed ? Color.WhiteSmoke : Color.Gray);
    DwmSetWindowAttribute(hWnd, DWMWA_TEXT_COLOR, ref color, sizeof(int));
}

protected override void OnSourceInitialized(EventArgs e)
{
    base.OnSourceInitialized(e);
    IntPtr hWnd = (PresentationSource.FromVisual(this) as HwndSource)?.Handle ?? IntPtr.Zero;
    Utility.DwmHelper.UseImmersiveDarkMode(hWnd, true);
    Activated += (object? _, EventArgs __) => Utility.DwmHelper.SetCaptionColor(hWnd, true);
    Deactivated += (object? _, EventArgs __) => Utility.DwmHelper.SetCaptionColor(hWnd, false);
}

Should be a global (default) setting with the option to adjust per repository:

• off
• fetch (selected remotes)
• fetch (all remotes)

• Update Documentation!
• Minor version bump

Have a system setup where only one new entry will be found.
Search (with Everything).
The result list shows the only found item.
The Apply button remains disabled (Bug)

• Use git branch -a
• If any branch has a equally named remote branch, the current branch has not --> warn!
• Extend icon indication:
  • Current branch is neither main nor master -> change shape of lower range, but stay white, when without local changes
  • If current branch does not have a remote, but other branches do -> change shape of upper range & red

Switch to Dark Window Title Bars for MainWindow and Dialog Windows (Settings, Search, About)

Context:
The Checkouts-Overview App follows a medium-dark design color schema. I did not overwrite the windows title bars, because I did not want to end up with non-OS look and maintenance effort.

I recently learned that there is an DWM-Switch, related to Dark Mode, which could work easily enough to adopt here:
https://www.meziantou.net/detecting-dark-and-light-themes-in-a-wpf-application.htm#updating-the-title-b-2cbb0b

Double-Clicking an entry should open the configured client.

and fix all warnings

• Add a Help-Link to the UI
• Add MD files to the repository to represent the Manual
• Create Section about the meaning of the Entry Icons
• Create up to date screenshot for main README.md

Use slight color gradients instead of flat colors.

Add "About" Dialog, with

• Version information
• License/Copyright information
• Link to the website(s)

https://github.com/sgrottel/EverythingSearchClient