mvnForum Homepage


Posted by rustianimal at May 5, 2011 2:27:13 AM
Re: Auto-Index?
There is a very significant difference. A batch process as I have mentioned should run as a foreground function and max out the CPU, RAM & disk to the detriment of all else in order to get the task done. This is because without the index there, no other useful work can be done.

In earlier versions you have the option to do a foreground index on a module by module basis, and you cannot do anything else whilst that foreground indexing is processing. I am saying I would like to be able to tell Eloquent to index not just the module I am trying to search on now, but every module that has not been indexed and do it NOW as I cannot use Eloquent any further until all the indexes are created.

Maybe it is as simple as creating a preference panel that allows you to say 'Index all modules as soon as downloaded', so that once a new module is added, it is indexed immediately.

Also, there should not be any need to use command line at all in a Mac application. So, even though you mention using command line options, it would be better to just include an extra menu item to do the specific housekeeping tasks for those who are not familiar with command line functions.

As regards the move from MacSword to Eloquent, unfortunately Eloquent has already deleted all my modules from my hard drive entirely. I have had to download all the modules again from scratch. I still have to index them or at least go into the command line and turn on background indexing for Eloquent if it is not already on as standard.