If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Agent Digger
So, what features are most important to you my fiends ?
I am most of the way through writing a file searcher. This may never become public but I will happily use it all to myself if that is what happens. If public it will be freeware (and Beta, i.e. never finished). Your suggestions are appreciated. So far the features a Multi-thread searches (searchlist divided up to maximize CPU) e.g. if search is Only C:\*.txt then all top level folders will compiled and divided up into groups such that an independent thread will be assigned to each group. Searches for filename or folder or folder\filename: Like (wildcards * ? # etc), Exact Search within files using: Mix of these used for some combinations are possible. Like Escaped e.g. \t == tab; and other escaped characters Radix(e.g. Hex, Octal etc) Near (specify distance between), AND (both must match), RegEx |
Ads |
#2
|
|||
|
|||
Agent Digger
eLeSeM wrote:
So, what features are most important to you my fiends ? I am most of the way through writing a file searcher. This may never become public but I will happily use it all to myself if that is what happens. If public it will be freeware (and Beta, i.e. never finished). Your suggestions are appreciated. So far the features a Multi-thread searches (searchlist divided up to maximize CPU) e.g. if search is Only C:\*.txt then all top level folders will compiled and divided up into groups such that an independent thread will be assigned to each group. Searches for filename or folder or folder\filename: Like (wildcards * ? # etc), Exact Search within files using: Mix of these used for some combinations are possible. Like Escaped e.g. \t == tab; and other escaped characters Radix(e.g. Hex, Octal etc) Near (specify distance between), AND (both must match), RegEx You haven't mentioned anything about character sets or representations. That's the very first part on Windows. Windows has 8 bit wide characters and 16 bit wide characters, and when you do searching in a utility, you have to support both. And preferably, have a solution for case insensitivity as well. Making features on the "next layer up" of the stack, yes, it's fun to think about that. If I were you though, I would make a static search for "fredbloggs" work first. Store fredbloggs in the Registry using wide characters, see if your utility can find it. Some of the things in the registry that "look like" binary, are actually strings if you decode them. Paul |
#3
|
|||
|
|||
Agent Digger
Case sensitivity is included, forgot to mention. Unicode currently is handled by Radix (Hex, etc) comparison of binary data of file being searched. Sufficient for me. There are too many languages, (pronounced, character sets) for me to worry about. Paul wrote: eLeSeM wrote: So, what features are most important to you my fiends ? I am most of the way through writing a file searcher. This may never become public but I will happily use it all to myself if that is what happens.Â* If public it will be freeware (and Beta, i.e. never finished). Your suggestions are appreciated. So far the features a Â*Multi-thread searches (searchlist divided up to maximize CPU) Â*Â*Â*Â* e.g. if search is OnlyÂ* C:\*.txt Â*Â*Â* then all top level folders will compiled and divided up into groups such that an independent thread will be assigned to each group. Searches for filename or folder or folder\filename: Â*Â* Like (wildcards * ? # etc), Â*Â* Exact Â*Search within files using: Â* Mix of these used for some combinations are possible. Â*Â* Like Â*Â* Escaped e.g. \tÂ* == tab; and other escaped characters Â*Â* Radix(e.g. Hex, Octal etc) Â*Â* Near (specify distance between), Â*Â* AND (both must match), Â*Â* RegEx You haven't mentioned anything about character sets or representations. That's the very first part on Windows. Windows has 8 bit wide characters and 16 bit wide characters, and when you do searching in a utility, you have to support both. And preferably, have a solution for case insensitivity as well. Making features on the "next layer up" of the stack, yes, it's fun to think about that. If I were you though, I would make a static search for "fredbloggs" work first. Store fredbloggs in the Registry using wide characters, see if your utility can find it. Some of the things in the registry that "look like" binary, are actually strings if you decode them. Â*Â* Paul |
Thread Tools | |
Display Modes | |
|
|