Ticket #200 (closed enhancement)

Opened 6 years ago

Last modified 6 years ago

Enhancing naming schemes for Default Erasure Methods

Reported by: Walda Owned by:
Priority: minor Milestone: Eraser 6.0
Component: User Interface (UX) Version: 6.0.4.875
Keywords: erasure method description Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

After the official name of the method there should be a brief (1-2 word) summary of the kind of data (zero/random/pattern/mixed) that is written by the method.

British HMG IS5 (Baseline) (1 Pass)
becomes
British HMG IS5 (Baseline) (1 Pass / zero bytes)

BTW, this ticket mustn't be confused with ticket #141 "Better method description". A tooltip for the methods would be also nice, but I believe prolonging some strings is an easier task for the time being.

Blocking

IdSummaryMilestone
#200Enhancing naming schemes for Default Erasure MethodsEraser 6.0

Blocked by

IdSummaryMilestone
#200Enhancing naming schemes for Default Erasure MethodsEraser 6.0

Change History

comment:1 Changed 6 years ago by Joel

  • Priority changed from major to minor

How do you propose coming up with the summary? It is easy for single-pass erasures, but how do you summarise the 35-pass Gutmann in a word?

comment:2 Changed 6 years ago by Walda

For more complex methods, there can't be much detail, that's true. So maybe:
"35 pass / complex"
"35 pass / mixed modes"
"35 pass / blended modes"
... and so on.

If the user wants the full description he can still see it in some other place, tooltip, documentation or a dedicated description text box.

comment:3 Changed 6 years ago by Joel

That's why -- we're back to square one. The user can refer to the documentation right from the beginning. Except that we don't have any docs yet because we don't have any documentors...

comment:4 Changed 6 years ago by Joel

  • Status changed from new to pending

comment:5 Changed 6 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.