----- Original Message ----- 
From: "Shawn K. Hall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 22, 2004 6:29 PM
Subject: RE: [DQSD-Devel] DQSD installer/uninstaller

> Also, this could cause duplication of many searches if we were to
> provide users with the ability to each have their own config. This
> would seriously need a different loading mechanism that didn't rely on
> file extensions to parse the search files - but rather a user config
> option, that listed what searches were disabled, probably in an XML
> file that we would use to filter the searches as they were loading,
> using an XSL transformation.

Yes!..  The renaming of the xml files was a workaround until something
proper could be worked out..  It allowed the disabled searches from being
loaded with the current design.  It was never intended to be a real method..

>
> The localsearches folder would need to be under:
>   %appdata%\dqsd\localsearches\
>

+1

> The 'base' searches should also go under
> "%CSIDL_COMMON_APPDATA%\dqsd\searches\" because they are files that
> must have read access in order for the application to run, but apps
> are not *supposed* to 'read' files under program files. Placing them
> under "common_appdata" puts them in the "all users" app data folder so
> everyone has access to them - but if we were to continue using the
> rename-to-disable-searches method we'd effectively disable searches
> for all users if one user were to disable their searches.

> Alternatively, we could duplicate all the searches in every users
> directory, but this is a waste of resources and (IMHO) we shouldn't
> seriously entertain it.

+1


I was poking around loader.js to see the function where the directory of xml
files is loaded etc..  There is old deprecated code to load localsearch.xml.
Originally the toolbar loaded a single xml file with all the defined
searches in it..  There was also a need to have localized searches, so a
second xml file 'localsearch.xml' was created to house them. Later the
searches were split out in to individual xml files, hence the search and
localsearch subdirectories.  Any code related to loading search.xml and
localsearch.xml could be removed I believe.

Monty




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to