Disabled Searches - Here I go againI have a slightly different idea. I
really dont like the idea of renaming the searches to enable/disable them.
1. I think there should be a local list file that is maintained for the
enabled searches, like enabledsearches.txt. (instead of listing all the
disabled ones, the list might be shorter to track enabled ones instead.)
2. I think the toolbar should check the list of enabled searches when
reading in the *.xml files. If a search is not on the list of enabled
searches, it isnt loaded.
3. the help window reads in all of the xml files, and sets the enabled flag
for the ones in the enabled searches list. (this will slow the loading of
the help window a little, but it isnt used very often)..
4. closing the help window writes out the enabledsearches.txt file based on
the settings at the time it is closed.
This method would eliminate all the hassle of keeping up with xml_disabled
searches etc...
Just my $.02.
Monty
>What I propose:
>1. On start up DQSD only loads enabled searches (ones named *.xml) like it
already does
>2. The help screen only loads enabled searches by default (change would be
to ignore >disabledsearches.txt)
>3. The help screen gets a check box or button that causes the
*.xml_disabled files to get loaded which >will allow the file to be enabled.
This will be a one-time performance hit while the disabled searches are
>loaded but worth it as it is specifically something you'd want to do (else
you wouldn't be doing it)
>4. Closing the help screen renames search files to *.xml or *.xml_disabled
as appropriate
>5. Closing the help file also deletes and re-creates disabledsearches.txt
(why later). The searches are >listed in this file by original file name
(*.xml)
>6. Closing the help screen also dumps and reloads DQSD (so that only
enabled searches are loaded thus >freeing up resources) <-- not a
requirement
>The only problem left that I can think of is what happens after upgrade.
here's where >disabledsearches.txt comes in.
>1. If disabledsearches.txt exists, the installer deletes *.xml_disabled
>2. If disabledsearches.txt exists, some function in the installer opens
disabledsearches.txt and builds an >array of files to rename to
*.xml_disabled and does the deed for us.
>Does this make sense? Does it sound possible? Am I missing anything?
Thoughts?
The list has been quiet for a while, so I thought I'd stir it up again.
JB
John W. Bairen, Jr.
www.bairen.net
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel
