Ticket #12 (closed task: fixed)
Create explorer extension
| Reported by: | Joel | Owned by: | Joel |
|---|---|---|---|
| Priority: | major | Milestone: | Eraser 6.0 |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
Eraser needs to have a context menu extension as in v5.
However a few things need to be taken care of.
- The Recycle bin context menu should have its entries in a submenu
- The menu items should optionally be customizable
I've gathered this from posts I've read in the suggestions forum.
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #12 | └ Create explorer extension | Eraser 6.0 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #12 | └ Create explorer extension | Eraser 6.0 |
Change History
comment:2 Changed 5 years ago by Joel
Additionally, the Eraser Secure Move menu item should be removed. Users should be educated on right-click dragging and dropping instead.
Joel
comment:3 Changed 5 years ago by Joel
Have multiple erase options on right click so a user can set the default overwriting pattern on the main screen of Eraser but whenever a user comes to deleting a file or folder they get the option to employ another type of pattern on a per file/folder basis. Sort of erase method on demand. This is done with a comprehensive drop down as used now by Eraser 5X on the recycle bin. Eraser will always automatically default to the default settings made in the options.
comment:4 Changed 5 years ago by Joel
Further tasks:
-Allow shift-delete to erase the file
-And optionally replace the recycle bin with Eraser
-Recycle bin erasure
-Allow users to select erasure passes from recycle bin context menu
comment:5 Changed 5 years ago by Joel
I wonder if this should be retargeted to 6.1/2 because explorer extensions should not be written .NET, since only one CLR can be loaded per-process. This probably can only be done together with IPC with the managing program if it is running using DirectExecutor?, and IPC with the host service if the host is the one running DirectExecutor?.
Both of which require IPC because the Eraser library is now written in C#.
comment:8 Changed 4 years ago by Joel
- Status changed from assigned to accepted
- Owner changed from Kaz to Joel
- Component set to Core
The main code has been written; what's left is Secure Move and Erase on Restart. The latter being a limitation of the command line. Will create tickets.
comment:10 Changed 4 years ago by Joel
- Status changed from accepted to closed
- Resolution set to fixed
Decision: I'll Close this ticket, and then create anew one as an enhancement to support Erase on Restart.
