[Feature] General improvements

[realahmed7777]

Great app, thanks for making it, these are some of my suggestions for improving the app
1- add file picker in rules's destination field

2-make it possible to search in history, along with adding search filters like size, creation or modification date date and the like

3- adding tooltips when buttons are hovered

4- for folders selected to be watched, add an optional option to deep watch (where even the children folders of these folders are watched) (or maybe add the option in rules so we can apply this rule on a folder and its children folders)

5- adding filters for rules like size, creation or modification date, wher ewe can for example onyl move files with specific extensions and newer than 2025 for example

6- adding support in rules for compiled native Linux executable which dont have file extensions
7- in rule page add a enable/disable button for easiliy enabling or disabling rules (i know there is the enable button in the rule configuration but its harder to access)
8- controlling what kind of information user can get

[hsr88]

Thanks for taking the time to write these suggestions - love it:)

1. A destination folder picker is a good usability improvement and is planned.
2. History search and filtering also make sense. I’d introduce this gradually, starting with file name, rule/type and date filters. Size filtering requires storing additional metadata. Added to local roadmap.
3. Tooltips and accessibility labels will be added to ambiguous icon-only buttons.
4. Recursive folder watching is useful, but it needs safeguards to prevent Mouzi from detecting files it has just moved into destination subfolders.
5. Size and modification-date conditions are good candidates for a future expansion of the rules engine. Creation dates may not be consistently available on every platform.
6. Detection of extensionless executables and other files is already tracked in Support file magic #49.
7. A quick enable/disable switch directly on each rule is a good idea and should be relatively straightforward.
8. Could you clarify what you mean by controlling what information the user can get, ideally with an example?

I’ll keep this issue as an umbrella for now and track the larger features separately as their scope is defined. Thanks again!

[realahmed7777]

8 i forgot why i wrote number 8 and what it was about :) i will retype it when i remember sorry

[realahmed7777]

i didnt remember it but her eare other general improvements,
1- an option to only organize when i choose to, no automatic organization
2-can undo from history for specific days or times

[hsr88]

Hi again :)
The first option is already available. Go to Settings - Folders and change the folder mode from "Silent" to "Manual (collect only)". Mouzi will still watch the folder, but it won't organize anything automatically. Files will only be organized when you click "Clean Now".
If you meant a slightly different workflow, please describe it and I'll take another look.
For the second suggestion, I understand it as selecting a specific day or time range in History and undoing all actions from that period. That's a good idea. I'll keep it in mind as a future improvement to History and Undo.

[SulimanAbdulrazzaq]

I would like to take item 7: add a quick enable/disable control directly to each rule card.

I will reuse the existing Rule.enabled state and updateRule persistence path, keep the edit form unchanged, and make the card control accessible with an explicit switch state and label. I will validate the TypeScript/Vite build and the persisted enabled/disabled behavior. This will be scoped only to item 7 and will reference, not close, the umbrella issue.

[SulimanAbdulrazzaq]

I would like to take item 1: add a folder picker beside the rule destination field. I will reuse the existing Tauri dialog integration, populate the current destination state without changing manual path entry, and keep the change scoped to the rule editor. I will validate the TypeScript/Vite build and the picker cancel/selection behavior. This will reference, not close, the umbrella issue.

[hsr88]

Thanks for taking this one as well. Please go ahead.
One important requirement: if the selected destination is inside the watched folder, Mouzi should store it as a relative path. This keeps the rule portable and prevents it from being tied to one user’s absolute path. If the destination is outside the watched folder, an absolute path is fine.
Manual path entry should remain available, and cancelling the picker should leave the current value unchanged.
I'm currently waiting for the SignPath production certificate before publishing the next Windows release, but that only blocks the public build. Development, review and merging can continue normally. Please open a PR referencing #52 when it’s ready. The umbrella issue should remain open.