I want to tell you, that you are doing good work. Even if there are things in TC that I am quite unhappy, about TC is by far the best filemanager available. So thank you.
1. Searching in separate thread or process Searching windows opened (not only searching in progress!) prevents me to do anything other in TC. I read the forum and found, that this was already requested before, but it's really annoying So I politely raise this request again.
This was put into separate discussion thread:
2. A) Content of pannels being fed by separate threads and B) Caching of directory contents while connected thru network Why? I cannot do more things paralely. Let's say, I am connected using TC to some slow server (i.e. by VPN or so), I can neither do anything in the panel, because until the first one is reloaded, TC is totaly stuck. (=not responding) Which makes me quite unhappy.
This was put into separate discussion thread:
3. Faster searching! TC itself could do some indexing or (better) use windows indexing service (yes, windows indexing service is one of the best indexing engines). if present. (This would be helpful especially in network environment, where it's possible to use index database already created by machine you are searching on!)
Question could be "How windows indexing service can handle compressed files?" (well, probably it cannot handle them. however: if you will use windows indexing, TC will immediately know where archives are.
It also brings other (mandatory) benefits like usage of different so called Indexing-service-filters (which can bring you for example content searching http://www.aimingtech.com/av_ifilter/)
Present way of searching takes a lot of time and stresses drive quite hard and to be straight forward, it seems me to be quite bellow stanrd. Implementation of any indexing would make it quite powerful searching tool. (btw: Current versions of Office 2007 makes you to install and use indexing service! And once it is running it can brings instant search results.)
4. colored folders (those ntfs-compressed ones and encrypted)
This was put into separate discussion thread:
5. packing and unpacking in separate thread. (So I can perform other operations. During this action).
This was put into separate discussion thread:
6. Improvements of ftp client... Ideal situation would be, if I could use it as easily and transparently as I can work on on my local system.
This was put into separate discussion thread:
7. always handle files using queues (that are running in separate threads). If I noticed well, there is always only one queue. When I perform extensive file operations, I would appreciate some or basic rules, the would drive the situation and made the work more effective. For example(!!!):
- IF copying(/moving/packing/unpacking/deletion/MD5 generating/ftp) between the same media where another operation is already in progress THEN put the new file job into the same queue.
- Otherwise create the new queue.
(This means, that jobs to same media will always run in series and to different paralely.)
Maybe this particular way is not the best one, but currently there are definitely things to optimize.
Thank you and have a nice day
]
